|
#1
|
||||
|
||||
If the OS supports APFS, we're happy to copy to APFS. Anything on 10.13 or later should be able to boot from APFS as well...unless that Mac has never had its firmware updated to add the support.
__________________
--Dave Nanian |
#2
|
|||
|
|||
Thanks. Not a big deal, but if the OS DOESN'T support APFS, it strikes me as a little funny that SuperDuper blasts ahead with trying to copy to a non-APFS disk. That is, you only find out half an hour later, when the copy you tried to make doesn't boot because, I guess, it isn't really there.
|
#3
|
||||
|
||||
If the OS doesn't support APFS, we would copy to a non-APFS disk...? And if the OS doesn't support APFS (eg 10.12) we won't.
If the firmware hasn't been updated for boot-time APFS support, we don't know - that capability isn't exposed. But installing the OS (rather then restoring) will ensure that the firmware is updated...these things are distributed with installers.
__________________
--Dave Nanian |
#4
|
|||
|
|||
Sorry, not being clear here. If you connect an APFS disk to an OS that does not know how to communicate with APFS, SuperDuper will STILL try to copy, and takes time grinding away seeming to do it. But what you end up with, after a long wait, is a disk that won't boot, and probably doesn't even have a copy on it. My point is that SuperDuper doesn't seem to recognize that it's trying to copy to a disk that the OS formally can't communicate with, and you don't find out until the disk doesn't work. Are you saying that SuperDuper has no way of polling the disk to see if it is really writable?
|
#5
|
||||
|
||||
No, Dan, it won't. If the system does not know how to communicate with APFS, the drive won't even mount.
__________________
--Dave Nanian |
#6
|
|||
|
|||
That makes sense but, as I recall, when I plugged that APFS SSD in to my High Sierra 2011 Mac, an icon DID appear on the screen. That's why I assumed I could back up to it. And when I commanded SuperDuper to back up to it, it ground and ground for twenty minutes and pretended to be backing up. It was only when I tried to boot from that backup twenty minutes later that the SSD didn't show in the Boot Manager. That is, the Boot manager knew that it wasn't a compliant disk, but SuperDuper didn't seem to be aware that it wasn't.
|
#7
|
||||
|
||||
Dan, it made the copy as it should. It didn't "pretend" to back up. (Feel free to send me the log to verify.)
If the boot manager doesn't see it, it may have had the wrong partitioning scheme, or High Sierra had never been *installed* to the system (it had been restored, or copied from elsewhere) and thus the BIOS doesn't have APFS capability, even if the *system* does.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Multiple errors of kind: "Caught I/O exception(5): Input/output error" | amagjo | General | 7 | 04-14-2009 10:01 PM |
Hard drive size doubled after backup.... | sanketr | General | 7 | 08-02-2008 12:16 PM |
Undersized disk image and a Boot Camp-related backup question | garybollocks | General | 3 | 10-23-2006 01:07 PM |
"Pull" a backup from a remotely mounted disk? | DrDan in MA | General | 6 | 02-08-2006 11:00 AM |
SuperDuper Backup of AES 128 Encrypted Disk Image | rwg4 | General | 3 | 11-30-2005 10:28 AM |