Kev600

Update - I replaced my SAS > SATA Cabling and updated to Unraid 7.2.4 > 7.2.6 and subsequently 7.3 and the server remains stable, with a massively reduced number of I/O related read errors on the SSD during the first Parity Check .... Subsequent Parity checks have shown ZERO read errors.. I still cannot really understand how Unraid got itself all messed up and becoming non-responsive - but I reseated my RAID card, and GPU when I changed the cabling; and rebooted cleanly after the first boot. (Still using USB to boot). I'm not sure whether using Duplicati had any impact on the Unraid server becoming non-responsive - It still seems to heavily load the CPU cores, despite me pinning two cores to that Container. (That seems to be ignored) - I've read how the CPU Scheduling could be conflicting, and it's better to leave all cores available for it. But - the error was 'Duplicate Default Server' - Which appeared to correlate with a new router being fitted - But I see there are fixes around dhcp in Unraid 7.3.1... (Although I'm not using dhcp!) Anyway - all is fixed and my server is running and responding well, remotely, from Thailand! ;) >>Different topic entirely but - Has CA gotten worse for failed updates/dangling images? 75% of my containers fail to update successfully, unless I manually pull an image from Terminal. And - That new Disk Talkers plugin, is AMAZING! :)

Thanks @JorgeB kbnas-diagnostics-20260514-1126.zip

Hello! I'm running an old ML310e - with 8TB Parity, 8TB/3TB/3TB Data + 4 bay 2.5" caddy, with 2* 1TB mirrored SSD Cache pool, and a 4TB SSD which I added to the Array (about 9 months ago), for faster NextCloud/Immich/Other app service. I regularly get I/O errors when running parity check on the 4TB disk - Always 856 Read errors - yet different sectors are reported. In general, there are no issues with the NextCloud/Immich services... but I am wondering if I'm playing with fire using the 4TB as part of the Array. Lately, I've had all kinds of issues with my Unraid installation; with Docker and nginx being unresponsive, (Duplicate Default Server - as per known issue) and nothing working even when executed via SSH; such as 'reboot', which says it's restarting, but doesn't. I'm not happy about the number of times I've needed to hit the power button to reboot... last night it hung trying to download the diags.. I have upgraded from 7.2.4 - 7.2.6 and it didn't help. Today I pulled out the RAID card for the 4 bay 2.5" disks, reseated it, and the cables. Since rebooting, it seems stable again, and docker apps are fine - But yes, 856 read errors still thrown on the 4TB SSD; which will not repeat if I run the Parity check a second time. It was running absolutely fine at my old place, but needing to move out, I migrated my server to another location - It was also running fine here; until the broadband was changed to FTTP... Then, even though the network config was the same, this is when the issues with nginx/docker started to get non-responsive, on 7.2.4. I'm about to go away for a while and I'm just looking for stability and functional availability of Unraid - I've had more success with Tailscale, than Unraid Connect, which sometimes works and sometimes doesn't. I appreciate this isn't particularly technical - and will upload diags if it goes all non-responsive again.. ;) Cheers guys, Kev

Thanks @SimonF I have a Nvidia Quadro P2000. I use it for transcoding, but wanted to try a PopOS Gaming VM also.

Ah that's disappointing... Thanks for the reply @SimonF

Hey, If I use the 'Bind Selected To VFIO At Boot' option for GPU/Audio, as referred to HERE; Will this prevent my Immich & Emby Servers from accessing the GPU for Transcoding? Or will both my VM, and Unraid Apps be able to share the GPU? (UR 7.1.2) Thanks! Kev

Don't know why I didn't think of this! I recently had a load of I/O errors after adding a new drive to my 4-bay icydock.. I reseated the power connectors and data cables and so far, it's been good since. Puzzles me how a running system can develop a bad connection like that..

I experience this behaviour too with Immich updates. I just repeat until it shows no updates available.

With over 6 years of usage and increasing errors, it's probably time to replace that drive. It might be possible to run a bad-blocks check and reformat, to limp along another year or so - depending on what data/usage that drive has. Treat yourself to a bigger drive mate.. (Matching or less than your Parity capacity, if using it in the array).

Oddly - I needed to manually start the Borg backup container. After that, everything else came up good - no data loss, and no need to restore from backup. Bottom line - Do NOT interrupt the browser (AIO Console) when it's running the update..

Progress made - I didn't think this would do anything, since I had tried rebooting my whole UR Server.. ..but I logged into the AIO Console, then manually stopped all Nextcloud containers in UR/Docker... After refreshing the AIO Console, once again, it told me that updates were ready to install. So I clicked the button to update and start containers. This has created a new nextcloud-aio-nextcloud container. At the moment, some auto backup process is pausing the database>nextcloud>apache>notify push containers, in that order; from starting. Essentially, I refreshed the AIO Console page a few minutes into the updates, the first time around - this is what I believe, caused this problem.

Does anybody else have a dead Nextcloud install following the upgrade to 10.13? Backup/Restore options are not available! Nextcloud log page shows 'Slim Application Error' The Nextcloud container has been orphaned!! Please can someone advise how to resolve this? Thanks Kev

Nope. I've lost my folders trying to resolve this. 🤣 Hopefully the new release will get pushed to CA Apps very soon.

Oh - I understood it to create the db as part of the Zipline set up.. Thanks!

Good catch!! Progress!! I'm now getting this; PrismaClientInitializationError: Database `zipline` does not exist on the database server at `192.168.0.140:5432`. at t (/zipline/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:112:2473) { clientVersion: '6.1.0', errorCode: 'P1003' } Removing and reinstalling...