jadedcritic
September 3rd, 2010, 09:07 PM
I'm a little hazy on whether or not this has already been posted or if it's in the right topic category, but it strikes me as worth discussing. Still trying to get my head around it.
I think this actually happened to me, without telling too long a story, I was scrubbing bloatware off my Dell box and my GRUB quit working. I didn't think too much of it at the time, but TADA! http://tinyurl.com/2ce54gy
(Quote) This is a bug in which some proprietary Windows-based software overwrites particular sectors in the gap between the master boot record and the first partition, sometimes called the "embedding area". GRUB Legacy and GRUB 2 both normally use this part of the disk to store one of their key components
Looks like the Debian guys figured this out??
Well, if it's already been posted, I apologize. I didn't manage to find it after 10 minutes or so of searching, but this strikes me as a really good thing to be mindful of for those of us with Win/Linux dual boots. I honestly never seriously thought that removing windows elements could potentially breka the bootloader!
I think this actually happened to me, without telling too long a story, I was scrubbing bloatware off my Dell box and my GRUB quit working. I didn't think too much of it at the time, but TADA! http://tinyurl.com/2ce54gy
(Quote) This is a bug in which some proprietary Windows-based software overwrites particular sectors in the gap between the master boot record and the first partition, sometimes called the "embedding area". GRUB Legacy and GRUB 2 both normally use this part of the disk to store one of their key components
Looks like the Debian guys figured this out??
Well, if it's already been posted, I apologize. I didn't manage to find it after 10 minutes or so of searching, but this strikes me as a really good thing to be mindful of for those of us with Win/Linux dual boots. I honestly never seriously thought that removing windows elements could potentially breka the bootloader!