Loading ...
Sorry, an error occurred while loading the content.

HDD or controller error

Expand Messages
  • Eric Heenan
    Hi I ve got an Inspiron 8100 on which I m running debian sid with a 2.4.17 kernel. All s been running 100% perfectly for about 6 months, but in the last 10
    Message 1 of 1 , Jun 3, 2002
    • 0 Attachment
      Hi

      I've got an Inspiron 8100 on which I'm running debian sid with a 2.4.17
      kernel.

      All's been running 100% perfectly for about 6 months, but in the last 10
      days I've been getting very frequent errors associated with /dev/hda.
      Essentially all I know about them is included in the log snippet below:

      May 30 20:03:14 glennpc kernel: hda: timeout waiting for DMA
      May 30 20:03:14 glennpc kernel: ide_dmaproc: chipset supported
      ide_dma_timeout f
      unc only: 14
      May 30 20:03:14 glennpc kernel: hda: status timeout: status=0xd0 { Busy }
      May 30 20:03:14 glennpc kernel: hda: drive not ready for command
      May 30 20:03:49 glennpc kernel: ide0: reset timed-out, status=0xd0
      May 30 20:03:49 glennpc kernel: hda: status timeout: status=0xd0 { Busy }
      May 30 20:03:49 glennpc kernel: hda: drive not ready for command
      May 30 20:04:19 glennpc kernel: ide0: reset timed-out, status=0xd0
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      1835272
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      1835328
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      2097976
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      2883648
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      2883656
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      2883888
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      2884280
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      4165608
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      4718712
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      4774408
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      9699360
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      135704
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      135704
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:02 (hda),
      sector
      786512
      May 30 20:04:19 glennpc kernel: IO error syncing ext2 inode
      [ide0(3,2):0000bcb9]
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      0
      May 30 20:04:19 glennpc kernel: EXT2-fs error (device ide0(3,5)):
      ext2_read_inod
      e: unable to read inode block - inode=603846, block=1212420
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      9699360
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      0
      May 30 20:04:19 glennpc kernel: EXT2-fs error (device ide0(3,5)):
      ext2_read_inod
      e: unable to read inode block - inode=603859, block=1212420
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      9699360
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      0
      May 30 20:04:19 glennpc kernel: EXT2-fs error (device ide0(3,5)):
      ext2_read_inod
      e: unable to read inode block - inode=603860, block=1212420
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      9699360
      May 30 20:04:19 glennpc kernel: end_request: I/O error, dev 03:05 (hda),
      sector
      0


      When this occurs I can't access anything on my hard disk( which is
      partitioned as:
      /dev/hda2 / ext2 defaults 0 2
      /dev/hda3 swap swap defaults 0 2
      /dev/hda5 /data ext2 defaults 0 2
      proc /proc proc defaults 0 0
      /dev/fd0 /floppy auto defaults,user,noauto 0 0
      /dev/cdrom /cdrom auto ro,defaults,user,noauto 0 0

      none /proc/bus/usb usbdevfs defaults 0 0

      /dev/hda1 /windows vfat uid=629,gid=230,umask=077 0 0
      )

      I can't even run shutdown or umount /dev/hda2 - when I try I either get a
      "input/output" error or a "bus error" or something similar. This occurs if I
      try to access or execute anything on the disk. The only option is to power
      off and on again.

      When the laptop restarts it sometimes can't find the hard disk at all. When
      this occurs I usually have to "fool" the BIOS into a different state by
      removing the battery and starting on only AC power. However, when it does
      start up again everything is usually fine - apart from the normal problems
      associated with improperly shutting down linux.

      This problem is pretty intermittent, but is occuring on average at least
      once a day, although sometimes it is 2 or 3 days before crashes, other times
      only hours. It doesn't seem to be linked to any event that I can put my
      finger on.

      It once occurred when I had an audio CD in the DVD drive - that time
      /dev/hdb had problems too.

      This last fact, coupled with the fact that all seems to be ok once it boots
      up again, makes me think it's more likely to be a controller than a disk
      error, but I don't really know. In any event I wouldn't know what to do if
      it was either anyway.

      I'm a bit reluctant to ring Dell Support since my impression from this group
      is that they'd probably think it was a linux, rather than a hardware error,
      and because I'm currently overseas for the next 2 months and dealing with
      support internationally will be a pain.

      Does anyone have any ideas, or has anyone encountered this before?

      Thanks
      Eric
    Your message has been successfully submitted and would be delivered to recipients shortly.