Comment

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 issu3 too. I figured that restarting docker with the drive properly mounted would fix this though. Still getting, “connection was reset,” though

source

Sort:hotnew top

qwestjest78@lemmy.ca ⁨1⁩ ⁨month⁩ ago
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

source
- aMockTie@lemmy.world ⁨1⁩ ⁨month⁩ ago
  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.
  
  source
  - plasticcheese@lemmy.one ⁨1⁩ ⁨month⁩ ago
    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/
    
    source