brelon

I replaced the flash drive, and its been a few days now. The server is happy and no more crashing.

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.

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

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.

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 problems ASRock B760M PG Lightning/D4 Intel i5-12600k 32GB Ram Cant remember what PSU, but I think its a Corsair. I will get model if its necessary 10 disks w/ single parity 1TB Teamgroup NVME for cache Cruzer Glide 16GB USB Plugins: GPU Statistics Unassigned Devices Preclear Appdata Backup CA Auto Turbo Write Mode CA Auto Update Applications CA Cleanup Appdata Comunity Applications Dynamix Auto Fan Control Dynamix Cache Directories Dynamix File Integrity Dynamix System Information Dynamix system Statistics Dynamix System Temperature Fix Common Problems Intel GPU Top ITE IT87 Driver Nuvoton NCT6687 Driver Spin Down SAS Drives Tips and Tweaks Unassigned Devices/Unassigned Devices Plus unbalanced Unraid Connect User Scripts unserver-diagnostics-20250523-0547.zip