February 14, 201313 yr I have 2 Seagate 2 TB drives on a ARC1200 controller configured as a 3 TB RAID0 volume for parity and a 500 GB RAID1 volume for cache. This has been working without a problem for 5 months first in baremetal unraid, later as an ESXi VM. 2 weeks ago in the ESXi VM the parity volume/disk red-balled. I un-assigned the parity volume and restarted the server. After rebooting I went in the ARC1200s BIOS and checked volumes and the disks SMART status. All seemed ok. After the server finished booting, this time baremetal unraid, I assigned the parity volume/disk again. Parity was rebuild at proper speed and without further problems. Today the same happened again, parity red-balled. I repeated all steps described before. And currently parity is rebuilding again. I noticed one thing: the fan in front of the two disk wasn't working. Can too high disk temperature be the cause of this? How can I troubleshoot the issue?
February 14, 201313 yr Can too high disk temperature be the cause of this? How can I troubleshoot the issue? Vibration and High or changing temperatures can cause connector creep. I've seen it many times. Not saying this is your problem, but that there could be an issue with the cables and the connection. Too hot a drive could cause it to go offline also. Although I've not seen this occur. It would be in the smart logs. There could be a lifetime value on the drive temperature.
February 14, 201313 yr Author Can too high disk temperature be the cause of this? How can I troubleshoot the issue? Vibration and High or changing temperatures can cause connector creep. I've seen it many times. Not saying this is your problem, but that there could be an issue with the cables and the connection. Too hot a drive could cause it to go offline also. Although I've not seen this occur. It would be in the smart logs. There could be a lifetime value on the drive temperature. Thanks Weebo for the quick response. The first what I did was mounting a new fan and check airflow. The two volumesare still intact and parity is currently build. SABNZB is still running of the cache volume. Let's see how the parity check goes tomorrow.
Archived
This topic is now archived and is closed to further replies.