January 23, 201016 yr Hi guys, See the attached syslog. essentially it appears that the drives reset their link continually. I've never had this problem before using 4.5 beta 6. my windows box can navigate through the directory structure but if you try and use a file you get a "server execution failure" . Restarting the unraid box solves the problem until it happens again later (5 -6 hours usually). Could this be due to the unraid MB wanting to put drives to sleep? any help appreciated.
March 10, 201016 yr Sorry for these very late comments, perhaps too late to be of help. I don't see any spinning down in your syslog, so I assume you have disabled spin down? So that is not involved here. There is one drive (Disk 4, sdd) that is causing almost all of the drive exceptions and resets, the first Seagate connected to the first motherboard SATA port. The errors are consistent (SATA link errors, PHYRdyChg and DevExch) but documentation on them is not particularly helpful (see the bottom of Libata error messages). To me, it almost looks like a loose cable to Disk 4, or a loose backplane connection to the drive, but could definitely be bad power to the drive. While none of the errors in the syslog are really serious, the performance of Disk 4 was hit pretty badly, because it stepped the mode all the way down to UDMA/33, which will result in about a third of the expected speed of access to this drive. Worth fixing ... I would first make sure all connections are rock solid, then if still no improvement, consider upgrading the power supply. About a half hour after the last error on Disk 4 in this syslog, there was a single timeout on Disk 3, but no specific error reported. Then about 4.5 hours later, there was a single timeout on Disk 2, again no specific error. Neither caused any performance loss. A timeout just means a response was expected from the drive, but was not received within a reasonable period (eg. within 5 seconds). It's possible that this too is related to power issues. The "server execution failure" error could possibly also be related to insufficient power, if it is occurring with an increased need for power to a drive. Another possibility, especially if you are seeing this after hours of use, is a heat issue somewhere. First make sure the drive temps are reasonable, well under 50 degrees. Then check board components (CPU, north bridge chipsets, etc) for overheating. The error message itself is strange to me, and I wonder who is reporting it. It would be useful to know who or what is actually reporting those specific words of "server execution failure".
March 12, 201016 yr Author Thanks Robj Eventually turned out to be 2 drives getting very flaky. Replaced the drives and all problems went away. Havent had much luck with drives lately but them the breaks. thx for the response, I'm getting better at diagnosis after all these "challenges". Paulk
Archived
This topic is now archived and is closed to further replies.