Timeline for Computer crashed, raid array in trouble
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2018 at 19:42 | comment | added | Azelphur | @cdhowie I have a feeling that was down to one of two things: A) One of the drives was technically part of the array, and up, but had an incorrect event count (it was behind all the other drives) B) I had a rather bad failure in the past, and had to rebuild the array with --assume-clean to get it back. This changed the arrays UUID, however, I did not update the UUID in /etc/mdadm.conf. | |
| Sep 25, 2018 at 16:20 | comment | added | cdhowie | Glad to hear. It's odd to me that the array didn't start degraded when the disk was missing, though... | |
| Sep 25, 2018 at 13:51 | comment | added | Azelphur | Hi @cdhowie - I ended up resolving this. sdg was broken (Shown in SMART results). I removed it and added a new drive. The array started, rebuilt, and now everything is working. | |
| Sep 23, 2018 at 19:32 | comment | added | cdhowie | Have you tried actually starting the array? It's listed as inactive. | |
| Jul 24, 2018 at 15:09 | comment | added | Tony Stewart EE75 | Run Spinrite on each | |
| Jul 24, 2018 at 14:19 | history | edited | Deltik | CC BY-SA 4.0 |
Embedded the most relevant command outputs
|
| Jul 24, 2018 at 14:15 | history | asked | Azelphur | CC BY-SA 4.0 |