June 13Jun 13 I updated from 7.2.4 to 7.3.1 yesterday. The update process seemed to go fine, but upon restart it reported errors on my second cache pool drive (which is made of 2 NVMe drives on a Supermicro riser card installed on a Supermicro X12SPi-TF motherboard) that had not been reported previously on 7.2.4.None of the Docker modules in the Arr stack (Prowlarr, Sonarr, Radarr) would start and gave an Execution Error - Bad Parameter. They were also listed as having invalid IP addresses.Diagnostics are attached.Any help appreciated. I have successfully reverted to 7.2.4 (I had the same problem with 7.2.7) but obviously cannot stay on that version forever.Many Thanks.Kevintower-diagnostics-20260613-1236.zip Edited June 15Jun 15 by kolepard problem solved
June 14Jun 14 Community Expert Let's start with the pool, one of the devices reporting corruption errors, also the docker image, start by scrubbing the pool and post the result from the GUI.
June 14Jun 14 Solution I had this same problem when I first updated to 7.3. It was caused by me using --net=container:<vpn container name> in extra parameters to route containers through another container. This no longer appears to work in 7.3+ (at least not for me). I had to remove this extra parameter and instead set Network Type to Container and below that set Container Network to the VPN docker that I want it to route through.
June 14Jun 14 Author @wgstarks Thank you! Editing the docker settings by setting "Network Type" to "Container" and then setting "Container Network" the "binhex-deluge-vpn" solved this problem! All Dockers are now working normally again.@JorgeB I ran scub twice once under 7.2.4 and a second time under 7.3.1. The results appear the same.Scrub result under 7.2.4UUID: 6b450441-1d2d-4b45-ab90-434d50d5cc7cScrub started: Sun Jun 14 08:07:15 2026Status: finishedDuration: 0:00:37Total to scrub: 186.42GiBRate: 5.04GiB/sError summary: no errors foundScrub result under 7.3.1UUID: 6b450441-1d2d-4b45-ab90-434d50d5cc7cScrub started: Sun Jun 14 08:53:02 2026Status: finishedDuration: 0:00:46Total to scrub: 281.30GiBRate: 6.12GiB/sError summary: no errors foundI also ran an extended SMART self-test on the NVMe drive that was reporting errors; that report is attached.Thank you @JorgeB for your help with this.Kevin tower-smart-20260614-0911.zip
June 15Jun 15 Community Expert Since no errors were found, clear the stats for the pool and keep monitoring, they are likely old errors.
June 15Jun 15 Author @JorgeB I will clear the pool state then.You mentioned a docker image problem, too. Are there additional steps I need to take with respect to that?Thank you.Keivn
June 15Jun 15 Community Expert If the containers are working fine it should be OK, but you can also recreate the Docker image to correct that.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.