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. |
Well, more than just a non-stock machine: this isn't Apple hardware at all, right? It's just a generic box you've managed to get OSX working on, no? (I don't mean this in a disparaging way, I just want to confirm the situation that I can't reproduce on any of the hardware I have here: this is not a standard OSX install, regardless of partition type.)
This has nothing to do with MBR: it's because the source partition doesn't have the proper standard configuration to be bootable in a standard way (for example, it doesn't have BootX in the right place). The files have been copied, and you'll have to repeat whatever you did to get the source partition booted on the destination. |
test case
Quote:
Quote:
Quote:
If you want to test for this situation with "stock" Apple hardware, you could:
(FYI, I use a registered copy of Superduper on a Pismo all the time and am thoroughly satisfied with it when used for that purpose.) |
Really, there was no need to be coy about this, and you could have saved us both a lot of time -- and me a lot of testing -- if you had just indicated this wasn't a real Mac in the first place.
Anyway, no, I just can't spend the time necessary to try to reproduce this situation -- once you step off the standards, you're kind of on your own. Sorry -- it's hard enough dealing with all the Macs that do get released to start dealing with non-Apple hardware with a nonstandard partitioning scheme (Disk Utility will partition with MBR, FYI) created with nonstandard tools, etc. As I indicated, your configuration doesn't have a BootX file in the proper place, so it's not going to be seen as a standard System folder and isn't going to bless properly. But if you mess about with it appropriately perhaps you'll be able to get it to work; feel free to indicate to others how you managed it, in this thread -- should they encounter a similar situation, they'll at least find this documentation. |
Sorry -- didn't mean to be coy. When asking for help with software, I try to pare down the details to just those that I believe to be necessary to reproduce the behavior, rather than just dumping everything I know and letting others sort out the details.
Can you point me to documentation of Superduper's requirement that a BootX file be in the proper place? The Superduper User's Guide does not include the word "bootx". |
It's not our requirement. It's OSX's.
|
I just did a quick Web search and found that BootX is only used with PowerPC-processor-based Macs. Those with Intel CPUs don't use BootX.
So the lack of existence of BootX must not be the problem in this case. |
Not really relevant: BootX is present for all Macs.
|
All times are GMT -4. The time now is 03:32 PM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.