DanW Posted June 17 Share Posted June 17 I had a failed disk today and I replaced it, during the rebuild another disk has failed ðŸ˜Â but to be expected, I have some older drives in my array. I'm planning to replace the second failed disk once the rebuild completes but the rebuild appears to be stuck. The disks appear to be actively copying data to the new disk but I see no progress change (it's been on 6.9% for hours)? Could anyone spot any clues as to what's going on? Many thanks!    dansunraidnas-diagnostics-20240617-2325.zip Quote Link to comment
JorgeB Posted June 18 Share Posted June 18 Emhttp crashed, reboot and post new diags after array start. 1 Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 Thank you @JorgeB! I can see the array is busy with the rebuild based on disk activity. Would you recommend waiting for it to complete then give it a reboot? Â Quote Link to comment
JorgeB Posted June 18 Share Posted June 18 Post new diags to see if it advanced comparing to last ones, but even if it finishes, not sure it will correctly mark the disks as rebuilt, because of the emhttp crash. Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 (edited) 37 minutes ago, JorgeB said: Post new diags to see if it advanced comparing to last ones, but even if it finishes, not sure it will correctly mark the disks as rebuilt, because of the emhttp crash.  Ah ok, @JorgeB please see attached. Is there no way of restarting the emhttp service while the array is live?  dansunraidnas-diagnostics-20240618-0929.zip  Edited June 18 by DanW Quote Link to comment
JorgeB Posted June 18 Share Posted June 18 It's still in the same position, so the rebuild is not advancing, the read/write stats are probably frozen, do you see the values changing? Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 (edited) 42 minutes ago, JorgeB said: It's still in the same position, so the rebuild is not advancing, the read/write stats are probably frozen, do you see the values changing? The values aren't changing but I can see it has stopped reading data from some of the HDDs just like during a normal rebuild which is why I think it is still doing the rebuild. Edited June 18 by DanW Quote Link to comment
JorgeB Posted June 18 Share Posted June 18 I meant the stats for the individual disk read/write speeds, are those changing? Â Still, doubt the disks will be marked as rebuilt, even if it reading them. Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 Just now, JorgeB said: I meant the stats for the individual disk read/write speeds, are those changing? Â Still, doubt the disks will be marked as rebuilt, even if it reading them. Oh yeah, the read / write speeds are moving, I've been keeping an eye on it. Quote Link to comment
JorgeB Posted June 18 Share Posted June 18 You can try to let it finish, quite curious myself on what will happen. 1 Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 1 minute ago, JorgeB said: You can try to let it finish, quite curious myself on what will happen. I'll leave it and we'll find out 🙂 Quote Link to comment
JorgeB Posted June 18 Share Posted June 18 [mdResyncCorr] => 1 [mdResyncPos] => 804548076 [mdResyncDb] => 5611620 [mdResyncDt] => 32 [mdResyncAction] => recon D6 [mdResyncSize] => 11718885324 [mdResyncCorr] => 1 [mdResyncPos] => 804548076 [mdResyncDb] => 5611620 [mdResyncDt] => 32 [mdResyncAction] => recon D6 [mdResyncSize] => 11718885324  BTW, this is why I suspect it won't really finish, this is were Unraid tracks the rebuild, the mdResyncPos variable is the current position, and it didn't change between both diags, I believe emhttp is what tracks that, and since it segfaulted, it should only start working again after a reboot. Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 10 hours ago, JorgeB said: [mdResyncCorr] => 1 [mdResyncPos] => 804548076 [mdResyncDb] => 5611620 [mdResyncDt] => 32 [mdResyncAction] => recon D6 [mdResyncSize] => 11718885324 [mdResyncCorr] => 1 [mdResyncPos] => 804548076 [mdResyncDb] => 5611620 [mdResyncDt] => 32 [mdResyncAction] => recon D6 [mdResyncSize] => 11718885324  BTW, this is why I suspect it won't really finish, this is were Unraid tracks the rebuild, the mdResyncPos variable is the current position, and it didn't change between both diags, I believe emhttp is what tracks that, and since it segfaulted, it should only start working again after a reboot. So the rebuild has finished (based on that there's no read / write activity on the disks anymore). The status of the disk hasn't changed but I can see that when I read files from the array that are on that disk, it does use the rebuilt disk (see below). I will reboot unraid and see what happens with the disk.  The elapsed time is still progressing. Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 (edited) 10 hours ago, JorgeB said: [mdResyncCorr] => 1 [mdResyncPos] => 804548076 [mdResyncDb] => 5611620 [mdResyncDt] => 32 [mdResyncAction] => recon D6 [mdResyncSize] => 11718885324 [mdResyncCorr] => 1 [mdResyncPos] => 804548076 [mdResyncDb] => 5611620 [mdResyncDt] => 32 [mdResyncAction] => recon D6 [mdResyncSize] => 11718885324  BTW, this is why I suspect it won't really finish, this is were Unraid tracks the rebuild, the mdResyncPos variable is the current position, and it didn't change between both diags, I believe emhttp is what tracks that, and since it segfaulted, it should only start working again after a reboot. @JorgeB after the reboot, it's doing a parity check which I have interrupted.  Edited June 18 by DanW Quote Link to comment
DanW Posted June 18 Author Share Posted June 18 I have now replaced disk 3 and I have started another rebuild. Quote Link to comment
JorgeB Posted June 19 Share Posted June 19 Interesting, the rebuild did finish, replace disk3 and you should be done. 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.