[SATLUG] RAID5 Recovery - Reassembly Commencing!
adlabens at swbell.net
Wed Aug 26 23:19:36 CDT 2009
Following your directions explicitly ...
San Antonio, TX
--- On Wed, 8/26/09, Samuel Leon <satlug at net153.net> wrote:
From: Samuel Leon <satlug at net153.net>
Subject: Re: [SATLUG] RAID5 Recovery - Reassembly Commencing!
To: "The San Antonio Linux User's Group Mailing List" <satlug at satlug.org>
Date: Wednesday, August 26, 2009, 11:17 PM
n/m, your version 2.6.7-3ubuntu8 has the bug as it wasn't fixed until 188.8.131.52-1ubuntu1
You can follow the version in the change log and see in jaunty where they finally update it:
Not sure how well ubuntu handles installing stuff from its other distros but updating mdadm to the one in jaunty would be as easy as changing your apt sources. They both seem to have the same deps, you would have to also update udev too it seems.
So vim /etc/apt/sources.list (probably should make a backup)
replace intrepid with jaunty:
save and quit vim:
install updated mdadm and udev(-P means prompt before making changes)
aptitude -P install mdadm udev
Before you press "y" to continue I would post the results here because anything more than mdadm and udev being updated could really mess up stuff.
Samuel Leon wrote:
> It is supposed to be fixed in this version. One possibility is to re-create the array using the create command. Do you remember the EXACT parameters that you used to create this array?
> Would look something like:
> mdadm --create /dev/md0 --level=5 --chunk=128 --raid-disks=4 /dev/sde1 /dev/sda1 /dev/sdb1 /dev/sdc1
> If that is correct we would have to recreate it with:
> mdadm --create /dev/md0 --assume-clean --level=5 --chunk=128 --raid-disks=4 /dev/sde1 /dev/sda1 missing /dev/sdc1
> Sorta what the guy did here: http://ubuntuforums.org/showthread.php?t=1061700
SATLUG mailing list
SATLUG at satlug.org
http://alamo.satlug.org/mailman/listinfo/satlug to manage/unsubscribe
Powered by Rackspace (www.rackspace.com)
More information about the SATLUG