One of my servers is temperamental.  Sometimes the first 8 disks aren't recognised at reboot, a hard boot usually fixes the problem, sometimes I get what appears to be disk cabling issues, but I'm fairly sure the cables are ok, they've been swapped around and some replaced (the first 8 disks are on a separate controller card).

 

I'm upgrading a disk (disk1) to a larger one at the moment and Parity 2 just dropped out, there are the usual sporadic errors I see in the logfile, but now it's saying disk29 write error as it dropped out Parity 2.  AFAIK, it shouldn't be writing to Parity 2 and in any event, I only have 17 data and 2 parity drives in this server

 

Does anyone have any idea what's wrong?

 

Many thanks in anticipation

Bruce

6.20 rc5, Dynamix cache directories, Dynamix webGui, nerd tools & PreClear disks, all latest versions

No SMART reports, but I'm sure the disks are ok

tower2-syslog-20160907-0834.zip

IMO not really a good idea to be doing disk upgrades when you know there's a problem.

 

You're getting lots of CRC errors on disk9, these are usually from a bad cable SATA cable, but it can also be a bad enclosure/controller port.

 

Parity2 is always disk29, and it had a read error, unrelated to your CRC problems, it does look like a disk error, after that happens unRAID calculates what should be there by using all the other disks and attempts to write that data, if it fails, like it did, the disk is disabled.

This system has always had the same error that appears as a bad SATA cable, even from when it was new, but it isn't a cable issue.  It normally resets and runs just fine.

 

It completed the disk upgrade but failed on rebuilding Parity 2 onto the same disk, so it is just possible that Parity 2 disk is faulty, ii've put it in another server and i'm preclearing it now, so we'll see.

 

I would like to tie down this isue, I'm worried if it's a mobo issue I just can't face all the work in changing it.

What is the exact model of your power supply?

 

If you continue to have problems, post a diagnostic, not a syslog. Diagnostic includes syslog but also a lot of other things such as SMART of all your disks. With V6 you should always post a diagnostic instead of a syslog.

Until I pull it out of it's cupboard, I can't see what the power supply is, but the system was built be greenleaf so it should be adequate. 

 

It turned out Parity2 is faulty (WD 6TB Red), in warranty so going back, it's currently rebuidig Parity 2 onto a spare, should finish in an hour or so.

 

It's so long since I swapped cables, I can't remember what I did, so I'll go through the process again and try and rule out the cable and disk enclosure.

attached are the diagnostics.  99% of the time it performs flawessly, it usually only fails on a warm reboot when either 1 or 8 drives don't appear.

tower2-diagnostics-20160908-0655.zip