WinXP fails to see second SATA drive

Associate
Joined
12 Aug 2003
Posts
37
Location
Dogsbodyville
SOLVED: WinXP fails to see second SATA drive

SHORT:

I have fitted a second SATA drive (non-RAID) to an existing P4C800, Win XP system, using the second SATA connector. The BIOS recognises the new drive, but when booting into Windows, there is no sign of the drive - in device manager, in 'Manage/Disk Management'. Nada, nowt, nothing. Do I have to do something in windows to force recognition of the drive?

Any other ideas :(

LONG:

Asus P4C800. WinXP SP2 + all patches. New drive is WDC WD2500K (250G SATA II).

In the BIOS,
the DVD drive appears as IDE Primary Master 1,
the existing Samsung SATA drive appear as IDE Master 3,
the new WD SATA II drive appears as IDE Master 4.

The new drive attributes, LBA, DMA etc, looks exactly as expected.

The BIOS boots from DVD then the Samsung. The option to boot from the new drive is not available.

The BIOS is set to non-RAID, Enhanced mode.

In device manager, there are no yellow '!'s.

Tried,

1. Booting from Linux installation disks. The new drive is presented as an option for installation/partitioning etc.

2. Booting from PartionMagic. The new drive is visible and partitionable.

3. Booting from the *original* XP installation disk. The new drive is presented as an option for the Windows installation, although, as expected, the drive size was limited to 128G.

4. Flashing BIOS to latest available.

5. Fitting jumper to new drive to limit interface speeds to SATA, not SATA II.

6. Swapped the new drive to the first SATA connector and the existing drive to the second SATA connector. Not suprisingly, WinXP fails to boot (boot.ini?)

7. Bashed head against nearest wall. :mad:
 
Last edited:
I've got the same mobo (except I've got the "deluxe" version). Can't think there will be much difference.

I had a few problems with installing new drives, but I've now got 4 SATA drives running without problems.

Does your mobo have 4 SATA slots??

Something like:

SATA1
SATA2
SATA_RAID1
SATA_RAID2

If your drives are connected to the sata1 and sata2 slots then they use one hdd controller (ICHR5 controller?). If they are on the other two slots (raid ones) then they use a different controller (promise controller?)

Which slot is your first drive connected to?? If its SATA1 then the second drive should be detected in windows if you connect it to SATA2.

If you are using the SATA_RAID1/2 slots then you may need to install more drivers in windows.

Boot into windows and insert your mobo cd. You can install the Promise controller from there. You want the IDE driver NOT the RAID driver!!

Hope this helps - if its just confused you I'll try and post more details when I get home from work. I'm trying to go from memory and I'm probably missing out a few things.

good luck!
 
I had the same issue 2 weeks ago with adding 2nd sata, use the manu's formating tools you can grab on floppy or iso, unplug good drive ideally, let tool see new drive, quick format going by on screen msg's, turn PC off and plug in prim drive and you will have 2 usuable drives on restarting.
 
Last edited:
Thanks guys. The non-deluxe MB just has the two SATA connectors - I think the ICHR5 is correct - since I'm not using RAID, my understanding is that the WinXP drivers will handle this situation without the 'F6' stuff. Using the AsusProbe S/W, it reports SATA1 and SATA2 (if my memory serves me correctly).

I have tried the WD tools, but only from windows. I'll have a go at the DOS/CD method tonight.

Thanks again. At least I have something to try :)
 
Windows will only see NF4 sata if your install cd is already XP-SP2 (slipstreamed), if your installing original XP or XP-SP1 then updating to SP2, it wont see HDD, you will need floppy and drivers and press F6.
Again even users who do this will want proper Nforce drivers installed later and not run MS ones.

I read into your post that you already have a primary drive running and are trying to add a 2nd drive as say storage, if so you can do as I said above, if windows own admin tools dont help format drive.
 
Last edited:
amdnv said:
I had the same issue 2 weeks ago with adding 2nd sata, use the manu's formating tools you can grab on floppy or iso, unplug good drive ideally, let tool see new drive, quick format going by on screen msg's, turn PC off and plug in prim drive and you will have 2 usuable drives on restarting.

amdnv, could I just clarify something. Have you used the Western Digital disk utilities, or were you just refering to the manufacturer's tools, in general?

If it was the former, was it the 'Data Lifeguard Diagnostic for DOS (CD)' or the 'Data Lifeguard Tools 11 for DOS'?

The reason I ask is that the bootable Diagnostic has a 'Write Zeroes' option, but not 'format'.
 
I added Raptor150 and I had to drag lot of data over from a Maxtor as a TEMP measure to format maxtor to fix bad windows file sys,to later drag back to use as storage only and format and use Raptor150 as prim, so i used WD tools as Maxtors formating tool called Maxblaster4 only works on Maxtors but the other Maxtor tool called Powermax works on any drive, but its not for setting up new drives only checking and erasing fully as in "0" filling.

Grab the floppy or bootable iso of WD tool and boot to it, then set up as screen talks you through it, choose quick format or quick NTFS (whatever it says)

It was 1st time I used WD tools, so cant remember, but read info on page and it will tell you what tool does.

Hey infact I think I grabbed a windows tool from WD, it installs to your current install and runs in windows, I really cant remember 100% and it was only 2weeks ago lol. :p
 
Last edited:
Aaaagggggghhhhhhhhhhhhhh!!!! :mad:

Ok, I tried the full test with the Western Digital utilities and it made no difference whatsoever. :( :(

So, I was rooting around in the device manager, looking at the properties of the 'Primary IDE Channel' (there are two of them, one for the real IDE interface and a further 'Primary IDE Channel' and 'Secondary IDE Channel' for the SATA interfaces.

I noticed that on the Advanced Settings tab, the Device Type was set to 'none'. Hmmm, I changed this to 'Auto Detection' and re-booted.

Alla-bloody-luia!!! The new disk popped up in the Disk Management section and I'm in business.

The really annoying thing is that I have used this facility in past to deliberately ignore some linux drives. I just forgot about it.

Thanks for your help, people. Hopefully, this will remind others to check the Device Type settings if they have simllar problems.
 
Back
Top Bottom