Jump to content

WebGui updates but the position in the rebuild process appears frozen


perfessor101

Recommended Posts

Hello

I'm on UnRaid 6.4.1

 

I had a drive failure over the weekend 

I started rebuilding it this morning but the WebGUI reports that I'm at 4.2% for the last thirty minutes 

The read(s) and write rate are in the 85MB/s range, but it continues reporting that the rebuild process is at 4.2%

 

I tried 

mdcmd status | egrep "mdResync|mdState|sbSync"

which returned
 

sbSynced=1519148002

sbSyncErrs=0

sbSynced2=0

sbSyncExit=0

mdState=STARTED

mdResyncAction=recon D7

mdResyncSize=2930266532

mdResyncCorr=1

mdResync=2930266532

mdResyncPos=330004368

mdResyncDt=30

mdResyncDb=2580396

and the mdResyncPos number is growing "rapidly"

 

I just wanted to be sure the rebuild is continuing as it appears to be  at 14.06%

 

Thanks for your time,

Bobby

 

 

 

 

storage-diagnostics-20180220-1055.zip

Link to comment

I've hit ctrl-F5 and navigated away from the page and back ... loaded it in a new tab

 

(all on chrome though so far)

 

Elapsed time , Current position, Estimated speed, Estimated finish all seem to be stuck

 

is there a mdcmd command  that might update the location the WebGUI is reading the information from?

 

 

Link to comment
43 minutes ago, bonienl said:

With unRAID 6.4 it is emhttpd which keeps track of the array status, including parity process, it updates in the background the file /var/local/emhttp/var.ini every second. The GUI will update the screen each time with the latest information stored by emhttpd.

 

 

 

It appears the mover started before I started the array rebuild?

 

I have the mover set not to start during parity checks at least, but to attempt to run every hour

 

will the mover run during parity rebuilding?

 

it said mover disabled earlier but in process of moving 

 

so I guess the mover was grinding away incredibly slowly

 

and when that finished the array progress indication started moving again

 

sorry for that 

just wanted to make sure the parity rebuild hadn’t halted

 

thanks for your help

bobby

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...