Cloning T60 With Apricorn (Update)
Posted: Wed Feb 28, 2007 7:53 pm
In another Post, I made some asumptions that proved to be wrong regarding the Apricorn Cloning Kit as used with the T60.
I use the Apricorn USB SATA Cloning Kit to produce a clone of my 60gb HD, as my form of Weekly Back-Up.
The first Clone that I produced was Non-Bootable (Just a Blinking Cursor following the BIOS Splash Screen).
I called Apricorn and they said to Disable Security for the Pre-Desktop-Area (in BIOS). This did not help.
I called them again and they said that I would have to:
1. Remove the HD from the T60 and mount it in the USB Cloning Enclosure.
2. Mount the HD to receive the clone in the T60.
3. Boot with the Apricorn CD and Clone, being sure to select the External (USB) drive as the Source Disk and the Internal HD as the Destination Disk.
I did this and The resulting Clone was Bootable. I would go through this "Backward Cloning" proceedure weekly.
Subsequently, I deleted The "Client Security" and "Rescue and Recovery" Programs from the C: Drive.
Then, I tried making a Clone Without switching Drives and was surprised to find that the resulting Clone was Bootable.
I thought that the Program Deletions enabled the "Standard" Cloning proceedure (Drives not Switched) to produce a Bootable Clone.
Additional experimentation with a 3rd Drive revealed the following:
The Program Deletions actually had no effect on the Cloning.
I found that the FIRST Cloning must be done (as Apricorn said) from USB to Internal Drive.
SUBSEQUENT Clonings can be made from the Internal Drive to the USB Drive to produce a Bootable Clone. (See edit below).
Note: In ALL cases the Clone (Bootable or Non-Bootable) included the IBM _Service Partition which is accessable with the ThinkVantage Button during the BIOS Splash Screen.
EDIT 5-4-07, Subsequent cloning experience has revealed that the "Easy" Cloning (From internal to USB) does not reliably produce a bootable clone. I haven't isolated the factors that cause this. However a "Reverse" (USB to Internal) cloning ALWAYS produces a Bootable Clone.
I use the Apricorn USB SATA Cloning Kit to produce a clone of my 60gb HD, as my form of Weekly Back-Up.
The first Clone that I produced was Non-Bootable (Just a Blinking Cursor following the BIOS Splash Screen).
I called Apricorn and they said to Disable Security for the Pre-Desktop-Area (in BIOS). This did not help.
I called them again and they said that I would have to:
1. Remove the HD from the T60 and mount it in the USB Cloning Enclosure.
2. Mount the HD to receive the clone in the T60.
3. Boot with the Apricorn CD and Clone, being sure to select the External (USB) drive as the Source Disk and the Internal HD as the Destination Disk.
I did this and The resulting Clone was Bootable. I would go through this "Backward Cloning" proceedure weekly.
Subsequently, I deleted The "Client Security" and "Rescue and Recovery" Programs from the C: Drive.
Then, I tried making a Clone Without switching Drives and was surprised to find that the resulting Clone was Bootable.
I thought that the Program Deletions enabled the "Standard" Cloning proceedure (Drives not Switched) to produce a Bootable Clone.
Additional experimentation with a 3rd Drive revealed the following:
The Program Deletions actually had no effect on the Cloning.
I found that the FIRST Cloning must be done (as Apricorn said) from USB to Internal Drive.
SUBSEQUENT Clonings can be made from the Internal Drive to the USB Drive to produce a Bootable Clone. (See edit below).
Note: In ALL cases the Clone (Bootable or Non-Bootable) included the IBM _Service Partition which is accessable with the ThinkVantage Button during the BIOS Splash Screen.
EDIT 5-4-07, Subsequent cloning experience has revealed that the "Easy" Cloning (From internal to USB) does not reliably produce a bootable clone. I haven't isolated the factors that cause this. However a "Reverse" (USB to Internal) cloning ALWAYS produces a Bootable Clone.