I've searched around all over the internet, and I may have made the mistake of following advice one after another, which could possibly lead to my data loss...
Heres the story:
A few days ago, my RAID5 array of 3x1TB drives went down due to a power outtage. Bootup was stalled due to a failed mounting of my array. CTRL-D to bootup, and take a look at what I'm dealing with.
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 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...
Improbably I had two drives fail in the same Raid5 array within 2 weeks of one another. Which means the array is dead. Yes yes hot spares not being lazy about replacing the failed drive I know. But let's move past that.
The data is somewhat backed up and not of critical importance, so I am not particularly panicked by this.
Came home from work to a crashed RAID5 array in my 10.04 box.
I went into Disk Utility and stopped the array, and when I tried to restart the array I received this error:
Error assembling array: mdadm exited with exit code 1: mdadm: metadata format 00.90 unknown, ignored.
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: /dev/sdc1 has no superblock - assembly aborted
OK, I think I am up and running again without any data loss.With the help of this post, the thread it is referencing and my newborn daughter on my chest for good luck I did the following:sudo mdadm --zero-superblock /dev/sdd1 /dev/sdb1 /dev/sdc1 /dev/sde1I then recreated the array:sudo mdadm --create -v -l 5 -n 4 --assume-clean /dev/md0 /dev/sdd1 /dev/sdb1 /dev/sdc1 /dev/sde1
mdadm: layout defaul
After a restart which stalled, I did a hard reboot and now mdadm can't see the RAID 6 array anymore, LVM can't find the volume which was on that raid array.
Hello all and thanks for reading.
up until yesterday I had a RAID5 array with 5 devices.
Today I added another 2TB devices (dame size as the others), first i formattted it right then added it to the raid (it showed up as a spare) then I grew the array.
Question 1 - Before you answer with "it just takes the smaller disk", hear me out quick. My 3TB WD Reds come out to be 3001 GB in size. Let's say I set up a mirror via mdadm for sdb1 and sdc1 which span 100% of the drive. But suddenly, one of the drives fail. The replacement is a 3TB, weighing in at 3000 GB.
Email this page
