Ubuntu
mdadm package

mdadm with raid 5 crashed..

Asked by qsummon

I have running a raid 5 with 5x1 TB raids (mdmad) for 2 years with no issues (just general maintenance like, grow, replace drives, etc...)

Suddenly, yesterday the raid just crashed with 3 drives kicked out of the array.
Now I see these 3 drives in "removed" state from the raid
If I try to add or assemble any of these drives I see the message ""does not appear to be an md device"

If I try to examine the drives I see

mdadm -E /dev/sdc
mdadm: metadata format 00.90 unknown, ignored.
/dev/sdc:
Magic : a92b4efc
Version : 00.90.00
UUID : a8218870:64885bf0:e9110788:09b4438a
Creation Time : Sun Mar 15 03:49:03 2009
Raid Level : raid5
Used Dev Size : 976762368 (931.51 GiB 1000.20 GB)
Array Size : 3907049472 (3726.05 GiB 4000.82 GB)
Raid Devices : 5
Total Devices : 5
Preferred Minor : 0

Update Time : Sat Nov 20 12:22:15 2010
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 1
Spare Devices : 0
Checksum : 79b3e1a6 - correct
Events : 1715280

Layout : left-symmetric
Chunk Size : 512K

Number Major Minor RaidDevice State
this 2 8 32 2 active sync /dev/sdc

0 0 8 0 0 active sync /dev/sda
1 1 8 16 1 active sync /dev/sdb
2 2 8 32 2 active sync /dev/sdc
3 3 8 48 3 active sync /dev/sdd

so, the examine is seeing these drives, but I can put them back in the raid
Any advice? I'm pretty desperate here :) , want to recover the data
Thanks a lot

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu mdadm Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

You shouldn't have to "recover data". You should have a "backup"

Revision history for this message
qsummon (qsummon) said : 		#2

I have backups of the important data, just looking if there is a way to fix the raid.
Thanks actionparsnip, your comments is very helpful.... Just keep your mouth shut.

Revision history for this message
ilias (ilisepe1) said : 		#3

what happens if you "mdadm --examine" the rest of the /dev/sd?? members?
since you are using uuid, what's the output of blkid?
do you get anything from: mdadm --detail --scan --verbose /dev/md???
can you access your disks with "fdisk -l"?
do you see any errors in the /var/log/messages or dmesg?
what's your current status in /proc/mdstat?

what happens if you stop and then reassemble the md:
mdadm --stop /dev/md??
mdadm --assemble /dev/md1
cat /proc/mdstat

Can you help with this problem?

Provide an answer of your own, or ask qsummon for more information if necessary.

To post a message you must log in.