multiple upload folders
Hi. I have somehow ended up with multiple upload folders. All the files are visible in the timeline, but only the ones in data/upload will load. The rest have blurry thumbnails and I get Error loading image when trying to view. I can go back as far as August 4th before things stop displaying correctly. I haven't changed the mountpath or touched the actual data, though I did access one image directly in the upload folder to confirm the files are intact and they appear to be. Any idea why this has happened and how I can fix it?
30 Replies
:wave: Hey @DiscordIsn'tAFuckingForum,
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_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.Could you post your compose/env
ah I've just seen the note about the new storage config, will see if that makes a difference
"it's truenas" would've sufficed 😛
There's a bunch of recent topics on this
ah so ya'll broke it for everyone then ;)
No truenas broke it
:3
https://discord.com/channels/979116623879368755/1408212608078577826/1408213263187181664 this should be it but I'm going to tag @Xiticks to verify
To have the thumbnails yes
But the /data/upload and /upload/upload seems weird
It's like migration started but then failed
is there a writeup or something that goes into detail? I remember doing a similar thing with nextcloud but that was like a year ago iirc
Mraedis linked a post with the command to run inside the immic container
However, I would check if data/upload contains the same data as upload/upload
I donk't know how to migration broke, it should not have
i had a quick look at a couple of folders and they weren't exact matches
stopped atm while I move the data but I'll check again once that's done
MOving data? wdym?
got ~200GB of data that needs moving around to setup the new dataset strcuture
Oh yeah, ok
Could check the contents of /mnt/Tank/immich/uploads, does data and upload exist in it?
nope, just uploads/long-hex-id
then all the subfolders
Wait @Mraedis, do you know if the folder list uses the to list the folders, or it checks the system?
No clue, no
I think that Immich listed both folder as the migration (the command to run) had to be done, I don't know what else could explain it
Once @DiscordIsn'tAFuckingForum once the migration is made to new strucure, before using the command, could you check if both folders are still listed?
yep was gonna start it with the new config and see what happens before doing anything else :)
If you're following the guide, the rsync might have to be run as root, or with sudo
all good, rsync and I are well acquainted :p
Okay so, recreating the container with the new config:
- worked fine aside from the backups folder. I hadn't configured this previously as I rely on snapshots and replications for that, so when i pointed it at the new directory, it didn't like that there wasn't a .immich file in there. Creating a blank file seems to have solved it.
The 2 upload folders are both still showing in the web ui,
upload/upload and /data/upload but they both appear to be pointing to the same directory, 6c0f35f5-ef28-4c38-ba20-faaf3046c339. That directory in the file system does have both of the sets of files, so I'm guessing it's just a case of reassigning the old ones to the new location in the app itself with the linked command?Yes creating a blank is the soluttion
However, I would suggest to enable it, because it is simply a dump of the database, and from what I read around here, snapshots/replications might sometimes corrupt it, so it's better to be safe (and it doesn't take much space)
And yes, I still think that the folders vues is used by the db, so running the command should fix it
probably solved, thank you both for the help :)
Nice!
Could you tell if both folders are still showed?
After running the command, I'm only seeing /data/upload
OK thanks! Would make sense that it uses the info in the db to display the folders, so everything should be fine
This thread has been closed. To re-open, use the button below.