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

Is my Harddisk dying ? What to do ?

Expand Messages
  • Marc Baaden
    Hi, this morning while a cronjob was running over my filesystem, I got loads of errors located near a certain block. Now I wonder whether this is ok or
    Message 1 of 4 , Jan 1, 2003
    • 0 Attachment
      Hi,

      this morning while a cronjob was running over my filesystem, I got
      loads of errors located near a certain block. Now I wonder whether
      this is "ok" or "alarming".
      Also my i8.2k is still under warranty, so should I try to have the
      harddrive replaced ? If yes, what steps should I take to claim my
      warranty (given that I do run linux) ?

      Thanks for any suggestions,

      Here is a little excerpt from the errors:
      Jan 2 06:38:36 baaden kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
      Jan 2 06:38:36 baaden kernel: hda: dma_intr: error=0x04 { DriveStatusError }
      Jan 2 06:38:40 baaden kernel: hda: dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=47862831, sector=17564176
      Jan 2 06:38:41 baaden kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
      Jan 2 06:38:41 baaden kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=47862831, sector=17564176
      Jan 2 06:38:41 baaden kernel: end_request: I/O error, dev 03:05 (hda), sector 17564176
      Jan 2 06:39:14 baaden kernel: ide0: reset: success
      Jan 2 06:39:14 baaden kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
      Jan 2 06:39:14 baaden kernel: hda: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=47862829, sector=17564176
      Jan 2 06:39:14 baaden kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
      Jan 2 06:39:14 baaden kernel: hda: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=47862829, sector=17564176
      Jan 2 06:39:27 baaden kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
      [..]

      Best wishes,
      Marc Baaden


      --
      Dr. Marc Baaden - Laboratory of Molecular Biophysics, Oxford University
      mailto:baaden@... - ICQ# 11466242 - http://www.marc-baaden.de
      FAX/Voice +49 697912 39550 - Tel: +44 1865 275380 or +33 609 843217
    • aupprojetc <aupprojetc@yahoo.com>
      First thing to do is to use the Dell Diagnostics CD-ROM (this is what support will tell you as well). The CD is bootable, otherwise I think you (or a friend)
      Message 2 of 4 , Jan 2, 2003
      • 0 Attachment
        First thing to do is to use the Dell Diagnostics CD-ROM (this is what
        support will tell you as well). The CD is bootable, otherwise I think
        you (or a friend) can downlaod a (windows) executable from the Dell
        site to create a diagnostics floppy.




        I recently had problems with my HDD, and used the diagnostics CD as
        instructed by Dell which then identified a problem somewhere. A day
        or two later Dell replaced the faulty HDD.




        HTH




        --- In linux-dell-laptops@yahoogroups.com, Marc Baaden <baaden@s...>
        wrote:


        >


        > Hi,


        >


        > this morning while a cronjob was running over my filesystem, I got


        > loads of errors located near a certain block. Now I wonder whether


        > this is "ok" or "alarming".


        > Also my i8.2k is still under warranty, so should I try to have the


        > harddrive replaced ? If yes, what steps should I take to claim my


        > warranty (given that I do run linux) ?


        >


        > Thanks for any suggestions,


        >


        > Here is a little excerpt from the errors:


        > Jan 2 06:38:36 baaden kernel: hda: dma_intr: status=0x51 {
        DriveReady SeekComplete Error }


        > Jan 2 06:38:36 baaden kernel: hda: dma_intr: error=0x04 {
        DriveStatusError }


        > Jan 2 06:38:40 baaden kernel: hda: dma_intr: error=0x01 {
        AddrMarkNotFound }, LBAsect=47862831, sector=17564176


        > Jan 2 06:38:41 baaden kernel: hda: dma_intr: status=0x51 {
        DriveReady SeekComplete Error }


        > Jan 2 06:38:41 baaden kernel: hda: dma_intr: error=0x40 {
        UncorrectableError }, LBAsect=47862831, sector=17564176


        > Jan 2 06:38:41 baaden kernel: end_request: I/O error, dev 03:05
        (hda), sector 17564176


        > Jan 2 06:39:14 baaden kernel: ide0: reset: success


        > Jan 2 06:39:14 baaden kernel: hda: read_intr: status=0x59 {
        DriveReady SeekComplete DataRequest Error }


        > Jan 2 06:39:14 baaden kernel: hda: read_intr: error=0x01 {
        AddrMarkNotFound }, LBAsect=47862829, sector=17564176


        > Jan 2 06:39:14 baaden kernel: hda: read_intr: status=0x59 {
        DriveReady SeekComplete DataRequest Error }


        > Jan 2 06:39:14 baaden kernel: hda: read_intr: error=0x01 {
        AddrMarkNotFound }, LBAsect=47862829, sector=17564176


        > Jan 2 06:39:27 baaden kernel: hda: read_intr: status=0x59 {
        DriveReady SeekComplete DataRequest Error }


        > [..]


        >


        > Best wishes,


        > Marc Baaden


        >


        >


        > --


        > Dr. Marc Baaden - Laboratory of Molecular Biophysics, Oxford
        University


        > mailto:baaden@s... - ICQ# 11466242 - http://www.marc-baaden.de


        > FAX/Voice +49 697912 39550 - Tel: +44 1865 275380 or +33 609
        843217
      • chris chambers
        Marc, Dell is very stingy about treplacing hard drives (BTDT), I suggest that you pull the drive out of the computer, it will give the message of no bootable
        Message 3 of 4 , Jan 2, 2003
        • 0 Attachment
          Marc,

          Dell is very stingy about treplacing hard drives (BTDT), I suggest that
          you pull the drive out of the computer, it will give the message of no
          bootable drive... Now call Dell and say hey my computer is giving me
          this error... They will ask you to try reseating the black drive
          adapter, and run their diagnostic test on it.. Then they will send you
          a new drive and ask you to return your old one.

          I have found this to be the easiest way for the consumer to get Dell to
          honor their warranty, with the least amount of hassle. Is it honest,
          mostly.. :-)

          Chris

          --- Marc Baaden <baaden@...> wrote:
          >
          > Hi,
          >
          > this morning while a cronjob was running over my filesystem, I got
          > loads of errors located near a certain block. Now I wonder whether
          > this is "ok" or "alarming".
          > Also my i8.2k is still under warranty, so should I try to have the
          > harddrive replaced ? If yes, what steps should I take to claim my
          > warranty (given that I do run linux) ?
          >
          > Thanks for any suggestions,
          >
          > Here is a little excerpt from the errors:
          > Jan 2 06:38:36 baaden kernel: hda: dma_intr: status=0x51 {
          > DriveReady SeekComplete Error }
          > Jan 2 06:38:36 baaden kernel: hda: dma_intr: error=0x04 {
          > DriveStatusError }
          > Jan 2 06:38:40 baaden kernel: hda: dma_intr: error=0x01 {
          > AddrMarkNotFound }, LBAsect=47862831, sector=17564176
          > Jan 2 06:38:41 baaden kernel: hda: dma_intr: status=0x51 {
          > DriveReady SeekComplete Error }
          > Jan 2 06:38:41 baaden kernel: hda: dma_intr: error=0x40 {
          > UncorrectableError }, LBAsect=47862831, sector=17564176
          > Jan 2 06:38:41 baaden kernel: end_request: I/O error, dev 03:05
          > (hda), sector 17564176
          > Jan 2 06:39:14 baaden kernel: ide0: reset: success
          > Jan 2 06:39:14 baaden kernel: hda: read_intr: status=0x59 {
          > DriveReady SeekComplete DataRequest Error }
          > Jan 2 06:39:14 baaden kernel: hda: read_intr: error=0x01 {
          > AddrMarkNotFound }, LBAsect=47862829, sector=17564176
          > Jan 2 06:39:14 baaden kernel: hda: read_intr: status=0x59 {
          > DriveReady SeekComplete DataRequest Error }
          > Jan 2 06:39:14 baaden kernel: hda: read_intr: error=0x01 {
          > AddrMarkNotFound }, LBAsect=47862829, sector=17564176
          > Jan 2 06:39:27 baaden kernel: hda: read_intr: status=0x59 {
          > DriveReady SeekComplete DataRequest Error }
          > [..]
          >
          > Best wishes,
          > Marc Baaden
          >
          >
          > --
          > Dr. Marc Baaden - Laboratory of Molecular Biophysics, Oxford
          > University
          > mailto:baaden@... - ICQ# 11466242 -
          > http://www.marc-baaden.de
          > FAX/Voice +49 697912 39550 - Tel: +44 1865 275380 or +33 609
          > 843217
          >
          >
          >


          =====
          93 Audi S4
          91 Mitsubishi Eclipse GSX
          85 VW Scirocco 2.0 not stock :-)
          73 Porsche 914 2.0 (67,000 original miles, stock)
          67 GMC Long Step pickup 95% complete frame off restoration
          86 VW Scirocco Wolfsburg (waiting for a restore or good home)
          It's not how much you make, but how much you don't spend!

          __________________________________________________
          Do you Yahoo!?
          Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
          http://mailplus.yahoo.com
        • Ian Bell
          ... Try running /sbin/badblocks. In its default mode it will just read all blocks on the disk and report any errors. Ian
          Message 4 of 4 , Jan 2, 2003
          • 0 Attachment
            On Thursday 02 Jan 2003 2:02 pm, you wrote:

            > >
            > > this morning while a cronjob was running over my filesystem, I got
            > > loads of errors located near a certain block. Now I wonder whether
            > > this is "ok" or "alarming".
            > > Also my i8.2k is still under warranty, so should I try to have the
            > > harddrive replaced ? If yes, what steps should I take to claim my
            > > warranty (given that I do run linux) ?
            > >
            > > Thanks for any suggestions,


            Try running /sbin/badblocks. In its default mode it will just read all
            blocks on the disk and report any errors.

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