Re: Grub2 reinstall on raid1 system.
On Thu, Jan 13, 2011 at 5:43 PM, Rob Owens <rowens@ptd.net> wrote:
> On Thu, Jan 13, 2011 at 08:23:11AM -0600, Jack Schneider wrote:
>>
>> I have a raid1 based W/S running Debian Squeeze uptodate. (was
>> until ~7 days ago) There are 4 drives, 2 of which had never been
>> used or formatted. I configured a new array using Disk Utility from a
>> live Ubuntu CD. That's where I screwed up... The end result was the
>> names of the arrays were changed on the working 2 drives. IE: /dev/md0
>> to /dev/126 and /dev/md1 became md127. Strangely the md2 array which I
>> setup on the added drives remains as /dev/md2. My root partition is/was
>> on /dev/md0. The result is that Grub2 fails to boot the / array. I have
>> tried three REINSTALLING GRUB procedures from Sysresccd online docs
>> and many others GNU.org, Ubuntu etc. The errors occur when I try to
>> mount the partition with the /boot directory. 'Complains about file
>> system type 'linux_raid_member' This machine has worked for 3 years
>> flawlessly.. Can anyone help with this? Or point me to a place or link
>> to get this fixed. Google doesn't help... I can't find a
>> article/posting where it ended successfully.
>> I have considered a full reinstall after Squeeze goes stable, since this
>> O/S is a crufty upgrade from sarge over time. But useless now..
>
> You might want to try configuring grub and fstab to use UUID's instead
> of /dev/mdX. That removes the possibility that the kernel will change
> the mdX designations.
>
> Use blkid to find out the UUID's of your partitions.
I don't think that the UUIDs'll change anything because mdadm.conf
establishes a one-to-one correspondence between mdX and its UUID. If
the superblock metadata's v0.9, the hostname's hashed and integrated
into the UUID (I can't imagine that the latter would've changed) and
if the superblock metada's v1.x, the hostname's held separately from
the UUID so it can change independently of the latter.
If the arrays are being name 127 and 126, they must be considered
foreign to the system; most probably because the metadata's been
modified while booted from the Ubuntu CD/DVD. Using mdadm's
"--homehost" flag to reset the hostname should reset them to being
recognized 0 and 1.
Reply to: