I have a 2012 Mac Mini with two external WD Hard Drives hooked up (USB3.0). Both drives are formatted HFS+.
When I first boot, the hard drives are fine. Disk Utility says they Verify fine, no action is taken if I attempt to Repair them, etc. All is well.
At some point (haven't figured out how to tell "when" this happens, much less why) the files no longer appear. The hard drives report the proper size\available space, but if I open any of the top level directories in the Finder, they're empty, and applications that expect files to be there, find nothing.
Attempting to Verify or Repair the disk at this point throws a bunch of errors. I can force eject the drive if I want to, but I can't mount it again. When I reboot - all is well. Disk Utility is happy again. SMART reports the drives have no issues.
I'd chalk this up to a failing hard drive, but it's happening to two newer drives, so that seems unlikely. I DO have both drives encrypted using FileVault2 - currently both drives are being decrypted to see if this still happens when the drives aren't encrypted...
In the mean time, has anyone experienced something like this?
When I first boot, the hard drives are fine. Disk Utility says they Verify fine, no action is taken if I attempt to Repair them, etc. All is well.
At some point (haven't figured out how to tell "when" this happens, much less why) the files no longer appear. The hard drives report the proper size\available space, but if I open any of the top level directories in the Finder, they're empty, and applications that expect files to be there, find nothing.
Attempting to Verify or Repair the disk at this point throws a bunch of errors. I can force eject the drive if I want to, but I can't mount it again. When I reboot - all is well. Disk Utility is happy again. SMART reports the drives have no issues.
I'd chalk this up to a failing hard drive, but it's happening to two newer drives, so that seems unlikely. I DO have both drives encrypted using FileVault2 - currently both drives are being decrypted to see if this still happens when the drives aren't encrypted...
In the mean time, has anyone experienced something like this?