From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1Rvt4N-0000wr-8g for mharc-grub-devel@gnu.org; Fri, 10 Feb 2012 11:11:31 -0500 Received: from eggs.gnu.org ([140.186.70.92]:45006) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvt4G-0000pg-Al for grub-devel@gnu.org; Fri, 10 Feb 2012 11:11:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rvt4B-0000uM-VX for grub-devel@gnu.org; Fri, 10 Feb 2012 11:11:24 -0500 Received: from mail-ww0-f49.google.com ([74.125.82.49]:60125) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rvt4B-0000uG-Qf for grub-devel@gnu.org; Fri, 10 Feb 2012 11:11:19 -0500 Received: by wgbdt13 with SMTP id dt13so2215764wgb.30 for ; Fri, 10 Feb 2012 08:11:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=4DgIiu2i44RaXP9bPcH7rhPeOi3h2Ex2dRTgZgAJELY=; b=bcJSf+Cuf+CQwPyRDQtqL8ujj2UxUoDHOxvmoXTPJRDiyKrcp1ttzIanuS5s4PSlD8 4tdbHVnTvA9oTgpald1/Oyz7FD6emR+kY0LNMv5bn3J06UF/PdIpe9sLecgdVzy27pPO 0brr3t/WefUi6cpexl2GjsCCCSi5WQZA4VjqI= Received: by 10.180.92.73 with SMTP id ck9mr10262759wib.2.1328890278957; Fri, 10 Feb 2012 08:11:18 -0800 (PST) Received: from debian.x201.phnet (93-93.203-62.cust.bluewin.ch. [62.203.93.93]) by mx.google.com with ESMTPS id ft8sm4167926wib.11.2012.02.10.08.11.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 10 Feb 2012 08:11:18 -0800 (PST) Message-ID: <4F3541A4.10502@gmail.com> Date: Fri, 10 Feb 2012 17:11:16 +0100 From: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120104 Icedove/8.0 MIME-Version: 1.0 To: Lennart Sorensen Subject: Re: Various build failures in current bzr tree References: <20120209190204.GW27742@caffeine.csclub.uwaterloo.ca> <20120209193301.GX27742@caffeine.csclub.uwaterloo.ca> <20120209205045.GY27742@caffeine.csclub.uwaterloo.ca> <20120209205603.GZ27742@caffeine.csclub.uwaterloo.ca> <4F34509C.5050005@gmail.com> <20120210155450.GB27742@caffeine.csclub.uwaterloo.ca> In-Reply-To: <20120210155450.GB27742@caffeine.csclub.uwaterloo.ca> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 74.125.82.49 Cc: The development of GNU GRUB X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 16:11:28 -0000 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: >>> >>> root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md0 --target=abstraction >>> diskfilter mdraid1x >>> root@rceng03new:~# /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/ but install_device is still /dev/sdaX -- Regards Vladimir 'φ-coder/phcoder' Serbinenko