On Thu, Oct 16, 2014 at 11:40:23AM +0100, Colin Watson wrote: > Right, you have two disks on this system and you're only installing GRUB > to the second one. There's probably a vestige of GRUB on the other disk > which happened to be compatible with the modules from 2.00-22 but not > the modules from the new version. I recommend running: > > sudo dpkg-reconfigure grub-pc > > Step through without changing anything until you get to the "GRUB > install devices:" question, and then select the master boot records of > both your hard disks, rather than just one of them. That should fix it.
I've recently been bitten by this: after I installed a new SSH in my laptop, grub stopped upgrading itself correctly. It's fixed now, finally, thanks to your message here. The take away message for me is that if I change or add a hard disk to my system, I need to remember to run "dpkg-reconfigure grub-pc". From my point of view, the most obvious way I had to learn about this was to wait until my system became unbootable, rescue it, then find your message when looking for what happened. Could grub's machinery could store somewhere the output of something like this: ls /dev/disk/by-id/ | grep ^ata | grep -v -- -part and print at least a big warning during upgrades if it sees that it has changed? Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
