Drazzilb Posted January 10, 2016 Share Posted January 10, 2016 Twice now my array has come off line due to a red x on one of my drives. I'm wondering if it is going bad (sadly its not that old). Attached is a copy of it's smart report. I don't know what I'm looking at on it to see if something is going wrong. Please help. oh if this isn't the right place for this. I'm very sorry. WDC_WD20EZRX-00DC0B0_WD-WMC301624101-20160110-1209.txt Link to comment
BRiT Posted January 10, 2016 Share Posted January 10, 2016 Do you have that drive operating in a freezer? It seems way too cold. It's not even registering 60 F (16 C). There is such a thing as having drives too cold to operate. There's an old discussion on these forums somewhere talking about ideal operating ranges. However, you should upload at least the syslog (if not diagnostics) to see what exactly the error reported was. From your drive's smart report: 194 Temperature_Celsius 0x0022 131 108 000 Old_age Always - 16 Link to comment
Drazzilb Posted January 10, 2016 Author Share Posted January 10, 2016 Do you have that drive operating in a freezer? LOL. I don't run my heater in my house so yeah it is cold today. However, this isn't the first time that this has happened. The other day was normal temp. (approx 60 degrees F, for outside temp) I've attached the complete diagnostics *.zip file tower-diagnostics-20160110-1333.zip Link to comment
Squid Posted January 10, 2016 Share Posted January 10, 2016 Since the diagnostics was done after a reset, there's nothing in there that really looks out of place. The smart for the drive looks good. Best guess, without any diagnostics showing the drive when it failed would be loose power / cable. Link to comment
Drazzilb Posted January 10, 2016 Author Share Posted January 10, 2016 Rodger that. I figure'd anything that was useful was removed after the reset. If or when it happens again. I'll repost with a new diagnostic log. thank you very much! Link to comment
BRiT Posted January 10, 2016 Share Posted January 10, 2016 Either I'm missing something, but I'm not seeing anything that is showing up to cause that drive to be marked with a Red X, at least nothing from the current syslog which seems to be a little over 70 minutes after a server restart/reboot. The only one that might be troublesome, but the value is so low that I dont think it would be an issue is a different drive. The WD WMC1T2985954 (sdc / disk3) drive has a UDMA CRC Error Count raw value of 1, but every other attribute looks perfect. 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 1 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.