Bug#586815: grub-probe: error: cannot find a device for / is still a problem with dmcrypt, lvm2 and /dev/sda

Colin Watson cjwatson at debian.org
Mon Jun 28 12:42:52 UTC 2010


On Tue, Jun 22, 2010 at 11:22:55PM +0200, Michael Ostermeier wrote:
>  Colin Watson wrote:
> > Looks like you're suffering from #550704.  Could you please try the
> > version in unstable?
> 
> Yes, this version is better, update-grub works now:
> 
> # update-grub
> Generating grub.cfg ...
> Found background image: moreblue-orbit-grub.png
> Found linux image: /boot/vmlinuz-2.6.32-5-686
> Found initrd image: /boot/initrd.img-2.6.32-5-686
> Found linux image: /boot/vmlinuz-2.6.32-3-686
> Found initrd image: /boot/initrd.img-2.6.32-3-686
> done
> 
> But the old setup was still better. On the new one:
> 
> * it still complains not to find /dev/hda

You already said you edited /boot/grub/device.map, so I'm not sure.
Could you please send me the output of:

  sh -x /usr/sbin/grub-mkconfig -o /boot/grub/grub.cfg

> * the background-picture is still not displayed
> * the resolution of the screen is still bad until the kernel is setting
>   the font later during booting 

vga= doesn't work with the 32-bit boot protocol now used by GRUB 2.  You
can use GRUB_GFXPAYLOAD_LINUX (see 'info grub' in unstable; there are
caveats), or you can edit /etc/grub.d/10_linux and change places where
it emits 'linux' and 'initrd' commands to 'linux16' and 'initrd16'
respectively.

-- 
Colin Watson                                       [cjwatson at debian.org]





More information about the Pkg-grub-devel mailing list