Software :: MD Raid5 Kicked Out Two Members And Won't Start After Reboot

Suddenly I noticed that all my file system had gone into read-only mode. My first thought was that the Sata data cable had got loose for one of the drives, but that wasn't it. All cables were connected correctly. So I booted up again, but I only came to a rescue mode terminal.

I have four software MD raid volumes:

Code:

Running mdadm -D on the volumes told me that the sdc drive had been kicked out from both md0 and md1. However, md3 had kicked out two drives, so I couldn't get any information from mdadm -D on that. For md0 and md1 I could just add the kicked-out partitions back into the volume, but for md3 I don't even know which partitions got kicked out...

Here are some outputs:

Before I rebooted the first time I saved the 200 last rows of dmesg to a memory stick. Here they are:

Code:

Trying to restart the md3 volume in the rescue mode terminal:

Commands:

Code:

Output:

Code:

The "Array State" row seems interesting. I guess that AAAA means all four drives are OK. But then why does the array state differ between the members?

Does anyone know how to figure out which two members that got kicked out? And how do I get them back in (assuming that they're OK)?