NewDisplayName Posted June 2, 2019 Share Posted June 2, 2019 (edited) So ive got a red thing at the parity drive. Should i just run a check or is the drive 100% broken? What should i do? Its a "relativly new drive", never had problems. unraid-server-diagnostics-20190602-2015.zip Edited June 2, 2019 by nuhll Quote Link to comment
JonathanM Posted June 2, 2019 Share Posted June 2, 2019 12 minutes ago, nuhll said: So ive got a red thing at the parity drive. https://lime-technology.com/wiki/index.php?title=Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F Quote Link to comment
NewDisplayName Posted June 2, 2019 Author Share Posted June 2, 2019 (edited) 10 minutes ago, jonathanm said: https://lime-technology.com/wiki/index.php?title=Troubleshooting#What_do_I_do_if_I_get_a_red_ball_next_to_a_hard_disk.3F Yo, so the question is, what does the smart values say (im not so good at reading these stats) My stats is in the diagnostics, or? (if not i post it here) unraid-server-smart-20190602-2239.zip Edited June 2, 2019 by nuhll Quote Link to comment
NewDisplayName Posted June 2, 2019 Author Share Posted June 2, 2019 I see now its empty... ill try restarting. Quote Link to comment
NewDisplayName Posted June 2, 2019 Author Share Posted June 2, 2019 Now its complete gone... wow. So its dead? unraid-server-diagnostics-20190602-2138.zip Quote Link to comment
JorgeB Posted June 3, 2019 Share Posted June 3, 2019 Disk dropped offline, so there's no SMART, but it looks more like a connection problem, power cycle an/or check connections and it should come back online, then check SMART. Quote Link to comment
NewDisplayName Posted June 3, 2019 Author Share Posted June 3, 2019 (edited) So if i check cables (then restart) and it still dont show up, its just dead? (never changed anything for months (its in a server cabinet)) Edited June 3, 2019 by nuhll Quote Link to comment
JorgeB Posted June 3, 2019 Share Posted June 3, 2019 1 minute ago, nuhll said: So if i check cables (then restart) and it still dont show up, its just dead? Most likely, but make sure it's power cycled. Quote Link to comment
NewDisplayName Posted June 3, 2019 Author Share Posted June 3, 2019 (edited) 24 minutes ago, johnnie.black said: Most likely, but make sure it's power cycled. Just a restart? Or shutdown and start? Or like remove cable and wait a minute? Edited June 3, 2019 by nuhll Quote Link to comment
JorgeB Posted June 3, 2019 Share Posted June 3, 2019 Power off, check cables, power back on. 1 Quote Link to comment
NewDisplayName Posted June 9, 2019 Author Share Posted June 9, 2019 okay, i did as you suggested. And it happend what i didnt thought... turned back on with the drive... (there were no feelable loose cables) my best guess would be the changed temperatures... Anyway, parity is currently rebuilding and i saved around 250€, thanks! Smart seems ok for me. unraid-server-smart-20190609-1844.zip Quote Link to comment
NewDisplayName Posted June 11, 2019 Author Share Posted June 11, 2019 (edited) So ive rebuild my server and i got the next error on another drive. All seems normal, besides these errors. 1.) Is parity working again? Or do i need to run a correction parity? 2.) If i googled correct, these disk error means i need to replace it, correct? 3.) (i would be safe, if drive fails, correct?) Notice [UNRAID-SERVER] - Parity disk returned to normal operation 11-06-2019 04:38Unraid Parity sync / Data rebuildNotice [UNRAID-SERVER] - Parity sync / Data rebuild finished (356818 errors)Duration: 1 day, 9 hours, 57 minutes, 46 seconds. Average speed: 65.4 MB/swarning 10-06-2019 16:02Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 205WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 15:32Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 204WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 15:01Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 203WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 14:31Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 202WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 14:01Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 200WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 13:30Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 198WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 12:59Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 123WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 12:28Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 33WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 11:57Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 30WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 11:26Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 29WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 10:56Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 28WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 10:25Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 24WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 09:53Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 22WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 09:22Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 20WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 08:51Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 15WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 06:48Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 12WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 06:18Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 11WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 05:46Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 10WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 04:44Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 9WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 04:14Unraid Disk 3 SMART health [197]Warning [UNRAID-SERVER] - current pending sector is 2WDC_WD30EFRX-68EUZN0_WD-WCC4N1XHR6PX (sdk)warning 10-06-2019 02:17Unraid array errorsWarning [UNRAID-SERVER] - array has errorsArray has 1 disk with read errorswarning unraid-server-smart-20190611-1752.zip Edited June 11, 2019 by nuhll Quote Link to comment
JorgeB Posted June 11, 2019 Share Posted June 11, 2019 Post the diagnostics but based on the times there were likely errors during parity rebuild. Quote Link to comment
JorgeB Posted June 11, 2019 Share Posted June 11, 2019 P.S. I warned you some time ago that this disk was failing, it should heave been replaced at the time. 1 1 Quote Link to comment
NewDisplayName Posted June 11, 2019 Author Share Posted June 11, 2019 (edited) 3 hours ago, johnnie.black said: P.S. I warned you some time ago that this disk was failing, it should heave been replaced at the time. didnt thought its really something... I move now all stuff from disk 3 to the other disks. unraid-server-diagnostics-20190611-1927.zip Edited June 11, 2019 by nuhll Quote Link to comment
JorgeB Posted June 12, 2019 Share Posted June 12, 2019 As suspected there were read errors on disk3 during the parity sync, so parity isn't valid, copy everything you can from disk3, remove it or replace it from the array and rebuild parity. Quote Link to comment
NewDisplayName Posted June 12, 2019 Author Share Posted June 12, 2019 (edited) You say pairty isnt valid, but unraid says it is. thats what is mysterios. Btw, all files moved without errors. I guess, then all data is intact? Is parity now valid, or not? (bc if it is, i could start the array without that drive, without new parity check, or not?!) I dont want to add a new drive. Just remove the faulty. Whats best way to archieve this? Stop array, new config, start array, question is, parity check or not? Edited June 12, 2019 by nuhll Quote Link to comment
JorgeB Posted June 12, 2019 Share Posted June 12, 2019 13 minutes ago, nuhll said: You say pairty isnt valid, but unraid says it is. thats what is mysterios. If there are read errors on other disks during a parity sync it should be obvious parity can't be 100% correct, and IMHO Unraid should reflect that, but it currently doesn't. Quote Link to comment
JorgeB Posted June 12, 2019 Share Posted June 12, 2019 21 minutes ago, nuhll said: Whats best way to archieve this? New config, remove bad disk, start array to sync parity. Quote Link to comment
NewDisplayName Posted June 12, 2019 Author Share Posted June 12, 2019 (edited) 3 hours ago, johnnie.black said: If there are read errors on other disks during a parity sync it should be obvious parity can't be 100% correct, and IMHO Unraid should reflect that, but it currently doesn't. Okay, so ill suggest that they change that. Edited June 12, 2019 by nuhll Quote Link to comment
NewDisplayName Posted June 12, 2019 Author Share Posted June 12, 2019 (edited) moved all files from disk 3 to other disks. stopped array. new config, perserved cache and parity start array with same config (except disk 3) Parity is building currently. Thanks for help. Any clever idea how to find out which drive in the case is this drive? Edited June 12, 2019 by nuhll Quote Link to comment
JorgeB Posted June 13, 2019 Share Posted June 13, 2019 The way to find is by the serial number, you can have the drives in the case using the same order as the array assignments, that's what I do, this way they are easy to find. 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.