![]() Save and exit, then: service netatalk stop In FreeNAS, this can be achieved by: nano /usr/local/etc/afp.confĪdd these lines to the section: log level = default:maxdebug So with the help of Ralph Boehme at netatalk, I enabled debug logging in netatalk (now at version 3.1.8) to track down the cause of the issue. With the recent release of FreeNAS 9.10, I decided it was probably time to track down the bug and get it fixed so I could upgrade. Rolling back to FreeNAS 9.2 fixed the AFP corruption issue for me. This is provided by a package on FreeNAS called “netatalk”, and it turns out that this package received an update between FreeNAS 9.2 and 9.3. Since I’m using a Mac, I figured I should use AFP (the Apple Filing Protocol) to connect the two together. So the problem wasn’t the image files at all, the problem was the connection between my MacBook and FreeNAS. Huh? In fact, if I just copied the photos from my NAS to my laptop using Finder, then opened them in Lightroom, the previously corrupt-looking photos displayed perfectly. I checked the MD5-sum of the perfect photos from the backup, and checked the MD5 of the corrupt photo on my NAS. And regular ZFS scrubs on my drive array never turned up any problems. Phew!īut how had the photos ended up getting corrupted? My FreeNAS runs ZFS, which detects and repairs/reports corruption. So I restored those photos to my desktop using my Crashplan backup, and those restored photos were fine. My newer photos all displayed fine, but a good percentage of my old photos displayed corrupted, as if the bits had rotted on the disk over time. ![]() They’d cut off halfway through and dissolve into a repeating pattern of stripes:Īs you can imagine, this was pretty devastating. However, a while back I noticed that many of my older photos displayed corrupt in Lightroom. I access my NAS’s photo drive over the network from my MacBook. I have so many raw Canon CR2 photos in my Lightroom library that they won’t fit on my MacBook, so I built myself a FreeNAS-based NAS to put them on. Recovering lost GPG public keys from your YubiKey.Installing macOS 12 “Monterey” on Proxmox 7.Expanding the disk of your Proxmox macOS VM.Driving a 4-pin computer PWM fan on the BTT Octopus using Klipper.Installing macOS 13 Ventura Developer Beta on Proxmox 7.2.Installing macOS 13 Ventura on Proxmox 7.2.Fixing Xcode on Monterey under OpenCore Legacy Patcher.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |