|
#1
|
|||
|
|||
can't boot from underlying volume but can from Sandbox
About a month ago I made a Sandbox, and since then have been booting from the Sandbox and have installed a variety of software updates, including the OS (10.5.3 on the Sandbox, 10.5.2 on the underlying volume).
I cannot boot from the underlying volume ("Macintosh HD"). The grey gear starts to spin, and the machine shuts down. This is, alas, reproducible. To boot off of Macintosh HD I am holding the option key down while booting, and then choosing Macintosh HD from the list of available drives. I can boot from and work from the Sandbox just fine, which is odd to me, since I thought the "guts" were shared. The Sandbox is of the "shared users and applications" variety. Is there any way to recover from this situation? I have a backup that is about a month and half old on an external drive, but I really would rather not rebuild everything I've done to my new system since then if I can avoid it! |
#2
|
||||
|
||||
I'd make a backup of the original drive, if you don't already have one, to a fresh volume. I'd then follow the instructions in the User's Guide to clone back.
I have no idea what might have happened to the internal, since the OS is not touched, as you might know.
__________________
--Dave Nanian |
#3
|
|||
|
|||
Wow, that was a quick reply! Thank you.
Sorry, but I'm a bit confused. The original drive is the one that I can't boot from (but I CAN boot from the Sandbox made from the original drive). Are you suggesting that I reclone the original (non booting) drive to a new volume somewhere, and then clone back? What am I misunderstanding? FWIW, I have a clone I made from the original volume shortly after creating the sandbox. That won't boot either (same issue...machine shuts down). Right now, the only volumes I can boot from are the Sandbox and a month old backup (clone) of the original drive. What would be the effect, if any, of "copying back" from the Sandbox to the original drive that now won't boot? Is that worth trying? Or are things likely to be sufficiently FUBAR that I should go back to the month old working volume and just rebuild forward from that? |
#4
|
||||
|
||||
Yes, I'm suggesting you back up your drive (since that's where all your data is). Then, clone back from the Sandbox to the regular drive, to replace the system that doesn't boot with one that does.
__________________
--Dave Nanian |
#5
|
|||
|
|||
OK. Just to be clear (I just reread this in the User's Guide):
To clone back from the Sandbox, I select "Backup - all files" and "Smart Update". This will NOT overwrite any data files, right? (yes, I WILL make a backup first before doing this!) |
#6
|
||||
|
||||
Right, but in case you make a mistake, or something unexpected happens, back up. :-)
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Updating main volume from Sandbox | camner | General | 1 | 06-08-2008 08:38 PM |
Apps installs in Sandbox show up in original volume | shermo | General | 1 | 10-03-2007 07:38 AM |
Changing the name of my Sandbox boot partition | denke | General | 1 | 07-21-2006 03:02 PM |
First Boot Experience, Seagate 400GB PushButton FW Works! | greenjeens | General | 5 | 05-25-2006 07:19 AM |
Boot from sandbox or just use it as a backup. | fred | General | 12 | 04-26-2006 01:11 AM |