russdyer77

great thanks.

Is it abnormal for a docker.img file to be 100+gb? Mine is 107gb and I'm seeing some posts where the limit should be 20gb or so? Should I start over? I started using the AppData Backup plugin - assuming I could just stop the Docker service, rename docker.img, start service, use previous apps to reinstall dockers? I had the "docker" folder with the docker.img under the "system" share - do others create a "docker" only share to limit the size of the docker vdisk? Am I better off switching to directory mode instead of using a docker.img? Thanks, Russ

ok great, thank you for the info.

phew...nvm, I figured it out - luckily I didn't wipe the old cache drive. it seems the move operation must have been incomplete - I was able to rename the old docker.img and libvirt.img and copy them into place and now they are both working! Thanks, Russ

I had an issue with one of my drives in a cache pool so I: closed down docker & VM Moved all from cache to array Removed and erased the existing cache pool (it kept failing when replacing with other drives) Created a new cache pool with two new drives, did a move operation from array back to cache for system, domains, app data Even though the files are in the same place both docker and VM manager show no data? Did I screw up by removing the existing pool (even though it's named the exact same)? Can I fix this? Thanks, Russ

Thanks, I'll try that.

I purchased some recertified drives online and this is the second time this drive has failed (Disk2)- attaching diags. Can somebody look to see if the drive is just dead or if maybe it's the bay it's installed in? I have running in a used SuperMicro server backplane. Thanks, Russ unruss-diagnostics-20250521-2313.zip

The only solution I didn't try fixed it - it seems the immich REALLY wants to run on port 8080 and not be redirected to another port. I changed my other conflicting container to use a different port than 8080 and gave Immich 8080 and it worked, very strange.

Are others having issues just getting the WebUI to load? I have another container on 8080 so changed the WebUI port to 8079 (or anything else) and it won't load. When looking at the log, everything looks good. text error warn system array login Connection to localhost (127.0.0.1) 2283 port [tcp/*] succeeded! [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/tags/:id/assets, PUT} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/tags/:id/assets, DELETE} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RoutesResolver] TimelineController {/api/timeline}: [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/timeline/buckets, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/timeline/bucket, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RoutesResolver] TrashController {/api/trash}: [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/trash/empty, POST} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/trash/restore, POST} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/trash/restore/assets, POST} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RoutesResolver] UserAdminController {/api/admin/users}: [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users, POST} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users/:id, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users/:id, PUT} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users/:id, DELETE} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users/:id/preferences, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users/:id/preferences, PUT} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/admin/users/:id/restore, POST} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RoutesResolver] UserController {/api/users}: [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/me, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/me, PUT} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/me/preferences, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/me/preferences, PUT} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/me/license, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/me/license, PUT} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/me/license, DELETE} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/:id, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/profile-image, POST} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/profile-image, DELETE} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/users/:id/profile-image, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RoutesResolver] ViewController {/api/view}: [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/view/folder/unique-paths, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:RouterExplorer] Mapped {/api/view/folder, GET} route [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:NestApplication] Nest application successfully started [Nest] 686 - 04/16/2025, 4:12:25 PM LOG [Api:Bootstrap] Immich Server is listening on http://127.0.0.1:2283 [v1.131.3] [production] [ig-init] done. Detected CPU Cores: 32 Starting microservices worker [04/16/25 16:12:27] INFO Starting gunicorn 23.0.0 [04/16/25 16:12:27] INFO Listening at: http://0.0.0.0:3003 (744) [04/16/25 16:12:27] INFO Using worker: immich_ml.config.CustomUvicornWorker [04/16/25 16:12:27] INFO Booting worker with pid: 746 [Nest] 706 - 04/16/2025, 4:12:28 PM LOG [Microservices:EventRepository] Initialized websocket server [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:DatabaseRepository] Running migrations, this may take a while [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:MetadataService] Bootstrapping metadata service [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:MetadataService] Initializing metadata service [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:MapRepository] Initializing metadata repository [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:MetadataService] Initialized local reverse geocoder [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:ServerService] Feature Flags: { "smartSearch": true, "facialRecognition": true, "duplicateDetection": true, "map": true, "reverseGeocoding": true, "importFaces": false, "sidecar": true, "search": true, "trash": true, "oauth": false, "oauthAutoLaunch": false, "passwordLogin": true, "configFile": false, "email": false } [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}} [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:StorageService] Successfully verified system mount folder checks [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:SystemConfigService] LogLevel=log (set via system config) [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:NestFactory] Starting Nest application... [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] BullModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] ClsModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] ClsCommonModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] OpenTelemetryModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] KyselyModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] KyselyCoreModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] DiscoveryModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] OpenTelemetryCoreModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] ClsRootModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] BullModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] BullModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:InstanceLoader] MicroservicesModule dependencies initialized [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:NestApplication] Nest application successfully started [Nest] 706 - 04/16/2025, 4:12:29 PM LOG [Microservices:Bootstrap] Immich Microservices is running [v1.131.3] [production] [04/16/25 16:12:32] INFO Started server process [746] [04/16/25 16:12:32] INFO Waiting for application startup. [04/16/25 16:12:32] INFO Created in-memory cache with unloading after 300s of inactivity. [04/16/25 16:12:32] INFO Initialized request thread pool with 32 threads. [04/16/25 16:12:32] INFO Application startup complete. I followed the SpaceInvader guide on YT but it's a little outdated, so the latest container has some new entries: SERVER_HOST: 0.0.0.0 SERVER_PORT: 2283 Leaving those as is loads the container, but I can just never get into the WebUI. According to SpaceInvader, he says the "PostgreSQL_Immich" container should have the same version number as the docker compose file, but the docker compose file is v14 0.20, yet SpaceInvader's own container is pg16-v0.3.0. Wouldn't I get Immich log file errors if the SQL version was wrong?

Thanks all, sorry for the delay in response - actually now running around 150 MB/s and has under 3 hours to go. Diags attached. Drives are now all in a newly built disk shelf using an old SuperMicro server (SM JBOD board and SAS cables from backplane back to main PC to LSI SAS9211 card) so maybe more latency there but didn't think there would be over direct to the LSI card. unruss-diagnostics-20250410-1703.zip

I had a 8TB parity drive in place, upgraded to a EXOS X20 20TB drive. Stopped array, assigned 20TB in place, started array - currently running around 30 MB/s, estimating 5 days to complete. This drive should run around 250+ MB/s - think something is going on? Should I have formatted the drive before replacing the parity drive? It's fluctuating between 7-30 days to complete: Any help is appreciated. -Russ

nvm, I'm dumb - my cache drive got unplugged. phew

I hope I'm not freaking out too soon - I stopped array, added an additional drive, preclear of new drive went fine, added drive to array, started array as normal. AppData and VM folders are now gone. Please help troubleshoot or find out what I did wrong?

Thanks for the help - got database errors during upgrade process (following pinned thread for manually updating), so I'm just going to start over. I didn't know manual upgrades needed to be done, i was just updating the docker container.

A few years ago I followed SpaceInvaderOne vids on setting up Nextcloud. Now getting this error when firing up Nextcloud now: This version of Nextcloud is not compatible with > PHP 7.4. You are currently running 8.0.25. Docker repository is = linuxserver/nextcloud When loading up updater.phar, I'm still on version 20.0.14 and that's the latest available to download. The latest Nextcloud should be 24 or 25? Current version is 20.0.14. Update to Nextcloud 20.0.14 available. (channel: "stable") Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-20.0.14.zip Open changelog ↗ Steps that will be executed: [✔] Check for expected files [✔] Check for write permissions [✔] Create backup [✔] Downloading [✔] Verify integrity [✔] Extracting [✔] Enable maintenance mode [✔] Replace entry points [✔] Delete old files [✔] Move new files in place [✔] Done Continue update? [y/N] Ideas on how to fix this (upgrade) without scrapping the entire Nextcloud install and reinstalling with latest docker? I saw SpaceInvaderOne has a new guide using Swag instead of letsencrypt, so wondering if I should just start over. Thanks, Russ