RLA113

Sorry for not following up. Took me multiple attempts to fix the issue and a while to troubleshoot and forgot about the thread. Tried changing over to ipvland, but did not fix the issue. I noticed when I could catch the fault quickly, the flash drive would be really hot. So I took a USB extender cable (like the ones that sometimes come with wireless mouse), and placed it away from the back of the case. Now it is staying cool and not having issues. Thinking the exhaust heat was causing the flash drive to heat up to where it was shutting itself down to save itself. My server does not run too hot. Motherboard under 40c and CPU under 60c most of the time, but when the heat from my A2000 GPU started porting out the back it think it was just too much. Since moving it away from straight attached to the motherboard, I have not had the issue. Hope this helps anyone else that might notice their flash drive getting hot.

Sounds good. I will change over to ipvland instead of macvlan. Running ECC memory so hopefully that is catching an faults.

Got a crash overnight. Was logging the syslog to a remote PC and attached. Let me know if there is anything I can do to help fix this issue. syslog

No, not sure the flash drive is the issue, just the symptom at this point. I have enabled syslog server and will post when I get another crash. Thanks for the reply and help!

Past few months I have been having issues with my USB getting corrupted and locking up Unraid. The server stays on, but is unresponsive. Power button reboot only to have the USB not be detected by the boot loader/BIOS. I have tried different USB ports on my tower, different USB flash drives (both Samsung) and the problem keeps persisting. After the crash I take a flash backup and restore it to the same USB and everything works for a few days to a few weeks, then out of the blue, it gets corrupted again. No major changes recently to my unraid setup. I have no idea what my next steps are for troubleshooting the issue. I am going to try a third USB flash drive when it arrives (Lexar brand 64GB 2.0) and see if that helps. I have also started logging the syslog to a networked computer that I will leave on all the time for now to get the log. Can post that when it happens again. Any help on next steps or what might be causing the issue would be greatly appreciated! jarvis-diagnostics-20230805-0623.zip

I uninstalled the old, installed the new. Made sure all paths were correct, tried to run a backup and nothing happens when I click the button. Waited several minutes to see if the 60 second timeout on apps was the issue. Uninstalled the new one, installed the old one again, and everything seems to work, backup is running right now. Not sure if anyone else has experienced this, please point me in the right direction if someone has.

Sounds like a good plan. Backup up what little I have on the drive. I already back up the AppData once a week in case of this failure. Then I will run a scrub. If that does not work, I will reformat. Thank you again for all the help!

Agreed, corrupted RAM should never be used. I took the corrupted dimm out. Running on only a single channel right now, until my order shows up. Then I will remove the single channel and add the two new sticks. Going to see if I can RMA the memory sticks, only got it in September.

Awesome, thank you for the advice, I did have a dimm that failed memtest. Other dimm passed. Have the cache drive in read only mode still. Not sure if the memory corrupted it.

I have tried to read-up on what might be happening. It appears that maybe my cache is corrupted? But I have a hard time diagnosing that is the problem. The message I get in the docker tab is this: [[ Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 967 ]] When I download the diagnostics, it appears that everything is okay, except that the cache drive is in a read-only mode. Not sure how it got that way though. Any help would be appreciated. Attached the diagnostics. jarvis-diagnostics-20221130-0656.zip

Probably going to go with ECC memory this round

Hey all, thank you very much for the help in diagnosing this issue. Turns out after running the memtest, it almost immediately found problems with the memory. Have two sticks on the motherboard. Took one out, and the stick left ran just fine. Confirmed that it was the memory stick by swapping the good stick into the slot that was bad, and memtest ran just fine. Also put the bad stick in the good slot, and it found problems within 30 seconds. Just bought the ram 4 months ago, upgrading from 16GB to 32GB, so trying to get an RMA going with G-skill, to get a replacement. Luckily with 32GB and two sticks, I can run off the 16GB for a while while trying to get a new ram stick. (I sold the 16GB pair.) I run a weekly backup of the appdata on the cache drive and is the only thing I keep permanently on the cache, so not much lost after a format of the cache and a restore of the appdata. After all of this, I am hoping my system is back to normal operating. Thank you again for all of the help troubleshooting.

Awesome, thank you for the help! I will run memtest, if that does not work I will backup cache and recreate.

Here you go. jarvis-diagnostics-20210202-1239.zip Thank you for the quick reply! Let me know if there is something in the zip file I should be looking for.

My cache pool thinks it is running a 1.5TB drive, but hardware of the drive is 1TB. All is in RAID 1 on the pool. I have setup a lower threshold to warn me. How do I fix the Cache drive to only see the pool as 1TB vs 1.5TB? Or some magical way do I have 1.5 on the pool? Any help/advice is appreciated.