this post was submitted on 23 Feb 2025
33 points (97.1% liked)
Selfhosted
60366 readers
846 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Drive was just connected with USB to mini PC so it was also unplugged and I had to remount it to the PC. I looked in the .env file and the path still looked good. I had considered this was an issue too. I figured that restarting docker with the drive properly mounted would fix this though. Still getting, "connection was reset," though
So I checked the config for the external drive again and discovered when it was remounted it had added a, "1" to the end of the drive name. I went back into the .env and changed the library location to reflect this. Restarted docker and it is now connecting again. Obviously it is not ideal to be using a external HDD, but I wanted to test immich out for a while before investing into a bigger self hosting rig for all my services.
Ultimately problem solved though
I would recommend editing your fstab and use the USB drive's UUID to mount it to a consistent location. That way, even if you reboot or disconnect the drive and the reconnect it to, say, a different USB port, it will always mount to the same mountpoint.
See this page from the arch wiki for more info.
This is the answer. Find your UUID with "blkid" and mount it in fstab with the ID.
It's worth learning how. This problem is something everyone goes through (hopefully) once.
https://ostechnix.com/mount-a-drive-permanently-in-linux-using-fstab/