DCox88

Thanks for the tip on that. I ran the mover and now the docker image is on cache, with libvert being on disk 1

I have a few Docker containers that have pending updates, including Immich, Seerr, Prowlarr, Radarr. When I click Apply Update, it takes a long time to perform and will usually fail to stop the container. After running this process, the Apply Update button is still there. Additionally, Immich, Seerr and Prowlarr have disappeared from my list of containers. This has happened once before with Immich, so I reinstalled the container, and it still shows Apply Update after installation. I have attached logs, a screenshot of my containers and a screenshot of the update process. tower-diagnostics-20260613-1945.zip

Correct, this shows in Safe Mode. I have booted normally, and the issue with dynamix.s3.sleep no longer appears in the logs, but is replaced by this error code: [14-Sep-2025 03:07:33 America/Los_Angeles] PHP Warning: Undefined array key "shareUseCache" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 78 [14-Sep-2025 03:07:33 America/Los_Angeles] PHP Warning: Undefined array key "shareUseCache" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 143 [14-Sep-2025 03:07:41 America/Los_Angeles] PHP Warning: Undefined array key "shareUseCache" in /usr/local/emhttp/plugins/fix.common.problems/include/tests.php on line 114

The error has not appeared again when in Safe Mode. Would that then indicate an issue with the Dynamix System Temperature plugin? Interestingly, there is a different error message, though this one is reporting much less frequently. The previous issue reported every 5 seconds, but this error seems inconsistent with times between the error logs. [13-Sep-2025 22:53:26 America/Los_Angeles] PHP Warning: file_get_contents(plugins/dynamix.s3.sleep/Sleep.php): Failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 69 tower-safemode-diagnostics-20250913-2253.zip

In the phplog.txt, the same error code keeps getting spammed: [09-Sep-2025 18:09:12 America/Los_Angeles] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78 Rebooting clears the log, but it will refill after 6 days. tower-diagnostics-20250912-2325.zip

Based on htop, the top process is consuming a lot of CPU, but I'm consistently hovering around 50% usage. Killing the process causes download speed on qbittorrentVPN to drop, and the process opens a few seconds later. tower-diagnostics-20250908-1918.zip

I have attempted to uninstall the doctor container, including removing the image, but I cannot start the container after pulling it down again. How do I access the directory in order to clear the data from the folder?

Yes. The system had become unresponsive. After completing the reboot, the system seem to detect my files again. Everything seems to be accounted for in my -arr suite.

Thanks for that. ls /var/log/syslog* /var/log/syslog

ls: cannot access 'var/log/syslog*': No such file or directory

I just actually took a look at the connections, and I can confirm that the five drives that encountered errors were all plugged into that controller. I have another controller I'm going to try swapping in, and redoing the parity check with corrections turned off. Going off the last parity check, I guess I'll be back in about 20 hours.

Numerous errors like this - kernel: md: disk1 read error, sector=6074046160 Unraid is still reading the correct disk capacity, but Sonarr, Lidarr, Radarr and Immich are all reporting missing files. It can't be hardware related, as the odds of 4 drives all having physical issues is unlikely. What might have happened, and can I recover my data? tower-diagnostics-20250512-2022.zip

Much appreciated for the information. Yeah, I guess I can understand how you USB would be problematic and maintaining a constant connection, so I think SAS is going to be the way to go. To get a bit more information from you, I am mostly looking to store some drives externally because the size of my array is making it extremely difficult to work inside of the case. What would I need for a deployment of four 3.5 in hard disk drives to connect to my PC via sas?

Care to elaborate?

From what I understand, the primary connection methods are USB, eSATA, and SAS. I have read that USB can be unreliable. I'm planning to have 4x 8TB drives stored externally, and I'm needing advice on the best way to connect them. I am using a ASUS PRIME B660M-A D4, with a Fractal Node 804 case.

Has anyone else had issues with "Getting release from indexer failed" from the Knaben indexer? I have it set up through Prowlarr, and I have tested the connection. Everything is green, but I cannot grab any releases through Radarr.

Steps taken: Unplugged and reseated SATA and power connectors. Rebooted server, errors still present on rebuild. Powered down server, replaced SATA cable with extra one. Rebooted server, errors still present on rebuild. Replaced SATA cable with old one. Disconnected Disk2 sata cable from PCIE sata card, swapped it to SATA port on motherboard with another drive. No errors for Disk2 on rebuild, 8 hour estimate for rebuild. No errors show on the drive that is newly connected to PCIE SATA card, will continue to monitor.

Disk 2 corrupted, and I'm attempting to rebuild. I've only had the drive a few weeks, it's a 4TB WD RED. The rebuild is estimating over 30+ days, and there's errors and warning messages appearing on the drive in question. The errors that concerned me were: Oct 4 20:29:03 Tower kernel: ata12.00: exception Emask 0x10 SAct 0xf0000 SErr 0x49f0000 action 0xe frozen Oct 4 20:29:03 Tower kernel: ata12.00: irq_stat 0x00400000, PHY RDY changed Oct 4 20:29:03 Tower kernel: ata12: SError: { PHYRdyChg PHYInt CommWake 10B8B Dispar LinkSeq DevExch } Oct 4 20:29:03 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Oct 4 20:29:03 Tower kernel: ata12.00: cmd 61/40:80:80:d5:6a/05:00:00:00:00/40 tag 16 ncq dma 688128 out Oct 4 20:29:03 Tower kernel: ata12.00: status: { DRDY } Oct 4 20:29:03 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Oct 4 20:29:03 Tower kernel: ata12.00: cmd 61/40:88:c0:da:6a/05:00:00:00:00/40 tag 17 ncq dma 688128 out Oct 4 20:29:03 Tower kernel: ata12.00: status: { DRDY } Oct 4 20:29:03 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Oct 4 20:29:03 Tower kernel: ata12.00: cmd 61/40:90:00:e0:6a/05:00:00:00:00/40 tag 18 ncq dma 688128 out Oct 4 20:29:03 Tower kernel: ata12.00: status: { DRDY } Oct 4 20:29:03 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Oct 4 20:29:03 Tower kernel: ata12.00: cmd 61/68:98:40:e5:6a/02:00:00:00:00/40 tag 19 ncq dma 315392 out Oct 4 20:29:03 Tower kernel: ata12.00: status: { DRDY } Oct 4 20:29:03 Tower kernel: ata12: hard resetting link Oct 4 20:29:04 Tower kernel: ata12: found unknown device (class 0) Oct 4 20:29:04 Tower kernel: ata12: SATA link down (SStatus 0 SControl 310) Oct 4 20:29:05 Tower kernel: ata12: hard resetting link Oct 4 20:29:10 Tower kernel: ata12: found unknown device (class 0) Oct 4 20:29:11 Tower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 4 20:29:11 Tower kernel: ata12.00: configured for UDMA/33 Oct 4 20:29:11 Tower kernel: ata12: EH complete tower-diagnostics-20231004-2040.zip