after upgrading grub from 2.00-22 -> 2.02~beta2-14 I was left in rescue grub console with an error about missing symbol (something related to color). After trying to resurrect the system I insmod linux in grub console and I was greeted with the same error again. I had to boot with a rescue usb and downgrade grub. Please be patient if you need I report the exact error. thanks
This almost certainly means that your system is misconfigured and is installing GRUB to somewhere that doesn't correspond to where your system actually boots from, resulting in the core image and modules being incompatible. Please post the output of: debconf-show grub-pc cat /proc/mounts ls -l /dev/disk/by-id/ Thanks,
I didn't reboot the box, I just updated the package again, run what you asked and downgrade grub again. If there was something wrong with the configuration I'd guess just downgrading wouldn't solve the problem. This is the first grub upgrade that has been made on this box and nothing was changed from installation. As you can see it runs on a RAID1. There are just 2 partition: / and swap. I can spot a difference between this non booting box and a box that boot: GRUB_CMDLINE_LINUX_DEFAULT="quiet" # not booting GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.dpm=1" # booting These are 2 very different machine in terms of partition layout etc... still the message was related to "color" that make me think "splash" could be an interesting difference. Sorry if I didn't take note about the exact error. If you need the exact missing symbol I'll upgrade again and reboot the box ASAP (a couple of days). thanks grub-pc/mixed_legacy_and_grub2: true * grub2/linux_cmdline_default: quiet grub-pc/install_devices_failed_upgrade: true grub-pc/kopt_extracted: false grub-pc/timeout: 1 grub-pc/hidden_timeout: false grub2/kfreebsd_cmdline_default: quiet grub-pc/install_devices_empty: false * grub2/linux_cmdline: grub2/device_map_regenerated: grub-pc/install_devices_failed: false grub-pc/disk_description: grub-pc/chainload_from_menu.lst: true grub-pc/partition_description: grub2/kfreebsd_cmdline: grub-pc/postrm_purge_boot_grub: false grub-pc/install_devices_disks_changed: * grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0855797 rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=250868,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=405044k,mode=755 0 0 /dev/disk/by-uuid/d823f9f2-691b-4124-8475-e0b38ebeda20 / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,clone_children 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=21,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=202524k,mode=700,uid=1000,gid=1000 0 0 lrwxrwxrwx 1 root root 9 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0755186 -> ../../sda lrwxrwxrwx 1 root root 10 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0755186-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0755186-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0755186-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0855797 -> ../../sdb lrwxrwxrwx 1 root root 10 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0855797-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0855797-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Oct 16 04:06 ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M0855797-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 9 Oct 16 04:06 md-name-kerberos:0 -> ../../md0 lrwxrwxrwx 1 root root 9 Oct 16 04:06 md-name-kerberos:1 -> ../../md1 lrwxrwxrwx 1 root root 9 Oct 16 04:06 md-uuid-c38629be:44b7139d:3be7b954:8121bf9f -> ../../md1 lrwxrwxrwx 1 root root 9 Oct 16 04:06 md-uuid-f6cbb5e7:f5bb5e0c:48bf2fe2:7e0cde66 -> ../../md0 lrwxrwxrwx 1 root root 9 Oct 16 04:06 wwn-0x50014ee003a4a179 -> ../../sda lrwxrwxrwx 1 root root 10 Oct 16 04:06 wwn-0x50014ee003a4a179-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 16 04:06 wwn-0x50014ee003a4a179-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 16 04:06 wwn-0x50014ee003a4a179-part3 -> ../../sda3 lrwxrwxrwx 1 root root 9 Oct 16 04:06 wwn-0x50014ee0ae4f2d64 -> ../../sdb lrwxrwxrwx 1 root root 10 Oct 16 04:06 wwn-0x50014ee0ae4f2d64-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Oct 16 04:06 wwn-0x50014ee0ae4f2d64-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Oct 16 04:06 wwn-0x50014ee0ae4f2d64-part3 -> ../../sdb3
[...] [...] 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 noticed it was installed just on one disk too... but I'm definitively not an expert, infact one of the things I tried to fix this was: grub-install /dev/sda grub-install /dev/sdb but I noticed the grub-pc/install_devices didn't change. I'm reasonably sure that during installation I chose both but it happened several month ago, so I won't bet on it... and I admit I started to be too confident in how smoothly sid behave recently ;) dpkg-reconfigure grub-pc did the trick and now I can see both dev in grub-pc/install_devices I upgraded, rebooted and now everything is fine Unfortunately I can't roll back time to confirm that I actually chose both at install time. If there is any bug actually it should be related to older versions/install and people should not be affected in the future. thanks
Dear Maintainer, my system became unbootable after upgraind from grub 2.00-22 to 2.02~beta2-14 with the error message symbol 'grub_term_highlight_color' not found I had to boot a rescue system and downgrade grub again to fix this. And now I have to learn that this problem is actually known and the packages was still allowed to migrate, which leaves me completely puzzled. I can attach a picture of the rror if that helps, but it seems you are more interested in the output of some commands, so here you go: $ sudo debconf-show grub-pc grub-pc/partition_description: grub-pc/install_devices_disks_changed: grub2/device_map_regenerated: grub-pc/disk_description: * grub-pc/install_devices: /dev/disk/by-id/ata-Hitachi_HTS547575A9E384_J2540059C322KE grub-pc/install_devices_empty: false grub2/kfreebsd_cmdline: grub-pc/mixed_legacy_and_grub2: true * grub2/linux_cmdline_default: quiet grub2/kfreebsd_cmdline_default: quiet grub-pc/kopt_extracted: false grub-pc/chainload_from_menu.lst: true grub-pc/hidden_timeout: false grub-pc/install_devices_failed: false * grub2/linux_cmdline: grub-pc/install_devices_failed_upgrade: true grub-pc/timeout: 3 grub-pc/postrm_purge_boot_grub: false $ sudo cat /proc/mounts rootfs / rootfs rw 0 0 sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=1010331,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=1620492k,mode=755 0 0 /dev/mapper/cryptvg-rootlv / ext4 rw,relatime,discard,errors=remount-ro,data=ordered 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=21,pgrp=1,timeout=300,minproto=5,maxproto=5,direct 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 tmpfs /tmp tmpfs rw 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/mapper/cryptvg-homelv /home ext4 rw,relatime,discard,errors=remount-ro,data=ordered 0 0 /dev/sdb2 /boot ext4 rw,relatime,discard,errors=remount-ro,data=ordered 0 0 /dev/mapper/store /mnt/store ext4 rw,relatime,errors=remount-ro,data=ordered 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 tmpfs /run/user/110 tmpfs rw,nosuid,nodev,relatime,size=810248k,mode=700,uid=110,gid=117 0 0 tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=810248k,mode=700,uid=1000,gid=1000 0 0 $ sudo ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 Oct 16 22:59 ata-Hitachi_HTS547575A9E384_J2540059C322KE -> ../../sda lrwxrwxrwx 1 root root 10 Oct 16 22:59 ata-Hitachi_HTS547575A9E384_J2540059C322KE-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 16 22:59 ata-Hitachi_HTS547575A9E384_J2540059C322KE-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 16 22:59 ata-Hitachi_HTS547575A9E384_J2540059C322KE-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Oct 16 22:59 ata-Samsung_SSD_840_PRO_Series_S1ATNSAD717874B -> ../../sdb lrwxrwxrwx 1 root root 10 Oct 16 22:59 ata-Samsung_SSD_840_PRO_Series_S1ATNSAD717874B-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Oct 16 22:59 ata-Samsung_SSD_840_PRO_Series_S1ATNSAD717874B-part3 -> ../../sdb3 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptpv -> ../../dm-0 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptvg-homelv -> ../../dm-2 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptvg-rootlv -> ../../dm-1 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-cryptvg-swaplv -> ../../dm-3 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-name-store -> ../../dm-4 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-uuid-CRYPT-LUKS1-406e399ce7b142b48a2ff35346797b8f-cryptpv -> ../../dm-0 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-uuid-CRYPT-LUKS1-931f27b22a6841f58108104d494cd284-store -> ../../dm-4 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-uuid-LVM-sApY335FtcFuHL2m19uYEfus1ztFVjpNKF1Y0gALnWEBRKiPAkcEYexuCXOFW40j -> ../../dm-1 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-uuid-LVM-sApY335FtcFuHL2m19uYEfus1ztFVjpNmTjHP0oJbPs8IQQZdXoyJHWy9XelP7kG -> ../../dm-2 lrwxrwxrwx 1 root root 10 Oct 16 22:59 dm-uuid-LVM-sApY335FtcFuHL2m19uYEfus1ztFVjpNOEiDlPiIwuIw9sD30JQ2Tn5K3fZNscH2 -> ../../dm-3 lrwxrwxrwx 1 root root 10 Oct 16 22:59 lvm-pv-uuid-pSnle7-vu3S-t2pM-Mt7p-dRlq-YiTP-VxucVI -> ../../dm-0 lrwxrwxrwx 1 root root 9 Oct 16 22:59 wwn-0x5000cca6dfc164ee -> ../../sda lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x5000cca6dfc164ee-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x5000cca6dfc164ee-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x5000cca6dfc164ee-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Oct 16 22:59 wwn-0x50025385a00884b2 -> ../../sdb lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x50025385a00884b2-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Oct 16 22:59 wwn-0x50025385a00884b2-part3 -> ../../sdb3 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. Kind regards Ralf
Hi again, 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
Hi. I have the same issue after upgrade. I access to my system with a rescue. Try dpkg-reconfigure grub-pc and found all my images. After that, i try to install grub with: # grub-install /dev/sda And I get this error: Grub-install: error: cannot copy `/usr/share/locale/sv.gmo' to `/boot/grub/locale/sv.mo': is a directory. And finish without install.
Hi. I found three directories .gmo in mi locale directory (sv.gmo one of them). I checked that they were equals to the locale and move them to a temp. After that, I purged grub-pc and installed it and it installed fine in my boot. That temp directories were the problem for me. I really don't know what program create them (they have date of 2007 :)) So, that fixed the problem for me. Thanks and sorry for the noise.
Hi, Indeed running "dpkg-reconfigure grub-pc" and telling it to install grub on both /dev/sda and /dev/sdb fixed the problem. Phew :D However, I still think some way to tell the user that this is actually necessary, would be a great improvement. For example, when running grub-install manually, it could say that while this installed the *current version*, further means have to be taken for future upgrades to be applied. Kind regards Ralf
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
I just hit this bug while upgrading from 2.00-22 to 2.02~beta2-15. I believe #743477 is a duplicate of this bug. The current behavior breaks an existing functional boot simply by noninteractively upgrading grub-pc, which happens in an apt-get upgrade and/or dist-upgrade. If this happens on a noninteractive upgrade from wheezy to jessie, it would be a very serious release blocker. By its definition, this should be a critical bug. Steps to reproduce: - Deploy this jessie vagrant box: https://downloads.sourceforge.net/project/vagrantboxjessie/debian80.box (or any box with grub 2.00-22) - apt-get update - DEBIAN_FRONTEND=noninteractive apt-get -y install grub-pc - reboot The "DEBIAN_FRONTEND=noninteractive" is there to reproduce what happenes during provisioning automation (ansible/puppet/salt/chef etc). An example vagrantfile is here: http://paste.debian.net/130854/ The workaround is to do a "grub-install --recheck /dev/sda" after upgrading the package. Due to the nature of deployable images like this, the install_devices from debconf will likely never match the newly created drive; even in cases where it is using /dev/sda it may be that an image would get deployed with virtio and the booted drive would end up being /dev/vda. For reference, the output of "debconf-get-selections | grep -i grub" before upgrading grub-pc packages: /usr/bin/debconf-get-selections |grep -i grub grub-pc grub-pc/chainload_from_menu.lst boolean true # Writing GRUB to boot device failed - continue? grub-pc grub-pc/install_devices_failed boolean false grub-pc grub-pc/kopt_extracted boolean false # Hide the GRUB timeout grub-pc grub-pc/hidden_timeout boolean false # GRUB install devices: grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-VBOX_HARDDISK_VB4950a3eb-80192436 grub-pc grub2/linux_cmdline_default string quiet # Remove GRUB 2 from /boot/grub? grub-pc grub-pc/postrm_purge_boot_grub boolean false # Writing GRUB to boot device failed - try again? grub-pc grub-pc/install_devices_failed_upgrade boolean true grub-pc grub2/linux_cmdline string debian-installer=en_US grub-pc grub2/kfreebsd_cmdline string # GRUB timeout grub-pc grub-pc/timeout string 5 # /boot/grub/device.map has been regenerated grub-pc grub2/device_map_regenerated note # Continue without installing GRUB? grub-pc grub-pc/install_devices_empty boolean false # GRUB install devices: grub-pc grub-pc/install_devices_disks_changed multiselect grub-pc grub2/kfreebsd_cmdline_default string quiet # Finish conversion to GRUB 2 now? grub-pc grub-pc/mixed_legacy_and_grub2 boolean true And after upgrading: grub-pc grub-pc/kopt_extracted boolean false # GRUB install devices: grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-VBOX_HARDDISK_VB4950a3eb-80192436 grub-pc grub2/linux_cmdline_default string quiet # GRUB install devices: grub-pc grub-pc/install_devices_disks_changed multiselect /dev/disk/by-id/ata-VBOX_HARDDISK_VB4950a3eb-80192436 # /boot/grub/device.map has been regenerated grub-pc grub2/device_map_regenerated note # Remove GRUB 2 from /boot/grub? grub-pc grub-pc/postrm_purge_boot_grub boolean false grub-pc grub2/kfreebsd_cmdline string grub-pc grub-pc/chainload_from_menu.lst boolean true # Continue without installing GRUB? grub-pc grub-pc/install_devices_empty boolean false # Finish conversion to GRUB 2 now? grub-pc grub-pc/mixed_legacy_and_grub2 boolean true grub-pc grub2/kfreebsd_cmdline_default string quiet grub-pc grub2/linux_cmdline string debian-installer=en_US # Writing GRUB to boot device failed - try again? grub-pc grub-pc/install_devices_failed_upgrade boolean true # What do you want to do about modified configuration file grub? # GRUB timeout; for internal use grub-pc grub-pc/timeout string 0 # Hide the GRUB timeout; for internal use grub-pc grub-pc/hidden_timeout boolean false # Writing GRUB to boot device failed - continue? grub-pc grub-pc/install_devices_failed boolean false
Control: severity -1 normal Control: retitle -1 Problems with grub upgrades getting out of step on a RAID configuration Hi Enrico, That looks like a generally useful thing to have, yes, but I don't think it's RC to *not* have it. Downgrading and retitling appropriately. I'll see what I can do to add support for something like that soon. In a related(ish) sense, we could do with some similar extra work to make EFI systems and RAID play nicely too... :-/