MBR partition table (instead of GPT) on Intel Mac okay for SD?
I'm using Mac OS X 10.4 on Intel hardware. The machine has an MBR partition table instead of the default partition table type, GPT, so that I can more easily run other operating systems on it.
I am able to successfully clone to another partition, but Superduper fails when it attempts to mark the other partition ("volume") as bootable. Is Superduper compatible with MBR partition tables? |
We don't really care what the partition scheme is, but OSX might. I'd need to see the error to attempt any kind of diagnosis, though.
|
error log
Quote:
Code:
| 04:51:36 PM | Info | PHASE: 3. After Successful Copy |
I need the whole thing, not just a clip.
|
why need entire log?
Quote:
|
Feel free to send it to me at the support address. But I do need the whole thing.
|
Where to find past logs?
Is it saved somewhere, or do I need to run another clone? (I closed Superduper after running it to get the error code you requested.)
|
Open SuperDuper!, press Cmd+L, then "Send to shirt pocket..."
|
entire log
Quote:
Code:
| 04:44:57 PM | Info | SuperDuper!, 2.1.3 (80), path: /Applications/SuperDuper!.app, Mac OS 10.4.6 build 8I1119 (i386) |
Quite weird. So, you're updating a 10.4.8 volume with a 10.4.6 install... something weird clearly happened. Can you try an erase-then-copy rather than a Smart Update to see if that works?
|
Quote:
|
OK. But could you try an erase-then-copy to see what that does?
|
error log #2
Quote:
Code:
| 07:56:26 PM | Info | SuperDuper!, 2.1.3 (80), path: /Applications/SuperDuper!.app, Mac OS 10.4.6 build 8I1119 (i386) |
This is quite peculiar, pmocek. It's almost like you're running on a non-Apple computer. Possible?
|
yes, non-stock machine for sure
Quote:
Is Superduper restricted to use with machines using GPT partition tables when running on OS X on Intel hardware? Truth be told, I have had trouble getting the cloned partition set as a startup disk. But I would think that if Superduper cannot do so, Shirt Pocket would prefer it to recognize this and then issue a warning, refuse to run until the option to set as startup disk is disabled, etc., instead of running all the way through the backup then failing with a cryptic error message. The latter is definitely not consistent with Superduper's otherwise excellent UI. So, any clues? I realize this is a corner-case for now, but I'm confident that with time you'll find yourselves with more customers running OS X on newer hardware, and more of us Unix geeks jumping on the bandwagon, pushing the boundaries of OS X and Superduper in the process. |
All times are GMT -4. The time now is 01:15 PM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.