Dreadino

The test is still running, but it doesn't look good. What would be the next steps in this situation? New RAM? ECC?

I did and tonight, seemingly after the CA Appdata Backup run, the server became unresponsive. No web ui, no ssh, no video output when using its monitor (which is not always the case). Note: I wanted to upload the backup.log for CA Appdata Backup, but it was not created and only a handful of apps were backed up, despite the backup being marked as successful (or at least, not being marked as failed). I guess the crash occurred during the process. Edit: I'll throw in diagnostics taken right now. Edit2: I'll add that the docker page is acting up now. It take a loooong time to load, there are no folders (I use the folder plugin), it shows "ghost" containers and when trying to update a container it fails telling me docker: Error response from daemon: Conflict. The container name "/qbittorrent" is already in use by container "b3726b12ae7aace567cce16d0fbbe34a69c3f2d817e3610136557834b2104f9f". You have to remove (or rename) that container to be able to reuse that name. See 'docker run --help'.. I had this 2 days ago and even after trying all the tricks I found to stop the array, something was still clinging to /var/lib/docker/graph, not allowing the array to stop. syslog-192.168.0.30.log nickfury-diagnostics-20241218-0659.zip

This is happening basically daily, for the last 10 days at least. Server works well, then all of a sudden in becomes unreachable, even using the monitor attached via hdmi. In one of the previous crashes, I was able to see the mode after a long freeze, opened the terminal in the ui, but it was not working. I’m pretty sure i also had a crash when the os was not in ui mode and the command line was not responding either. I also tried SSH, but it is not working. My only option is a hard reset at that point, but this already created a lot of problems with storage becoming unmountable. I’ve attached diagnostics taken seconds after the restart, I’m not sure Unraid saves data from previous the crash. nickfury-diagnostics-20241214-1503.zip

I decided to try with raid0 instead of mirror for the pool, so I stopped the array and changed it. When I restarted the array, the SSDs were working, but in mirror. I have no idea what happened, but I'm checking if they're actually working. Doesn't seem to be working, I'm receiving a lot of these when reinstalling my docker containers: rc.docker: homepage: Error response from daemon: error creating overlay mount to /var/lib/docker/overlay2/13f8978548b9d019912dc8c7b8fca926b4f3fec0e0f4bf44aa85a30d7bfcd5d7/merged: no such file or directory

Done nickfury-diagnostics-20241212-1636.zip

I stopped the array, formatted both SSDs via the Unassigned Device plugin, reassigned them to the pool. Now I see a partition format of "MBR: 1MiB-aligned", but they're still unmountable. nickfury-diagnostics-20241212-1622.zip

I have a pool with 2 Samsung SSDs. They were formatted in brtfs, after a hard reset they became unmountable. I reformatted them in zfs. Still unmountable. I then precleared them. Still "Unmountable: Unsupported or no file system", while showing "zfs" under the FS column. I've also attached a screenshot of the cache settings. I'm not sure what my next steps would be. nickfury-diagnostics-20241212-1516.zip

Will this remove the data on the SSDs? EDIT: performed the scrub, this is the status UUID: 0c6ff596-13dc-449a-bc07-06cbc7e94c13 Scrub started: Sun Nov 17 13:56:09 2024 Status: finished Duration: 0:00:32 Total to scrub: 143.97GiB Rate: 4.50GiB/s Error summary: no errors found

Last few days were rough for my Unraid server. Day 1: it started with a container (Manyfold) that filled the docker.img (by unzipping multigigabyte files in a temp folder inside the image), locking down the entire system. I solved by backing up the .img, then changing the docker setting to folder. Rebuilt my containers via the "recent apps" function. Day 2: I woke up to all some of my containers not starting up after the backup, error 403. Restarted Unraid, seems solved. Day 3: after a failed Appdata Backup (error 403), I woke up to the SSD pool not mounting. Formatted the pool, and started again. Rebuilt my containers via the "recent apps" function, recreated my VMs, restored everything via backups. Changed the problematic container temp folder to be a share on the array. Day 4 (today): woke up to an unreachable web UI for Unraid, but my Home Assistant VM was running perfectly (and was reachable). Restarted Unraid, the array and cache pool seems fine, but all my containers are gone. Appdata is still there. I'm not sure what happened. At this point, I'm not sure what to look for. I will rebuilt the containers again via "recent apps", but it's not something I can do everyday. The docker directory in /mnt/share/system seems fine, the "containers" folder is full of folders, the volumes seem to be all there. I'll attach the diagnostics I run a few minutes ago. nickfury-diagnostics-20241117-1002.zip