raid 5 out of sync and I think I just hosed myself
As per the subject, I think I just hosed myself. I'm well aware of what I did wrong. I'm just hoping there is a way to recover.
I had a raid 5 that was slightly out of sync and wouldn't come back online when I reassembled it. I tried the --force option with assemble but forgot to put my /dev/md2 device as the first device so I hosed my superblock on the first device. This is what I did Code:
mdadm --assemble --force /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 Code:
mdadm --assemble --force /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 missing /dev/sdc1 To give you an idea of how out of sync things were before I hosed it, here's the abbreviated output of mdadm -E. I have the full output as well if that helps. Code:
[root@heisenberg]# mdadm -E /dev/sdc1 |grep Events |
Turns out that I didn't hose myself as badly as I thought. I just blew away the /dev/sdc1 and /dev/sdd1 device nodes. A simple reboot fixed my problem. I'm back at the point where I have 5 drives that are slightly out of sync.
I'm trying to determine if I should continue down the path I was going which as to force an assemble or should I look at another path? |
Quote:
Code:
mdadm -assemble --force /dev/md2 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 |
All times are GMT -5. The time now is 08:32 AM. |