Cloned C drive appearing as slave

Dvc UNKNOWN
December 12, 2008 at 09:13:38
Specs: WinXP Srv Pk2, Dual PIII500
I cloned my C drive with Seagates/Maxtor Maxblast to a same make drive which are attached to a Promise ATA133tx2.

All went ok. But when I put the cloned C drive on the IDE cable on the master plug and set jumper to master, in the Promise ATA133tx2 boot it says its on D1 IDE 1 which is the slave part of the cable.

So when I plug in a slave drive or dvd in the slave plug and set to slave, the PC wont boot, says cant find Ntldr error.

I think the C drive is still trying to use ide 1 when its supposed to be ide 0.

The original C drive appears on ide 0 fine.

Is there something in the partition of the disk that I need to change? Any help much appreciated. :)

Bill


See More: Cloned C drive appearing as slave

Report •


#1
December 12, 2008 at 09:31:38
I don't know what you mean by "slave plug"?

If you're using master or slave jumpers rather than cable select, it doesn't matter which drive is connected to which plug.


Report •

#2
December 12, 2008 at 09:52:34
@I don't know what you mean by "slave plug"?

As in the hard drive is plugged into the second plug on the cable. I usually refer to the top plug master and second slave. Apologies for confusion. I never use cable select on drives.

Ive tried putting the C drive on either plug, Promise controller reports its on D1 regardless when its supposed to be on D0. The "D" number is location of drive on cable.

Bill


Report •

#3
December 12, 2008 at 09:53:23
HDD0 is going to be connected to the PRIMARY IDE channel. If you have the cable for the desired drive plugged into the SECONARY IDE channel it WILL appear as HDD1.

If you are using Master settings on the hard drive then you must use slave settings on the other drive connected to the same cable. You may have the optical drive set as CS (cable select) or Master.

I am not sure if you have ONE or TWO controllers on your Promise card. Are there TWO IDE connectors?

In addition MOST promise controller cards do NOT support ATAPI (optical) drives. Check the Promise site to verify. If you just bought the controller card then check the documentation. What model is the card?

edit

It appears Promise may have finally gotten their act together. I looked at newegg.com and the promise cards there DO support ATAPI drives.


Report •

Related Solutions

#4
December 12, 2008 at 10:10:40
My C drive is set as master on the primary. If i dont have anything else attached the promise card sees it on HDD1 and its supposed to be HDD0.

If i plug something in the secondary as a slave, Promise will see the slave on HDD1 but nothing is detected in HDD0 and the pc wont boot, i get the cant find Ntldr error. So theres a conflict going on there.

@I am not sure if you have ONE or TWO controllers on your Promise card. Are there TWO IDE connectors?

I have 1 Promise ata133tx2 ultra card and yes there are 2 ide slots on it. There are ide ports on the motherboard but theyre unused as theyre too slow. Hope that helps.

Bill


Report •

#5
December 12, 2008 at 10:32:06
So, does this mean the computer doesn't boot? Verify your clone drive is bootable by connecting to the onboard IDE controllers.

How are you identifying the Promise card in the BIOS settings? Try setting as a SCSI device. If your card is a RAID version you may need to configure differently.

I wouldn't be too concerned about how the drive is designated.

Below is an excerpt from the manual for your Promise card.

The card fits
into any available 32-bit PCI slot (must be PCI 2.1 or 2.2 compliant)

If you are fitting this card into a motherboard that doesn't support ATA133 then the PCI standard may pre-date the needed 2.1/2.2.

What is the model of your motherboard?


Report •

#6
December 12, 2008 at 10:51:59
It boots fine if theres nothing on the secondary.

@How are you identifying the Promise card in the BIOS settings?

Promise card is identified fine during post. It displays hard drives that are attached to it. I cant set as scsi or raid as its an IDE card. Theres no options for it.

Motherboard is compatible.

Its only with cloned drives thats doing this. If I use my original C drive and put a another drive on secondary it works fine.

Something on the cloned drive is causing it to not use hdd0.

Bill


Report •

#7
December 12, 2008 at 11:12:48
Below is another excerpt from the manual for the card. From page 4.

"WARNING: If you wish to use your current bootable drive with the
Windows NT4, 2000, or XP operating system on the Ultra133 TX2,
do NOT connect this hard drive to the Ultra133 TX2 controller before
installing the NT, 2000, or XP driver. You MUST install the NT, 2000,
or XP driver first (see “INSTALLING DRIVERS” section) to the boot
drive using your existing hard drive controller".

So the solution is to cnnect the cloned drive to the integrated IDE controller and boot into WinXP. Install the appropriate drivers on the cloned drive. Shut down and THEN connect the drive to the controller card.


Report •

#8
December 12, 2008 at 11:30:43
But its a cloned drive of my copy of xp which already has the drivers on it. I dont see how installing windows drivers is going to solve the detecting by promise card which happens in post. Or am I missing something?

Ive just done a test, and found the following:

When disk is on Primary as Master or Slave, it always is detected at D1.

When disk is on Secondary as Master its correct at D0. As Slave its D1.

So its correct on the secondary but not primary. Weird.

Bill


Report •

#9
December 12, 2008 at 11:35:40
Good catch Othehill.

I was just about to mention that moving/cloning drives between controllers is always a bad idea.

Different controllers will layout the disks geometry differently. This usually results in a drive that can boot on one controller but not on another.

Which is what the article Othehill found is really saying.

Example of Oxymoron:
Person who is pro life and anti sex education.
Education is key to prevention. Prevent conception you prevent abortion. Abstinence training clearly isn't working.


Report •

#10
December 12, 2008 at 11:53:07
Ok. So I take it there wouldnt be a way to alter the mapping by editing the mbr or something?

Heres a screenshot of the post boot of the drive just so you know what I mean by D0's and 1s :)

http://img119.imageshack.us/my.php?...

Bill


Report •

#11
December 12, 2008 at 12:13:16
Why not just connect the clone to the integrated IDE and boot. If it does boot to WinXP then RE-INSTALL those drivers. When dis the clone happen? after you installed the Promise controller? If so, did you follow the instructions when installing the Promise controller the first time?

BTW, referring to your comment about the card not being SCSI but IDE. Below is another excerpt from your Promise manual. It states your card SHOULD be identified in WinXP device manager asw a SCSI device.

"Click the “+” in front of “SCSI controllers”. “WinXP Promise Ultra133 TX2 IDE
Controller” should appear".


Report •

#12
December 12, 2008 at 12:19:10
I think you have the primary and secondary ports backwards. I think what you assume is the secondary (D1) is really the primary (D0) and vice versa.

Report •

#13
December 12, 2008 at 14:06:25
@I think you have the primary and secondary ports backwards. I think what you assume is the secondary (D1) is really the primary (D0) and vice versa.

Not likely as its marked on the cable itself.

@Why not just connect the clone to the integrated IDE and boot. If it does boot to WinXP then RE-INSTALL those drivers. When dis the clone happen? after you installed the Promise controller? If so, did you follow the instructions when installing the Promise controller the first time?

Ill give it a go booting on the integrated IDE tommorrow and try reinstalling drivers.

I installed xp on the original drive via Promise controller a long time ago. Pressing F6 during xp setup to install controller cards drivers then continue as normal just as described in the manual.

I tried a repair installation which reinstalls the promise drivers but it still stays on D1.

I might also try cloning again but keep the drive to clone to on the integrated ide and see what happens.

Bill


Report •

#14
January 9, 2009 at 06:14:07
Fixed it by doing the following:

* Did a repair install to the original xp drive which fixed the hal which wasnt working properly as the drive BSOD'd when trying to boot on the onboard ide.

The following was done on the Promise ATA133tx2 ide controller card.

* Put the old cloned drive that kept reporting itself to be on the D1(secondary) when it should be D0(primary), on the secondary on the ide and set to slave.

* Reinstall the Maxtor Maxblast software otherwise cloning wont work. It wont see the original drive if youve done a repair install of xp on it. So reinstall Maxblast or upgrade to latest one.

* Complete the clone operation.

* After cloning is complete and you shutdown and put the cloned drive onto the primary plug on the ide, it now reports itself to be D0 (primary), remember to set the jumper to master.

Im glad it all finally works! I think the whole problem was caused by the corrupted hal on the original xp drive so cloning it would have messed something up onto the cloned drive.

Hope that helps someone. Cheers.

Bill


Report •


Ask Question