abbyqueue

I recently rebuilt my system and bought a new 120GB Western Digital hard drive to serve as master to my old, smaller Western Digital hard drive. Also bought new motherboard. When I tried to install the drives as cable select, the system ignores (or doesn't recognize) the old hard drive and simply goes right to the new one (on which I installed WinXP Pro, same as my old one). There is no mention of the old hard drive anywhere in the system. When I tried to install the drives as master (new) and slave (old), the system hangs when "Detecting IDE drives" when booting. Finally, I took the new hard drive off altogether and tried to boot from the old hard drive; I got a BSOD with a STOP error. My solution thus far has been to use the new drive exclusively, but, as always, there's data on the old hard drive I would like to have (specifically, one folder I forgot to copy when changing drives!).

I've tried messing around with the jumpers and even changing out cables, but to no avail. I hope the BSOD when booting from the old hard drive alone doesn't mean that it's dead -- I can't see how that's possible; I just took it right out of my old PC and installed it in the new one.

If anyone has any suggestions, I'd love to hear them. Thanks for your help!

mark3567

Hi,

I do think that it is probably not dead. If the old drive was formatted and then the OS put on with another mother board, it just probably won't boot because it is looking for the drivers from the old board. Therefore, you are going to have to leave it as a non-booting drive somewhere. I would suggest trying it as master on IDE #2 alone on the cable and and placed on the end of the cable (black connector). Since it is Western Digital, take all jumpers off of the drive and try it that way in the master position. Be sure you put your CDrom as slave on IDE #1 with your new drive. See how that goes.

Addendum: Don't forget to make sure your boot order is set to:

CDRom - 1st
Floppy - 2nd
New Hard Drive - Boot Drive - 3rd
(note: make sure the old hard drive is not here anyplace in the boot order)

Don't forget to save before you exit.

abbyqueue

First, thanks for your speedy reply.

OK, I tried what you said -- put it on IDE #2 alone, on black connector (I had to disconnect my CD-ROM and CD-R drives for this; they were plugged into the IDE #2 position). I took all jumpers off both hard drives. I left my new hard drive in the master position on the cable for IDE #1, but the gray/slave connector won't reach my CD-ROM drive, so I left that unplugged. (As an aside, how would I get that to reach?) Made sure my boot sequence was in the order you said, and booted. The new hard drive booted fine as always, but the old one still isn't being detected at all.

Also, does it matter whether or not the BIOS is set to auto-detect or manual? I think I left it on auto this time.

Could the problem be that I need a BIOS upgrade? I downloaded one but was pretty freaked out about installing it -- Soyo's website was talking about doing it at your own risk and re-flashing, whatever that is...

mark3567

Hi,

I was just trying a hunch (but missed I guess) so put it back like you had it, meaning the cd drives on IDE $2 and the hard drives on IDE #1. Leave your new one as Master with jumpers set to master and on the end of the cable (black connector) and the old drive jumpered as slave and on the gray connector (middle of the cable).

Yes, the BIOS area for hard drives needs to be set to automatic. Also, since this is not a new build, do you have the 80 pin ribbon cables? If you have the old 40 pin, then that might be part of the problem.

Well, a bios upgrade won't hurt any, but it does not sound like that would be it, but I am just guessing.

Might be a good idea to tell us what all your components are, like motherboard, CPU, memory, video card, so we get a better picture of what you have and are dealing with.

abbyqueue

OK, I put it back like you said, with the CD drives on IDE 2 and hard drives on IDE 1. I jumpered the new as master and old as slave, but, as always with that configuration, the system hangs at "Detecting IDE Drives" when it boots. So I had to disconnect the old hard drive and just use the new, as usual.

The BIOS is set to automatic. I have the 40-pin cables (the ones that came with my new motherboard); my friend (who knows a little about computers but is never readily available to me as a resource) said those should be fine. I mean, they fit... I guess that means something. :)

He also said don't do a BIOS upgrade because that shouldn't be the problem, so I haven't done that yet.

My components are:
Soyo CK8 Dragon Plus motherboard
512 MB RAM
AMD Athlon 64 Processor 3000+
Don't remember video card, but Device Manager under "Display Adapters" is saying "NVIDIA GeForce2 MX/MX 400 (Microsoft Corporation)," if that means anything
new Western Digital hard drive

Everything else is the same as it was on my old system:
old Western Digital hard drive
Acer CD-R drive
CD-ROM drive
floppy drive
Added USB 2.0 PCI card

mark3567

Hi,

That helps somewhat. By the way, do you have the Raid feature (assuming your board has promise raid) or promise raid feature enabled? The default setting for that feature is enabled, but you need to turn it off if it is not in the BIOS setup menu.

If the cables have a Blue, a Gray, and a black connector, it is likely they are an 80 connector cable. And, if they aren't like that, then you need to trade them for the 80 connector cables for the hard drives only. Unfortunately, the wiring on the 40 connector cables looks very much like the 80 connector cables, so the color coding of the 80 is the best way to tell on most (not all) cables.

I did say last time I didn't think it would be a BIOS issue although if you wanted to upgrade, it would not hurt it. I would not go that route just yet if it were me. Therefore, I agree with your friend for now. There are some boards that won't boot with the Athlon 64 unless you have the newest bios, but yours does boot, so not the issue.

Also, you mentioned that you had a PCI USB card. I would take that out of the mix until you get this settled. Those cards can sometimes cause big problems when you first set up. In fact, disconnect all the usb devices for now. Try it that way with those out while you troubleshoot.

Another thought, since you are using WinXP, be sure your PnP is set to disabled in the BIOS setup menu.

abbyqueue

OK, my motherboard's manual says that it does have some sort of RAID feature:
"Storage: nForce 3 150 Integrated Parallel ATA controller supporting up to 4x UDMA 33/66/100/133 Parallel ATA devices.
nForce 3 150 Serial ATA RAID controller supporting up to 2x UDMA 150 hard disks"

The manual never mentions how to turn it off. I went to their website and found this:
"2. Make sure the onboard RAID is enable in the BIOS, some boards have to be done by jumper on the motherboard in addition to the settings in the bios, some only need to be enabled in the bios, other may already enabled by default. This setting should be in the "Soyo Combo Features" submenu in the BIOS."

I went to that menu, and every other menu in the BIOS, but didn't see anything pertaining to RAID. So I'm stuck -- I have no idea how to turn it off.

The cables do have blue, gray, and black connectors. I disabled all my USB devices in order to troubleshoot as directed. PnP was set to disabled in the BIOS menu.

I'll try to reconfigure the drives as master and slave and boot while waiting for your response (thanks again, by the way) regarding the RAID stuff.

mark3567

Hi,

Actually don't know if this could be the problem and does not sound like it , but need to make sure we have everything set up correctly. Anyway, I don't know that board, but wanted to make sure you have the drives in the right place. For example, my board has under the advanced area, Onboard Promise controller and the default is enabled, but if not using raid, that needs to be disabled. (I seriously doubt a board like this would have a jumper you would need to change, most of the new ones have the BIOS setup for raid with no jumper setting needed). There should be a little sub-head under that which would say operating mode - RAID if it is enabled. The board should have probably four connectors for ATA which would be Raid One, Raid Two....then IDE #1, IDE #2, plus the floppy drive connection. Check your chart. If not using Raid, leave the Raid connectors empty.

Addendum: Is there any way you could try this drive as a slave in another computer so we can rule out your computer being the cause?

dai

you need the 80 wire cables
wd drives are a bit different to set up to most drives
single master=jumpers removed
master with slave= set the jumpers to this position
slave =set the jumpers to this position
if your original drive was the only drive then you will have to change the jumpers on it,to reflect the new setup

abbyqueue

OK, I finally found the larger version of the help manual online (www.soyousa.com) but it still only mentions RAID once in 100 pages:
"nForce 3 150 Serial ATA RAID controller
supporting up to 2x UDMA 150 hard disks"

I then took a look to see if it told me how to disable it in the BIOS section. The only things I found that look remotely close to yours or even relate to HDDs at all are these:

"Setting Description Note
IDE HDD Auto-Detection Press Enter To auto-detect the HDD’s cylinders, head, sectors and size on this channel
Auto BIOS detects hard disk type automatically.
Default
User User defines the type of hard disk.
IDE Primary Slave (User Type)
None
Auto BIOS detects hard disk mode automatically.
Default
CHS Normal IDE hard disk <528MB
LBA Enhanced IDE hard disk >528MB
Access Mode
Large Large IDE hard disk (for certain
hard disks)

Then this:
"HDD Enabled S.M.A.R.T. Capability Disabled
Enabled this field when your HDD supports the S.M.A.R.T. function.
Consult your HDD provider for details.
Default"

Now this is what I found under Integrated Peripherals, and thought this might be of note:

"On-Chip IDE Channel0/Channel1
Enabled Use the on-board IDE Default mode 0-4 0 is the slowest speed 4 is the fastest speed
IDE
�� Primary Master PIO
�� Primary Slave PIO
�� Secondary Master PIO
�� Secondary Slave PIO
Auto For better performance and stability, we suggest you use the Auto setting to set the HDD control timing.
Default
IDE Disabled
�� Primary Master UDMA
�� Primary Slave UDMA
�� Secondary Master UDMA
�� Secondary Slave UDMA
Auto Select Auto to enable Ultra DMA Mode support.
Default
IDE Prefetch Mode Disabled
Enabled
Enabling this option allows reads from the IDE controller to be prefetched to cache to speed up accesses to it.
IDE DMA transfer Enabled Default access Disabled
This option allows the 82801ER (ICH5R)’s IDE controller to directly transfer data to memory without intervention or the CPU if enabled.
IDE HDD Block Mode Disabled
Enabled Invokes multi-sector transfer instead of one sector per transfer. Not all HDDs support this
function."

That's all I see mentioned about hard drives. Sorry it's formatted so badly here; you can find the full manual at http://www.soyogroup.com/downloads/s...77&col3=Manual if you want.

Also in that manual, it has the motherboard layout. I have an IDE 1, IDE 2 and IDE 3 (also listed as the floppy disk controller). Then I have SATA 1 and SATA 2. I'm currently using IDE 1, IDE 2 and IDE 3. The SATAs are empty. There are no specific labels that say "RAID."

Sorry, I don't have another computer to test the old hard drive in... I'll look in the BIOS again to make sure I didn't miss a submenu or something that they didn't mention in the manual.

Wait a minute: I just realized that if the manual mentions RAID as a part of the serial ATA controller (SATA, right?), and if I'm not using SATA 1 or SATA 2, it shouldn't be a RAID problem, should it?

mark3567

Hi,

I can't see anything to tell you that should be different when looking at the board diagram. I also did not see anything that would indicate that raid is enabled on the IDE slots. Will do some more thought on this one and try to get back when I get home later. This does look like a great board. I am almost afraid the only way you will know if it is dead in the water except to try it in another computer.

dai

enable s.m.a.r.t
make sure this is enabled and set to auto detect
IDE Disabled
?? Primary Master UDMA
?? Primary Slave UDMA
?? Secondary Master UDMA
?? Secondary Slave UDMA
Auto Select Auto to enable Ultra DMA Mode support.
Default
check the jumpers are set correctly
set them as master and slave
i have the feeling you have one set as master and the other cable select,you cannot mix the settings

caldonia

Pardon me if you already tried this, but if you haven't, it may be worth a shot.

As Dai mentioned, make sure your jumper on your new hard drive is set to "Master /w Slave Present". I got burned myself on that one once. Easy fix though.

If that doesn't get it, I'd try this:

Disconnect all peripherals except videocard, mouse, keyboard.

Leave your new drive connected to IDE 1 Master
Put your old drive alone on IDE 2 Master
Both drives set to master / no slave present.

Good luck,
-Chip

abbyqueue

OK, here's what happened:
When I did what dai suggested and set one as master and one as slave, the same thing happened that always happens: it hangs when "Detecting IDE drives" at boot.
When I did as caldonia suggested, it simply boots right to the new HDD and doesn't recognize the old one at all, as usual.

Thanks for your suggestions! (Always welcoming more!)

dai

if the old drive was originally master,put it back as master and the new one as slave

abbyqueue

Since trying to boot from the old hard drive alone produces a BSOD, wouldn't it do the same thing when trying to boot the old HDD as master and the new HDD as slave?

abbyqueue

OK, did as dai suggested and the system ignores the old HDD as master completely, just boots right to the slave.

Update: Fixed a stupid problem only to encounter a real problem.

I changed the power supply to the old hard drive. Poof: it recognizes it. I guess that was the problem there. The new problem, of course, is the STOP error I get (and a nice BSOD, of course) when I set the old as slave and the new as master. It's something like this:

"Check for viruses. Remove any newly installed hard drives or hard drive controllers. Check hard drive to make sure it's properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, then restart your computer.

STOP: 0x0000007B (0xF88C0528, 0xC0000034, 0x00000000, 0x00000000)"

That's what I get when I chose to "Start Windows Normally." When I choose to start in Safe Mode, I still get a BSOD, but a slightly different STOP error number.

Now, my question is, is this worse or better problem to have? :)

dai

then it is a hardware problem
the drive is either not jumpered correctley
not on the end plug
faulty cable
drive faulty
faulty power plug

abbyqueue

Well, I can assure you that the drive is jumpered correctly. It is on the end plug. I've switched cables, so it's unlikely to be a faulty cable, and I've switched power supplies, so it's getting power now. There could be something wrong with the drive, but I doubt it. Once I began having this new problem last night, I did a search for the STOP error 0x0000007B and returned a lot of results with what mark3567 said earlier: the new motherboard and old HDD don't sync. I called Microsoft and they said the same thing. They had me do a chkdsk on the old HDD and it came out OK.

So, in searching for solutions, this is basically what I got from Microsoft:
1. Flash the BIOS. Go to mobo's website and download chipset drivers.
2. Copy drivers to a bootable floppy.
3. Install chipset drivers.

Which, essentially, is what this guy is saying, I think:
"How to fix this problem for real...
1) Go to the intel web site enter your chipset (example 915P)
2) Download the boot floopy.exe
3) open it create a boot disk
4) change your BIOS settings (more than likely diffrent for diffrent MB Manufacturers but hopefully you can get the drift)in intergrated peripherals to:
On Chip IDE (Enable)
SATA RAID (Disable)
On Chip SATA (Enhanced)
HW RAID (Enable)
5) Boot with your XP disk press F6 to load controlers (if you cant get your CD dive to work change your BIOS settings in Advanced BIOS Features, on the gigabyte MB the first option you see you press enter & move the card to first and SATA drive second, change this back after you've finished)
6) When you get to the part asking you to press "S" load your boot floopy in press "enter"
7) THIS IS THE PART WHERE THERE IS SO MUCH DIS-INFORMATION YOU DON'T NEED TO LOAD THE SCSI DRIVER WINDOWS ALREADY HAS A SUITABLE ONE INBUILT, YOU NEED TO LOAD THE AHCI 82801FR or 82801ER DRIVER...
you will have to reinstal Xp first dont use the recovery console unless you know what your doing but at the apropriate time select repair from 3 options givin to you later (the others being new install & exit) if you want to keep your old profile and settings.
9) Let it reinstall XP & away you go PROBLEM FIXED"

The only problems now are, I'm not really sure what I downloaded from the mobo's website are the "chipset drivers." Does this sound like a good solution to anyone/everyone? Can anyone go into more detail as to how to fix this problem?

Also, the procedure for flashing the BIOS as described in the mobo manual involves downloading the BIOS file and awdflash utility to a bootable diskette -- is this the same thing as loading the chipset drivers, or is this just flashing the BIOS?

dai

the awdflash is for a bios update
the chipset drivers should be on your m/b setup cd
http://aumha.org/win5/kbestop.php
scroll down to
inacessable boot device