Unable to access unraid after certain amount of up time

[FranciumF]

My unraid server have been in operation for the last 3 month of so, but in recent days, it tend to become inactive suddenly.
no access to shares, cannot ping the server, or any docker service/container on it. 

attached is the diagnostics file.

bisectechunraid-diagnostics-20200508-2331.zip

[JorgeB]

Syslog starts over after a reboot, if it keeps happening try this.

[FranciumF]

On 5/11/2020 at 5:13 PM, johnnie.black said:

Syslog starts over after a reboot, if it keeps happening try this.

syslog-20200508-232355.zip
does any of these helps?

[JorgeB]

A date/time when it crashed would help.

[FranciumF]

My last access is usually 3-6am 

And by morning around 11-1noon i wouldve lost access. 

[JorgeB]

Sorry, nothing jumps out, try running the server in safe mode for a couple of days.

[FranciumF]

its ok. thanks  will continue to monitor

 

[JorgeB]

10 minutes ago, FranciumF said:

will continue to monitor

You should try safe mode.

[FranciumF]

i've isolated the events that could be causing the problem
last time i check was around last night around 10.
and by this morning 11 it stopped responding, therefore i rebooted.

within this time span, i see crond and trim taking place. 
will disable and monitor again.

Quote

May 12 22:59:52 BisecTechUnraid CA Backup/Restore: #######################
May 12 22:59:52 BisecTechUnraid CA Backup/Restore: appData Backup complete
May 12 22:59:52 BisecTechUnraid CA Backup/Restore: #######################
May 12 22:59:52 BisecTechUnraid CA Backup/Restore: Backup / Restore Completed
May 13 00:00:54 BisecTechUnraid crond[2010]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
May 13 06:00:16 BisecTechUnraid crond[2010]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
May 13 06:29:57 BisecTechUnraid dhcpcd[1813]: br0: adding default route via 192.168.1.1
May 13 08:30:38 BisecTechUnraid root: /etc/libvirt: 19.5 GiB (20936896512 bytes) trimmed on /dev/loop3
May 13 08:30:38 BisecTechUnraid root: /var/lib/docker: 487.9 GiB (523905687552 bytes) trimmed on /dev/loop2
May 13 08:30:38 BisecTechUnraid root: /mnt/cache: 412 GiB (442307100672 bytes) trimmed on /dev/sde1
May 13 11:08:49 BisecTechUnraid init: Switching to runlevel: 0
May 13 11:08:49 BisecTechUnraid init: Trying to re-exec init
May 13 11:08:51 BisecTechUnraid kernel: mdcmd (41): nocheck cancel
May 13 11:08:52 BisecTechUnraid emhttpd: Spinning up all drives...
May 13 11:08:52 BisecTechUnraid emhttpd: shcmd (2153): /usr/sbin/hdparm -S0 /dev/sde
May 13 11:08:52 BisecTechUnraid kernel: mdcmd (42): spinup 1
May 13 11:08:52 BisecTechUnraid kernel: mdcmd (43): spinup 2
May 13 11:08:52 BisecTechUnraid kernel: mdcmd (44): spinup 3
May 13 11:08:52 BisecTechUnraid kernel: mdcmd (45): spinup 4
May 13 11:08:52 BisecTechUnraid root: 
May 13 11:08:52 BisecTechUnraid root: /dev/sde:
May 13 11:08:52 BisecTechUnraid root:  setting standby to 0 (off)
May 13 11:08:53 BisecTechUnraid emhttpd: Stopping services...

 

[FranciumF]

Quote

May 14 05:04:41 BisecTechUnraid kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 14 05:04:41 BisecTechUnraid kernel: ata1.00: failed command: FLUSH CACHE EXT
May 14 05:04:41 BisecTechUnraid kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 20
May 14 05:04:41 BisecTechUnraid kernel:         res 40/00:ff:81:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
May 14 05:04:41 BisecTechUnraid kernel: ata1.00: status: { DRDY }
May 14 05:04:41 BisecTechUnraid kernel: ata1: hard resetting link
May 14 05:04:42 BisecTechUnraid kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 14 05:04:42 BisecTechUnraid kernel: ata1.00: configured for UDMA/133
May 14 05:04:42 BisecTechUnraid kernel: ata1.00: retrying FLUSH 0xea Emask 0x4
May 14 05:04:42 BisecTechUnraid kernel: ata1: EH complete

another new set of issue, changed out the cable for my cache, running checks now and continue to monitor.