Rebooted and restarted array and nothing has happened for over 90 mins now.

 

Can't generate diagnostics either. Gets stuck on this:

 

smartctl -x '/dev/sdd' 2>/dev/null|todos >'/fs-diagnostics-20230109-1643/smart/WDC_WD120EDBZ-11B1HA0_5QJMG4XB-20230109-1643 (sdd).txt'

 

Everything else seems fine, web admin and ssh working okay,

 

Here's the log:

 

Jan 9 15:13:29 fs nmbd[28811]: [2023/01/09 15:13:29.828715, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce)
 Jan 9 15:13 :29 fs nmbd[28811]: process_local_master_announce: Server SHIELD at IP 192.168.0.41 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Jan 9 15:13:29 fs nmbd[28811]: [2023/01/09 15:13:29.828890, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
 Jan 9 15:13 :29 fs nmbd[28811]: *****
 Jan 9 15:13:29 fs nmbd[28811]:   
 Jan 9 15:13:29 fs nmbd[28811]: Samba name server FS has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.0.250
 Jan 9 15:13:29 fs nmbd[28811]:   
Jan 9 15:13:29 fs nmbd[28811]: *****
 Jan 9 15:13:46 fs nmbd[28811]: [2023/01/09 15:13:46.035908, 0] ../.. /source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
 Jan 9 15:13:46 fs nmbd[28811]: *****
 Jan 9 15:13:46 fs nmbd[28811]:   
 Jan 9 15:13: 46 fs nmbd[28811]: Samba name server FS is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.250
 Jan 9 15:13:46 fs nmbd[28811]:   
 Jan 9 15:13:46 fs nmbd[28811] :*****
Jan 9 15:14:05 fs nginx: 2023/01/09 15:14:05 [error] 28899#28899: *1309 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.21, server : , request: "POST /update.htm HTTP/1.1", upstream: " http://unix:/var/run/emhttpd.socket:/update.htm ", host: "fs", referrer: " http: //fs/Main "
Jan 9 15:24:01 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down
 Jan 9 15:24:02 fs ntpd[2390]: Deleting interface #2 eth0, 192.168.1.250#123, interface stats: received=0, sent=56, dropped=0, active_time=1341 secs
 Jan 9 15:24:02 fs ntpd[2390]: 216.239.35.0 local addr 192.168.1.250 -> <null>
 Jan 9 15:24:02 fs ntpd[2390]: 216.239.35.4 local addr 192.168.1.250 -> <null>
 Jan 9 15:24:02 fs ntpd[2390]: 216.239.35.8 local addr 192.168.1.250 -> <null>
 Jan 9 15:24: 02 fs ntpd[2390]: 216.239.35.12 local addr 192.168.1.250 -> <null>
 Jan 9 15:24:02 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:24:04 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
Jan 9 15:24:06 fs ntpd[2390]: Listen normally on 3 eth0 192.168.1.250:123
 Jan 9 15:24:06 fs ntpd[2390]: new interface(s) found: waking up resolver
 Jan 9 15: 24:20 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
 Jan 9 15:24:20 fs nmbd[28811]: [2023/01/09 15:24: 20.694854, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce)
 Jan 9 15:24:20 fs nmbd[28811]: process_local_master_announce: Server SHIELD at IP 192.168.0.41 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Jan 9 15:24:20 fs nmbd[28811]: [2023/01/09 15:24:20.695016, 0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
Jan 9 15:24:20 fs nmbd[28811]: *****
 Jan 9 15:24:20 fs nmbd[28811]:   
 Jan 9 15:24:20 fs nmbd[28811]: Samba name server FS has stopped being a local master browser for workgroup WORKGROUP on subnet 192.168.0.250
 Jan 9 15:24:20 fs nmbd[28811]:   
 Jan 9 15:24:20 fs nmbd[28811]: *****
 Jan 9 15:24: 39 fs nmbd[28811]: [2023/01/09 15:24:39.237831, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
 Jan 9 15:24:39 fs nmbd[28811 ]: *****
 Jan 9 15:24:39 fs nmbd[28811]:   
 Jan 9 15:24:39 fs nmbd[28811]: Samba name server FS is now a local master browser for workgroup WORKGROUP on subnet 192.168. 0.250
 Jan 9 15:24:39 fs nmbd[28811]:   
 Jan 9 15:24:39 fs nmbd[28811]: *****
Jan 9 15:25:00 fs vnstatd[25241]: Detected bandwidth limit for "eth1" changed from 1000 Mbit to 100 Mbit.
Jan 9 15:25:23 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:25:59 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
Jan 9 15:26:00 fs webGUI: Successful login user root from 192.168.0.16
Jan 9 15:26:50 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:26:53 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
 Jan 9 15:28:55 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:28:58 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
 Jan 9 15:28:59 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:29:03 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
 Jan 9 15:29:03 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:29:05 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down
Jan 9 15:29:06 fs ntpd[2390]: Deleting interface #3 eth0, 192.168.1.250#123, interface stats: received=0, sent=12, dropped=0, active_time=300 secs
 Jan 9 15:29: 06 fs ntpd[2390]: 216.239.35.0 local addr 192.168.1.250 -> <null>
 Jan 9 15:29:06 fs ntpd[2390]: 216.239.35.4 local addr 192.168.1.250 -> <null>
 Jan 9 15: 29:06 fs ntpd[2390]: 216.239.35.8 local
 addr 192.168.1.250 -> <null>
 Jan 9 15:29:06 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
 Jan 9 15:29:06 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:29:09 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
Jan 9 15:29:10 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
 Jan 9 15:29:10 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
 Jan 9 15:29:12 fs ntpd[2390]: Listen normally on 4 eth0 192.168.1.250:123
 Jan 9 15:29:12 fs ntpd[2390]: new interface(s) found: waking up resolver
 Jan 9 15:29:14 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Down
 Jan 9 15:29:15 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX /TX
 Jan 9 15:29:16 fs ntpd[2390]: Deleting interface #4 eth0, 192.168.1.250#123, interface stats: received=0, sent=3, dropped=0, active_time=4 secs
 Jan 9 15: 29:16 fs ntpd[2390]: 216.239.35.0 local addr 192.168.1.250 -> <null>
Jan 9 15:29:16 fs ntpd[2390]: 216.239.35.4 local addr 192.168.1.250 -> <null>
 Jan 9 15:29:16 fs ntpd[2390]: 216.239.35.8 local addr 192.168.1.250 -> < null>
 Jan 9 15:29:16 fs ntpd[2390]: 216.239.35.12 local addr 192.168.1.250 -> <null>
 Jan 9 15:29:17 fs kernel: ixgbe 0000:05:00.0 eth0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
 Jan 9 15:29:19 fs ntpd[2390]: Listen normally on 5 eth0 192.168.1.250:123
 Jan 9 15:29:19 fs ntpd[2390]: new interface(s) found: waking up resolver
 Jan 9 15:30:30 fs vnstatd[25241]: Detected bandwidth limit for "eth1" changed from 100 Mbit to 1000 Mbit.

 

Post the syslog at least:

cp /var/log/syslog /boot/syslog.txt

 

Got diagnostics working as it seems to be up now. Took 2 hours though!

 

1. Why can't I start Docker? Apply is greyed out and I can only click reset which I don't know what it does.

2. Why does the array take sooooo long to start?

fs-diagnostics-20230109-1718.zip

Other than shfs using a lot of CPU not seeing much wrong, try updating to v6.11.5 and post new diags if still issues.

I can't update as it messes up loads of things I have set up. I just don't know why Docker won't let me start it still? Is it because I am rebuilding?!

Rebuild should not interfere with docker.

2 hours ago, JorgeB said:

Rebuild should not interfere with docker.

So what is wrong with docker then? The apply button is greyed out no matter what I do... 

Reboot in safe mode and post new diags if it's the same.