#Filesystem becomes readonly during immich-go upload. Are my new drives toast?

1 messages · Page 1 of 1 (latest)

raw prism
#

Hello. I'm a newbie, and I seem to be having an issue. Any advice is appreciated. Thanks!

How it started

I've been running immich-go to transfer my Google Photos. I uploaded around 800GB without issues. Then, with about 100GB left to go, it began failing to upload anything and I see that the filesystem became readonly...

My setup

ZimaBlade NAS Kit running ZimaOS with 2 new WD Red Plus 4TB drives in RAID1.
Immich version 2.3.1

immich-go command:
immich-go upload from-google-photos --log-file immich_upload.log --server=XXX --api-key=XXX --sync-albums --include-unmatched --client-timeout=180m --on-errors=continue takeout-*.zip

What I've explored

After running btrfs scrub the filesystem becomes writable, but the scrub result says that there are uncorrectable errors. I tried immich-go again which uploaded 26GB before failing as the filesystem became readonly again with more uncorrectable errors. 😬

I've attached some output from dmesg showing BTRFS errors linked to specific Immich thumbnail files.

I see several other posts about filesystems becoming readonly, and the verdict is typically that the drives are toast, but my disks still appear to be healthy according to ZimaOS and Scrutiny.

Questions

  1. Should I try removing the thumbnail files linked to checksum errors?
  2. Should I change the way that I upload my photo library?
  3. If my brand new drives really are toast after just a few days of running immich-go, could there be an opportunity to modify how bulk uploads/jobs are handled in order to protect future drives from suffering a similar fate?
📎 dmesg.txt
oak treeBOT
#

:wave: Hey @raw prism,

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. :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.

vapid zephyr
#

If writing to your drives makes them become readonly, they are probably dying, yes. The application code cannot induce scrub errors

#

Or you have bad RAM, faulty PSU etc

#

Smart reports are not proof of drive health, btw

raw prism
#

In your opinion, would you say that I made a poor choice (or just bad luck) with my drives and/or the ZimaBlade NAS Kit?
Would you recommend requesting replacements of the same hardware, or try to get my money back because it doesnt work as advertised?

vapid zephyr
#

No clue. You’d have to do a lot more testing to isolate that