TI 2010 Plus Pack 'killed' my drive.

Hi;
I recently purchased the 6053 'Plus pack', and when I used it restore my system it 'killed' my hard drive.
I have an ASUS 'Rampage Formula' X48 based motherboard, and have been successfully making and restoring Windows 7 64-bit C: drive images with 6029 and 6053.
I recently installed the Plus pack and created a backup image of my entire C: drive (from a running Win 7 64 Bit system as usual).
I restored the image using the 'downloaded' 6053 Plus-Pack boot CD (without selecting Universal restore). I restored the entire drive (C: partition and MBR. As I understand it I need to restore the entire drive to preserve the 1 MB partition offset, which is needed for SSD performance).
When I rebooted my system, it would no longer go all the way through the BIOS boot! It hung at 'Auto-detecting AHCI Port #3' (which is the port my Intel SSD C: drive is on.)
I couldn't get to my my BIOS setup menu (it would say 'Entering setup, but never got there after 15 minutes...) Moving my hard drive to another port just moved how far it got before hanging on that new port number.
I though my drive was dead. If I removed the cable to my c: drive, I could again get into setup. I eventually figured out that if I set the BIOS drive mode to IDE instead of AHCI (and reconnected my C: drive) the system would boot. (Of course this made Windows 7 re-detect all the drives).
After much (much) investigation, I found that I could get back to AHCI mode by removing the partitions from the C: drive (in IDE mode), and resetting back to AHCI mode. Restoring an image with the Plus-pack boot disk again 'toasts' the drive.
I got back to working by again removing the cable, resetting to IDE mode, re-attaching the cable, removing the partitions, restoring an old image (using the pre-plus pack media), and resetting to AHCI mode.
As far as I can tell, using the Plus-pack media to restore my image writes something to the drive that causes the BIOS to hang when it gets to that drive. Searching the internet for people with similar hang problems shows that the people who've reported similar problems seem to also have ASUS motherboards.
I never had this problem with the non-plus pack restore CDs.
Has anyone else seen this problem? Or, has anyone with an X38/X48 ASUS motherboard restored successfully with the TI 2010 Plus-pack boot media?
I don't know if this would also happen if I tried to restore only the C: partition (instead of the entire drive w/MBR).
Thanks;
-Greg

- Se connecter pour poster des commentaires

> As far as I understand, you're not able to even load BIOS after the image recovery
> to SSD drive, you have restored the partition and MBR, is that correct?
Close. When I'm having this issue, the BIOS boot process starts, but then 'hangs' indefinitely at the point where it says it's 'Auto-detecting' the SATA drives. Part of the screen says (something to the effect of ) 'Hit delete to enter setup' at this point. If I hit the delete key at this point, the message changes to 'Entering setup', but it never gets there.
When things are working normally, after a few seconds of 'auto-detecting' the SATA drives, I see the drives listed and boot continues. If I've hit 'delete' I then enter the BIOS setup. It appears that 'auto-detection' must complete before I can get into the BIOS setup panels.
> If yes, could you please clarify, which build have you used to create the image?
I believe it was an image created from my 'running' Win-7 64-Bit OS with TI 2010 6053 installed. I'm not sure, but I think this also had the updated SNAPAPI files installed at the time.
> If the issue still persists, please select 0 option at ISO boot (collect Linux information file),
> and save it to your flash drive.
I'm preparing to try and recreate this problem (albeit with a conventional drive to save wear and tear on my SSD drive). I've previously downloaded the TI 2010 6053 Bootable media (as well as the TI 2010 6053 Plus-Pack bootable media.
When I boot these CDs, I only see options of '1' and up. Is there supposed to be an option for a '0' type of boot?
Thanks;
-Greg
- Se connecter pour poster des commentaires

Hi;
> Then please provide me with the case number you receive from our system,
I was able to recreate the problem using a regular mechanical drive (to save wear and tear on my SSD drive).
I zipped up the data I collected (along with a detailed description), and submitted it under case 00462732.
So far, it appears that the problem is only seen when I restore images created from my running Windows 7 system using the 'Plus-pack' restore boot CD media.
Thanks;
-Greg
- Se connecter pour poster des commentaires

Hello Gregory,
Thank you very much for submitting a case!
I have found it in our database and checked the information. Then I have forwarded the case to our Experts Team, so they will contact you as soon as possible (it may take some time to get an answer from them, probably several days or even a week, since we have a high volume in our queues), but please be sure that we will take care about the issue you experience.
Thank you very much for your cooperation!
Best regards,
- Se connecter pour poster des commentaires

Gregory Bohn wrote:Hi;I recently purchased the 6053 'Plus pack', and when I used it restore my system it 'killed' my hard drive.
I have an ASUS 'Rampage Formula' X48 based motherboard, and have been successfully making and restoring Windows 7 64-bit C: drive images with 6029 and 6053.
I recently installed the Plus pack and created a backup image of my entire C: drive (from a running Win 7 64 Bit system as usual).
I restored the image using the 'downloaded' 6053 Plus-Pack boot CD (without selecting Universal restore). I restored the entire drive (C: partition and MBR. As I understand it I need to restore the entire drive to preserve the 1 MB partition offset, which is needed for SSD performance).
When I rebooted my system, it would no longer go all the way through the BIOS boot! It hung at 'Auto-detecting AHCI Port #3' (which is the port my Intel SSD C: drive is on.)
I couldn't get to my my BIOS setup menu (it would say 'Entering setup, but never got there after 15 minutes...) Moving my hard drive to another port just moved how far it got before hanging on that new port number.
I though my drive was dead. If I removed the cable to my c: drive, I could again get into setup. I eventually figured out that if I set the BIOS drive mode to IDE instead of AHCI (and reconnected my C: drive) the system would boot. (Of course this made Windows 7 re-detect all the drives).
After much (much) investigation, I found that I could get back to AHCI mode by removing the partitions from the C: drive (in IDE mode), and resetting back to AHCI mode. Restoring an image with the Plus-pack boot disk again 'toasts' the drive.
I got back to working by again removing the cable, resetting to IDE mode, re-attaching the cable, removing the partitions, restoring an old image (using the pre-plus pack media), and resetting to AHCI mode.
As far as I can tell, using the Plus-pack media to restore my image writes something to the drive that causes the BIOS to hang when it gets to that drive. Searching the internet for people with similar hang problems shows that the people who've reported similar problems seem to also have ASUS motherboards.
I never had this problem with the non-plus pack restore CDs.
Has anyone else seen this problem? Or, has anyone with an X38/X48 ASUS motherboard restored successfully with the TI 2010 Plus-pack boot media?
I don't know if this would also happen if I tried to restore only the C: partition (instead of the entire drive w/MBR).
Thanks;
-Greg
Hi Gregory,
Go into Computer Bios. Go to the screen, where you can monitor the Power Supply Voltage. Look at the Volts for the 12 V Supply. If the Volts are changing moment to moment, replace the Power Supply in the Computer Case.
Why? I had the problem you are describing. I worked with Seagate and had me remove the Cables from the Seagate SATA Hard Drive. Remove the Power Cord from the Computer Power Supply and hold the Power Button in for 30 seconds.
Then I reconnected everything and everything worked just fine without problems.
Much later the problem reoccurred. I went into Computer Bios and use the Hardware Monitor for the voltage, I noticed that the 12 Volt Power was changing from 11.51 to 11.71.
Replaced the Power Supply where all voltages are steady and working just fine, now.
You might wish to check the Power Supply.
I have multiple operating systems on this Computer with 3 Hard Drives.
- Se connecter pour poster des commentaires

I had intended to comment here about a recovery problem, but it looks like I wrote it in the wrong forum, so take a look at Acronis forum #6937.
It relates to being unable to even get a BIOS response after a recovery operation.
Copied here:
I have had a problem for the second time and have been able to resolve it in the same way, however I will describe it here in case anyone else has also run into it!
Computer: hp laptop model DV4 running Win 7 (32-bit). Acronis Build 6053. 320GB SATA hd. 3 partitions.
I wanted to restore the hd after having conducted some software tests and initiated a restore from within Windows. Naturally, Acronis required a re-boot, so I clicked Drive C and MBR then, OK.
When the restore had finished I rebooted the machine. Oh dear, nothing, not even able to enter the BIOS!!!
I removed the hd and checked it on another machine using a USB adapter - all OK!
So I put the hd back in the laptop but just not connected, the Acronis recovery CD in the CDrom drive and switched ON. As soon as the CD started up I pushed the hd into it's socket. Acronis recognised the hd and I had it repeat the restoration from the same file.
After that, the machine was able to operate correctly again.
.
- Se connecter pour poster des commentaires

Rodney,
As you found out, the preferred method to restoring your system drive or to new disk is to perform the procedure when booted from the TI Rescue CD. This takes Windows out of the picture and the transaction is much cleaner and fewer problems.
You should be able to take a disk option backup and then restore that backup (when booted from the CD) and receive the same hardware settings.
- Se connecter pour poster des commentaires

I can't say I've had any problems starting an image restore within Windows and letting it re-boot into the Linux recovery environment.
What I find peculiar in Rodney's case is that the restored disk did not get identified at all in the BIOS startup routine and even caused it to hang such that he couldn't even start the PC with the drive connected.
I'll give him credit for intestinal fortitude of letting the PC boot up and then slam the HD into the connector. I also find the fact the rescue CD saw the drive even if it had been inserted after the bootup started a little strange.
- Se connecter pour poster des commentaires