wgstarks Posted January 6, 2016 Share Posted January 6, 2016 Ive been getting notifications most of the day. Started some time last night. Not sure what to do about this? 9:18PM Event: unRAID Disk 1 SMART health [187] Subject: Warning [bRUNNHILDE] - reported uncorrect is 27 Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: warning 11:24PM Event: unRAID Disk 1 SMART health [187] Subject: Warning [bRUNNHILDE] - reported uncorrect is 28 Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: warning 4:55AM Event: unRAID Disk 1 SMART health [187] Subject: Warning [bRUNNHILDE] - reported uncorrect is 31 Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: warning 5:46AM Event: unRAID Disk 1 SMART health [187] Subject: Warning [bRUNNHILDE] - reported uncorrect is 32 Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: warning 12:03PM Event: unRAID Disk 1 SMART health [187] Subject: Warning [bRUNNHILDE] - reported uncorrect is 33 Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: warning 6:01PM Event: unRAID Disk 1 SMART health [197] Subject: Warning [bRUNNHILDE] - current pending sector is 65528 Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: warning 6:01PM Event: unRAID Disk 1 SMART health [198] Subject: Warning [bRUNNHILDE] - offline uncorrectable is 65528 Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: warning 6:04PM Event: unRAID Disk 1 SMART message [198] Subject: Notice [bRUNNHILDE] - offline uncorrectable returned to normal value Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: normal 6:04PM Event: unRAID Disk 1 SMART message [197] Subject: Notice [bRUNNHILDE] - current pending sector returned to normal value Description: ST3000DM001-9YN166_Z1F0KHH2 (sdi) Importance: normal I've attached a smart report. brunnhilde-smart-20160105-1919.zip Link to comment
HellDiverUK Posted January 6, 2016 Share Posted January 6, 2016 It's a ST3000DM001. Replace it. Now. Link to comment
3605481mah Posted January 6, 2016 Share Posted January 6, 2016 It's a ST3000DM001. Replace it. Now. Totally agree. Link to comment
wgstarks Posted January 6, 2016 Author Share Posted January 6, 2016 It's a ST3000DM001. Replace it. Now. What is this based on? Link to comment
HellDiverUK Posted January 6, 2016 Share Posted January 6, 2016 It's a ST3000DM001. Replace it. Now. What is this based on? They're the worst drives ever made. Source: everyone. Seriously, Google "st3000dm001 failure". Link to comment
JorgeB Posted January 6, 2016 Share Posted January 6, 2016 Reported uncorrected is one the bad ones, I would replace it asap. Link to comment
wgstarks Posted January 6, 2016 Author Share Posted January 6, 2016 Thanks all for the replies. There's not much data on this drive so I'll probably just move it to another drive in the share with unbalance. Not quite sure how to remove a drive if I'm not going to replace it right away? Should I stop the array and then do a "New Configuration" without this drive? Link to comment
trurl Posted January 6, 2016 Share Posted January 6, 2016 Thanks all for the replies. There's not much data on this drive so I'll probably just move it to another drive in the share with unbalance. Not quite sure how to remove a drive if I'm not going to replace it right away? Should I stop the array and then do a "New Configuration" without this drive? Yes, then let it rebuild parity. Link to comment
wgstarks Posted January 6, 2016 Author Share Posted January 6, 2016 Thanks all for the replies. There's not much data on this drive so I'll probably just move it to another drive in the share with unbalance. Not quite sure how to remove a drive if I'm not going to replace it right away? Should I stop the array and then do a "New Configuration" without this drive? Yes, then let it rebuild parity. Thanks. And then I'll have to powerdown to remove the drive from the cage, right? Pretty sure hot swapping isn't supported. Link to comment
JonathanM Posted January 6, 2016 Share Posted January 6, 2016 then I'll have to powerdown to remove the drive from the cage, right? Pretty sure hot swapping isn't supported. Hot swapping depends on your hardware, not unraid. If your controller and cage support it, unraid is fine with it. Just don't try to hot swap an array drive with the array started, as that is not supported. Swapping with the array stopped, or messing with a drive not managed by unraid works fine. My cages have power buttons, and I swap drives for preclear or data transfer using unassigned devices plugin with no issues, all with the array started. I wouldn't hot swap without the ability to spin down the drive or power it off first, as yanking a spinning drive out of a cage could be BAD. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.