Bug#514201: grub-pc: update-grub failing only reporting "exiting with value 1" when problems with /boot/grub/device.map

[Arthur Marsh]

Even weirder... I don't get an error if I have the correct device.map, a 
device.map that includes a non-existent drive, no device.map or an empty 
device.map.

Maybe there was something wrong that has just cleared itself.

Feel free to tag as unreproducible

Arthur.

Felix Zielcke wrote, on 05/02/09 21:58:
> Am Donnerstag, den 05.02.2009, 16:39 +1030 schrieb Arthur Marsh:
> 
>> Could someone please fix the update-grub script to better report a 
>> failure due to problems with /boot/grub/device.map?
> 
> This is weird. Normally it does report to check device.map if it's
> wrong:
> 
> fz:/boot/grub# rm device.map 
> fz:/boot/grub# touch device.map
> fz:/boot/grub# update-grub
> Generating grub.cfg ...
> Found linux image: /boot/vmlinuz-2.6.26-1-amd64
> Found initrd image: /boot/initrd.img-2.6.26-1-amd64
> grub-probe: error: Cannot find a GRUB drive for /dev/hda2.  Check your device.map.
> 
> grub-probe: error: Cannot find a GRUB drive for /dev/hda2.  Check your device.map.
> 
> done
> fz:/boot/grub# 
> 
> Are you sure that this was with grub2 and not grub-legacy?
> There was a version which failed silently but that has been fixed now.
>