Recently I have encountered an issue where the unraid server stops working after starting the server. It can be in 24hr or a few days. It happened once in a week or two now more frequent. I must power down the server with power button and reload server and things work and then same cycle occurs hours to days later. I can not access the GUI sometimes at all and the docker apps load but do not work. I have included the diagnotic file when it loads back up. This last time it loaded up but was not working correctly and the diagnotic file would not download. Can any help explain what is going on and what I can do to fix it? Thank You

ashlab-diagnostics-20250801-0944.zip

Edited August 2, 2025Aug 2 by ashkasto

Enable the syslog server and post that after a crash.

9 hours ago, JorgeB said:

Enable the syslog server and post that after a crash.

How and where do I do that on my server? Thank you

...nvm I turned on the sys log to save on my casche drive...hope to catch what is happening

Edited August 2, 2025Aug 2 by ashkasto

This is the syslog after the server stop responding and screenshot on unraid screen with error, unable to access usb drive. Do I need a new USB drive?

syslog-192.168.12.9.log

On 8/1/2025 at 10:26 AM, JorgeB said:

Enable the syslog server and post that after a crash.

can Anyone help with this please?

Flash drive dropped offline, try a different USB port, if the same, replace the flash drive:

Aug 2 09:18:35 Ashlab kernel: usb 1-11.3: USB disconnect, device number 6

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 14341168 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 14341184 op 0x1:(WRITE) flags 0x800 phys_seg 5 prio class 0

Aug 2 09:18:35 Ashlab kernel: sda: detected capacity change from 31711232 to 0

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 10865 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 8817, lost async page write

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 26333 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 24285, lost async page write

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 10865 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 8817, lost async page write

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 12239200 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 12237152, lost async page write

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 894352 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 892304, lost async page write

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 12239200 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: FAT-fs (sda1): unable to read inode block for updating (i_pos 195794441)

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 2049 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 1, lost async page write

Aug 2 09:18:35 Ashlab kernel: device offline error, dev sda, sector 894256 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 892208, lost async page write

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 892304, lost async page write

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 894832, lost async page write

Aug 2 09:18:35 Ashlab kernel: Buffer I/O error on dev sda1, logical block 894833, lost async page write