On Mon, May 14, 2007 at 09:23:24PM +0200, Robert Millan wrote: > On Mon, May 14, 2007 at 09:59:15AM +0100, Sam Morris wrote: > > On Mon, 2007-05-14 at 10:54 +0200, Robert Millan wrote: > > > On Sun, May 13, 2007 at 08:32:58PM +0100, Sam Morris wrote: > > > > > Can you try arranging this code to include the missing "/dev/" and > > > > > report if > > > > > everything still works? > > > > > > > > Now this is more interesting. I no longer have the broken menu that I > > > > mentioned in the other bug report! However, when I actually select one > > > > of the entries, I get 'error: you need to load the kernel first'. > > > > > > > > This seems to be caused by 'root' not being set in grub.cfg any more. Or > > > > rather, it's set to an empty string. Looking closely at update-grub, I > > > > guess changing grub_guess_root_device broke other parts of grub-probe: > > > > > > > > + echo 'Updating /boot/grub/grub.cfg ...' > > > > Updating /boot/grub/grub.cfg ... > > > > + cat > > > > ++ grub-probe --target=device /boot/grub > > > > + export GRUB_DEVICE=/dev/md0 > > > > + GRUB_DEVICE=/dev/md0 > > > > ++ grub-probe --target=drive /boot/grub > > > > cannot find a GRUB drive for /dev/md0. > > > > > > Check your device.map. If it's broken, check if your newly modified > > > grub-mkdevicemap generates the right thing. > > > > Adding '(md0) /dev/md0' triggers another error: > > 'error: /boot/grub/device.map:5: Bad device name'. > > Sorry, I'm lost now. I would suggest running a regression test from the > latest > known-good date (look for Jeroen's RAID-related commits in upstream > ChangeLog), > if you have the time. > > I don't have time atm, but maybe later I can setup an LVM system to be able to > test such things. Software RAID support is kinda abandoned atm.
It seems that upstream just reviewed this. Can you try latest CVS and report if that works for you? -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
