System occasionally hangs, { DriveReady SeekComplete Error} in syslog

scuzzman · 02-06-2006, 07:59 PM

Since I installed a new hard-drive (200GB Maxtor, mounted at /home) in my box, it has been occasionally hanging up out of nowhere (I don't even have to be doing anything). When I take a look in syslog, I see pages and pages of this:

Code:

Feb  6 20:48:57 slackdell kernel: ide: failed opcode was: unknown
Feb  6 20:48:57 slackdell kernel: ide0: reset: success
Feb  6 20:48:57 slackdell kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Feb  6 20:48:57 slackdell kernel: hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78126290, sector=78126290
Feb  6 20:48:57 slackdell kernel: ide: failed opcode was: unknown
Feb  6 20:48:57 slackdell kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Feb  6 20:48:57 slackdell kernel: hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78126290, sector=78126290
Feb  6 20:48:57 slackdell kernel: ide: failed opcode was: unknown
Feb  6 20:48:57 slackdell kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Feb  6 20:48:57 slackdell kernel: hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78126290, sector=78126290
Feb  6 20:48:57 slackdell kernel: ide: failed opcode was: unknown
Feb  6 20:48:57 slackdell kernel: hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Feb  6 20:48:57 slackdell kernel: hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78126290, sector=78126290
Feb  6 20:48:57 slackdell kernel: ide: failed opcode was: unknown
Feb  6 20:48:57 slackdell kernel: ide0: reset: success

I've researched those error messages, and get a lot of results pertaining to DMA and fdisk, so I include this as well:

Code:

[root@slackdell /home/scuzzy]$ hdparm /dev/hda

/dev/hda:
 multcount    =  0 (off)
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 65535/16/63, sectors = 40000000000, start = 0
[root@slackdell /home/scuzzy]$ hdparm /dev/hdb

/dev/hdb:
 multcount    =  0 (off)
 IO_support   =  0 (default 16-bit)
 unmaskirq    =  0 (off)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 24792/255/63, sectors = 203928109056, start = 0
[root@slackdell /home/scuzzy]$ fdisk -l

Disk /dev/hda: 40.0 GB, 40000000000 bytes
255 heads, 63 sectors/track, 4863 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        4834    38829073+  83  Linux
/dev/hda2            4835        4865      249007+  82  Linux swap

Disk /dev/hdb: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1               1       24792   199141708+  83  Linux
[root@slackdell /home/scuzzy]$

Any ideas?

halvy · 02-06-2006, 08:18 PM

if its under warranty take the dammened thing back, i dont' like maxor anyway, they really dont' have that great of reputation.. just hype and cheap drives.

scuzzman · 02-06-2006, 08:40 PM

Thats the thing though - the errors are on /dev/hda, the Maxtor I just installed is on /dev/hdb.

Matir · 02-06-2006, 09:06 PM

Try replacing the IDE cable. Perhaps a conductor was broken when installing the new drive. I've often seen these errors with bad cables.

scuzzman · 02-06-2006, 09:46 PM

Thanks. I have badblocks running right now on the new drive (the Maxtor) just to be sure. I'll replace the IDE cable in the morning.

scuzzman · 02-10-2006, 04:26 AM

OK - the problem wasn't with the IDE cable. Though, after running badblocks on the hdb (the new Maxtor) this has been happening less frequently. Any other ideas?