Hi,

 

I have been using unRAID 4.2.4  pro version for a while and keep adding more disks. Last Friday I add a new 650G disk to the system and move the original 500G parity disk to be my 5th data disk. Tonight, I have just found that there are disk write errors and the GUI show red button with no temp after ripping a DVD to the disk#5. It seems to me that the system is fine after the upgrade and I have copied a few movies from other disks to disk#5. I did noticed that the temp is a bit higher than before at around 50 while other disks are about 43-47. Please advise if this is just software problem or it is a hardware failure.

 

Thanks,

--Tom

As you might suspect, disk 5 has failed.  Yes, you can still read and write to it, but that is because of the RAID array software simulating writes, and reconstructing reads by using the contents of all your other disks.  There is no temperature because the disk cannot be read.

 

First and most important DO NOT USE THE RESTORE BUTTON.  You will lose any data that was on disk5 if you press it at this time.

 

Since you just moved disks around, it might just be a loose cable on disk5.  To verify, stop your array, power down, check for a loose data or power cable.  If you find one, you will need to  go through a few steps to get it back on-line as described here in the wiki http://lime-technology.com/wiki/index.php?title=UnRAID_Manual_-_FAQ#How_do_hard_drives_become_disabled.3F.

 

If the procedure does not get you back running, it is time to replace disk 5.  When you do, you must use the "Start" button to rebuild the contents of disk 5 onto it. (You will probably need to check the little checkbox below the start button to enable it)  Again, do not use the Restore button.  Pressing it with a failed disk will cause the unRAID array to forget the failed disk ever existed, and all of that disks data will be gone.

Joel,

 

Thanks. I just found the noise coming from the PC, so stop the array and shut down the PC. I will need to go to work, so will investigate any hardware faults once I get home today. Your reply gave me some guide line to follow. I will investigate once I get back home from work and keep you updated.

 

Thanks again.

--Tom

Hi,

 

I found the culprit after I open the PC. The problem is the SATA cable was too close to the cooling fan and the skin was damaged by the fan blades. I am glad that there was no fire inside the case when it was happening. I need to move all the SATA cable away from the cooling fan. I was happy about the cooling fan when I got the case, but now I have to watch out for that.

 

I followed the procedure to basically treat the drive as a replacement drive and now the drive is back to work now. I appreciate Joel's prompt reply.

 

--Tom

I found the culprit after I open the PC. The problem is the SATA cable was too close to the cooling fan and the skin was damaged by the fan blades. I am glad that there was no fire inside the case when it was happening.

 

Yikes!! 

 

Glad you found this & thanks again to Joe for the help.