Find the answer to your Linux question:
Results 1 to 5 of 5
Hello, I have CentOS release 6.3 (Final). When I copy a large file (say above 1GB or so), I get the following error very frequently Code: WARNING: Kernel Errors Present ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. 01-22-2013 #1
    vaibhavs
    vaibhavs is offline
    Just Joined!
    Join Date
    Jun 2008
    Posts
    9

    hda: DMA timeout error

    Hello,

    I have CentOS release 6.3 (Final).

    When I copy a large file (say above 1GB or so), I get the following error very frequently
    Code:
    WARNING: Kernel Errors Present
hda: DMA timeout error ...: 4 Time(s)
hda: dma timeout error: status=0x48 { D ...: 4 Time(s)
ide0: reset: master: error (0x00?) ...: 1 Time(s)
    What does this mean ?
    Is my hdd end of life ?

    Thx & Rgds,
    Vai
    Reply With Quote Reply With Quote
  2. 01-22-2013 #2
    Irithori
    Irithori is offline
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,008
    If the device you are copying to or from is /dev/hda:
    Yes, this device has an hardware issue.
    You must always face the curtain with a bow.
    Reply With Quote Reply With Quote
  3. 01-22-2013 #3
    vaibhavs
    vaibhavs is offline
    Just Joined!
    Join Date
    Jun 2008
    Posts
    9
    Thx @Irithori
    Appreciate your prompt help.

    Yes, I am copying files from & to the same drive.

    (1) Any way to test & confirm that the drive is bad? Any tool, script, test etc

    (2) On this HDD, I have Virtualbox installed along with 8 VMs.
    Is it safe (advisable) to simply clone the HDD (using clonezilla) on to another disk?

    Reinstalling & reconfiguring will be one long exercise, but if required, I will go that route.
    If simply cloning is safe, then I will be happy to use clonezilla.


    Best regards,
    Vai
    Reply With Quote Reply With Quote
  4. 01-22-2013 #4
    Irithori
    Irithori is offline
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,008
    I would shut down the VMs and start a file copy to a new drive.

    The advantage vs a image is:
    You already know/highly suspect a failed drive. So the image creation is likely to fail.
    A filecopy on the other hand tells you, which files are damaged.

    So first safe your data (VMs), then test that disk with the tool badblocks.
    Why do the test later?
    Again, you already suspect a failed drive.
    And badblocks by its nature is very IO demanding as it goes over the whole disk, potentially damaging it more.
    You must always face the curtain with a bow.
    Reply With Quote Reply With Quote
  5. 01-26-2013 #5
    Rubberman
    Rubberman is offline
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    10,233
    If this disc is S.M.A.R.T. enabled, open Applications->System Tools->Disk Utility and look at the SMART data. That will tell you if the drive is starting to fail. You may need to install the smartmontools package first.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules