Having some errors, not sure when did the docker service failed and for how long (hope it wasn't long).

 

Saw the log with lots of errors, not sure what to do or what's happening.. currently the monthly parity check is running. Would appreciate any advice.

tower-diagnostics-20210701-0534.zip

In the syslog I see:

Jul  1 04:43:01 Tower crond[1988]: failed parsing crontab for user root: #015
Jul  1 04:54:04 Tower kernel: nvme nvme0: I/O 785 QID 5 timeout, aborting
Jul  1 04:54:06 Tower kernel: nvme nvme0: I/O 322 QID 9 timeout, aborting
Jul  1 04:54:06 Tower kernel: nvme nvme0: I/O 323 QID 9 timeout, aborting
Jul  1 04:54:06 Tower kernel: nvme nvme0: I/O 425 QID 13 timeout, aborting
Jul  1 04:54:11 Tower kernel: nvme nvme0: I/O 324 QID 9 timeout, aborting
Jul  1 04:54:14 Tower kernel: nvme nvme0: I/O 325 QID 9 timeout, aborting
Jul  1 04:54:14 Tower kernel: nvme nvme0: I/O 326 QID 9 timeout, aborting
Jul  1 04:54:14 Tower kernel: nvme nvme0: I/O 327 QID 9 timeout, aborting
Jul  1 04:54:35 Tower kernel: nvme nvme0: I/O 785 QID 5 timeout, reset controller
Jul  1 04:55:05 Tower kernel: nvme nvme0: I/O 0 QID 0 timeout, reset controller
Jul  1 04:56:08 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
Jul  1 04:56:09 Tower kernel: nvme nvme0: Abort status: 0x371
### [PREVIOUS LINE REPEATED 7 TIMES] ###
Jul  1 04:56:39 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1
Jul  1 04:56:39 Tower kernel: nvme nvme0: Removing after probe failure status: -19
Jul  1 04:57:10 Tower kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1

Which suggests that the cache drive dropped offline, and after that you are getting continual errors trying to access the Docker image file.

 

there is also that message about an invalid entry in the crontab file for the root user - it might be worth trying to sort out what is the invalid entry and thus what might have created it.    Not sure if it is a related error or not as the diagnostics do not show what the invalid entry actually is.

Thanks. A reboot should be fine when the cache drive is detected again alright? Should I wait for the parity to complete first? I reckon it will start from zero again if I restart now

 

As for the invalid entry, any idea where can I find the source of it?