Jump to content
  • Announcements

    • spinynorman

      Mandriva Official Documentation

      Official documentation for extant versions of Mandriva can be found at doc.mandriva.com.   Documentation for the latest release may take some time to appear there. You can install all the manuals from the main repository if you have Mandriva installed - files are prefixed mandriva-doc.
    • paul

      Forum software upgrade   10/29/17

      So you may have noticed the forum software has upgraded !!!
      A few things that have changed. We no longer have community blogs (was never really used) We no longer have a portal page.
      We can discuss this, and decide whether it is needed (It costs money) See this thread: Here
Sign in to follow this  
fuzzylizard

Hard Drive I/O Errors - Help

Recommended Posts

I am getting the following errors showing up in /var/log/messages about every 5 - 20 seconds and I don't really understand what they mean.

 

Oct 18 21:55:16 Rivendell kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
Oct 18 21:55:16 Rivendell kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=89894191, sector=17039416
Oct 18 21:55:16 Rivendell kernel: end_request: I/O error, dev 03:03 (hda), sector 17039416
Oct 18 21:55:16 Rivendell kernel: EXT3-fs error (device ide0(3,3)): ext3_get_inode_loc: unable to read inode block - inode=1054725, block=2129927
Oct 18 21:55:16 Rivendell kernel: EXT3-fs error (device ide0(3,3)) in ext3_reserve_inode_write: IO failure

 

In addition, I tried to reboot the server and was welcomed with a ton of disk errors. I did a manual fsck and simply selected the defaults when it asked to fix/ignore/save something. This took about an hour to run through.

 

I restarted the computer and everything seemed to be going fine, although I had lost some functionality. This lasted for about 10 minutes.

 

I tried the following command to see if there were any bad blocks on the drive:

 

$ /sbin/badblocks -v /dev/hda

 

This basically killed the drive. The entire computer became inactive. When I tried to switch to another console (ctrl-alt-1, 2,3,4,etc) all I got, on every screen, were the error listed above. I finally had to turn the machine off.

 

My next move is to pull the drive out, put it in another computer and run the Maxtor disk diagnostic tools on. (no floppy drive in the server).

 

Anyone have any idea as to what might be going on here.

Share this post


Link to post
Share on other sites

have you modified your system files (like fstab)? if not, i do think the disk is slowly dying... :sad:

Share this post


Link to post
Share on other sites

Nope, I haven't done a thing to the system. I was checking my logs for an SSH attack that is currently going around and found the log entries above.

 

I have to agree that the drive is dying.

Share this post


Link to post
Share on other sites

Just for an update on my little drive - I downloaded Knoppix and booted the computer using it. This allowed me to do a badblocks check independent of running the kernel.

 

I eventually stopped the check after what looked like several thousand bad blocks scrolled by in the console window. Needless to say, the drive is toast.

 

For anyone else in this situation, a great command for checking your drive is badblocks. It performs a non-destructive read of every block on your drive. If your drive is really bad, you may want to run it from something like Knoppix though. Here is the syntax

 

# /sbin/badblocks -v /dev/hda

 

or whatever drive you want to check

Share this post


Link to post
Share on other sites

Nice tip, thanks. But for checking a hard drive, I've found nothing better than the hard drive manufacturer's diagnostic utilities. All the majors have them freely downloadable on their websites. Typically, you get a file that when executed in windows creates a bootable floppy with the hard drive utilities on it. They come in very handy as most of them have a zero fill utility that can totally wipe the drive if it's completely borked. Also, if your returning the drive under warranty, most manufacturers ask that the defect is confirmed by their utilities before giving you an rma.

Share this post


Link to post
Share on other sites

Yep, I agree. In my case, the drive is no longer under warranty so there is no point in trying to return it. In addition, I don't have a floppy drive on the computer that has the drive. I will probably try the manufacturer's tools this weekend on the drive to see just how bad things really are.

 

If the drive is still under warranty, definitely run it through the diagnostic tools first. I have done this with other drives that have failed and it has always helped when it comes to getting them replaced.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×