SCSI Drive Copy Problem

[jswintx]

I just completed a full drive copy from one SCSI HD to another using Drive Copy 4.0. My system information is:

OS: 98SE (fully updated)
MB: Asus K7V w/512 PC133 Memory
SCSI Adapter: Tekram DC-390U2W
Source Drive: IBM Ultrastar 18ES (18G)
DNES-318350 68 pin
New Drive: IBM 36XP(36G) DHRS 36-V
(with 68 pin adapter)

Using Drive Copy 4.0 I copied the entire source drive including C: partition and logical extensions D: and E: to the "new" drive. I did not have the partitions on either drive hidden by the program because I had no intention of booting with both drives connected. The copy went well and I shut down the computer after so that I could disconnect the source drive and boot to the new drive. I did this and went into the SCSI configuration for the adapter and set the new drive as the boot drive. Then I reset the computer. When it came to the boot sequence I get a message that there is no valid partition on the new drive so the boot will not complete.

When I try to run Drive Copy again it will not recognize the new drive at all, probably because it is not registering as a INT 13H device which that program requires. I have checked the Tekram SCSI Bios and it does show that new disk is recognized by the adapter (the source disk is disconnected to prevent any corruption due to both having C: partitions installed). In the boot process the drive is also indicated as a SCSI device up to the point of actually booting to the HD. Then the process stalls as it recognizes no bootdrive.

Any help with information on how I can get the system to recognize the new drive will be greatly appreciated.

Jim W.

[glc]

I've even used Drive Copy 3.0 on SCSI drives, so I don't think Drive Copy is the source of your problem. I'd start reviewing your cabling, jumpering, and terminations.

http://www.hitachigst.com/hdd/support/download.htm

Download Drive Fitness Test and make the bootdisk - see what it has to say. You may have to use it to zero out the drive and try your cloning again.

If you are running 98SE, you can get a good clone the "old fashioned" way - set up the new drive the way you want using FDISK and using the freeware XXCOPY utility to clone each partition in Windows.

[jswintx]

GLC,

Thanks for the response. I will try your suggestion. I do think I may have traced the problem to my bios in the MB. Since this board is five years old it may have a restriction on the size of drive that the MB bios will accept that the new HDD exceeds. I cannot confirm that for sure at this time, but do know that after what I feel was a successful Drive Copy cloning when I tried to reboot nothing would recognize the new HD. I could not even get Drive Copy to recognize it so I could try to use the tools to confirm the partition.

Fdisk would also not access it because it can't "see" it. In booting to a boot disk I got one message that said that "drive not set in Bios." Of course it could mean the SCSI adapter bios, but I don't know that for sure either. Both the MB and Tekram are five years old even though both their bios have been upgraded all that they can be (considering the age).

Could it all mean that it is time to upgrade stuff? LOL I strongly suspect so, but it might have to wait a bit.

Thanks so much for your help and suggestions.

Sincerely,
Jim W.

[glc]

The motherboard bios won't affect it at all - it's the SCSI bios that totally controls anything hooked to the SCSI adapter. I'm not familiar with the settings in a Tekram so I can't really suggest what to look for in there. You might want to order up one of these - it can handle just about anything and is highly configurable:

http://tekgems.com/Products/adaptec-aha-2940uw.htm

[jswintx]

Thanks. I actually have an Adaptec 2940U2W that I picked up on ebay awhile back. Do you think that would work as well?

I did note that the Tekram never reported the size of the drive when I viewed the device stats inside the adapter program that I accessed by F6 at startup. I thought that was kind of strange, but if it was the bios in the adapter why would Drive Copy be able to read the "virgin" drive before the copy, but not after the copy? It made the copy and resized the partitions and this was all confirmed by Drive Copy at the end of the cloning. However after shutting down the computer and disconnecting the source drive, resetting the adapter to boot from the "new drive" and rebooting nothing would recognize the drive then. I can see it registered in the adapter program, but beyond that it is invisible to the computer.

Since Fdisk won't recognize it I suspect that the diagnostic program won't either, but I can't say for sure since I have the new drive out right now.

I appreciate the time you have spent with me working on this.

Thanks,
Jim W.

[glc]

I'd replace that Tekram with a 2940U2W in a heartbeat. Adaptec is *the* standard in SCSI controllers and Tekram is the price leader.

[jswintx]

GLC,

OK, that is what I am going to do at my first opportunity. I already have the drivers and board. I, in looking back over the "Compatabilty Files" for the 36XP find that that Tekram is not listed as being determined to absolutely work with this drive while the Adaptec is...so the issue seems determined as far as I can see.

Thanks so much for you help. I will check back and let you know what happens.

JIm W.