daysis

I'm running into a problem on my server getting docker and VM's to start. Yesterday all of my docker containers and VM's hard crashed and I wasn't able to get them restarted. Every time I tried I got a generic 403 error and neither the containers or VM's would start. I tried to reboot my server a couple times and the docker service fails to start. It currently look like the the VM's are working but It took a couple reboots and I'm pretty sure my Windows ones got corrupted. I've had a similar issue in the past and rebooting the server always fixed it, but it hasn't any more. Because I've had similar issue docker containers before I swapped over to a new flash drive around 2 weeks ago. This is the first time I've had an issue on the flash drive. I have two 32 Gb sticks of ram in my server and I booted the server with one stick in at a time to see if it was a ram issue. It didn't appear to have any impact. I've attached a diagnostic file that was taken right after reboot when the docker services failed to start. lab-diagnostics-20241117-1406.zip

I'm not sure if this is the thread section or not but I'm having a weird issue with my Windows 11 VM. I'm studying for an IT certificate and I wanted to spin up a VM to work out of. The study plan I'm following has you download docker desktop. Every time I try to install docker desktop my windows image corrupts upon reboot and I'm unable to recover it. Is this a known issue/bug or I am trying to do something that everyone knows shouldn't work and I'm just unaware?

Yes. I currently have it sending to a remote syslog server. I can set it to use a local syslog server/mirror to flash if that would help

I did a scrub, it reported no errors. I've attached a new diagnostics log taken after the scrub. UUID: e84b215c-ffa0-4bb3-b44e-0014f1480711 Scrub started: Wed Jan 10 20:20:09 2024 Status: finished Duration: 0:07:47 Total to scrub: 485.18GiB Rate: 1.04GiB/s Error summary: no errors found lab-diagnostics-20240110-2228.zip

Yes! I had already started the array so I stopped it, restarted it and then pulled the logs Thank you for helping me with this! lab-diagnostics-20240110-2205.zip

I ran the memtest from memtest86. I did the default test and it passed without any errors after 4 iterations. I also ran the SMART extended self-test on both of the drives in the app_data pool and both drives passed without any errors. I've attached the memtest result I ran last night. I did end the test a little early on the last pass which is why the Test complete shows 46/48 but it passed them on the other three passes and I wanted to end it before I went to bed. MemTest86-Report-20240110-002643.html

Hello! I'm new to the Unraid ecosystem and I'm running in a problem I can't solve or intentionally recreate. I'm not sure if it's bug, something wrong with my Unraid Config or a Hardware issue. My System will become totally unresponsive and I can't can't figure out what's causing it. My network connection to the server will suddenly drop and I'm not able to connect. At first I thought it was a network issue but I'm not getting output when I direct connect a monitor to the system either, and any I/O devices I connect to server don't work when I plug them into the server after it enters the failure state. The system doesn't lose power. The only way I have found to recover the system is a full power reset. The issue appears to happen at random intervals between ~8 hrs and ~48 - 72 hrs. I have not ran into the failure state right after rebooting and my system hasn't lasted longer then three days with hitting it. I can't think of anything I do to cause to stop working. Twice the server was working when I went to bed and failed before I woke up the next morning so I wasn't making any manually changes that could have triggered it. I have preformed a memory test that I saw mentioned in a different thread and it completed four passes with running into any errors. I have attached two log diagnostic Zip files and two text files containing the syslog information from the server. After the server crashed a couple times I set it to send it's syslog's to a remote server. The files from 01/09 were gather pretty quick after the incident occurred, the files from 01/10 were gather about ~9 -10 hours later when I found the server in the failed state when I got home from work but it was right before posting this so I thought I'd include it. Unraid version: 6.12.6 Thank you for taking the time to look at this! lab-diagnostics-20240109-1732.zip lab-diagnostics-20240110-1719.zip Unraid_Syslog_1009.log Unraid_Syslog_1010.log