Why clone only starts in safe mode?

[PhilipTobias]

Any ideas why I can only start in safe mode, when starting from a cloned hard drive on a different Intel Mac computer?

I regularly clone my MacBook Pro using SuperDuper's Smart Update option. Earlier this week I got an Intel Mac Mini for use if any emergencies arise. Both computers are running Mac OS X 10.4.11 (8S2167).

However, I am only able to start from either of my cloned external drives in safe mode. When trying to start normally from either cloned drive, instead of the normal loading and login screens, a nearly-black screen with some artifacts displays at that point.

This problem occurs when choosing the cloned startup drive after pressing Option at startup, or after selecting the drive in the System Preferences > Startup Disk panel and clicking Restart.

Both cloned drives are partitoned using GUID. One drive is a LaCie, the other an EZ Quest. The MacBook Pro starts up just fine from the same cloned drive.

Prior to updating to the Intel computers, I was always able to trade SuperDuper cloned drives between my G4 laptop and G4 Mac Mini. That ability saved my bacon more than once.

Any idea what is going here, or how to further troubleshoot the problems?

Thanks in advance. ...pt


Following is the crash report:
panic(cpu 1 caller 0x001A49CB): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00c20000, CR4: 0x000006e0
EAX: 0x02a94dc0, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x015d6c18
CR2: 0x00000000, EBP: 0x14153ee8, ESI: 0x02a94dc0, EDI: 0x00000000
EFL: 0x00010246, EIP: 0x0037de63, CS: 0x00000008, DS: 0x02a90010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14153c68 : 0x128d0d (0x3cc65c 0x14153c8c 0x131f95 0x0)
0x14153ca8 : 0x1a49cb (0x3d2a94 0x1 0xe 0x3d22b8)
0x14153db8 : 0x19b3a4 (0x14153dd0 0x2a94dc0 0x4b09b4 0x3c2564)
0x14153ee8 : 0x37e97e (0x4af440 0x2fb2c00 0x4af2e0 0x4af2d8)
0x14153f58 : 0x3b9375 (0x466260 0x4000b 0x14153f78 0x19e23a)
0x14153f78 : 0x13d989 (0x272ab00 0x4000b 0x14153fc8 0x39a8fc)
0x14153fc8 : 0x19b21c (0x0 0x0 0x19e0b5 0x308bcec) Backtrace terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386

Model: Macmini2,1, BootROM MM21.009A.B00, 2 processors, Intel Core 2 Duo, 1.83 GHz, 1 GB
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 1.2.2
Bluetooth: Version 1.9.5f4, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS541680J9SA00, 74.53 GB
Parallel ATA Device: MATSHITACD-RW CW-8124
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: Hub, Up to 12 Mb/sec, 500 mA
USB Device: USB KVM Switch, Justcom Technology, Up to 1.5 Mb/sec, 500 mA
USB Device: Hub, Up to 12 Mb/sec, 500 mA
USB Device: Back-UPS ES 500 FW:801.e5.D USB FW:e5, APC, Up to 1.5 Mb/sec, 500 mA
USB Device: Kensington Wireless Desktop, Kensington, Up to 1.5 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA

[dnanian]

Looks to me like the OS version that came with the laptop isn't compatible with the Mac mini, and (likely) vice versa...

[PhilipTobias]

>>Looks to me like the OS version that came with the laptop isn't compatible with the Mac mini, and (likely) vice versa...

Thanks, Dave, for the prompt reply.

I didn't realize that Apple had regressed to such OS version incompatibilities.

Based on that, I'll have to rethink my entire backup strategy. I'll probably use SuperDuper for cloning my main computer, and then occasionally use ChronoSync to synchronize the user files from my main computer to my emergency computer. And then hope my laptop doesn't get stolen or die unexpectedly.

In prior emergencies, it was much simpler when I could start and operate from a SuperDuper cloned disk for a few days, and then clone it back when my main computer was available again.

...pt

[dnanian]

New hardware almost always comes with a 'special build' of the OS, and those builds aren't synchronized until the next release after that. 10.4.11 is a tough one, because Macs that came with 10.4.11 won't sync up until 10.5...

[PhilipTobias]

>>New hardware almost always comes with a 'special build' of the OS, and those builds aren't synchronized until the next release after that. 10.4.11 is a tough one, because Macs that came with 10.4.11 won't sync up until 10.5...


So at the point I get around to upgrading to 10.5, then I *should* be able to go back to my previous strategy - where a cloned drive from my laptop can start up my Mac Mini in an emergency?

That would be nice. However, while waiting for various programs to be upgraded for 10.5 compatibility, I may not upgrade for a few months yet.

Thanks. ...pt