Server failing to start due to wrongly seeing a "read-only" filesystem
I'm using the AUR package immich-server rather than the docker container. I've stored the /upload folder on my ZFS pool mounted at /mnt/storage.
My immich.conf file is this (minus the database environment variables):
After updating somewhat recently, it broke many things due to problems with postgres and the pgvector extension, but that's all fixed now.
My problem as of right now is that when I attempt to boot the server, I get the following error from Nest:
I've made sure that my files aren't locked, I'm not out of inodes or anything, immich is being ran as the user immich, which owns the files/folders in question with rwx as the owner, and I even made sure to remove the ACL that I was messing with it before with.
Any help or insight would be appreciated!
7 Replies
:wave: Hey @Dr America,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJAChecklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like
fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.GitHub
immich-app immich · Discussions
Explore the GitHub Discussions forum for immich-app immich. Discuss code, ask questions & collaborate with the developer community.
FAQ | Immich
User
GitHub
Issues · immich-app/immich
High performance self-hosted photo and video management solution. - Issues · immich-app/immich
Didnt' you already open a ticket?
sorry, I was doing that on my laptop and it died, should I just copy/paste some of this over there?
I forgot I'd posted it
nvm, saw your message
I'll post about it there as well, but I'm not exactly sure what the problem here is. I saw there was some incompatibility with certain file systems, but I didn't see ZFS in that list. Maybe it's just some weird config error, idk.
yeah, not sure, we explicitly don't support non-docker setups just because the support burden is so high
it's one of those things where it could work perfectly, but when it doesn't it's a huge pain to figur eout
Btw, I got it, I looked through my immich-server.service file and noticed that they define the upload folder there as well. I just had to use systemctl edit to get it to stick
cool!