[SOLVED] Shares/webUI Not Responsive after Drive Addition

[lishpy]

Running v5b13.

 

I upgraded my parity drive without any problems and parity sync finished about an hour ago. I went to reassign the old parity drive to a data slot in the array, and now the webUI is not responding.

 

I can load the flash drive from SMB but my shares don't show up and again the webUI isn't responsive, it just hangs.

 

Advice?

[lishpy]

I hoped the server would be responsive when I woke up this morning but still no webUI or shares access. Syslog seems to be identical too. Should I shut down the server and if so what's the best way to go about it?

 

[Joe L.]

I hoped the server would be responsive when I woke up this morning but still no webUI or shares access. Syslog seems to be identical too. Should I shut down the server and if so what's the best way to go about it?

 

If you did not preclear the newly added disk,  before re-assigning it to the unRAID array as a data disk, then unRAID is clearing it for you.   While it clears it, the array is off-line.

 

Depending on the size of the disk, and how few hours you sleep, it might still be performing that task.

The array will be off-line until that completes.  If you interrupt it, it will only start clearing it again when it reboots.

 

Post a syslog from this morning.   The one from your initial post shows nothing abnormal.

 

Joe L.

[lishpy]

Thanks Joe.

 

Didn't realize the preclearing of the old parity disk would make the entire system unusable. It's been a REALLY long time since I've let unRAID do any preclearing, I forgot about any of that. Everything is back up now. Much appreciated.

[Joe L.]

Thanks Joe.

 

Didn't realize the preclearing of the old parity disk would make the entire system unusable. It's been a REALLY long time since I've let unRAID do any preclearing, I forgot about any of that. Everything is back up now. Much appreciated.

It is exactly why the preclear_disk.sh script was originally developed... and that was when a large disk was 500Meg and clearing took the server off-line for 3 or 4 hours.