My system has crashed a couple of times, each time the two drives have
dropped off of the RAID.
Previously I simply did the following, which would take all night:
mdadm -a --re-add /dev/md2 /dev/sde3
mdadm -a --re-add /dev/md2 /dev/sdf3
mdadm -a --re-add /dev/md3 /dev/sde5
mdadm -a --re-add
Hello.
I have a degraded 4 disk raid 5 array consisting of:
/dev/sdd3
/dev/sdc3
/dev/sdb3
/dev/sda3
Recently on boot the system crashed mid-boot for another unrelated (I
think) config issue. I then booted with a live cd and when I tried to
re-build /dev/md0, /dev/sdb3 came up as faulty. Upon
I apologize for being so verbose in my last post...it was late. My
problem again, in a more succinct form:
After a system crash during bootup, I attempted:
mdadm --add /dev/md0 /dev/sdb3
This caused the following:
Number Major Minor RaidDevice State
0 8 510
Thank you for the feedback Neil.
Although, your last comment did confuse me a little...run what in
parallel? Should I be running badblocks against the unassembled
components of the raid and then doing something like:
fsck -l /badblockfile_sda3.txt /dev/md0
fsck -l /badblockfile_sdb3.txt
