Bug#709808: [grub-pc] boot failure after updaing
On Tue, May 28, 2013 at 08:45:59PM +0200, Steven Post wrote: > On Tue, 2013-05-28 at 10:30 +0100, Colin Watson wrote: > > sudo dpkg-reconfigure grub-pc > > > > ... and configure it properly. Presumably you switched disks at some > > point in the past and didn't tell the GRUB packaging so that it could > > sort this out; in general this does work if done properly. > > Thanks, looks good now. > I don't recall ever seeing the screen where it asks for the disks like > that. Maybe a recent introduction? I have been tracking testing/sid > since Squeeze went into freeze, so perhaps I missed it. I never > 'switched' disks in this system afaik, only added except maybe that > one time were I was kind of forced to replace the motherboard. It dates back to April 2009. The installer would have dealt with configuring it on systems installed afresh with GRUB 2; at least some changes in hardware will force grub-pc to display it again on upgrade, but it is probably still possible to confuse it, certainly if the old disks are still around but no longer used for booting. Unfortunately the PC architecture doesn't really make it possible to do a fully correct job here without constantly nagging people with upgrade prompts. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709808: [grub-pc] boot failure after updaing
On Tue, 2013-05-28 at 10:30 +0100, Colin Watson wrote: > sudo dpkg-reconfigure grub-pc > > ... and configure it properly. Presumably you switched disks at some > point in the past and didn't tell the GRUB packaging so that it could > sort this out; in general this does work if done properly. > Thanks, looks good now. I don't recall ever seeing the screen where it asks for the disks like that. Maybe a recent introduction? I have been tracking testing/sid since Squeeze went into freeze, so perhaps I missed it. I never 'switched' disks in this system afaik, only added except maybe that one time were I was kind of forced to replace the motherboard. signature.asc Description: This is a digitally signed message part
Bug#709808: [grub-pc] boot failure after updaing
On Tue, May 28, 2013 at 10:53:18AM +0200, Redalert Commander wrote: > I have the same issue, however it is not just after updating the > latest version, but pretty much every grub update that breaks. > > The issue is in either grub failing to install to the MBR on some > drives or grub skipping that step altogether. > I have an 8 disk system, the first one is a HDD for /home, this is the > one my BIOS points to for booting. The second is an SSD with / and > /boot (same partition). the other 6 are HDDs for data and grub is > unable to install the bootloader there (not really an issue since they > aren't used for booting). > I think grub is failing on those 6 drives. > Whenever there is a grub update I need to manually execute > "grub-install /dev/sda /dev/sdd" to make the system bootable. sudo dpkg-reconfigure grub-pc ... and configure it properly. Presumably you switched disks at some point in the past and didn't tell the GRUB packaging so that it could sort this out; in general this does work if done properly. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709808: [grub-pc] boot failure after updaing
Hi, (not a grub maintainer) I have the same issue, however it is not just after updating the latest version, but pretty much every grub update that breaks. The issue is in either grub failing to install to the MBR on some drives or grub skipping that step altogether. I have an 8 disk system, the first one is a HDD for /home, this is the one my BIOS points to for booting. The second is an SSD with / and /boot (same partition). the other 6 are HDDs for data and grub is unable to install the bootloader there (not really an issue since they aren't used for booting). I think grub is failing on those 6 drives. Whenever there is a grub update I need to manually execute "grub-install /dev/sda /dev/sdd" to make the system bootable. I forgot that last week and had to use a live image and chroot to fix it. For some reason my system refuses to boot if I set the SSD as first boot device in the BIOS, hence the rather unusual setup. It appears to me that grub will fail to upgrade cleanly as soon as the device with /boot isn't the primary drive in the system. Which is also probably the case for your RAID1 setup. Regards, Steven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709808: [grub-pc] boot failure after updaing to 2.00-14: error: file not found -> rescue console
Package: grub-pc Version: 2.00-14 Severity: critical --- Please enter the report below this line. --- upgraded all my packages after the freeze and grub doesn't boot anymore. the error message is "error: file not found" and then it drops into the grub rescue console. i fixed it by chrooting via a live cd and running "dpkg-reconfigure grub-pc" (telling it to install to /dev/sda and /dev/sdb). works fine since then. my hard drives are setup like this: /dev/sda1 and /dev/sdb1 -> 500 MB /boot partition with software RAID1 /dev/sda5 and /dev/sdb5 -> root partition with software RAID1 further / has luks encryption and after that LVM with one PV for / (all setup with the debian installer) let me know if you need more info. here's what i found from the log files before upgrading grub: --- /var/log/messages: May 23 19:37:57 dsteiner3 os-prober: debug: /dev/sda1: part of software raid array May 23 19:37:57 dsteiner3 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda2 May 23 19:37:57 dsteiner3 50mounted-tests: debug: /dev/sda2 type not recognised; skipping May 23 19:37:57 dsteiner3 os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests May 23 19:37:57 dsteiner3 os-prober: debug: /dev/sda5: part of software raid array May 23 19:37:57 dsteiner3 os-prober: debug: /dev/sdb1: part of software raid array May 23 19:37:57 dsteiner3 os-prober: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sdb2 May 23 19:37:57 dsteiner3 50mounted-tests: debug: /dev/sdb2 type not recognised; skipping May 23 19:37:57 dsteiner3 os-prober: debug: os detected by /usr/lib/os-probes/50mounted-tests May 23 19:37:57 dsteiner3 os-prober: debug: /dev/sdb5: part of software raid array May 23 19:40:07 dsteiner3 shutdown[29838]: shutting down for system reboot --- /var/log/apt/term.log: Preparing to replace grub-pc 1.99-27.1 (using .../grub-pc_2.00-14_amd64.deb) ... Unpacking replacement grub-pc ... Preparing to replace grub-pc-bin 1.99-27.1 (using .../grub-pc-bin_2.00-14_amd64.deb) ... Unpacking replacement grub-pc-bin ... Preparing to replace grub2-common 1.99-27.1 (using .../grub2-common_2.00-14_amd64.deb) ... Unpacking replacement grub2-common ... Preparing to replace grub-common 1.99-27.1 (using .../grub-common_2.00-14_amd64.deb) ... Unpacking replacement grub-common ... [...] Setting up linux-image-3.8-2-amd64 (3.8.13-1) ... Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 3.8-2-amd64 /boot/vmlinuz-3.8-2-amd64 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.8-2-amd64 /boot/vmlinuz-3.8-2-amd64 update-initramfs: Generating /boot/initrd.img-3.8-2-amd64 run-parts: executing /etc/kernel/postinst.d/pm-utils 3.8-2-amd64 /boot/vmlinuz-3.8-2-amd64 run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.8-2-amd64 /boot/vmlinuz-3.8-2-amd64 GRUB >= 2.00 has been unpacked but not yet configured. grub-mkconfig will not work until the upgrade is complete. It should run later as part of configuring the new GRUB packages. [...] Setting up grub-common (2.00-14) ... Installing new version of config file /etc/grub.d/05_debian_theme ... Installing new version of config file /etc/grub.d/00_header ... Installing new version of config file /etc/grub.d/10_linux ... Installing new version of config file /etc/grub.d/20_linux_xen ... Installing new version of config file /etc/grub.d/30_os-prober ... Installing new version of config file /etc/grub.d/41_custom ... Setting up grub2-common (2.00-14) ... Setting up grub-pc-bin (2.00-14) ... Setting up grub-pc (2.00-14) ... Installing new version of config file /etc/kernel/postinst.d/zz-update-grub ... Installing new version of config file /etc/kernel/postrm.d/zz-update-grub ... Undefined subroutine &conffile::abs_path called at /usr/bin/ucfq line 529, line 8. Installation finished. No error reported. Generating grub.cfg ... Found background image: .background_cache.png Found linux image: /boot/vmlinuz-3.8-2-amd64 Found initrd image: /boot/initrd.img-3.8-2-amd64 Found linux image: /boot/vmlinuz-3.2.0-4-amd64 Found initrd image: /boot/initrd.img-3.2.0-4-amd64 done --- --- System information. --- Architecture: amd64 Kernel: Linux 3.8-2-amd64 Debian Release: jessie/sid 500 unstableftp.at.debian.org --- Package information. --- Depends(Version) | Installed -+- debconf(>= 0.5) | 1.5.50 OR debconf-2.0 | grub-common | 2.00-14 grub2-common (= 2.00-14) | 2.00-14 grub-pc-bin (= 2.00-14) | 2.00-14 ucf | 3.0027 Package's Recommends field is empty. Package's Suggests field is empty. --- Output from package bug script --- *** BEGIN /proc/mounts /dev/mapper/vg-lv / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 /dev/md0 /boot ext4 rw,relatime,data=ordered 0 0
