#WD MyCloud NAS docker install multiple issues.

1 messages · Page 1 of 1 (latest)

pastel basalt
#

I'm trying to setup immich on my PR4100 NAS. I setup the stack in Portainer following the documentation. The issue I find is if I restart my NAS (so unexpected power outage) I lose all files and have to even redo the initial setup (Admin email etc.) I also noticed if I upload any large videos over 500mb, it causes my entire docker to crash and it won't recover unless I reboot my entire NAS. The only error I get in the logs is vm.overcommit_memory which I enabled to see if it would resolve the issue and it didn't work.

Has anyone gotten this to work on a Mycloud NAS? (I've done a lot of googling and haven't found anything along with using the search feature in this discord.)

No changes were made to docker-compose.yml or example.env other than exactly what was specified in the install instruction (stack.env and I only set a password for the DB. I did try changing locations, but yield the same results.)

Docker version 20.10.14.
Portainer community edition 2.19.4
Mycloud version 5.29.102.

south heronBOT
#

:wave: Hey @pastel basalt,

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

#

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.

south heronBOT
surreal laurel
#

Likely you’re using the cache drive to store the database, which is getting reset

#

How much RAM do you have?

pastel basalt
#

That's kind of what I thought was happening, but I have another container and was monitoring my ram usage as well while I let the transfer go. 4GB of ram and I never went above 25% usage while doing a transfer.

#

My other container is for a plex usage monitor and all the data has been retained.

surreal laurel
#

That’s probably the cause of the crashes. 4GB is on the edge of doable for immich

#

I find it hard to believe immich runs with only 1GB ram (25%) so I’m not sure of your system stats

pastel basalt
#

Well for the file transfer, I could agree. But what about when I restart? I have also done a test where I do not crash the server. I upload say 5-10 pictures which is around 10mb in size total. I leave it alone for a bit and then I reboot my NAS. Same result happens where the photos are gone and I'm forced to do the inital setup.

surreal laurel
#

The restart is related to the cache drive

#

Your DB_DATA_LOCATION must be ona drive that persists between reboots

pastel basalt
#

I don't see why the DB_DATA_LOCATION wouldn't be by default.

surreal laurel
#

I mean, Immich doesn’t have control over that

#

It’s however you configure it

pastel basalt
#

And it's set to a persistent drive, because my tautulli data is retained.

surreal laurel
#

You should post everything the bot asked for if you need help with it

#

I would say it’s rather likely not haha give the symptoms

pastel basalt
#

Sure. Let me get some photos posted.

vagrant shell
#

From your screenshots you've saved the immich_redis volume to /data instead of the immich_postgres container

#

the redis container is expendable, the postgres container is not

pastel basalt
#

Thank you! That helped. I found where both the server/postgres were pointing to the NAS internal storage. I changed the location and was able to get everything working.

olive tulip
#

HI, I tried ton install immich on a WD PR4100 without success ... It seems versions à docker / docker compose are outdated... If anyone as encountered the same case & can help ... it would be great ...

vagrant shell
#

No clue, and it seems Heavens has left the server