bioneye

Thank you for the suggestion. I replaced my controller and the SATA cables with a recommended one -> still had errors -> I replaced the power cables for the drives and updated to the newest BIOS for my mainboard -> no more errors and the system is very stable and responsive even on 7.3.0. So either the power cables, the BIOS or a combination of those were the culprit. I am glad to be "online" again, as I have otherwise never had issues with unRAID.

Sorry for the late reply. I currently have no different flash drive until next week when I can buy one. In the meantime I rolled back to 7.2.4. Everything seems to work fine again (like always after a rollback), but I noticed a lot of errors in my log (see attached screenshot). I also noticed, that my Parity-rebuild is really slow, only about 20mb/s. Could maybe this have to do something with "bricking" my server when updating?

Hey everyone, I've been using unRAID for years now and never really had any issues. Updates have always gone smoothly. However, I'm currently dealing with a problem where I can't update from version 7.2.4 without my server basically breaking. Whenever I update to 7.2.5, 7.2.6, or 7.3.0, the WebUI becomes incredibly laggy and unresponsive. I can't stop the array once it's running, and I can't reboot or shut down. Rebooting or shutting down via the console doesn't work either, so I end up having to do a hard reset using the physical power button on the machine. On top of that, if I go to "Shares" and try to open one, the WebUI just loads endlessly and won't display any content. The shares are also not reachable with my PC e.g. I currently have Docker and VMs disabled. If I turn them on, I can access some WebUIs (like Sonarr) to an extent, but then—sticking with Sonarr as an example—it suddenly shows 0 episodes for every single show. The second I roll back to 7.2.4, everything works perfectly fine again. Note: I have currently no Parity configured as I am waiting for the update issue to "be resolved" before mounting the Parity again. I have it not configured, because the Parity disk became disabled and I have to rebuild it again. Second note: I had two Cache pools configured ("Cacheone" and "Cachetwo") and after updating to 7.3.0 "Cachetwo" showed errors. I have since removed the second Cache pool (it's a rather slow SSD I used for overnight backups of remote VPS servers). I have attached the diagnostics and also S.M.A.R.T-Test-Results I did a couple of days ago. unraidimir-diagnostics-20260513-1552.zip [DISK5]ST16000NM000J-2TW103_ZR52K0HG-20260509-1452.txt [DISK4]ST16000NM000H-3KW103_ZYD017KL-20260509-1452.txt [PARITY]ST16000NM000H-3KW103_ZYD014XE-20260509-1451.txt [DISK3]WDC_WD80EZAZ-11TDBA0_7HJSMZUF-20260507-2025.txt [DISK2]WDC_WD80EZAZ-11TDBA0_7SJMS56U-20260507-2025.txt [DISK1]WDC_WD80EZAZ-11TDBA0_7HJYYDNF-20260507-2024.txt

Hi, for me it is the same: I am not using PIA, I am using Mullvad and out of the blue I cannot access the WebUI anymore (btw. the same thing goes for sabnzbd-vpn from binhex). As I was on vacation, I have no idea when this issue started, but I did not change anything...

Hello, thank you very much for this container. I have it encoding my TV shows and movies to H.265 and it works like a charm. I wondered: is it possible to tell HandBrake to ignore music files in the watch folder? Thank you very much in advance and best regards, bioneye

Hello fellow unRAID users, first I'd like to thank the Linuxserver-Team for the great work with this and all the other containers. I have one small question: - Will there be added TLS 1.3 support in the future? If yes, do you have an ETA? Reason behind my question: I would like to use TLS 1.3 for my services running on unRAID. I'd like to avoid creating my own letsencrypt container as I really like the easy-to-use letsencrypt container provided by the Linuxserver-Team. Thank you very much in advance and kind regards, bioneye