Salta al contenuto principale

Random Reboots Using Cloned Boot Drive

Thread needs solution

Afraid this is going to be a bit long - apologies.

I used ATI2016 to clone the boot drive on a Dell PWS 530 MT (2x1.8 GHz Xeons, 2 GB ECC RAM, ATI All-In-Wonder x800, three SCSI drives:  "Boot" (36 GB, SCSI ID=0), "Apps" (36 GB, SCSI ID=1), and "Data" (73 GB, SCSI ID=2).  The ID on "Boot" was set by removing all jumpers, on "Apps" by position on the SCSI cable (i.e., no jumpers), and on "Data" with a jumper.

I backed up the contents of "Data" to an external drive and the used ATI2016 to clone "Boot" to "Data" allowing it to expand the cloned partition.  I then replaced "Boot" on its position on the SCSI cable with its clone on "Data" and added a "New" 147 GB drive where "Data" had been. I also set the SCSI IDs using jumpers.  So now I had:

Drive       Cable Position      SCSI ID

"Data"          First                    0

"Apps"        Second                  1

"New".          Third.                   2

The first attempt to reboot made it to the WinXP splash screen before to machine crashed with unknown diagnostic lights and beep codes.  The second attempt didn't make it that far before crashing with different, but still unknown, lights and beeps.  I left the machine powered up while I went to look for a dull knive to cut my throat.

Decided to try again (and again, and again, etc.) getting a different BSOD each time.  Only the first generated a mini-dump and that pointed to the SCSI driver.  Finally, the machine successfully booted WinXP.  Only problem is that it randomly reboots with no error messages or ant logging in Event Viewer.  Once I was sitting in front of the machine and I saw one on the text boxes indicating that it was doing an orderly shutdown.  There isn't any software on it that would initiate a reboot.

I have updated the system BIOS, done a "repair" install of the anti-virus package, and run a registry cleaner but am still getting the random reboots. Reinstalling the operating system isn't an option - although I have a WinXP SP3 DVD, it would literally take days to try to reinstall all the software.  I've tried booting a Live Linux CD but the primary DVD drive is having trouble reading it.

Anybody have any ideas?

0 Users found this helpful

Windows XP x64 is not supported in 2016 - 32-bit is (barely).  

https://kb.acronis.com/content/56517

Unfortunately, XP support in general for many current applications is going to be limited or non-existent considering the age of the OS and lack of support even from Microsoft for patching and updates.

You also have a fairly complicated setup with a dual processor motherboard and ECC memory with SAS drives and it looks like you install your apps to a separate drive.  XP is not known for good driver compatibiltiy between hardware configurations (limited drivers that are more specific than those found even in Windows 7 and especially in Windows 8/8.1 and Windows 10).  I'm assuming you also have a custom RAID controller in this system (maybe not), but RAID controllers and custom storage devices usually need to be included at the time that  the image is being restored (if it is not a 1 to 1... exact same backup to restore on a replacement drive). 

If you were imaging one for one (full system image with all paritions), I'm pretty sure it would restore to a different drive just fine (even in XP).  But because you are using XP, it's not supported in 2016, looks like you've modified the physical configuration of the SAS drives and are not restoring the full system to the same state the backup was made in, it's going to be pretty hard to pinpoint the exact problem.

****My only suggestion is to  first try taking a full system image "entire disk" of the original "Boot" disk.  Don't take a clone image, just take a full backup image of the entire disk and store it somewhere else (another disk or external drive).  Don't do any jumper ID changes or anythig like that, just take the image as it is.

 Then push the image back using offline bootable Acronis recovery media to what used to be our DATA drive (Old drive 3).  When the recovery is complete, power down (don't let it try to boot yet) and physically move the old data disk (which is now your new "boot" disk) onto the SCSI cable that was originally your "boot" disk (drive 1).  Does it boot then with just the one new boot disk as the OS and your second disk (apps)?  If it does, then try adding the third new data drive after that.