Thread: Disk Errors - Need Advice
July 31st, 2005, 10:53 AM #1
Disk Errors - Need Advice
Last night after I experienced a few random system lockups, I checked the event viewer to find 50+ system errors spread over a few hours of time:
Event ID:51 An error was detected on device \Device\Harddisk2\D during a paging operation
That particular drive no longer showed up in windows explorer until I rebooted.
Then all was good for a few hours...I woke up today, checked again and saw this about 10 times over a 2 hour period:
Event ID:51 An error was detected on device \Device\Harddisk3\D during a paging operation
This isn't much help to me:
What is Event ID 51 in the Windows XP System event log?
I have a Soyo KT333 Dragon Ultra motherboard:
My drives are configured as such, obvioulsy all masters on their own channels...all PATA:
IDE 1: LiteOn 16x DVD Burner Field (LITE-ON DVDRW SOHW-1633S)
IDE 2: Western Digital 200GB HD (Maxtor 6 Y200P0 SCSI Disk Device)
IDE 3 (RAID port, but no RAID config): Maxtor 60GB HD (MAXTOR 6 L060L3 SCSI Disk Device)
IDE 4 (same as IDE 3): Western Digital 160GB HD (WDC WD1600JB-00GVA0)
In that order, disks 2 & 3 are both on my RAID ports...although my disk management shows this:
That would indicate disks 1 & 2 having issues, not 2 & 3.
It should obviously be a RAID controller/driver issue, as it would be a very slim chance that 2 of my drives are failing at once. I noticed that although my board is discontinued, there is an updated RAID driver,
v 2.341 (April 03)...my current driver is 2.31 (Jan 02)
You think this newer driver could resolve my issue? If so, why would it just happen all of the sudden?
Anyone have experience with this issue? I googled a bit and it seems that the errors are mostly RAID related.
I already have everything backed up, just in case:
Last edited by Martoch; July 31st, 2005 at 11:15 AM.
July 31st, 2005, 12:26 PM #2
Now every time I start up my system, J: needs to be checked for consistency and I have this in my system log:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume J:.
July 31st, 2005, 12:30 PM #3
Yup. Sounds like your RAID array headed south. Looks like it's time for updating the drivers and a rebuild.
July 31st, 2005, 12:45 PM #4
I didn't actually have a true RAID array set up, just utilizing the RAID ports or normal IDE channels.
Just flashed my BIOS to the latest version and moved the J: drive to a non-RAID port...rebooted, still got the chkdsk checking J: for consistency and this in my system event log:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume J:
So the problem with the drive is not RAID related...maybe my WD 200GB drive is failing...but I'm a bit confused, that drive has F, H, and J...but only J is coming up with errors and event logs. Wouldn't the other partitions have the same errors if the entire drive was failing? Why would only J: have issues?
I'm running a chkdsk /f /r on J: now:
The /f command automatically fixes any errors encountered, the /r command locates bad sectors and recovers readable information.
Seems to be taking forever, it's been at stage 4 of 5 (verifying file data) at 0% for 5 mins.
Question: Can I update the RAID controller drivers without moving my system drive to a normal IDE port? I've never updated the driver...only loaded it from the mobo disc when I put the system together.
Last edited by Martoch; July 31st, 2005 at 12:51 PM.
July 31st, 2005, 02:31 PM #5
I ran Maxtor's PowerMax disk diagnostic utility and so far the drive passed both the simple and advanced tests.
I'm running the burn-in test with 2 passes now...I'm sure it will take a while, and I'll be baffled if it passes that as well. There are no more tests to run...my next PMax option is a low level format.
July 31st, 2005, 02:41 PM #6
Hmm. I'm sure you can update the RAID drivers in your current config. I'm not sure either, I did the same as you with my trusty ol' KT7A-RAID. I've heard of the early SATA controllers corrupting HDDs, but I didn't think it was as common with RAID controllers.
July 31st, 2005, 03:24 PM #7
Thanks, I'll update the RAID driver after the burn-in tests are done, but that still won't solve the issue of only my J: partition having issues on a non-RAID channel, while the other 2 partitions on the same drive aren't showing any errors.
July 31st, 2005, 05:05 PM #8
Okie Dokie...just saw that the drive passed the burn-in test as well. Booted up and J: did not get checked for consistency this time and there are no recent errors in the system even log. A little consistency would make it easier to troubleshoot.
I have no idea what's going on here.
July 31st, 2005, 05:15 PM #9
July 31st, 2005, 05:27 PM #10
Yeah, duh...of course I did.
Did you think I had no idea what was going on or something?
July 31st, 2005, 05:36 PM #11
I had full confidence in your abilties Martoch.
Now, where's my M&Ms for helping?
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By rhflee in forum Technical SupportReplies: 2Last Post: January 30th, 2005, 09:16 PM
By quiksan in forum Technical SupportReplies: 7Last Post: June 30th, 2004, 12:54 PM
By cau in forum Applications and Operating SystemsReplies: 0Last Post: May 4th, 2004, 12:21 AM
By robin801 in forum Storage RelatedReplies: 21Last Post: February 18th, 2003, 07:09 PM
By vass0922 in forum Applications and Operating SystemsReplies: 5Last Post: June 7th, 2002, 04:24 PM