May 23, 20251 yr I am having some random errors over the past week that I believe is due to a bad USB boot device. I have gotten different errors at different times, and sometimes the web UI has been unresponsive. I have attached my diagnostics file from this morning (had to do this from direct terminal). Currently, it is saying I have 7 disks with read errors, and disk 4 is emulated. This is new today, over the past week I have not seen any disk errors at all. Sometimes the dockers continue to run, but cannot access any shares. I have had a lot of trouble trying to get the diagnostics file as well. Every time I have tried that through the GUI it has never completed. I just get a blank popup. When it crashed 2 days ago I was not able to get the diagnostics file through the GUI or through direct connection.I have attached a screenshot of the first error I received last week. I rebooted the machine manually (unclean) and this error has not come back, but it continues to crash. Since then, I have rebooted multiple times due to either no connection to the web GUI, but dockers running, or no connection to anything. During this past week the reboots have been bringing everything back up for 2-3 days at a time. I have also attached a pic of what the terminal was telling me this morning. This is a new error that I have not seen yet. It says "Filesystem has been shut down due to log error (0x2)."I thought this meant that my USB was getting ready to die, but now I am not so sure about that. This system was built back in December, but all the array disks came from my old machine that was running very happily for years. I just swapped the USB over to the new motherboard/CPU. System specs: Unraid 7.1.2 - just updated this from 7.0.0 a few days ago after a couple days of problemsASRock B760M PG Lightning/D4Intel i5-12600k32GB RamCant remember what PSU, but I think its a Corsair. I will get model if its necessary10 disks w/ single parity1TB Teamgroup NVME for cacheCruzer Glide 16GB USBPlugins:GPU StatisticsUnassigned Devices PreclearAppdata BackupCA Auto Turbo Write ModeCA Auto Update ApplicationsCA Cleanup AppdataComunity ApplicationsDynamix Auto Fan ControlDynamix Cache DirectoriesDynamix File IntegrityDynamix System InformationDynamix system StatisticsDynamix System TemperatureFix Common ProblemsIntel GPU TopITE IT87 DriverNuvoton NCT6687 DriverSpin Down SAS DrivesTips and TweaksUnassigned Devices/Unassigned Devices PlusunbalancedUnraid ConnectUser Scripts unserver-diagnostics-20250523-0547.zip
May 23, 20251 yr Community Expert May 22 17:15:15 unServer e-suspend[2295899]: Performing sleep operation 'suspend'...May 22 17:15:15 unServer kernel: PM: suspend entry (deep)There's something trying to suspend the server, and the HBA didn't like it, this is not stock.
May 23, 20251 yr Author I do have the Spin Down SAS Drives plugin, but I've had that for years. I just removed it to see if that changes anything. I do not have the S3 Sleep plugin, I have found another thread that referenced that causing an issue.
May 23, 20251 yr Author I found those events in the log and tried to correlate that time to what was happening in the house. I think that is a one off event and I don't see it anywhere else in the log. I currently still have my wired keyboard connected to the server, and sitting on the floor. As dumb as this sounds, I think the keyboard was attacked by my robot vacuum yesterday at 5:15pm.I also forgot that I have syslog server enabled, so I have attached the log from May 1st to earlier today. This version doesn't seem to be as detailed as the one from diagnostics, but it does show the error on or around the first day of crashing that led me to the USB being the culprit. I'm hoping to have someone smarter than me confirm that I am not wasting my time. syslog-10.0.2.26.txt Edited May 23, 20251 yr by brelon attached log incorrectly
May 23, 20251 yr Community Expert Solution May 20 08:59:22 unServer kernel: SQUASHFS error: Failed to read block 0x19ea10f8: -5May 20 08:59:22 unServer kernel: I/O error, dev loop0, sector 849160 op 0x0:(READ) flags 0x800 phys_seg 2 prio class 0May 20 08:59:22 unServer kernel: SQUASHFS error: Failed to read block 0x19ea10f8: -5May 20 08:59:22 unServer kernel: I/O error, dev loop0, sector 849160 op 0x0:(READ) flags 0x800 phys_seg 2 prio class 0May 20 08:59:22 unServer kernel: SQUASHFS error: Failed to read block 0x19ea10f8: -5May 20 08:59:28 unServer kernel: fat_ent_bread: 30 callbacks suppressedMay 20 08:59:28 unServer kernel: FAT-fs (sda1): FAT read failed (blocknr 1707)May 20 08:59:28 unServer kernel: FAT-fs (sda1): FAT read failed (blocknr 1707)May 20 08:59:28 unServer kernel: FAT-fs (sda1): FAT read failed (blocknr 1707)May 20 08:59:28 unServer kernel: FAT-fs (sda1): FAT read failed (blocknr 1707)May 20 08:59:28 unServer kernel: FAT-fs (sda1): FAT read failed (blocknr 1707)These are a flash drive problem
May 23, 20251 yr Author That's what I thought, but this will be my first time having to go through this, so I wanted to confirm before I just throw parts at it. I appreciate your help. I will swap it this weekend and report back.
May 30, 20251 yr Author I replaced the flash drive, and its been a few days now. The server is happy and no more crashing.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.