sahuff2

I've been having issues with my unraid server not shutting down or rebooting when given the command. I've used the buttons on the dashboard, the buttons at the bottom of the Main page, and terminal commands. I've also tried short-pressing the power button, and while it says it is shutting down, it never does. The only way I can get a clean shutdown/reboot is to manually disable Docker and stop the array. This is a new issue, and it has shutdown fine for me in the past. Something is obviously hanging, but I can't figure out what it is. If I'm looking at the Web GUI, it will say Array Stopped Syncing Filesystems, but I've waited 30+ minutes and it never completes. I have to force power off, which is giving me unclean shutdowns. Things that have changed recently: I've setup FileFlows to process video files, and it's setup to send/receive files from the server to the nodes. I've tried stopping the FileFlows docker before shutting down, but that doesn't change anything. Could the file transfers be causing the shutdown to hang? Is there a script I can run to make sure everything is stopped at shutdown? I've also installed a 10G SFP+ network card, but this was happening before that was added. I've attached my diagnostics file. Can you take a look and see if there are any obvious issues that could be causing this problem? Thanks. tower-diagnostics-20250817-1520.zip

I have an unraid server that was built in a PC case that held 8 drives. They are connected either on the motherboard SATA ports or by an SATA HBA card. I later added a Mediasonic Probox external USB enclosure with a couple more drives (I know...not recommended and I might be paying the price now). Anyway, all of my array data disks and one parity disk were internal so their drive identification/name in the array list correctly showed the serial number. I added a second parity disk later and it was in the external enclosure (probably a mistake). It is reading the serial number and drive data correctly when I look at the drive details, but the ‘Identification’ in the array list has weird formatting from the enclosure. It looks like this: ST20000N_M004E-3HR103_152D00539000-0:0 - 20.0 TB . Like I said, when I look at the drive details, it correctly shows the right serial number and smart data. I'm wanting to eliminate the external enclosure completely. If I move the second parity disk (that’s in the external enclosure) into an internal slot on the HBA card, will the weird formatting of the drive name mess things up when I reassign the drives to their spots? Or will it read the serial number correctly despite the weird name formatting the external enclosure is adding to the name? All I’m wanting to do is remove the drive from the external enclosure and put it in the PC case with the other drives on the HBA card. What is the best way to do this to ensure that I don’t mess up my data? Can I just reassign the same second parity disk to that parity slot and it will rebuild the parity leaving my data okay?

I am trying to setup a new Wireguard VPN connection. I have existing connections that I've setup in the past with no issues and they are still working. I first tried to 'Import Tunnel' and load the config file. The page refreshes, but there's no new connection added to my list. I thought it was odd, but thinking maybe something was wrong with the config file, I clicked on 'Add Tunnel' as if I wanted to setup a new VPN connection. It still won't add a new connection in my list. I've restarted the server and updated the OS to the latest stable version (6.12.13), but this didn't change anything. Does anyone know why it will not allow me to add a new Wireguard connection? I've attached the diagnostic file. Thanks. tower-diagnostics-20240831-2100.zip

I think I figured my problem, finally. I will post my solution in case someone else has similar issues. I KNOW I setup the Plex container to use the Intel iGPU when I installed it (100% did it because it intially worked without issues for weeks), but somehow the settings were cleared in the advanced docker settings and it was doing full CPU transcoding, which was throwing errors in the log with the x264 encoder (new errors that weren't in the original log I posted). I was also getting Plex Transcoder segfault log messages. Thinking that it might've been bogging down the CPU, I began by limiting the CPU cores in the docker setting to four cores and it stopped locking up. But then I discovered the iGPU wasn't being used at all for transcoding!! I followed this guide and re-enabled the iGPU and it seems to have fixed my problem. Thanks for looking at my log/diagnostic and helping me. I'm glad it ended up being something that I inadvertently caused and my hardware is okay.

I did what you recommended and disabled all docker containers, and so far I'm nearing two days of uptime. This is definitely an improvement, but I will let it run it a little longer to test it. I'm happy this is starting to suggest it is a docker container and not hardware problem, but I know that will take more testing to confirm. I will update this post when I discover the culprit causing my problems. Thanks for the reply.

I built my first unRAID system about six weeks ago, and I've been having issues with it becoming unresponsive, sometimes multiple times per day. I know when it happens because I get the notification that my Nextcloud can't connect. I try to go to the web GUI and there's no response. I've tried pinging it from my computer and get no response. When I go to the machine, it is still powered on but there's just a blank screen on the video output. I have to do a hard shutdown and reboot, which I know is not ideal but it never responds otherwise. I've not found any obvious or consistent cause, but I'm new at this so I'm hoping someone else may be able to see a problem. I turned on the system log output to the cache drive last month, so I'm attaching the entire cumulative log along with the diagnostics file. This is frustrating because I actually built two systems, and this is the one I bought "better" parts for but it's the only one that I'm having trouble with. System info: i7 14700k, 128GB DDR5 RAM, two 1TB NVME cache drives. I'm running roughly 15 docker containers (Plex, Nextcloud, the Radarr/Sonarr type apps, etc.), but I haven't set any VMs up yet because the stability is not great. At idle, the CPU is running 2-4% and the RAM is only at 4% so it's not being stressed at all. (The other machine I built is using an Aliexpress motherboard/CPU combo and it is rock solid, staying on for days and days without lock ups. Go figure.) I ran the memtest86 overnight on my main machine and it passed. I'm reading that maybe I should run that longer to catch any RAM issues. I've installed Fix Common Problems plugin and it didn't find any errors, but I wanted to see if there's anything obvious in the log/diagnostic file. I'd appreciate if anyone could take a glance at these files to see what's going on. tower-diagnostics-20240330-1828.zip unraid_log.txt