May 17, 201214 yr I recently upgraded my server to a different motherboard and CPU, in order to be able to run Plex Media Server. I ran that for a few days with no issues, then upgraded to 5.0 rc2, and then rc3. With rc3, I've started to have some serious issues. I'm not sure which are hardware related and which are software. The major issue right now is that two disks are being red-balled. One (disk8) appears to be a regular red-ball, although a cursory inspection of the syslog doesn't show that. The other (disk2) is shown as "wrong", and appears to be reported as a 2TB drive, when it's clearly a 1.5TB drive. The syslog shows all kinds of issues for this drive, and I'm feeling totally lost. I need to get this back to at least only one bad drive, so I can rebuild the array. syslog-2.txt
May 17, 201214 yr Author I've just noticed that if I unassign disk2, then it shows up properly as a 1.5TB drive. If I assign it again, it shows up as 2TB. I think the drive is hosed. I have unassigned and reassigned disk8, which put the array in an initial configuration mode. I don't want to start it and force it to trust the parity until I get some direction. I don't see anything relating to this drive in the syslog. It mostly seems to pertain to disk2 (sde). I'm also noticing what look to be memory errors at the top of the syslog.
May 18, 201214 yr Author I decided to power down the system and see if it came back any better. I replaced the SATA cable on Disk2. I don't know if that changed anything in and of itself, but Disk2 is now being properly recognized. Disk8 is still red-balled, so it must have failed a write, although I can't find it in the syslog. I ran through two passes of MemTest with no errors. syslog-3.txt
Archived
This topic is now archived and is closed to further replies.