I don’t have the SATSmart kext installed here, as I try not to use any third-party KEXTs any more. The snag here is that this drive enclosure is connected via USB-C, and Apple is too bloody lazy and uncaring to support SMART over USB-C, which is disgusting for a premium brand. If you look at Binary Fruit’s front page, you’ll see this blog’s icon as one of those recommending DriveDx, as I regularly do in MacFormat and Mac|Life.
#DRIVEDX AND WINDOWS DRIVES FULL#
I can therefore let CCC make its routine daily backup of the restored disk, safe in the knowledge that its full contents remain in a separate backup. Even if my restored disk has lost a file or two somewhere in the process, that will still be available from those Time Machine backups of the original SSD. Now I have a first full backup of my root working folder as restored from its CCC backup, together with all the older backups Time Machine made of that same folder going back for over a year. So I had to rebuild my exclusion list, which made the next backup a full one.Īs it turns out, that works in my favour. That only served as a reminder that you can’t fool Time Machine just by renaming a volume: its pane had trashed my previous lengthy exclusion list and added the new external disk to that list, giving itself nothing to back up at all. Once my fresh SSD was fully loaded, it was time to turn on Time Machine automatic backups and daily CCC backups again. Thankfully, I didn’t need to restore from the latter as no files had been changed since its last full backup. In the small hours of every morning, Carbon Copy Cloner makes a full backup of the disk, which is supplemented by hourly Time Machine backups of my root working folder. In this case, as this external storage contains a mixture of my most active documents and many kept only for reference, it could have required two restore operations. With the old SSD carefully labelled as being suspect (at least), I formatted its replacement and gave it the same name before restoring from backups. It looked like the SSD itself was at fault, so I replaced it with a spare 2 TB SSD which I had been keeping in reserve in the second bay of the StarTech enclosure. At first, that seemed good, then up popped the improper ejection notification once again.
So I removed the whole chain from the port on my Mac, installed the wobbly SSD in a plain SATA case with a Thunderbolt 3 cable inserted into a different port. That has been one of its very few irritations over the three years that it has been my production system. I’ve never liked the USB-C/Thunderbolt ports on this iMac Pro, as sometimes just adjusting the tilt of the display is sufficient to elicit disk ejection warnings.
#DRIVEDX AND WINDOWS DRIVES MAC#
Back in normal mode, though, it soon ejected itself improperly.Īny part of the chain from the SSD to the Mac could have been at fault. It was time to start up in Recovery and run Disk Utility’s First Aid on the offending disk, which not only remained fully connected during the checking of its 27 snapshots and the active file system, but returned no warnings or errors. However, notifications of that external SSD being ejected improperly were infrequent, and didn’t coincide with apps freezing. Then other apps started freezing, until even Safari stopped responding. Its error messages indicated that the source disk had become disconnected, but that disk still appeared to be working fine. The first to go was, ironically, ChronoSync, which kept freezing when trying to back up my main working folder stored on an SSD inside a StarTech two-bay enclosure. Over the last couple of days, various apps had been freezing.
0 kommentar(er)
