Verifying DMI Pool Data problem

I recently purchased a 200GB Maxtor IDE drive and installed it into my system. Try to go through the normal formatting procedure, nothing happens. Check the cables, everything fine. Several other possible solutions were tried, nothing works. I assume the drive is defective, so going to return it.

After removing that hard drive is when I started hitting some larger problems. The 200GB drive mentioned earlier was on my secondary IDE channel with another 120GB drive. After removing the 200, I turned the computer on and noticed that the 120GB drive is no longer being recognized as formatted/useable. If I open up Disk Management, it wants me to format, but if I try to do so the computer will simply hang and do nothing.

So I check my BIOS, and notice that my 2nd IDE channel is set to be disabled (not sure when that happened). So, I re-enable it. Save preferences, quit the BIOS, and my computer now hangs at Verifying DMI Pool Data in the bootup sequence. Go back to BIOS, change it back, everything works fine, except for not seeing the IDE drive.

Not sure what the hell is going on at this point, I test the drive in my other computer and it works normally.

I had gotten the DMI error before a couple times, and found that the cables for my SATA drives had become loose. I checked those, they’re fine still.

Any idea how I can get the IDE drive working in this computer again?

Specs: Chaintech VNF3-250 w/ AMD g4 3000+, dual 80GB SATA drives (non-raided, one is the boot drive), the IDE drive, Radeon 9800 Pro, 2x512mb Crucial DDR400 ram

Likely, you’ve got the jumpers set wrong on one or more HDDs. The drive at the end of the IDE chain should be the master, while the one in the middle should be slave. Don’t use ‘cable select’ as a setting, since that has been known to cause problems.

Tried the jumpers, still getting the same problem. I only have the one HDD in at the moment as well.

The next think I’d check out is the BIOS. It’s probably a good idea to set all IDE devices to “AUTO” and let the motherboard sort it out.

Everything is on auto except for the 2nd IDE channel, and enabling that in any way brings up the DMI error.