My Mdadm Raid5 array of 4 drives failed during synchronization after replacement of one failed drive. It threw me to RamFS where after a while I couldn't mount the array any more (don't know what I did...
i had an mdadm raid6 array with 13x1TB drives. Within 10 minutes 3 of these drives fell out of the array... we assume bad cable to the controller card and replaced, however now we need to get the drives back into a working array.
because md0 was marked as failed we removed the mdadm array and made a new md0 with the original 13 drives. 1 failed again during rebuild so we now have a degraded md0.
I have a new BackBlaze Pod (BackBlaze Pod 2.0).
It has 45 3TB drives and they when I first set it up they were labeled /dev/sda through /dev/sdz and /dev/sdaa through /dev/sdas.
I used mdadm to setup three really big 15 drive RAID6 arrays.
However, since first setup a few weeks ago I had a couple of the hard drives fail on me.
Hi All, I'm having a bit of a time with MDADM. Basically I have a RAID6 system setup w/ 10 hard drives (1.5GB). Last night I had a failed drive and i accidentally failed out the wrong drive trying to fix it. Right now I can get the array to assemble successfully but I cant read anything off of md0, it can't mount either.
My older 2 CPU server (32-bit LV Xeon, centos 5) drives a raid6 array.
After reinstallation of my OS, I decide to manually assemble a RAID6 array.
# mdadm --assemble --auto=yes --scan=auto /dev/md0
I don't exactly remember a message but program mdadm return a resizing raid array.
$ more /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sdc1[0] sdf17 sdh1[6] sdd1[5] sdg1[4] sda1[3] sdi1[2] sdb1[1]
4883799680 blocks level 6, 64k chunk, algor
I have a 6x2TB software RAID array configured as RAID6 (two redundant drives, 8GB of usable space) running in Fedora 17. After the power issues in the NE last week, the system booted up to some problems with the array and maybe some other issues since it forced into maintenance mode.
I have a 4x 2tb raid 5 mdadm array which I had begun to grow onto a 5th disk.
~# mdadm --add /dev/md1 /dev/sdb
~# mdadm --grow /dev/md1 --raid-devices=5
midway through the grow I recieved this in an email;
A Fail event had been detected on md device /dev/md/fubox:1.
It could be related to component device /dev/sdf.
Faithfully yours, etc.
P.S.
Hi
No longer able to access my raid, not sure what caused this, but im not able to start it either, help!
mdadm -E /dev/md0
mdadm: no md superblock detected on /dev/md0
mdadm -D /dev/md0
mdadm: md device /dev/md0 does not appear to be active
cat /proc/mdstat shows
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0: inactive sdb1[2](S) sdc1[1](S)
Email this page
