I had a very similar problem this week. (Note: a happy ending follows.) The computer (Dell 4100, Pentium III, Seagate 160 HD, running Windows XP) had been working fine, and I rebooted, and got this message on the black screen... "A disk read error occurred Press Ctrl+Alt+Del to restart." The message repeated on the restart. I was unable to get into safe mode using F8, or run the diagnostics with F12, but I was able to get into the Setup by pressing F2 or Del on the restart, and in the Event log I noticed numerous messages produced by all my restarts... "Pre-Boot Error Keyboard not functional." But there didn't seem to be anything wrong with my keyboard. The green lights flashed on the restarts and all the keys seemed to work.
I was able to use the Windows XP CD to get into the Recovery Console, and at the prompt [C:\WINDOWS>] I typed [dir] to see if there was anything on the hard drive. Much to my relief I saw the entire contents of the Windows folder (I had heard of viruses creeping in through the boot sector and wiping out all data on the hard disk). I was beginning to think there was some kind of problem with the master boot record. I had read of other people with similar problems having great success using the fix master boot command [fixmbr]. But others had warned that you were taking quite a risk with your data on your drive if you did this.
I was really tempted to use fixmbr, but I decided to call Dell support. They ran a diagnostic on my computer, reset the BIOS to default settings, ran another diagnostic, and told me my hard drive was dead. They even offered to sell me a new one on the spot! I asked them if I could try running fixmbr or fixboot, and they said the only command they would recommend using was chkdsk.
My Seagate drive was only one and a half years old, and I was really hoping there wasn't anything seriously wrong with it. My previous Maxtor drive lasted over six years. So after talking to Dell I decided to get back into the BIOS with the F2 key on the restart, and checked to see what changes were made by Dell from the BIOS default reset. Previously, I had made a detailed list of all the variable settings in the BIOS. In the Boot listing, I noticed the Boot Device order had been changed so that [ATAPI CDROM] was now behind [IDE-HDD]. I wanted to try the Recovery Console one more tiime before I gave up, so I reversed the order so the computer would attempt to start from the CD before attempting to start from the hard drive.
I went back into the Recovery Console, and checked the definition of fixmbr by typing [help fixmbr] at the prompt. From the description, I knew that fixmbr would not proceed with any rewrite of any line in the boot sector unless I responded with a yes to the prompt. So, at the prompt [C:\WINDOWS>] I typed [fixmbr] pressed Enter, and held my breath. I got the following message...
**CAUTION**
This computer appears to have a non-standard or invalid master boot record.
Fixmbr may damage your partition tables if you proceed.
This could cause all the partitions on the current hard disk to become inaccessible.
If you are not having problems accessing your drive, do not continue.
Are you sure you want to write a new MBR?_
Well, I did not have any partitions in my hard drive, but at least I could still access the Windows folder. I was afraid of doing more harm than good at this point. I typed in [n] at the prompt, and then [exit] to get out of Recovery Console.
I took my Dell to my local computer repair shop. He ran a diagnostic test on the hard drive and discovered it was... still good! No damage, no errors. He too, was concerned about the fixmbr warning, so he removed all the data I wanted to save from my computer, and ran fixmbr. It did not correct the problem. He ran fixboot. Same result. Then, he reinstalled Windows XP. The computer worked fine. He put all my data back on, and I'm back to normal. As far as he could tell, there apparently was some glitch that caused the boot record to be corrupted or some part of the boot record to have been written somewhere else on the hard drive. He didn't think it was a virus, but he couldn't rule it out either.