Josh

I posted a reply that my parity disk wasn't my largest, but realized I was wrong about that. There are two disks of the same size, but for some reason df is reporting one of them is smaller than it is supposed to be. Output from lsblk sdb 8:16 0 2.7T 0 disk /mnt/disk1 sdc 8:32 0 3.7T 0 disk /mnt/disk2 sdd 8:48 0 2.7T 0 disk /mnt/disk0 sde 8:64 0 3.7T 0 disk /mnt/parity Output of df -h: /dev/sdd 2.7T 2.2T 503G 82% /mnt/disk0 /dev/sdb 2.8T 2.3T 503G 83% /mnt/disk1 /dev/sdc 3.6T 2.9T 536G 85% /mnt/disk2...

I would delete this thread if I could. I just realized that my parity disk is not on the largest disk in the array. I don't know how that happened.

Hello, I'll start off by saying that I have been negligent. I run a diff and sync script nightly, but I haven't actually checked the logs in quite some time, and I didn't notice that the parity file has grown so big that the disk is full. I have no idea how long it has been since a sync was successfully run, but in the meantime I have done a huge amount of file operations, using exiftool to rename my entire photo and video catalog. When I run snapraid check, I get a lot of errors, many of them "unrecoverable"....