From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jes Sorensen Subject: Re: Install grub2 to /dev/md126 fails Date: Tue, 03 Jan 2012 11:55:31 +0100 Message-ID: <4F02DEA3.4050901@redhat.com> References: <760811954.244872.1325303953552.JavaMail.root@sz0019a.westchester.pa.mail.comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <760811954.244872.1325303953552.JavaMail.root@sz0019a.westchester.pa.mail.comcast.net> Sender: linux-raid-owner@vger.kernel.org To: jlcenter@comcast.net Cc: linux-raid@vger.kernel.org List-Id: linux-raid.ids On 12/31/11 04:59, jlcenter@comcast.net wrote: > Hi, > > I've been trying to install Ubuntu 11.10 on a mdadm imsm raid1 array, but it fails installing grub. I had to chroot /target to install mdadm from the distribution. I've also upgraded to the latest version of mdadm, hoping this would fix the problem. This is the error I'm getting: > > root@ubuntu:/# grub-install --recheck /dev/md/V1 > /usr/sbin/grub-probe: error: no such disk. > Auto-detection of a filesystem of /dev/md126p3 failed. > Try with --recheck. > If the problem persists please report this together with the output of "/usr/sbin/grub-probe --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to > > Here's how mdadm sees my config: > > root@ubuntu:/dev# mdadm --examine --scan > ARRAY metadata=imsm UUID=92ae2913:95d651ca:62154f33:7069b04c > ARRAY /dev/md/V1 container=92ae2913:95d651ca:62154f33:7069b04c member=0 UUID=71b12777:c6a51a84:5b0f1d11:0bd6e497 > > I also tried with several variations of /dev/md126, etc., but always with the same result. I also tried to install directly to one of the disks in the array, but this didn't work, either. When I ran grub-probe, I got the following error: > > /usr/sbin/grub-probe: info: opening mduuid/71b12777c6a51a845b0f1d110bd6e497,3. > /usr/sbin/grub-probe: error: no such disk. > > What could be causing this problem? How do I fix it? Please let me know if I need to supply more information to troubleshoot this problem. Did your raid device(s) get added to /boot/grub2/device.map correctly? If not, does it install properly if you add the devices there manually? I've had a pile of problems with grub2 on Fedora, including something like this. Cheers, Jes