Restoring the original state found as unmounted. The volume BigDaddy could not be repaired.
When it came back up, it almost immediately complained that the external 4TB USB3 hard drive that I had cloned from earlier had an irreparable problem, which subsequent manual repairs also failed to repair and it will now only mount read-only. Later that day the monitor wouldn't wake up again and I couldn't connect via Screen Sharing or ssh this time, so I had to force power off. Problem -69842 occurred while restoring the original mount state. Restoring the original state found as mounted. The volume TimeMachine could not be verified completely.
Attempts to repair TimeMachine drive failed and it is still in that state. When the system came back up and I had logged in, it almost immediately reported that the TimeMachine drive (internal drive that had been the factory boot drive before adding the SSD) had an irreparable error and was being mounted read-only. Soon the screen sharing disconnected and refused to re-connect (also a recurring problem after the monitor won't wake up), so I reconnected via ssh and watched until the rsync processes used by CCC went away. At some time during the copy the screen refused to wake up (which is a recurring problem I've had with this mac-mini / monitor combo), so I attached from my iMac via screen sharing to monitor the clone progress.
Only then did I discover that my last TimeMachine backup was several months old.įast-forward to few days ago, with mac-mini mostly sitting idle and only running was was on it from the new install and upgrade, I added Carbon Copy Cloner and did a clone of an external 4TB USB3 hard drive to a new identitical model.
Since I believed I had an up-to-date TimeMachine backup (and I knew I had a full image from 6 months ago when I did a full reformat/reinstall), I booted to recovery mode and did a reformat and clean install of Sierra that was successful, followed by successful upgrade to High Sierra. Subsequent attempts to boot normally all resulted in a black screen for a few minutes followed by an automatic shutdown. I tried that and it was unable to repair. Last week I started the initial upgrade and went to bed and when I came back I was at a screen that was complaining about problems on the boot drive (a third party SSD upgrade) that couldn't be repaired (I believe it was doing a pre-check before converting to APFS) and suggested booting to recovery mode and doing a disk repair from there. Anyone else having issues with HFS+ disk corruption on High Sierra? I upgraded my late-2012 Mac-mini from Sierra to High Sierra last week and it's been one irreparable disk corruption after another on 3 separate disks.