gnollo Posted March 6, 2020 Share Posted March 6, 2020 I had the first pending sector alert yesterday afternoon, followed by a second shortly after. I also had a batch of read errors twice a couple of months ago from the same drive, but I dismissed it as a cable issue. This one looks serious. Time to replace to replace the drive? Smart report attached tower-smart-20200306-0922.zip Quote Link to comment
JorgeB Posted March 6, 2020 Share Posted March 6, 2020 45 minutes ago, gnollo said: Time to replace to replace the drive? I would, the pending sectors are real since it failed the SMART test, also these attributes look very bad: Quote ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 6424 200 Multi_Zone_Error_Rate ---R-- 001 001 000 - 629204 They should be zero, or at least very low, on a healthy WD drive. Quote Link to comment
gnollo Posted March 7, 2020 Author Share Posted March 7, 2020 OK, I bought a new 10TB drive to replace my 8TB parity, will replace parity first then use parity to replace the failing drive Quote Link to comment
Frank1940 Posted March 7, 2020 Share Posted March 7, 2020 I believe that this is the procedure that you will need to follow: https://wiki.unraid.net/The_parity_swap_procedure I have never done it so I think these are the latest instructions. (I would wait a few hours before and see if anyone else jumps in to comment differently.) 1 Quote Link to comment
trurl Posted March 7, 2020 Share Posted March 7, 2020 2 hours ago, gnollo said: OK, I bought a new 10TB drive to replace my 8TB parity, will replace parity first then use parity to replace the failing drive You don't want to rebuild parity with a bad data disk in the array. Do not replace parity first. 57 minutes ago, Frank1940 said: I believe that this is the procedure that you will need to follow: https://wiki.unraid.net/The_parity_swap_procedure I have never done it so I think these are the latest instructions. (I would wait a few hours before and see if anyone else jumps in to comment differently.) Yes, this is definitely what you should do. Do it all in the same process. Quote Link to comment
gnollo Posted March 7, 2020 Author Share Posted March 7, 2020 Interesting, didn't know you could do that. I will give that a try. I am running 6.7.0. Quote Link to comment
gnollo Posted March 9, 2020 Author Share Posted March 9, 2020 As the UI became unresponsive, I used the console to type REBOOT and upon restart, parity check started. Shall I let it take its course or cancel it? I have not started the parity swap process yet. I couldn't as I did not have access to the GUI Quote Link to comment
trurl Posted March 9, 2020 Share Posted March 9, 2020 Since it was an unclean shutdown parity check, it should be nocorrect. Might be useful to see if it thinks you have parity errors, though I'm not sure what the best course of action would be if it did. Do you correct parity when you know you have a bad data disk? On the other hand, it is possible the unclean shutdown would result in parity errors, especially if anything was writing to the array at the time. If there are parity errors, and they are real and not caused by problems reading that bad data disk, then relying on the parity for the later rebuild could be problematic. Any idea why the UI became unresponsive? I know there are a lot of threads on the forum where this seems to happen, but it is not the usual way for Unraid to work, and of course nobody bothers to post when things are going well. Has the parity check found any errors so far? Post a new diagnostic. Quote Link to comment
gnollo Posted March 9, 2020 Author Share Posted March 9, 2020 (edited) Total size:8 TB Elapsed time:8 hours, 52 minutes Current position:1.80 TB (22.4 %) Estimated speed:65.7 KB/sec Estimated finish:1083 days, 5 hours, 4 minutes Sync errors detected: 5 I am guessing it's working on disk2 which has the pending sectors as it's showing 894 read errors. Edited March 9, 2020 by gnollo Quote Link to comment
JorgeB Posted March 9, 2020 Share Posted March 9, 2020 The sync errors are likely from the unclean shutdown, since it would be risky/impossible to do a correcting check, I would just cancel the parity check and replace the disk now, but keep the old disk in case it's needed. Quote Link to comment
gnollo Posted March 12, 2020 Author Share Posted March 12, 2020 Going through the parity swap, also got this message, which is unrelated, every time I power on the server during the parity swap process USB flash drive failure: 12-03-2020 13:24 Alert [TOWER] - USB drive is not read-write UDisk (sda) Quote Link to comment
gnollo Posted March 12, 2020 Author Share Posted March 12, 2020 Also is not picking up the new drive for some reason. It is a 10Tb drive I extracted from a WD elements external case. Quote Link to comment
Frank1940 Posted March 12, 2020 Share Posted March 12, 2020 1 minute ago, gnollo said: Also is not picking up the new drive for some reason. It is a 10Tb drive I extracted from a WD elements external case. Make sure you do not have the Pin3 +3.3v problem that is common with many shucked drives. See Here: https://www.instructables.com/id/How-to-Fix-the-33V-Pin-Issue-in-White-Label-Disks-/ 9 minutes ago, gnollo said: USB flash drive failure: 12-03-2020 13:24 Alert [TOWER] - USB drive is not read-write UDisk (sda) About this issue, I would be looking at the Flash drive and would run a chkdsk on it in a PC. Quote Link to comment
gnollo Posted March 12, 2020 Author Share Posted March 12, 2020 I connected the drive directly to a molex sata cable and power supply, esternally, it works that way. Does not work when I insert it in the cages, tried different slots, same result. But the parity swap didn't work, too many wrong disks, it said. I had no option but to revert. It would seem I have the pin issue. I will take a look at the tutorial, thanks. In the meantime, what do I do about the parity swap? Quote Link to comment
JorgeB Posted March 12, 2020 Share Posted March 12, 2020 10 minutes ago, gnollo said: But the parity swap didn't work, too many wrong disks, it said. We'd need diags to see what the problem was. Quote Link to comment
gnollo Posted March 12, 2020 Author Share Posted March 12, 2020 Diagnostics attached. Also if I use a molex to molex adapter before I connect the Norco Caddy, would that remove the white label disk pin issue? Or is it only a Molex to Sata adapter that removes the pin issue? tower-diagnostics-20200312-1554.zip Quote Link to comment
JorgeB Posted March 12, 2020 Share Posted March 12, 2020 9 minutes ago, gnollo said: Diagnostics attached. I meant when you were getting the "too many wrong" disks, to see what you were doing wrong on the parity swap procedure. 10 minutes ago, gnollo said: Also if I use a molex to molex adapter before I connect the Norco Caddy, would that remove the white label disk pin issue? No, problem is that some backplanes still have 3.3v on the SATA ports despite being power by molex connectors (that don't have 3.3v). Quote Link to comment
gnollo Posted March 12, 2020 Author Share Posted March 12, 2020 (edited) Thanks Johnnie, so I need to put the tape on the third pin, will try the procedure again and then capture the diagnostics. Thank you all for the support, it is one of the reasons I love unraid. The community is so good. Edited March 12, 2020 by gnollo Quote Link to comment
gnollo Posted March 13, 2020 Author Share Posted March 13, 2020 Third pin fixed with tape, parity swap worked, now copying. Thanks for your help! Quote Link to comment
gnollo Posted March 14, 2020 Author Share Posted March 14, 2020 Parity copy almost complete. Next step rebuilding the drive. Once complete, is there an app running in a docker that I can use to make sure that the old drive and the new drive contain the same data? Basically a way to check that unraid did the job correctly, and I am not missing any data. Quote Link to comment
gnollo Posted March 14, 2020 Author Share Posted March 14, 2020 I wonder if I could use this 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.