TwoStroke

Hey mate, there's two possible reasons there: 1. That file never copied properly, or doesn't exist. Some users had issues with this, and to resolve you can do a sudo touch <immich upload location that leads to encoded-video/.immich> Or It's a permissions error. If the file exists, but Immich can't read it, you will get this error. You can go to your immich dataset and ensure that apps user & group has permissions to your new dataset. Make sure when you apply the permissions to apply them recursively.

There is another option for any users that got completely stuck on a previous version that is now so deprecated updating to a current version skips too many to work. I went through this process, I was on 1.24 I believe and needed to be on a 1.32-1.36 version to then be able to upgrade past 2.0 due to a change in how postgres worked. I ended up using dockge to create a docker container running Immich, pointing to my exact locations. I stopped my existing app, started my docker container, let it upgrade the database, then performed the migration through rsync as per the above guides, and then confirmed it worked by updating the file locations below. Then I just updated Immich through TrueNAS after stopping this docker container, and it was all happy! services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:v1.136.0 # extends: # file: hwaccel.transcoding.yml # service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding volumes: # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file.(AFTER YOU MIGRATE DATA) # - ${UPLOAD_LOCATION}:/data - /mnt/HDDs/Photos:/usr/src/app/upload/library - /mnt/HDDs/Applications/immich/uploads:/usr/src/app/upload/upload - /mnt/HDDs/Applications/immich/encoded_videos:/usr/src/app/upload/encoded-video - /mnt/SSDs/Applications/immich/thumbs:/usr/src/app/upload/thumbs - /mnt/SSDs/Applications/immich/profile:/usr/src/app/upload/profile - /mnt/.ix-apps/app_mounts/immich/backups:/usr/src/app/upload/backups # - /mnt/SSDs/Applications/immich/data/thumbs/:/thumbs # - /mnt/SSDs/Applications/immich/data/profile/ - /etc/localtime:/etc/localtime:ro env_file: - .env ports: - 30041:2283 depends_on: - redis - database restart: always healthcheck: disable: false immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:release env_file: - .env restart: always healthcheck: disable: false redis: container_name: immich_redis image: docker.io/valkey/valkey:8-bookworm@sha256:fea8b3e67b15729d4bb70589eb03367bab9ad1ee89c876f54327fc7c6e618571 environment: TZ: ${TZ} healthcheck: test: redis-cli ping || exit 1 restart: always database: container_name: immich_postgres image: ghcr.io/immich-app/postgres:15-vectorchord0.4.3-pgvector0.8.0-pgvectors0.2.1 environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} POSTGRES_INITDB_ARGS: ‘–data-checksums’ TZ: ${TZ} # Uncomment the DB_STORAGE_TYPE: ‘HDD’ var if your database isn’t stored on SSDs # DB_STORAGE_TYPE: ‘HDD’ volumes: # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file - ${DB_DATA_LOCATION}:/var/lib/postgresql/data restart: always networks: {} Environment File UPLOAD_LOCATION=/mnt/HDDs/Applications/immich/data/ # use this only after you have upgraded and unified the library folders. DB_DATA_LOCATION=/mnt/SSDs/Applications/immich/postgres_data IMMICH_VERSION=v1.133.0 DB_PASSWORD={GET THIS PASSWORD FROM YOUR CURRENT IMMICH INSTALL UNDER TRUENAS>APPS>IMMICH>EDIT>DATABASEPASSWORD} ML_DATA_LOCATION=/mnt/tank/immich/mldata DB_USERNAME=immich DB_DATABASE_NAME=immich TZ=YOURTIMEZONE NVIDIA_VISIBLE_DEVICES=void NVIDIA_DRIVER_CAPABILITIES=all LD_LIBRARY_PATH=/usr/lib/jellyfin-ffmpeg/lib:/usr/lib/wsl/lib: MACHINE_LEARNING_CACHE_FOLDER=mlcache PUID=568 PGID=568 It was a bit of a fluff around, but I can confirm that this method works. My only regret is going so long without upgrading Immich that this became an issue in the first place.

Update was to go to 25.04 Fangtooth - I had the same error pop up on mine when I updated, but the update installed correctly. Unsure what the error stems from.

Very excited to see 25.04 and start being able to look at VMs now! With this update and the Install Script v2 giving us things like choosing a hardware acceleration option with regards to Plex, have the issues surrounding Intel GPU acceleration hardware permissions been resolved? It's the only thing holding me back from running Plex on HexOS at this stage.

If you're referring to the Quicksync issues where it won't transcode due to permissions problems, this has not been resolved. Just tested this for myself.

Could we get a forum section for install scripts? That way as a community we can post a thread for a specific app and people can share their scripts and ask for feedback? I think that'd be handy, but I don't think it needs to go in the normal Applications support forum because that might confuse people as it's definitely a more advanced thing at the moment! Thanks

Loving the update, am looking now at install scripts and seeing about uninstalling my current applications and reinstalling with install scripts (This might take a while!). I like we can update apps now through the dashboard, that's awesome. I would love in future for a toggle-able option of Auto Update on certain apps, and then we can set a time period on when to do these, like how Watchtower works.

Oh absolutely, I was referring to when they change over to a v1.0 and go full release instead of beta. Honestly, very excited for the app curation system. It's really the part of HexOS that myself and I am sure most others have been looking forward to for a very long time. Re: Issues - The main ones for me are Plex not working with intel quicksync GPUs (HexOS specific), and Immich now being on a deprecated dataset (Not necessarily HexOS specific - When the app update drops I'll do a backup / reinstall of Immich and I am assuming the latest curated app template for Immich will include the correct dataset config). It's hard when the App Dev changes how the functionality of their app works and you have to scramble to keep up.

Yeah, as mentioned in the post, I saw this. I just thought it meant instead of being early in 2025 it would be late 2025. I understand this, but your website only says "*Some features will not be immediately available upon beta release.". If you are launching the product and having people pay full price for it, you need to either update your website to remove the not available features, or update it to make it VERY clear that these are future state features and not applicable to the current state of the product. I am mostly excited for the new App Curation system, and to see how the team resolves the issues with the existing apps (Plex & Immich). I am cautiously optimistic about this update being the first time it feels like I will be using HexOS instead of TrueNAS.

Hi all, Just seeking clarification here - the HexOS team have said they're still targeting V1.0 for release this year. A topic on Reddit has a response from the HexOS_Official user stating Can the team clarify when VM support is coming, as that was a major selling point for HexOS. Will V1.0 be launched without a major feature? I understand that 25.04 pushed back the release of VM features, but from the how I read the Q1 update (the last time this was spoken about, in March...) I took it to be that it was being done, just at a lower priority than the App support, but would still be coming this year. If I am looking at the HexOS website, we are currently at 3/6 of the below features. Even if they launch App deployment in the next few weeks for their Q3 update, I don't see how they are able to complete VMs, Buddy Backups & Snapshots in the next 3 months, which means they can't actually be targeting a 2025 release, but we've had no official word saying the release has been pushed back. The last word on this was from March 7th:

I'm loving it so far. My only issue is that it was a *very* tight build , and sometimes the drives get a little warmer than I would like. Because fan curves on this board only run based on CPU temps, I can't seem to find an easy way to have the fans ramp up as the temp on the drives increase, but I just have the fans running at like 50% constantly and it seems to have fixed most of my heat issues. How do you like their 4U ones? I am thinking of building a rack mount gaming PC next, using their CX4170A. I am mostly concerned about thermals though, and since it can only run one 360mm rad I don't think I can do full watercooling either.

I should probably have thought of a grinder, but my rack is underneath an IKEA butchers block which is my desk, so I didn't want to set that on fire. Or the carpeted floor in my office....

Oooh this is a *very* good idea. I will get onto this right away. Do you have any recommended tutorials on automating this backup to OneDrive / Google Drive? I am under the assumption that as of right this moment, if it dies and I restore my TrueNAS I can't bring it back into Hex, but this will be something that will be possible in the future.

That makes a lot more sense than what I was thinking, I clearly didn't comprehend the AnyRaid-Mirror vs AnyRaid-RAIDZ differences, but have now read it more closely and see what they are saying!

In the blog post - Does this line: Mean they will support migration from RAID-Z to AnyRaid? Because I absolutely *love* this feature, and I am already thinking where I can migrate my data to to start changing to this when it comes out... But if there's a planned simple way to migrate, that would be even better!

Next item for me on the list is probably looking at a 10Gbps NIC, but at the moment 2 x 2.5Gbps on the motherboard has been plenty in a bond.

I had to open my NAS up to put some new 2.5" SSDs in it for my LANCache to run on as it had just been running on my HDDs as a test, so I figured what better time than now to take some photos and do a post? Specs: Case - Sliger CX3702 Motherboard - Asus Pro W680M-ACE SE CPU - Intel 14600k Cooler - Noctua NH-D9L RAM - 2x Kingston 32gb ECC DDR5 HBA - LSI 9400-16i Power Supply - Corsair 850W SF850L HDDs - 2x 4tb Ironwolf Pro, 2x 16tb Ironwolf Pro, 2x 18tb Ironwolf Pro SSDs - 1x 128gb 2.5" Samsung Boot Drive (This is an old SSD that I used to have in a PC?) - 2x 2tb NVME Drives - 2x 2tb 2.5" SSDs Notes for people in future - If your rack is 18" deep and the server is 17.72", you won't have room for cables, so I needed to get some tin snips and cut a hole in the back of my rack so that ethernet and power would fit.. But then I used tape so it wasn't sharp on the cables! (Also, I promise I vacuumed those spider webs...) Looks just like a bought one! Here's a photo before I tidied my rack, still has the old Synology on top of the new NAS before I transferred all my data. I'll add another photo after I get everything back in the rack, I have tidied things up a lot since then Other items in the rack: Synology DS916+ (Replaced with this new NAS) Intel NUC (Runs my Plex server until HexOS supports intel GPU passthrough) Eufy Homebase (For my doorbell) Raspberry Pi 4 running HomeAssistant (Only until HexOS official VM support comes!) Unifi UDM-SE Unifi 24Port Pro switch

In this section, below Featured Posts, this is spelled 'Annoncements'. Not a big issue, but hopefully quick to fix!

This is excellent to know that we are actually helping! Things like Plex HW Transcoding not working on Intel GPUs, there's so much work that was done there by users in this community to create a workaround to get it working on HexOS, that it's good to know that this is being used for bug fixes and further progress down the line, even if the devs / yourself don't have time to specifically tell people "Yep, we hear you, we are working on X".

My disappointment is that a lot of the guides we have built should specifically not be required once HexOS is actually in it's fully functional state - Apps should just work, things like implementing TailScale should be as simple as clicking a few buttons, etc. We also haven't *really* been solving, hacking or working around within HexOS, we have just been.. doing things in TrueNAS? Which I understand is the same thing, but also not. We're essentially using this community as a TrueNAS noobs community, which we all are, and learning TrueNAS instead of helping provide feedback on the development of HexOS, which is what I think all of us here actually want to do! I can't wait for the Q3 update and to see what this community comes up with then, because I think that will be a great time to be involved here & all our current knowledge of TrueNAS will be very useful in working out how to get apps running within HexOS.

This is my biggest concern, especially given that they're intending to allow community app curation. The apps need to be working and working seamlessly before they release "1.0", and given that the curation templates are slated for Q3 this year and launch is also "This year", I am very concerned at their timeline. To me, this is the biggest feature that HexOS has, easy installation of apps & VMs (coming soon tm). Now that Fangtooth has been out a few months, I assume they're probably targeting a 25.10 version as the upgrade path for HexOS, instead of 25.04. To me, even if they miss the 1.0 release this year, that's OK. Don't officially launch it too early, because that's how people become disappointed in the product. All of us are here because we understood that this was a Beta. Community engagement and updates on progress is all that we require.

It looks like it should support all drive configurations support in Scale, from what their wording says? Saying that this is required to adopt existing Scale installs into HexOS makes me think all Scale drive types will be supported, except maybe not cache drives or meta data drives yet because they're kind of off to the side of storage?

No mention of local dashboard, so I guess that's a Q4 / 1.0 task right before launch?

I am mildly concerned they are losing out on their best window to have beta testers by not keeping people more involved. When I first installed HexOS I was checking the forums every single day, waiting to see what's next and what I could test next. I decided to go 'All-In' because I wanted to properly beta test this product and I run HexOS as my primary NAS now, but it's gotten to the point where I never even go to the HexOS Dashboard anymore, everything is done through the TrueNAS UI. If I disconnected it from the Deck, I would not notice a difference in my experience. Without engagement from the team (I understand they are very busy, and they launched at the worst time you could possibly launch a product, leading into the holiday period where most places shutdown for a while, hiring freezes, etc), I am losing my motivation to "care" at the moment, which is sad. However, I could definitely see a new road map announcement making me excited again! It's just hard to see at the moment. I have been holding off migrating my Home Assistant to a VM until they release their VM manager, and I am holding off migrating Plex to HexOS until they "officially" support hardware transcoding, so when some of these things happens I will get excited again, I am sure.

Hey mate, You may be running into the same issue I was having, which occurred after uninstalling and reinstalling Immich. Here is how I resolved it, please give this a try before going through with resetting your server.