restore from ghosted copy

Serena wrote on 5/27/2013, 11:24 PM
Recently I used Ghost to copy my C drive (an SSD) to a HDD prior to installing Vegas Pro 12 v563. I had a bit of a problem (the preview RAM thing) and uninstalled to revert to the previous version. The RAM problem persisted. Sony advised a complete uninstall of all Sony software, which didn't thrill me. So time to use the clone. This being my first attempt at this I asked a computer- prof friend to check my intended procedure of changing the bios to boot from the clone, then reformat the SSD and ghost across the original data. Seems I was right off the planet, and needed to physically replace the SSD with the HDD, or at least change the jumpers to make the HDD look like drive C (no fiddling with the bios). Since I'm only passing familiar with computer hardware I'm disinclined to attempt this. How should I have gone about this business?

Comments

john_dennis wrote on 5/28/2013, 12:15 AM
Generally, you don't want to have two "identical" boot images on the machine at the same time. This is especially true if the disks have the same Disk ID from being clones of the same disk. I usually keep the GHOST images on a data drive and write them back to the same SSD. The whole process takes so little time It's not a burden.

You might become familiar with the concept of "Unique Disk ID" on your favorite search engine. Here and here are links to discussions of the unique disk id concept.

For a long time I had three bootable systems on one drive and I would swap from one to the other for variuos tasks, but the whole process got somewhat tedious. Now, if I want to boot another O/S, (which is rare) I write it to the same SSD and replace the O/S when I'm finished.
Serena wrote on 5/28/2013, 2:01 AM
That sounds easy, John, but don't assume I'll be insulted if you give me pretty elementary instructions!

When I have the clone in the bay it is only identified by the name I gave it (clone of C). Are you saying boot up normally (the SSD being drive C) and then copy the clone to the SSD which caries the OS? That sounds a bit worrisome.
cohibaman#1 wrote on 5/28/2013, 2:36 AM
I'm not sure how you go about using a ghosted copy, and maybe somebody else might be able to help you here. I use, and recommend Acronis True Image Home 2012 and do a complete image back up of my SSD (C Drive) on to an external hard drive. Before I install any major program, I do a complete backup so I don't have to worry about having to do a complete install of all programs again. I just go to the last image backed up , install and everything is good. I can swear that it has saved me so many times when things have gone array. And even if things are running good I still do a complete image backup after a couple of weeks just to stay up to date with updated driver installs and Win7 updates. Even if your SSD fails, just install the backup onto a new SSD. It is well worth the investment as it takes between 30 to 45 min. to do a backup (pending on the size of your HD), and you can set it up to shut down your computer when it has finished. A reinstall of the image takes about the same time, and you don't have to enter your BIOS to run the install. I know other members use, and attest to it on this forum, and that is what put me onto it. After going through a few agonizing sessions of total OS installs, it was the best buck spent for any program. Definitely takes the stress and pain out screw ups. Didn't mean to go into a rant, but I feel your pain, hopefully you get things up and running... but check out the program for peace of mind. Good luck. (I have no affiliation with Acronis)
diverG wrote on 5/28/2013, 6:28 AM
I run two instances of W7 stored on separate drives. I initially installed W7 allowed it to update and then loaded favourite NLE's and plugins. At that stage I saved an image to my video drive D. Then replaced my system drive with a clean HD and used my W7 install disc to load the image onto the new system disc. At this stage I renamed the computer before adding the original system disc back into the computer. Now if I restore an image I usually boot to the appropriate drive use Windows to restore the image. When I added a SDD both of my system drives were physically disconnected and the SSD installed. Again I used the windows system disc to replace load the image. I suspect all my disks have the same ID. All my system discs are 256Gb.

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & 122(194), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP17, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

Rob Franks wrote on 5/28/2013, 7:07 AM
"Seems I was right off the planet, and needed to physically replace the SSD with the HDD, or at least change the jumpers to make the HDD look like drive C (no fiddling with the bios)"

This "c" drive... "d" drive stuff is not part of the computer but rather part of windows (written into the registry). In other words the computer doesn't know who or where or what c drive is. Only windows knows that. Once you boot into what ever windows version you're booting to, it will be recognized as the official "C" drive. The only thing you need to do is REDIRECT the boot to the proper drive which of course is done through the bios. Now there are software boot loaders like BOOTitNG which allow you to boot to what ever os without having to diddle with the bios every time but Disk imaging (as opposed to cloning) might be a better bet though for you in the future if you have no interest in running multiple os's

Disk imaging basically duplicates your drive and compresses it into a file which can be stored anywhere Then when something goes wrong you simply recall your disk image and load it back onto THE SAME drive and it is all EXACTLY the same when you took that image.
gpsmikey wrote on 5/29/2013, 4:58 PM
Any time I want to play with a restore, I usually "restore" to a new (or at least a spare) drive so if things go bad, the original is still there. One thing to be careful of is to NOT reboot into windows with two bootable images "visible" to windows - under the right (or wrong) conditions, it boots off the restored one that it finds first then gets all sorts of things screwed up in the registry if the boot was not what windows thought was "C". I forget the exact sequence, but I have made that mistake before in XP and had a heck of a time unscrambling what happened. What I do is restore from an image, then shut down and configure the system so that the restored image is where the system expects to find it. Images can save your tail, but you need to be careful not to catch the dreaded "HIFD" (Hole In Foot Disease)

mikey