![]() One saving grace is that the Mac file system is "journaled" and has a much better chance of recovering from a disk error than any Windows system. It's slower, but infinitely safer than improper disk ejects. If you have a backup device and there is another Mac on the same network, I'd transfer the device to the "properly working" Mac and then access it via File Sharing. Click on the Apple icon then select System Preferences Click on Energy Saver Enable Prevent computer from sleeping automatically when display is off. It will see it for a moment and then give me that error. Gone in under finder preferences and made sure that my external drive was set to show up. ![]() I have changed cables, rebooted my system. If you have a USB device you are currently using as a backup device, I would stop using it until the issue is resolved. I had been moving files around and all of the sudden it keeps giving me the disk not ejected properly error. ![]() From past experiences, don't expect Apple to acknowledge this issue, nor address it with any urgency (it's ONLY you're data, right?). I would bet that USB and TBolt use a common library and that library has issues. Under Windows, I can't use two of the exact same USB drives on the same computer (it loads, then ejects the devices, rotating betwixt the two drives, over and over and over and over). After the second update, it seemed to stabalize. ![]() I had a whole slew of error -36 problems when 10.12 first came out. It seems that Apple and Microsoft can't get their USB and Thunderbolt drivers to work right.
0 Comments
Leave a Reply. |