From: NeilBrown <neilb@suse.de>
To: Ricky <rickyorbixx@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Successfully recovered Raid5 no longer boots
Date: Thu, 9 May 2013 15:09:28 +1000 [thread overview]
Message-ID: <20130509150928.51689192@notabene.brown> (raw)
In-Reply-To: <CALzQTgJZ0t018RAYvymP7=Po6-2N6RdiP=qgdojnMri_4mKzaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 7660 bytes --]
On Tue, 7 May 2013 00:35:10 +0100 Ricky <rickyorbixx@gmail.com> wrote:
> Hello everybody,
>
> First time posting to this list, so please forgive any oversights with
> etiquette and missing information and such.
>
> I've not long recovered a Raid-5 array compromising of 4 disks with 2
> failing (not failed) disks, with a 1-by-1 swap-out of new matching
> disks. I did this with a live CD and the data was totally fine,
> mountable, no issues at all.
>
> Then I go to boot it back up, and kernel output shows that only 2 of the
> 4 disks could be brought up and the raid could naturally not be brought
> online, resulting in obvious failure. I panic, go back to the live CD,
> but nope, the raid is totally fine according to all the output.
>
> I spoke to a friendly person on freenode's ##linux who suggested
> checking if all disks including the new ones were using the 0.9
> superblock that my older disks were, I jumped the gun a bit and decided
> to upgrade them all to 1.0, only to find the kernel of the system on
> disk did not have a version of md that supports that new superblock, so
> I downgraded it. I performed this by offlining the array and recreating
> it based on the output of --detail but specifically passing the
> superblock parameter, as per your Wiki instructions, still no good
> however. Didn't mess up the recreation as the partition still totally
> accessible via the live CD.
>
> It's at this point that I'm stuck, I've no idea what to do next and hope
> you can advise. Details below:
>
> System: CentOS 5.9, kernel 2.6.34.6
You probably need to find someone who knows something about the boot sequence
of Centos.
Maybe you need to create a new initrd with a new mdadm.conf in it. Or maybe
you just need to install grub onto the mbr or something.
NeilBrown
>
> mdadm --examine /dev/sd*2
> /dev/sda2:
> Magic : a92b4efc
> Version : 0.90.00
> UUID : 06dc023e:47dbfdaa:a4d2adc2:26fd5302 (local to host
> localhost)
> Creation Time : Mon May 6 23:45:15 2013
> Raid Level : raid5
> Used Dev Size : 1462512576 (1394.76 GiB 1497.61 GB)
> Array Size : 4387537728 (4184.28 GiB 4492.84 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
>
> Update Time : Mon May 6 23:47:24 2013
> State : clean
> Active Devices : 4
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
> Checksum : bdf0c5f1 - correct
> Events : 1
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Number Major Minor RaidDevice State
> this 0 8 2 0 active sync /dev/sda2
>
> 0 0 8 2 0 active sync /dev/sda2
> 1 1 8 18 1 active sync /dev/sdb2
> 2 2 8 34 2 active sync /dev/sdc2
> 3 3 8 50 3 active sync /dev/sdd2
> /dev/sdb2:
> Magic : a92b4efc
> Version : 0.90.00
> UUID : 06dc023e:47dbfdaa:a4d2adc2:26fd5302 (local to host
> localhost)
> Creation Time : Mon May 6 23:45:15 2013
> Raid Level : raid5
> Used Dev Size : 1462512576 (1394.76 GiB 1497.61 GB)
> Array Size : 4387537728 (4184.28 GiB 4492.84 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
>
> Update Time : Mon May 6 23:47:24 2013
> State : clean
> Active Devices : 4
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
> Checksum : bdf0c603 - correct
> Events : 1
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Number Major Minor RaidDevice State
> this 1 8 18 1 active sync /dev/sdb2
>
> 0 0 8 2 0 active sync /dev/sda2
> 1 1 8 18 1 active sync /dev/sdb2
> 2 2 8 34 2 active sync /dev/sdc2
> 3 3 8 50 3 active sync /dev/sdd2
> /dev/sdc2:
> Magic : a92b4efc
> Version : 0.90.00
> UUID : 06dc023e:47dbfdaa:a4d2adc2:26fd5302 (local to host
> localhost)
> Creation Time : Mon May 6 23:45:15 2013
> Raid Level : raid5
> Used Dev Size : 1462512576 (1394.76 GiB 1497.61 GB)
> Array Size : 4387537728 (4184.28 GiB 4492.84 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
>
> Update Time : Mon May 6 23:47:24 2013
> State : clean
> Active Devices : 4
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
> Checksum : bdf0c615 - correct
> Events : 1
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Number Major Minor RaidDevice State
> this 2 8 34 2 active sync /dev/sdc2
>
> 0 0 8 2 0 active sync /dev/sda2
> 1 1 8 18 1 active sync /dev/sdb2
> 2 2 8 34 2 active sync /dev/sdc2
> 3 3 8 50 3 active sync /dev/sdd2
> /dev/sdd2:
> Magic : a92b4efc
> Version : 0.90.00
> UUID : 06dc023e:47dbfdaa:a4d2adc2:26fd5302 (local to host
> localhost)
> Creation Time : Mon May 6 23:45:15 2013
> Raid Level : raid5
> Used Dev Size : 1462512576 (1394.76 GiB 1497.61 GB)
> Array Size : 4387537728 (4184.28 GiB 4492.84 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
>
> Update Time : Mon May 6 23:47:24 2013
> State : clean
> Active Devices : 4
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
> Checksum : bdf0c627 - correct
> Events : 1
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Number Major Minor RaidDevice State
> this 3 8 50 3 active sync /dev/sdd2
>
> 0 0 8 2 0 active sync /dev/sda2
> 1 1 8 18 1 active sync /dev/sdb2
> 2 2 8 34 2 active sync /dev/sdc2
> 3 3 8 50 3 active sync /dev/sdd2
>
> mdadm --detail /dev/md0
> /dev/md0:
> Version : 0.90
> Creation Time : Mon May 6 23:45:15 2013
> Raid Level : raid5
> Array Size : 4387537728 (4184.28 GiB 4492.84 GB)
> Used Dev Size : 1462512576 (1394.76 GiB 1497.61 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
> Persistence : Superblock is persistent
>
> Update Time : Mon May 6 23:47:24 2013
> State : clean
> Active Devices : 4
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> UUID : 06dc023e:47dbfdaa:a4d2adc2:26fd5302 (local to host
> localhost)
> Events : 0.1
>
> Number Major Minor RaidDevice State
> 0 8 2 0 active sync /dev/sda2
> 1 8 18 1 active sync /dev/sdb2
> 2 8 34 2 active sync /dev/sdc2
> 3 8 50 3 active sync /dev/sdd2
>
> Many thanks in advance for any advice you have,
> Ricky Burgin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-05-09 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 23:35 Successfully recovered Raid5 no longer boots Ricky
2013-05-09 5:09 ` NeilBrown [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-06 22:21 Ricky Burgin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130509150928.51689192@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=rickyorbixx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).