May 4, 200917 yr Hi, I'm running Unraid Pro 4.5b4, and yesterday one of my drives (Seagate 1.5TB) was showing that it was disabled, with 93 errors. I purchased a new one today, and installed it and started the rebuild. Now, a few hours later, it is showing 288 errors, and has been disabled. I have attached a syslog (Sorry.. its Zipped because Maximum upload size here is only 128kb). I don't really believe that I have had two drive failures in 24hrs.. I don't want to lose the data. Can anyone see anything in the syslog that might explain what is going on. Thanks Daniel Parker
May 4, 200917 yr I did not look at the syslog but, did you check the cable ? Sometimes, the disk seems to be bad but it is in fact the sata or ide cable that is the cause. It also could come from a bad UPS.
May 4, 200917 yr Whenever you have a hard disk failure / problem, it is a good idea to get a smart report. Follow the "troubleshooting" link in my sig for instructions. Post the results on your new (and old if it is still available) drives and I should be able to give you a good idea of whether it is a cabling or actual drive problem.
May 4, 200917 yr I too suspected a cabling issue, but that usually results in a long series of communication related errors. In your case, there is a single hard error at 18:34:06 that looks like a drive change. I would suspect this is in a backplane, that is loose, or a severe vibration momentarily caused it to become loose? It was almost immediately disabled ("kernel: ata14.00: disabled"), and that is fatal. All of the subsequent errors are because the drive has been disabled. Although the kernel tries valiantly to recover a disk here, which produces more errors, it is not successful. It does show that the newest kernel seems to have new methods of drive recovery, which is hopeful for the future, although I am not sure you would want to trust the results, when in the middle of a drive rebuild. Very good point above, always need SMART reports for any troubled drive. Only too often, it turns out to be a cabling or connection or even a controller issue, possibly even a firmware related issue. In your case, I suspect that both drives are fine. You might want to re-insert the previous drive, if nothing else, for testing.
May 4, 200917 yr Another possibility (to a loose or poorly seated backplane) is a loose cable connection. Check both ends of the SATA data cable, as well as the power cable, including any splitters in the path.
Archived
This topic is now archived and is closed to further replies.