Appreciate any guidance here. Situation went sideways a bit. Don't want to do anything rash. I'm long time user. I've done a number of disk rebuilds in past. Never faced this behavior. 

 

notice I had a failed disk so snapped a quick pick of the drives. 

Stopped Docker

Shut down 

replaced the disk 

booted system

assigned the replacement disk on the old failed disk slot

it did show the disk was to be rebuilt so I started the array/rebuild process

 

This is where it got weird. I was expecting a warning about the format but upon the screen refresh I got a refused to connect, this site can’t be reached. I am using its ip. I can ssh to the server. I can see my apps are running. Server appears to be functioning to some degree. 

 

From the log I can see 

Oct 29 10:42:41 Tower Parity Check Tuning: Parity Sync/Data Rebuild detected
....
Oct 29 10:51:21 Tower  emhttpd: spinning down /dev/sde
Oct 29 11:30:07 Tower kernel: mdcmd (38): nocheck PAUSE
Oct 29 11:30:07 Tower kernel: 
Oct 29 11:30:07 Tower kernel: md: recovery thread: exit status: -4
Oct 29 11:30:12 Tower Parity Check Tuning: Paused: Parity Sync/Data Rebuild (4.5% completed)

 

My questions are how long before I see the rebuild percentage increase. It seems to be sitting at 4.5%. 

Should I have seen a popup confirming the drive was to be reformatted? I selected start array and the screen went blank. 

I'm not seeing any rebuild entries after the "4.5% completed". Is there a way I can confirm rebuild is actually happening without the gui? 

 

I have 20+ drives so rebuild would take 24 hours or so. I'm running 6.11.4. 

 

 

 

Edited October 29, 20232 yr by daniel.boone
diags removed, marked solved

You have the Parity Check Tuning plugin installed and it looks like it has paused because of the settings you have set for that plugin.   If you post your system’s diagnostics zip file then it should be possible to tell you which setting is causing this.

I was pretty sure I have the tuning disabled for rebuilds. Diags posted 

 

Thanks

According to the diagnostics you HAVE enabled the option to run rebuild/sync in increments, and the increment active time is 01:15 to 04:00 so outside that timeslot it will be paused.

Appreciate the help, figured out webgui could be started with this command '/etc/rc.d/rc.nginx reload'. It came back with 'Nginx is not running' so I ran '/etc/rc.d/rc.nginx start'. Daemon started without issue. With that I got the webgui back and was able to correct the configuration. Rebuild is running once again. 

 

Thanks again, post marked solved.