Dice81

Hi I had this exact problem and for me it was the usb flash drive. Flashed a new one and now it works. But maybe someone with knowledge should check the diagnostics.

No expert here, but I had the same problem. But i just copied the files over to the new USB and it worked. I also wonder why the usb creation tool dont make a complete usb Flash from the zip.

Got my unraid to work again. It was GluetunVPN that caused the problem.

towerofhallsta-diagnostics-20250609-1704.zip

Hello, I'm not exactly an expert on Unraid or servers in general, but I have some experience, mainly coming from OMV. I dont now where to begin, I have so many strange problems. I built a new server two weeks ago, and everything went fine. I created a pool with one parity disk and another 8 TiB disk. For the cache pool, I have two SSDs — one 1TB and another 3TB (the 3TB SSD has a CRC error). Everything worked well and I installed some Docker containers, and the server ran smoothly. However, after a day or so, the server crashed and I couldn’t access the web UI via the browser. I performed a hard reset and it came back up. A few days later, the same thing happened again. This time I managed to access the UI briefly and saw that there was an issue with the flash USB drive. I followed the guide and replaced the flash USB. The server worked again and I resumed using it. I added more Docker containers and created a custom Docker network — everything worked fine. Later, after doing some reading, I realized that it would be a good idea to place the docker.img file on the cache pool (appdata was already there). I followed a guide where I stopped Docker and deleted the docker.img file. I changed the Docker location to the cache pool, restarted Docker, and reinstalled my containers using the "Previously Installed Apps" feature. I also recreated the custom Docker network using the same name. But now the problems started getting serious. Almost none of the Docker containers are working properly. I occasionally can't access the Unraid server, not even via SSH. SMB stops working on and off, and the tower.local address only works sometimes. After a reboot, it might work for a while. I’ve tried deleting network.cfg, deleting docker.img, and everything else I could think of, but I can’t get it to work optimally. I still get the feeling that there's been a deeper issue from the start. At the moment, I’ve managed to get most containers running using network mode "host", but not all of them. What could be wrong, and how can I generate a diagnostic log? I would be very grateful if someone could help me out.