From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1NPD8b-00016G-Qk for mharc-grub-devel@gnu.org; Mon, 28 Dec 2009 05:47:45 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPD8Z-00014f-7K for grub-devel@gnu.org; Mon, 28 Dec 2009 05:47:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPD8U-00012B-Ay for grub-devel@gnu.org; Mon, 28 Dec 2009 05:47:42 -0500 Received: from [199.232.76.173] (port=52863 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPD8U-000122-4N for grub-devel@gnu.org; Mon, 28 Dec 2009 05:47:38 -0500 Received: from moutng.kundenserver.de ([212.227.126.186]:60730) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NPD8T-0000hc-G0 for grub-devel@gnu.org; Mon, 28 Dec 2009 05:47:37 -0500 Received: from [85.180.12.33] (e180012033.adsl.alicedsl.de [85.180.12.33]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0MTtCv-1NYOCQ3tNB-00QoqR; Mon, 28 Dec 2009 11:47:32 +0100 From: Felix Zielcke To: The development of GNU GRUB In-Reply-To: <714466.91538.qm@web88207.mail.re2.yahoo.com> References: <714466.91538.qm@web88207.mail.re2.yahoo.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 28 Dec 2009 11:47:30 +0100 Message-ID: <1261997250.3183.13.camel@fz.local> Mime-Version: 1.0 X-Mailer: Evolution 2.29.3.2 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/5oPy4idBr+TEK6olYD7QV6tNjkJFbBEYX6dh OnIxoKxaqO+5cqWGDIxeeMXIV5rAO3jcxcF876l8VgensEmhjw bR509WysksulikF8Y5jGg== X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: grub-setup: error: no mapping exists for ... in GRUB2 v1.97.1 on fake (IMSM) RAID X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 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: Mon, 28 Dec 2009 10:47:43 -0000 Am Sonntag, den 27.12.2009, 17:50 -0800 schrieb Lapohos Tibor: > Thanks for your reply. > > What the OROM says is that both of my volumes are bootable. > /dev/md126 corresponds to Volume0, and its first partition (ext4) has > the boot flag set. > > My problem is that I cannot get grub2 installed on the device at all. > I did try, as you suggested, to set You're problem is that you're using metadata 1.x and not the older default 0.90. Which we don't support yet. I made a Baazar branch for metadata 1.x support, but it's still broken. At least RAID != 1. But I tested RAID 1 only with grub-probe, not actual booting from it. And it's a bit complicated to get grub-probe working, because the devicename must macht the name stored in the superblock. If you want to try it nevertheless: bzr co http://bzr.savannah.gnu.org/r/grub/people/fzielcke/raid > (hd0) /dev/md126 > > in the device.map file and then issue > > > grub-install --modules=raid /dev/md126 > > but I still get the same error message(s): > > grub-probe: error: no mapping exists for 'md126' > grub-setup: error: no mapping exists for 'md126' device.map isn't used at all for mdraid devices. > What is interesting is that, at the grub shell, I can do > > grub> probe -l (hd0,1) > > it returns "OS" which is the label I set for it, so the device can, > under certain circumstances, definitely be detected. Nevertheless, > grub-install does not seem to behave the same way. (hdX,Y) devices are normal disk devices though and not the RAID ones. They're (mdX) and (mdX,Y) so it only works with RAID 1, but only by using one disk of them. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer