Thinkpads Forum

I don't know how you can say the clone went 100% perfect without any problems, when you cannot boot up your clone.

It is difficult to diagnose your problem because we do not know exactly which steps you are taking to make your clone. If you care to write out a detailed step-by-step procedure of what you are doing, perhaps we can figure out where your problem is. Be sure and state where the drive is that you are cloning from, and where the drive is that you are cloning to. Also, what are your BIOS settings for the Predesktop Area?

I can boot it up, actually I am typing this reply on my T60 now. Its just in the device manager there is a yellow mark next to the new drive.

Wondows don't seem to like it for some reason.

BR,
Ed

Paul Pavlik wrote:DenTP4rm: I used to have a Sony Laptop with a failing HD. I bought a Apricorn Cloning Kit. Apricorn calls it a "Upgrade Kit because a different (usually higher capacity) drive can be cloned from the internal HD. This worked fine and I replaced the HD in the Sony. I also bought another spare HD and did a Clone TO the spare External drive once a week as my form of Data Backup.

Paul, thanks for the very thorough explanation. That really helps. I had a similar problem with a similar process on my T60p. I was using Apricorn's SATA drive housing and trying to clone from the main disk to it. It would not boot.

Then, somehow I was able to get it to clone and be bootable. Rather foolishly I didn't write down the steps and that was about 8 months ago. I think what I did was use the Ultrabay SATA Adapter, leaving the main drive in its place. I use Acronis True Image which is basically what Apricorn sends you with their drive kits. I have so far used Acronis 8 with no problems.

Anyway, since that time I haven't tried cloning again. I don't have my Thinkpad with me and won't see it again for a few months but when I do I'll try your process. If you don't have the restore CD set I recommend you get one or make one. They do come in handy.

Thanks again,
DenTP4rm

DenTP4rm: I Shouldn't need the Restore Disks because The Recovery Partition is intact. (When I say that I deleted "R&R", I mean that I deleted the "ThinkPad Rescue & Recovery" Program on the regular C: Partition.)

In fact, even with a "Non-Bootable" Clone in the T60, I was able to use the ThinkVantage button (Pressed during the initial Splash Screen) to access the utilities on the Service Partition.

However, the only restore that I could have done would be a Full Factory Restore because I had previously turned off auto-backups and deleted them anyway. (This was before I deleted R&R and Client Security).

I never did try running the IBM MBR Repair program on a "Non-Bootable" Clone since I didn't need to (After deleting Client Security). Might be interesting to try, but I don't want to screw anything up.

One more thing that I should mention: Sometime after deleting R&R and Client Security, I upgraded the HD Firmware for the (Source) HD in the T60 (Using a file from IBM). This was before I made the first Bootable Clone the "Easy" way.

Nevertheless, I really think that the "Safeguard" Software included in "Client security" is what caused the "Regular" Clones to be Non-Bootable.

In all cases, the Cloning Process clearly shows that both the regular C: Partiton and the IBM_Service Partition are Cloned.

Actually, I have a 3rd 60gb HD and will do more experimenting!

Wow, sorry about the dumb response, I read it incorrectly. As far as I'm aware, hard drives don't have special drivers. Have you tried allowing it to search Windows Update? My current Fujitsu drive on Windows Vista uses Apsx86.sys (v1.51.0.0), disk.sys (v6.0.6000.16386), and partmgr.sys (v6.0.6000.16386). The only one that could possibly be specific is the first, but I have not done anything special to install it. Maybe you should try to download and reinstall the Intel Storage Matrix driver from Lenovo? That might kick something into gear...

Fixed it now, with a Win XP Repair Install.



BR,
Ed

I have started another Message: Cloning T60 With Apricorn. It corrects some incorrect conclusions that I made in my entries in this Post.