> I got basically the same device map back again, though. > > (fd0) /dev/fd0 > (hd0) /dev/disk/by-id/ata-ST3320620AS_3QF0SGE4 > (hd1) /dev/disk/by-id/ata-ST3320620AS_3QF0QNYW > > I quote my current grub.cfg below. This gives an error after booting, > saying it cannot find the newdebian volume group. > I need the output of: sudo sh -x grub-install /dev/sda And also the output of "ls" on boot
> > a) set root='(newdebian-root)' > > Comment: I have seen in various places the suggestion that for a > software raid device > Correct behavior > b) There are two search lines, with different uuids, namely > Correct behavior > > 3) linux /vmlinuz-2.6.32-5-vserver-686-bigmem > root=/dev/mapper/newdebian-root ro quiet > Correct behavior > *************************************************************************** > > > Stray observation - it turns out that mdadm was not installed in my > chroot, and when installed, it promptly updated my initrd. Does grub > not require mdadm to be installed? > really recommended -- Regards Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bug-grub mailing list Bug-grub@gnu.org http://lists.gnu.org/mailman/listinfo/bug-grub