Moved everything into new case. Now it won't boot up 2

[pantichd]

Hello,

I had outgrown my old case so I moved everything into a new case. When I try to boot up it won't boot. During bootup I can see that it detects my hard drives but when it tries to boot it displays message:
"Disk Boot Failure, Insert System Disk and press ENTER"

My configuration is:
Gigabyte GA-7VT600 motherboard
1GB memory
AMD Athnlon XP2700+ CPU
160GB Seagate hard drive (Win XP installed on this one)
120GB Seagate hard drive
CD drive
Floppy drive

I checked all connections and tried again with same result. So I started from scratch. Disconnected everything but the 160GB drive. Same result.

Connected the floppy too and booted from the Data Lifeguard Tools floppy that came with the Seagate drive. When I tried to run diagnostics against the hard drive I got the following message:
"Unable to find IDE drive for Int 13h drive number 80H. This may be because of a SCSI drive or some other non-IDE drive type or there maybe a problem with your drive connections or BIOS settings."

How is it possible that the BIOS recognizes the hard drive but then the data from the drive can't be read during bootup?

Thanks in advance for any feedback.

 

[edfair]

What kind of cable? Changes in cable routing?
And the possibility that one line got grounded. The standoffs in the new case should probably be in the same place as in the old case. And look closely if the standoffs are made differently.
You could try it with cardboard under the M/B.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[wolluf]

Have you tried drive on both IDE connections?

Presume you've checked all cabling & haven't changed jumpering so should be ok?

Have you tried putting drive (& minimal to support it) back in old case?

It was just a case change (nothing else)?

You have checked the bios settings are all ok (still as they were in old case)?

 

[pantichd]

Ed,

I used the exact same cables as in the old case for the hard drives, cd and floppy drives.

I had posted this question on another forum and people there also mentioned standoffs. I checked the motherboard and the standoffs are in the same spots as the old case.

I haven't tried putting the motherboard on cardboard. Someone had suggested that in the other forum but then a subsequent post in that thread cautioned against doing that.

You mentioned "the possibility that one line got grounded". Is there a way for me to tell if that happened?

Thanks!

 

[paparazi]

If it just plain can't find the drive, then have you got the cable orientation correct? and is the drive properly powered? have you accidently swopped drives around on differant channels, have you changed your bios settings?
Martin

Replying helps further our knowledge, without comment leaves us wondering.

 

[edfair]

Assuming same cables and the drives can be seen in the proper places the problem has got to be some line gone or noise on the cable.
40 or 80 cable? How are the drives jumpered?

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[pantichd]

woolluf,

>>Have you tried drive on both IDE connections?
Yes

>>Presume you've checked all cabling & haven't changed >>jumpering so should be ok?
You are correct

>>Have you tried putting drive (& minimal to support it) >>back in old case?
Not yet. I used the old case to build a new machine for my kids. I have been avoiding that because I'm afraid I'll screw something up on their pc. : )
One thing I did try was to try a spare hard drive with nothing else connected on the new case. Same result.

>>It was just a case change (nothing else)?
That's correct. Nothing else.

>>You have checked the bios settings are all ok (still as >>they were in old case)?
Well, they were the same when I started out but since then I've tried many different combinations to reflect the hardware that I have installed during that test. Today I even removed the battery to clear the CMOS and started from scratch again.

Thanks!

 

[pantichd]

Martin,

>>If it just plain can't find the drive, then have you got >>the cable orientation correct? and is the drive properly >>powered? have you accidently swopped drives around on >>differant channels, have you changed your bios settings?

It does recognize that the drives are there. During the startup process I see a message "Detecting IDE drives" and then it lists the correct information about the hard drive

That's why I asked how it is possible for it to recognize that the drive is there but not to be able to read the data from it.

 

[pantichd]

Ed,

>>Assuming same cables and the drives can be seen in the >>proper places the problem has got to be some line gone >>or noise on the cable.
>>40 or 80 cable? How are the drives jumpered?

Yes, I'm using same cables. I'll try different ones. Is there any kind of diagnostic tool/utility I can use to test for "some line gone" or "noise on the cable"?

I have to show my ignorance here... I don't know what you mean by "40 or 80 cable". Can you elaborate please?

The 160GB drive is the one where XP is installed and it's jumpered as master. I also attach the END of the IDE cable to it. That's right isn't it?

thanks!

 

[edfair]

What colors are the IDE connections? The 80 line cables have black, blue, and gray connectors. And the drives are normally set for CS , the board end is blue, the master plugs on the end. The slave wire ends at the middle and so the drive in the middle is slave.
40 wire cable has the same color IDH connectors.
At higher speeds the cables are sensitive to crosstalk, and the fix may be as simple as going to 80 line cable. Or a different length. The 80s have ground lines between signal lines to cut down on crosstalk.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[pantichd]

Well, problem solved. All I did was set the jumpers on all the ide drives to Cable Select.

I'm glad it worked but I don't understand why it didn't work when I had the jumpers set to specify how (master/slave) I was using each drive.

Thanks everyone for your feedback!!

 

[paparazi]

pantichd
Thats what I was getting at.
The motherboard seeing the drive but not booting from it would indicate jumper/drive or cable configuration was wrong somewhere along the line, that's why I asked if you had swopped the drives around accidently.
Anyways, nice to see you have it fixed.
Martin


Replying helps further our knowledge, without comment leaves us wondering.