emmcee Posted February 3, 2018 Share Posted February 3, 2018 (edited) I've had a red X pop up on one of my disks. I've been able to move the data to other drives with unBalance and I have replaced the SATA cable. Can someone take a look at my diagnostics and let me know if it's OK to rebuild or shoud I just replace it? If it needs to be relaced, it is possible to remove it competley (it's currently emty), Edited February 3, 2018 by emmcee Quote Link to comment
emmcee Posted February 3, 2018 Author Share Posted February 3, 2018 Of course, it would help if I posted the diagnostics... tower-diagnostics-20180203-1612.zip Quote Link to comment
Frank1940 Posted February 3, 2018 Share Posted February 3, 2018 Give us the last four digits of the drive's serial number.... Quote Link to comment
emmcee Posted February 3, 2018 Author Share Posted February 3, 2018 1 hour ago, Frank1940 said: Give us the last four digits of the drive's serial number.... 1012 Quote Link to comment
JorgeB Posted February 3, 2018 Share Posted February 3, 2018 These are a very bad sign on WD disks: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 2843 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 12 I recommend replacing it 1 Quote Link to comment
emmcee Posted February 3, 2018 Author Share Posted February 3, 2018 OK - good to know. Is it possibe to remove a failing drive completley without relpacing it? I found this article on the wiki which explains how to remove a drive, but it says: Quote This method can only be used if it's a good drive that is completely empty, is mounted in the array, and can be completely cleared. Quote Link to comment
JorgeB Posted February 3, 2018 Share Posted February 3, 2018 Disks in that state tend to error mostly on reads, you should be able to clear it and then remove, but if there are write errors you'll need to use the other method, remove the disk, do a new config and resync parity. Quote Link to comment
emmcee Posted February 3, 2018 Author Share Posted February 3, 2018 (edited) Great. Thanks for the help. I'll run a parity check overnight and attempt it tomorrow. Edited February 3, 2018 by emmcee Quote Link to comment
JorgeB Posted February 3, 2018 Share Posted February 3, 2018 4 minutes ago, emmcee said: I'll run a parity check overnight and attempt it tomorrow. Make sure it's a non correcting check in case there are read errors on that disk, or any other for that matter. Quote Link to comment
trurl Posted February 3, 2018 Share Posted February 3, 2018 4 hours ago, emmcee said: I've had a red X pop up on one of my disks. I've been able to move the data to other drives Just thought I would mention that this is not really the best first action when you have a disabled disk. Moving to other disks in the array is doing a lot of writes to an unprotected array. And just rebuilding would have saved your files anyway. Quote Link to comment
emmcee Posted February 4, 2018 Author Share Posted February 4, 2018 15 hours ago, trurl said: Just thought I would mention that this is not really the best first action when you have a disabled disk. Moving to other disks in the array is doing a lot of writes to an unprotected array. And just rebuilding would have saved your files anyway. It's reallly obvious now that you said it! Anyway, luckily for me parity check has completed without error and I've kicked off the clear script. Thanks all for the help! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.