does this make sense or am I off the track.

[Friendly]

When I 1st tried to boot from my 60 gig 2000 pro, it booted up fine. I then installed a scanner on it and went to reboot.
Thats when the bios wouldnt recognise it at 1st, then it would only recognise it as a 25 gig. I kept rebooting it and trying I finally got the bios to recognise it as a 60 gig.
But now it will only boot up to the Verifying DMI data pool.

I checked all the cables, jumper settings, virus scan etc.

I reinstalled a hard drive with winxp on it and installed the 60 gig as a secondary drive to check out what was on the 60 gig. It showed nada. The O/S and all the data including all the partitions had just up and vanished.
'Why would this happen. The hard drive still spins nice and quietly and appears to work fine.

set up as a slave in xp it is shown under disk managment as a healthy unforamtted drive and all the info, partitions have just up and dissapeard.

suggestions that i have had are

.
Corrupt boot files on the computer. How there is none as they have vanished?

Settings for hard disk drive are not correct. Jumpers checked

Boot devices not set properly. My other hard drive boots up fine. also boot order has been checked

BIOS corrupt or misc. setting not set properly. It reads my other hard drive fine

Connections loose or disconnected. Been checked.

Bad Hard disk drive or other bad hardware Bad hard drive maybe but it seems to be working fine and is seen be
a healthy drive in xp disk management. ( just says not formatted)

any body got any ideas as to what is going on?
I have noticed that my old 10 gig is running much much colder than the newer 60 gig problem drive.
It is very very warm all though not that hot that I cant handle it comfortably. Could this be the cause.

Also is this a problem not sure if this means much but the spec sheet says. cyl 16383 head 16 sector 63
But the BIOS reads cyl 7297 head 255 sector 63.
The hard drive is a Seagate Barracuda ATA IV Model ST360021A 60 gig

I have all the data backed up so it is no biggy but would love to try to figure out what has caused this problem. :disgust::evil::frown:

 

[yelo333]

you could try removing the scanner.

my 80 megabyte(not gigabyte, mebgabyte) hard drive had something corrupted with the beginnings of the disk(the media descriptor table, or something), which would cause scandisk, and any other disk health program to hang, as well as not let it boot, so you might have the same problem here, but that's a bit of a long shot

how do you pick which drive too boot off of?
maybe your multi-boot software is confused.

also, I don't know how old your mother board is.

awhile back, the award bioses had a bug that wouldn't let them use drives larger than about 30 gigs.
my PII motherboard has this problem.
you could check your manufacturer's website for any bios updates which might address the problem.

That's all I can think of!