On Fri, Sep 29, 2006 at 12:23:14PM +0200, martin f krafft wrote:
> Thanks for your efforts, Robert! Here are the data you requested:
> 
> also sprach Robert Millan <[EMAIL PROTECTED]> [2006.09.24.2204 +0200]:
> > Can you please send the output of "grub-probefs -v /" ?
> 
> mdadmp:~# grub-probefs -v /
> grub-probefs: info: changing current directory to /dev
> grub-probefs: info: changing current directory to mapper
> grub-probefs: info: changing current directory to input
> grub-probefs: info: changing current directory to by-path
> grub-probefs: info: changing current directory to net
> grub-probefs: info: changing current directory to loop
> grub-probefs: info: changing current directory to shm
> grub-probefs: info: changing current directory to pts
> grub-probefs: info: changing current directory to .static
> grub-probefs: info: changing current directory to dev
> grub-probefs: info: changing current directory to md
> cannot find a GRUB device for /.

Note: I assume you're running the latest grub2 from sid (1.94+20060926-1), cause
at the time you reported this bug there were other bugs that caused the same
behaviour in grub-probefs.

> > Oh, and the contents of your device.map, and (if different), the output of
> > "grub-mkdevicemap -m -".
> 
> mdadmp:~# cat /boot/grub/device.map 
> (hd0) /dev/sda
> (hd1) /dev/sdb
> (hd2) /dev/sdc
> (hd3) /dev/sdd
> mdadmp:~# grub-mkdevicemap -m -
> (fd0) /dev/fd0
> (hd0) /dev/sda
> (hd1) /dev/sdb
> (hd2) /dev/sdc
> (hd3) /dev/sdd

Ok.  grub-mkdevicemap needs to learn about /dev/md_d0, but maybe grub-probefs
does too (it has other, more generic pathname checks).  Please try:

  echo "(hd0) /dev/md_d0" > /boot/grub/device.map
  grub-probefs -v /

Thanks

-- 
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]

Reply via email to