Hi chaps,

I am running ver.6.1.9 on an HP n40L with 6GB RAM.

I believe the only docker i have running is RuTorrent.

 

Earlier i logged into the web gui to observe progress of a data rebuild and a disk preclear nearing completion. About 30 mins later I was unable to resolve the web gui. I can still access my SMB shares, and SSH into the box.

 

Please see my diagnostics zip attached.

 

Help much appreciated, don't want to reboot just yet as not 100% my data has rebuilt.

 

James

syslog.zip

Disk3 rebuild finished yesterday, are you rebuilding another?

 

May 30 23:33:01 Tower kernel: md: recovery thread woken up ...
May 30 23:33:01 Tower kernel: md: recovery thread rebuilding disk3 ...
...
May 31 18:36:52 Tower kernel: md: sync done. time=68630sec
May 31 18:36:52 Tower kernel: md: recovery thread sync completion status: 0

 

You say shares are working but the array was stopped after the rebuild:

 

May 31 23:16:58 Tower emhttp: Unmounting disks...
...
May 31 23:17:01 Tower kernel: mdcmd (58): stop 
May 31 23:17:01 Tower kernel: md1: stopping
May 31 23:17:01 Tower kernel: md2: stopping
May 31 23:17:01 Tower kernel: md3: stopping
May 31 23:17:01 Tower kernel: md4: stopping
May 31 23:17:01 Tower kernel: md5: stopping
...
May 31 23:17:19 Tower emhttp: shcmd (144): /sbin/poweroff
May 31 23:17:19 Tower shutdown[21963]: shutting down for system halt
May 31 23:17:19 Tower init: Switching to runlevel: 0
May 31 23:17:22 Tower rc.unRAID[21983][21987]: Powerdown V2.20
May 31 23:17:22 Tower rc.unRAID[21983][21991]: Array is Stopped

 

Wrong syslog?

Ah, apologies. You are right, wrong log!

New one attached.

tower-diagnostics-20160601-1803.zip

I can see the rebuild start:

 

May 31 23:30:13 Tower kernel: md: recovery thread woken up ...
May 31 23:30:13 Tower kernel: md: recovery thread rebuilding disk2 ...

 

But don't see the end, and it looks to me like it aborted, you can confirm by typing in the console:

 

mdcmd status | egrep "mdResync"

 

Post output.

Thank you, i will check later and post output and another syslog just in case - oddly after our posts yesterday i checked the web GUI....alive again...?

 

If the GUI is alive you can see the rebuild status.

I'm still able to access the web GUI. Though there is no status of the disk rebuild, all array disks showing green.

Also the output of mdcmd status | egrep "mdResync" is :

mdResync=0

mdResyncCorr=1

mdResyncPos=0

mdResyncDt=0

mdResyncDb=0

 

Can i safely assume the rebuild was ok? Should i now perform a parity check? Syslog attached.

I wonder why the web GUI failed and came back...?

tower-diagnostics-20160602-1851.zip

Disk was rebuilt successfully:

 

May 31 23:30:13 Tower kernel: md: recovery thread woken up ...
May 31 23:30:13 Tower kernel: md: recovery thread rebuilding disk2 ...
...
Jun  1 18:58:11 Tower kernel: md: sync done. time=70077sec
Jun  1 18:58:11 Tower kernel: md: recovery thread sync completion status: 0

 

Don't know what caused the unresponsive GUI but it was probably waiting for other operation to complete.

Thanks for identifying the completion - mind at rest!

I'll mark this as solved given that it righted itself.

 

Thanks again.

James