Scheev

Hello, I've been noticing more and more that my server seems generally unstable. My intuition tells me its related to my USB as its a USB 3.0 and as time has gone on I can't go more than a few days without things cropping up and having to restart. Most recently in no particular order, these issues have come up and going away after a restart. Unraid GUI being unreachable (this seemed like a plugin problem) Unraid GUI not serving me all the tabs. they are reachable but just blank. Followed by these errors in my syslog. Server nginx: 2023/11/25 19:22:46 [crit] 3437#3437: *375050 pread() "/usr/local/emhttp/webGui/styles/default-white.css" failed (5: Input/output error) while sending response to client, client: 10.0.0.70, server: , request: "GET /webGui/styles/default-white.css?v=1692979133 HTTP/1.1", host: "192.168.0.69", referrer: "http://192.168.0.69/Dashboard" Server kernel: SQUASHFS error: Unable to read fragment cache entry [101f4a8c] Server kernel: SQUASHFS error: Unable to read page, block 101f4a8c, size 2d04 Server nginx: 2023/11/25 19:22:46 [crit] 3437#3437: *375065 pread() "/usr/local/emhttp/webGui/styles/default-white.css" failed (5: Input/output error) while sending response to client, client: 10.0.0.70, server: , request: "GET /webGui/styles/default-white.css?v=1692979133 HTTP/1.1", host: "192.168.0.69", referrer: "http://192.168.0.69/Dashboard" Server kernel: SQUASHFS error: Unable to read fragment cache entry [101f4a8c] Server kernel: SQUASHFS error: Unable to read page, block 101f4a8c, size 2d04 Alot of messages that look like the following in my syslog Server kernel: SQUASHFS error: xz decompression failed, data probably corrupt Server kernel: SQUASHFS error: Failed to read block 0x10079bf0: -5 Server kernel: SQUASHFS error: Unable to read fragment cache entry [10079bf0] Server kernel: SQUASHFS error: Unable to read page, block 10079bf0, size 829c Dockers being completely unresponsive and the full context menu not appearing when trying to open webGUIs on them. SMB just straight up crashing Maybe im on the right track with the USB? I have a 2.0 USB on order to eliminate that possibility. Ive checked the USB for any errors on windows and nothing stands out. Any help or thoughts is appreciated! server-diagnostics-20231126-2256.zip

Parity is always a good idea for data safety. Unraid stores the docker data in a share folder called appdata, if you want that backed up then parity is important. Same with the array data. But if all that data was suddenly gone and that doesn't bother you then its risky but could be done The beauty of unraid is mix and matching sizes and types of drives into an array, so you could conceivably have a mix of SSDs in the array and it wouldn't really matter. A cache is useful for ssd -> hdds because when you download a movie or tv it can be done initially to the cache. Then later moved when you are not accessing it. Thus speeding up the process by writing to the cache first and moved later. In terms of all ssds? maybe not as useful. Maybe could be setup to go nvme -> SATA ssd? smaller benefit but still useful. Now a few TB of SSD storage right now might seem like a lot of storage but I could forsee that becoming a problem down the road as you accumulate shows/movies because the arr suite makes it dead easy. So I would consider rethinking how much storage you would want for a media server. My advice: Definitely have a parity drive, and increase the storage capacity.

Thanks! I did end up doing essentially this with the boot USB. But didn't go through the trouble of restoring a few files at a time to discern the culprit and opted to just wipe my settings and plugins to restore functionality. I have suspicions about what happened though, I believe there were some updates on plugins that likely hadn't quite finished yet when I rebooted. More importantly I think the nvidia driver plugin may have been interrupted, and I think that it may have cause the issue I was seeing. Hard to say specifically. For anyone who finds this post later. In order to start fresh without losing all data, I only carried these files over from the config/ folder to my boot usb that was wiped fresh with the unraid utility. *.key files super.dat /shares /pools /plugins/dockerMan/templates-user/*.xml These are the docker configs After I did that all my data and docker containers were correctly restored after rebooting. I just had to re-add my plugins and update settings. Otherwise all shares were there properly.

Update: When I create a new USB config and don't copy over my old one, I am able to access the GUI so there must be a problem with my config file but I have no idea what the problem is.

Hello, I've tried scouring these forums for solutions, but I feel like its a cascading issue that I am now out of my depth in. Essentially some dockers were getting server errors and wouldn't start at all. So I figured okay, quick reboot and we will be back! Wrong. Wouldn't boot at all after that. Wouldn't show the boot messages at all, it would get past the mobo startup and thats it. So I tried the following steps to debug this. 1. Saved my config and reflashed It booted and got to the IP display. But the gui was inaccessible via LAN, weird, but okay. 2. Tried to boot into the GUI on the server This properly showed the boot sequence as before, but now when the GUI launches its just a blinking cursor in the top left. Okay odd. 3. Maybe this is just a network issue? Removed the netowrk.cfg and the DHCP reservation in my router. Nothing, didn't help, it has a new IP but GUI is still not accessible. 4. Cut power and did a hard reboot Still no change. So here I am, I suspect there is something wrong with the nvidia drivers? not exactly sure, I see these new messages when booting. I am running a 1660 super. mv: cannot stat '/usr/local/bin/mover' : No such file or directory xz: (stdin): Compressed data is corrupt modprobe: FATAL: Module nvidia not found in directory /libmoudules/6.1.49-Unraid Any help is appreciated on where to go with this. I have also attached my diagnostics. tower-diagnostics-20231101-1025.zip

I actually had a really similar problem but disabling fastboot wasn't fixing it. Disabling Secure Boot did fix it for me, hopefully this helps someone.