Hi again, > Regarding my setup, I have two disks in my laptop. /dev/sda in the HDD that > was shipped > with the machine, which I originally installed Debian on. Later, I added an > SSD /dev/sdb > and moved Debian to it. However, as far as I remember, the machine is still > booting > from the HDD (and the debconf output seems to support that). This always > worked fine, > until today. > > I will check my BIOS configuration for the main boot device.
So it turns out I was wrong, and the system actually boots from SSD. But it probably updated only the HDD. Sorry for this. So I admit that this is probably hard or impossible to catch in an update. I still think the situation could be improved, by doing one or both of * Upon upgrades, scan *all* disks for Grub signatures and offer upgrading others as well. * When running grub-install on a device other than the "default" one, tell the user how to make sure grub will run this update in future. Actually, I still have no idea how to do the latter. I assume the dpkg-reconfigure you mentioned will do that, but I currently don't feel like breaking my boot again ;-) When I moved my system, I was not aware that and how I had to tell grub about the location to change on update, I assumed "some magic" would figure out how I booted and act accordingly. After all, "some magic" already configures Windows installations etc., so what I do know what other kinds of tricks Grub can do... Kind regards Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
