Re: setup-storage + grub2
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? Thanks, Michael pgpAu7zaOX3GA.pgp Description: PGP signature
setup-storage: preserve_lazy for LVM fails on empty disk
Hello, Context: FAI 3.4~beta1+experimental11, disk is empty, and the preserve_lazy option is set for two LVM volumes. The volume group is not created by setup-storage, pvcreate is followed by vgextend instead of vgcreate. I'm pretty sure this has been working before, I think I have successfully used it with experimental9. Of course, I just need to remove the preserve_lazy option to make it work again. The format.log file is on http://paste.debian.net/71013/ -- Nicolas
Re: setup-storage: preserve_lazy for LVM fails on empty disk
> Hello, > > Context: FAI 3.4~beta1+experimental11, disk is empty, and the > preserve_lazy option is set for two LVM volumes. > The volume group is not created by setup-storage, pvcreate is > followed by vgextend instead of vgcreate. > > I'm pretty sure this has been working before, I think I have > successfully used it with experimental9. > Of course, I just need to remove the preserve_lazy option to make it > work again. > > The format.log file is on http://paste.debian.net/71013/ > It is claimed that vg0 exists (lines 68-72), but that seems pretty odd. Could I ask you to redo the experiments, maybe even just do a setup-storage run without -X, but rename vg0 to vg1 in the config? It seems likely that this entry in the hash is unintentionally created. Could you try to confirm that? Thanks a lot, Michael pgpgHpaMGowIV.pgp Description: PGP signature
Re: setup-storage: preserve_lazy for LVM fails on empty disk
Context: FAI 3.4~beta1+experimental11, disk is empty, and the preserve_lazy option is set for two LVM volumes. The volume group is not created by setup-storage, pvcreate is followed by vgextend instead of vgcreate. I'm pretty sure this has been working before, I think I have successfully used it with experimental9. Of course, I just need to remove the preserve_lazy option to make it work again. The format.log file is on http://paste.debian.net/71013/ It is claimed that vg0 exists (lines 68-72), but that seems pretty odd. Could I ask you to redo the experiments, maybe even just do a setup-storage run without -X, but rename vg0 to vg1 in the config? It seems likely that this entry in the hash is unintentionally created. Could you try to confirm that? Same result, vg1 is in the hash although it has never existed on this disk. -- Nicolas
Re: setup-storage + grub2
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
Re: setup-storage: preserve_lazy for LVM fails on empty disk
> > >> > >>Context: FAI 3.4~beta1+experimental11, disk is empty, and the > >>preserve_lazy option is set for two LVM volumes. > >>The volume group is not created by setup-storage, pvcreate is > >>followed by vgextend instead of vgcreate. > >> > >>I'm pretty sure this has been working before, I think I have > >>successfully used it with experimental9. > >>Of course, I just need to remove the preserve_lazy option to make it > >>work again. > >> > >>The format.log file is on http://paste.debian.net/71013/ > >> > > > >It is claimed that vg0 exists (lines 68-72), but that seems pretty odd. > >Could I > >ask you to redo the experiments, maybe even just do a setup-storage run > >without > >-X, but rename vg0 to vg1 in the config? It seems likely that this entry in > >the > >hash is unintentionally created. Could you try to confirm that? > Same result, vg1 is in the hash although it has never existed on this disk. > I believe this should be fixed in 3.4~beta1+experimental14. Could you please verify that? Thanks a lot for the quick test, it helped a lot! Best, Michael pgpPYZ4pnhkOV.pgp Description: PGP signature
Re: setup-storage + grub2
[...] > > > > 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. > Err, yes, of course, there was nothing that would create device.map. I've added a call to grub-mkdevicemap in 3.4~beta1+experimental14, could you give that one another try? Thanks a lot, Michael pgpIE9HJYPu4Z.pgp Description: PGP signature
