Cleared the CMOS...

[linuxconvert]

I was trying to overclock my computer and it stopped, so I cleared the CMOS and now it won't recognize any of the drives! any suggestions?

Specs:
Celeron 400 MHz socket 370
Procomp BS61M motherboard
384 MB PC66???
Fujitsu 4.31GB HDD
Fujitsu 8.48GB HDD
Seagate 10.2GB HDD
Lite-On CD-RW

BTW i'm using this for a beowulf cluster

 

[JimPhelpsMI]

Hi, With most MBs you would have to go into the BIOS Setup and re-set the drives. You should find a way to get the BIOS to do it for you. Some you select the drive and press enter. Others have a function that will do them all at once. If you can't find either some will allow you to set the drives to "AUTO" and the BIOS will pick them up on Boot.
Good Luck, Jim

 

[furballi]

Disconnect AC power and remove the CMOS battery for about 1/2 hour. Retest. Should work unless you have hard drive corruption.

 

[porcorosso]

You said that the computer "stopped" when you tried to overclock it. What do you mean by that? If the drive controller itself sustained actual damage during this event that would give you the symptoms I think you're reporting. It sounds as though the BIOS sees none of your drives. If the drives were merely corrupted (messed up file systems) they would still be detected during POST, methinks.

When you say the system won't recognize any of the drives, are you saying that it doesn't even see your CD-RW drive?

 

[wseyller]

my mobo will output a message saying "overclock failed" and will make you restart or go to bios settings. Maybe it set the bios settings to default settings since the overclock failed. Maybe some settings need not be at default.

 

[linuxconvert]

just to update, I've set the BIOS settings to default, tried inserting the drive information in the BIOS, and even tried to auto detect them. All of which were to no avail. I know that they aren't dead because they all spin. And yes, it won't recogize the CD-RW drive.

When I said it "stopped" i mean that it wouldn't post.

 

[porcorosso]

Ouch! I'm thinking this sounds like damaged hardware. I hope I'm wrong, but I don't think so.

 

[arcenite]

no comment

 

[linuxconvert]

is there an easy way (any way really) to check if the hardware is damaged?

 

[porcorosso]

Originally posted by: linuxconvert
is there an easy way (any way really) to check if the hardware is damaged?

Well, in essence, you've already proved that the problem is a hardware issue. The problem is finding out WHICH hardware. Since you can't even boot the system you can't run the types of diagnostics that run under the auspices of the operating system.

If I were you I'd go over the system carefully, being sure that all internal and external connectors / cables /whatever are solidly connected and undamaged. I'd also look at the MB carefully to see if there were any obviously damaged components. If you find no loose connections / damaged cables / burned or blown components then going further will require you to have test gear (and knowledge of how to use it) and spare parts (for those parts of the system that can be swapped out with known good replacements).

Basically what I'm saying is that, by refusing to even try to load the OS, the system itself is proving to you that you have a hardware problem. But, in the absence of a beep code or visual clues from the components, it can be pretty hard to know exactly which hardware has failed.

 

[linuxconvert]

lol
ok, thanks