PROBLEM: Backup copy won't boot computer

[dnanian]

We're not aware of any problems in this area. It's possible that your kernel extension cache -- once built -- was retained on your second copy, and this allowed the system to boot due to some weird peculiarity of your particular configuration, but you didn't indicate how you moved it, so it's hard for me to say.

If you moved it and retained the kextcache, try creating a copy script that doesn't ignore this file. This is something that shouldn't be retained, especially when a backup might move to new hardware, but in your case retaining it might not do any damage, and could explain what you're seeing.

[stevea]

I physically moved the drive from firewire to the ATA card...
________
Penny Stocks To Buy

[dnanian]

Ah. Well, then, it seems quite possible that this would be the cause, especially given the unusual setup you've got.

I'll try to do some research on this end to figure out what's up. I have no way of simulating your hardware configuration, though. If you're willing, the following test would be helpful:

- Try to Smart Update the (now-on-the) ATA drive from the original, booted from the original, and see if it continues to boot
- If not, create a new Copy Script.
- In the 'include' tab, include the "Backup - all files" script.
- Also in the 'include' tab, include the "Exclude system cache files" script.
- Save this to an appropriate name, and choose it in the main window's script pop-up
- Repeat the Smart Update and boot

Let me know if that works...

[stevea]

I will try it later as time permits.

Do I understand correctly- you're thinking the correctly-refreshed kextcache needs to exist to startup on ATA card?

I don't understand why it can boot with refreshed kextcache, but cannot boot without it. (I could understand why it might not boot if the kextcache is wrong.)

Is the kextcache copied by SuperDuper (backup all files) or not?


(I am assuming kextcache is some kind of cache relating to kernel extensions, yes?)
________
XTUBE

[dnanian]

The kextcache is copied with "Backup - all files", as is the BootCache.playlist. What I'm thinking is that, given the unusual configuration, these two caches are somehow preventing your boot when using a non-native ATA controller (when they were generated on a drive that has it onboard).

It's just a guess, as I'm not a kernel engineer and can't step you through the entire boot process, but given that they have to do with startup I thought it was worth a try.

(The kextcache is a kernel extension cache, and the BootCache helps with rapid startup.)

[stevea]

Seems to be a likely explanation, thanks!

Apparently, starting up on ATA is prevented by the bad caches, and starting up on firewire somehow overcomes problem with the bad caches.

Next test (when time allows)- I'd like to see if it will start on ATA without the caches...
________
FREE WORDPRESS THEMES

[dnanian]

That's what I'm thinking. You can, of course, delete the files by hand after doing the copy, but for anyone who might be following along, I thought it best to include the "easy way".

[stevea]

Tried again, deleted cache files, but drive won't startup.

(However, this test might be flawed. Intechusa.com has a solution and created a driver for high-capacity drives. They document that the startup volume must still be completely contained within the first 128GB of the startup drive. The Intech driver was never used, though. The first time I encountered the problems here and solved it by the firewire trick, the startup was within the first 128Gb. On this test, however, it was in the last 128GB. But, this drive was also connected to ATA card that supports 128GB+ drives. Also, I have not tried starting this drive on firewire yet.)

These are files that were deleted:
System/Library/Caches
Library/Caches
System/Library/Extensions.mkext
System/Library/Extensions.kextcache

Are these the correct files to delete (yes?)?

Any other ideas why starting up on Firewire blesses the drive so it will subsequently startup on the ATA card?

I think my next test is to try this again, but put the startup volume in the first 128GB of the hard drive. But, any other ideas I might try now more quickly?

Ultimately, I require a solution so that this will work flawlessly without requiring use of the firewire trick...
________
Chevrolet 150

[dnanian]

Well, no -- the files you want to delete are:

/System/Library/Extensions.kextcache
/private/var/db/NetworkingInterfaces.xml
/private/var/db/BootCache.playlist

What I'd suggest, rather than manually deleting the files, is to create a new Copy Script. Include "Backup - all files" and, following that, also include "Exclude system cache files".

[stevea]

Originally Posted by dnanian

/private/var/db/NetworkingInterfaces.xml
/private/var/db/BootCache.playlist

Those files did not exist...

(BTW, I looked at a working startup, and it had BootCache.playlist but not NetworkingInterfaces.xml)
________
Suzuki katana

[dnanian]

That's unfortunate: it was worth a try, though.

I'm not sure what to suggest at this point, Steve. This seems to be a peculiarity of your particular hardware combination: perhaps they'll have a suggestion as to what might prevent boot...