Error 36000 using Ghost Advanced to clone

qsilver2@bendcable.com's picture

I have been using Ghost 2003 for several years without any problems. Last 5 times it dies and I get the 36000 error. I use the Clone feature to copy one internal hard drive to the other. Both drives are the same model and have been working fine. I have run CHKDSK on the destination drive, no errors. Tried the reformat solution, and set it up as 1 partition, not difference. Any ideas of what to try next?

Jim Yount's picture

I've seen the 36000 error on

I've seen the 36000 error on occasion.  Try using the -fni command line switch.  This forces Ghost to ignore direct IDE access and choose another access method.  I've also seen situations where we have had to use GDISK to delete all of the partitions on the destination drive first: GDISK 1 /Y /DEL /ALL (substitute the 1 with the drive letter of the destination drive).

qsilver2@bendcable.com's picture

I also tried the GDISK

I also tried the GDISK command, no difference. Should they be tried together?

qsilver2@bendcable.com's picture

Hi JIm; I tried the  command

Hi JIm;
I tried the  command switch and it didn't change the outcome.  Is GDISK a DOS program and if so should it be run through the MSDOS screen that I can get in WIN XP or should I boot up to a DOS environment? Couldn't  I delete all partitions on the destination drive through Control Panels's Admin tools going through Computer Management and using Disk Management? I have already reformated the destination drive and it has 1 partition which shows up as HEALTHY (Active).

Jim Yount's picture

The Ghost Solution Suite

The Ghost Solution Suite includes both a DOS version of GDISK, as well as a 32-bit "Windows" version.  Most of my experience has been with using the DOS version, while booted from a bootable CD running the "Windows 95 version of DOS".  I would suppose that you could use the Control Panel's Administrative Tools, but I haven't done it.  The only times I've seen the 36000 error, we used GDISK (as I stated above) and it allowed us to successfully reimage the drive afterward.