Filesystem becomes readonly during immich-go upload. Are my new drives toast?
Usage🗄️Server❓QuestionHello. I'm a newbie, and I seem to be having an issue. Any advice is appreciated. Thanks!
Immich version 2.3.1
immich-go command:
I've attached some output from
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.
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?
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-*.zipWhat I've explored
After runningbtrfs scrubI've attached some output from
dmesgI 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.txt27.53KB
