Re: Disk Read Error...What the Heck??
Well I'll be damned if I can understand it... some of it was the drive
Cable afterall. After cable replacement, did Chkdsk /P from the Rec
console: said there were problems with the drive, yet the Manufacturers test
prog Powermax gave drive clean bill of health. The test program wouldn't
even work with the old cable. Have Chkdsk set to run on next reboot to see
what is uncovered.
C J. <no.reply@example.invalid> wrote:
> GHalleck <ghalleck@arrakian.mining.com> wrote:
>> C J. wrote:
>>
>>> Today when turning on my PC - I was greeted with a "Disk Read Error -
>>> press ctrl - alt - del to restart." message. My PC has been running
>>> great - up to today. I'm thankful I thought to make a NT Boot floppy a
>>> while back just for stupid things like this happening.
>>>
>>> Anyway, I typed in the error and found a KB article relating to using
>>> older versions of Windows (multi boot) with Windows Vista. They
>>> recommend correctly re-installing the older OS.
>>>
>>> My problem however, is I'm running Windows XP SP2. Theres no Vista
>>> installed on my System, and I've had no problems starting up until
>>> today.
>>
>>
>> Disk read error can also signify the beginning of hard disk problems
>> or issues. Open Event Viewer and look for any error reports as they
>> provide clues of where to start troubleshooting. Run Chkdsk. Download
>> diagnostic programs from the maker of the HD and run them. Having a NT
>> bootable floppy is not good enough if the hard drive physically crashes;
>> make backups of whatever is important. This error might be very minor
>> and of no consequence but be prepared.
> Thanks G for the heads up.
>
> Funny you suggested looking in the Event viewer. I did this yesterday,
> and didn't find anything in SYSTEM. This morning is a different matter.
>
> 1 item -- Source: ATAPI Event ID: 5 Parity Error detected in
> \Device\ide\ideport0
>
> 6 -items Source: Disk Event ID: 11 Controller error detected in
> Harddisk 0\D
>
> I'm thinking this 7 y/o Intel Motherboard has finally decided to go out.
> I've got another Maxtor boot drive with a valid copy of OEM WinXP Pro
> installed on it (first XP I ever used.)
>
> I'm going to scan harddisk first, and see if any errors are detected with
> Maxblast.
>
> Then I'm going to plug old drive in the primary ide channel, Slave this
> one on secondary IDE - and see if the error duplicates with the older
> drive in the chain.
>
> Per the links Rock provided (thanks much.) The threads were over 3 years
> old. Most of the problems reported consistently varied with different
> brand Drives, hardware such as cabling. People tried Repair installs,
> Chkdsk /p Fixboot and fixmbr with a mixed bag of results. Some posters
> even suggested reformatting the drive to Fat32 (which I'm not about to
> do.)
> I'll report back my results.