Re: Various build failures in current bzr tree

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 10.02.2012 16:54, Lennart Sorensen wrote:
> On Fri, Feb 10, 2012 at 12:02:52AM +0100, Vladimir 'φ-coder/phcoder' Serbinenko 
> wrote:
> > On 09.02.2012 21:56, Lennart Sorensen wrote:
> > > On Thu, Feb 09, 2012 at 03:50:45PM -0500, Lennart Sorensen wrote:
> > > > grub-install also still (as reported about 2 years ago) tries to use
> > > > $grub_device rather than $install_device when getting the partition
> > > > table type.
> > > >
> > > > However, I did now manage to boot after fixing that.
> > > >
> > > > So there is a chance I can make a patch to fix grub-install soon so it
> > > > actually works on IBM power systems.  Given I have a production machine
> > > > and a new machine around for a few days I can experiment until it
> > > > is right.
> > > Is this supposed to work:
> > >
> > > address@hidden:~# /usr/sbin/grub-probe --device /dev/md0 --target=abstraction
> > > diskfilter mdraid1x
> > > address@hidden:~# /usr/sbin/grub-probe --device /dev/md1 --target=abstraction
> > > /usr/sbin/grub-probe: error: Couldn't find PV (null). Check your device.map.
> > >
> > > md0 is raid1, md1 is raid5, but with a missing device at the moment.
> > >
> > > Does grub-probe not work if the raid5 isn't fully healthy?
> > The problem is how to figure out which partmap module is used on the
> > missing disk (which isn't necessarily the same as on the other
> > disks). Do you have any ideas?
> Hmm, good question.  So not working in this case is expected then at
> this time.  However, is not returning the partition table of the devices
> you can find better than returning the partition map of what is found?
Imagine following setup: 2 disks with msdos and one with gpt. GPT one is 
missing on install time and so no part_gpt is inserted. On boot time is 
then one of msdos disks is missing and so GPT one is needed to complete 
a readable device but it's inaccessible since no GPT module is loaded.
> By the way, does grub-probe have any way to return the underlying device
> of an md device?
This and the rest of your e-mail is because of confusion of 2 concepts: 
grub_device and install_device.
grub_device is whereever GRUB modules reside and is determined from 
$boot_directory/grub (default is /boot/grub)
install_device is whereever the core is and is the argument to grub-install.
They are independent since you want to put core wherever firmware will 
find it independently of where your root is.
install_device is not infered from grub_device or vice-versa.
In mdraid example grub_device=mduuid/<UUID> but install_device is still 
/dev/sdaX

--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko