jaybee Posted December 23, 2011 Posted December 23, 2011 I am still getting my unraid server setup. Taking a while due to lack of time. I had previously precleared 3 drives at once (2 x Hitachis and 1 x Samsung) a few times, and left the server running for a few days in a row with no stability issues. I havenot built an array, formatted drives or done anything yet. Just preclearing drives and configuring and preparing. I have just added a brand new Seagate drive to the server. I ran a preclear on all 4 drives as I thought I might as well whilst the preclear for the new drive was running. I noticed that I got email updates for all 3 drives except the new one. The emails I got showed progress and all 3 drives (except new one) got to 75% pre read state but no further emails. I realised that about 6 hours into the preclear the server had become unresponsive. I could not telnet to it or get to the http menu pages. What I find most frustrating, is that I can't see any logs for this at all. I have to physically power off and back on the server to get it back up, and all i get in syslog is obviously a brand new syslog. How can I get the logs for the time of when the preclear failed? I have checked in the preclear reports folder but I do not see any new reports. Is this because it will only write to there upon completion of a preclear in full and not show any failures? If I were to hook up a monitor to the server and leave that connected whilst running preclear from console, would I get atleast a message on the screen to aid troubleshooting atleast or would it just hang and not help much? Thinking it was the new drive, I decided to run a preclear on JUST THAT DRIVE which is still running now. I will update on progress. As for now I did manage to get smart history installed and have noticed a log it seems to complain about on this new drive. Could this be a big clue as to the problem? I searched and this error below can indicate sometimes that there is a bad sata cable or power connection to the drive? EDIT: The preclear failed when ran on JUST the new drive as well again about 6 hours in. It got as far as the first email saying it was going to zero the drive then nothing more. EDIT2: Now running a preclear on a drive that has successfully precleared before to see if that preclears ok again. I guess I could test the cable theory quite easily to see if the issue follows the cable to another drive.
jaybee Posted December 24, 2011 Author Posted December 24, 2011 Update, managed to run a full preclear to PASS state on a different disk over 25 hour period. So it appears to be definitely to do with the new disk I have added. I am going to change the SATA cable today and retest. If the same I will change the power cable.
jaybee Posted December 25, 2011 Author Posted December 25, 2011 Just to update this thread. I was correct with my first assesement in that it could be the cable. I was not aware of SATA cables being a particular SATA standard, like SATA1, SATA2 etc. I thought a SATA cable was a SATA cable. However, the one I was using was the thinnest and narrowist one I have ever personally come accross. I'm not sure how it can only partially work to be honest but it did. Something about that cable was not right. I swapped the cable out and kept everything the same - even the port on the mortherboard - and the first attempt at preclear passed in 24 hours with no errors. Tags for future ref and searching: *ERROR* - UDMA_CRC_Error_Count it is now 13897 (error threshold is 75)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.