Re: grub-probe seems to be having problems

[Lennart Sorensen]

On Thu, Mar 01, 2012 at 09:07:34PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko 
wrote:
> On 01.03.2012 20:47, Lennart Sorensen wrote:
> >address@hidden:~# /usr/sbin/grub-probe --device /dev/md1 --target=partmap
> >/usr/sbin/grub-probe: error: disk `mduuid/dc00bd3a0e9491bb0b66fa8b9246c2e8' 
> >not found.
> Is the uuid correct?

Yes.  No idea about mduuid/ in front, but it matches the uuid I see in
mdadm --detail /dev/md1 (other that it has : every 8 characters).

> >That seems wrong.
> >
> >So does:
> >
> >address@hidden:~# /usr/sbin/grub-probe --device /dev/md0 --target=partmap
> >/usr/sbin/grub-probe: error: Couldn't find physical volume `(null)'. Check 
> >your device.map.
> The problem is that code stops scanning as soon as it detects enough
> devices to read from RAID.

So why is it complaining if it has what it needs?

> >address@hidden:~# cat /proc/mdstat
> >Personalities : [raid1] [raid6] [raid5] [raid4]
> >md1 : active raid5 sdd3[4] sdc3[3](F) sda3[0] sdb3[1]
> >       284773376 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] 
> > [UUU]
> >
> >md0 : active raid1 sdd2[2] sda2[0] sdb2[1]
> >       976884 blocks super 1.2 [3/3] [UUU]
> >
> >unused devices:<none>
> >
> >grub-install never seems to generate a device.map file anymore either,
> >although --recheck happily deletes it for me.
> >
> >What is supposed to generate the /boot/grub/device.map these days?
> Nothing, it's not used by default anymore and its main use is manual
> override.

Should grub-probe be suggesting checking your device.map if it doesn't
exist and doesn't need it?  That's confusing.

-- 
Len Sorensen