setup-storage + grub2

[Waldemar Brodkorb]

Hi Michael,
Michael Tautschnig wrote,

> Hi Waldemar,
> 
> [...]
> 
> > 
> > > AFAIK grub-install takes care of a lot of things and just takes a device name as
> > > argument, if you omit the parentheses!? It could be necessary to re-add the
> > > grub-mkimage, if update-grub chokes on that one.
> > 
> > Still failing. Only thing that works is either:
> > $ROOTCMD /usr/sbin/grub-install --no-floppy --modules="biosdisk part_msdos ext2 lvm raid" "(hd0)"
> > $ROOTCMD update-grub
> > or 
> > $ROOTCMD /usr/sbin/grub-install --no-floppy --modules="biosdisk part_msdos ext2 lvm raid" /dev/sda
> > $ROOTCMD update-grub
> > 
> > Anything speaks against "(hd0)"? This would work for most of the
> > cases. For RAID1 users an example like this might be enough:
> > $ROOTCMD /usr/sbin/grub-install --no-floppy --modules="biosdisk part_msdos ext2 lvm raid" "(hd0)"
> > $ROOTCMD /usr/sbin/grub-install --no-floppy --modules="biosdisk part_msdos ext2 lvm raid" "(hd1)"
> > $ROOTCMD update-grub
> >  
> 
> I think I've been kind of stupid - obviously the device where the MBR resides
> (which doesn't affect LVM in any way...) must be given. Sorry. Now, doing
> vgdisplay or the like in this script isn't all that nice when setup-storage has
> all the information anyway. This should have been fixed in
> 3.4~beta1+experimental12, where setup-storage includes the disks that make up a
> volume group in $BOOT_DEVICE. I've also tried to simplify the 10-setup script
> even further (well, the really simple version is in experimental13).
> 
> Could you give that one another try?

Still no green blinking lights:
=====   shell: GRUB_PC/10-setup   =====
Can't open /target/boot/grub/device.map
/usr/sbin/grub-setup: error: no mapping exists for `sda'.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.32-21-generic
Found initrd image: /boot/initrd.img-2.6.32-21-generic
Found memtest86+ image: /boot/memtest86+.bin
done
GRUB_PC/10-setup     FAILED with exit code 1.

device2grub fails because, /target/grb/boot/device.map does not 
exist. BOOT_DEVICE is /dev/sda.
And if grub_dev is empty, /dev/sda is converted to sda, which does
not work as argument for grub-setup.

greetings,
        Waldemar