Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: hdd error {DRDY err}

  1. #1
    Join Date
    Mar 2006
    Beans
    2

    hdd error {DRDY err}

    My system has two identical Maxtor 200GB SATA drives.

    Ubuntu is installed on the Primary, which runs perfectly.
    However when the second hard drive is connected Ubuntu won't boot. I get an error screen which reads:

    [272.854943] ata2.00: status: {DRDY err}
    [xxx.xxxxxx] ata2.00: error: {UNC}
    [xxx.xxxxxx]ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
    [xxx.xxxxxx] ata2.00: BMDMA stat 0x24
    [xxx.xxxxxx] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in

    the x's are all different numbers. The message repeats several times. Sometimes it says Buffer I/O error on device sdb1, logical block x (where x is a changing number)

    In the forum a similar question has been asked before by others, but not answered.

    I have tried switching the cables, the result was the same as before.

    Since I can't get Ubuntu to boot with the second drive connected I can't use any tools to analyse or fix the disk as far as I know.

    My guess is the disk is broken, am I correct?
    If not how might I fix this?

    Thanks in advance,

    Asrael

  2. #2
    Join Date
    Apr 2007
    Beans
    17

    Re: hdd error {DRDY err}

    I am getting the same error my self when trying to install Xubuntu.

    Previously I had Ubuntu running on this machine with no problems whatsoever. I have 2x 120 gb disks SATA running off a "pesudo-RAID" card configured with each disk in "striping mode"

    Any help is appreciated....

  3. #3
    Join Date
    Oct 2007
    Location
    England
    Beans
    96
    Distro
    Kubuntu 7.10 Gutsy Gibbon

    Re: hdd error {DRDY err}

    I'm having the exact same problem. I'm on a dual booting Dell inspiron 1500, and Windows won't start either (which leads me to believe that it's a hardware problem). Googling 'DRDY' error gives a lot of links that says it's something to do with hardy. Are you running Hardy as well?

    Here's a link that might help: http://ge.ubuntuforums.com/showthread.php?t=812562

    I don't know how my laptop could be damaged, I'd left it in my room, and the power got drained off, and it wouldn't start normally anymore.

    Please do let me know if you've had a similar problem.

  4. #4
    Join Date
    Sep 2008
    Beans
    2

    Re: hdd error {DRDY err}

    Quote Originally Posted by mushroomcloudwarrior View Post
    I'm having the exact same problem. I'm on a dual booting Dell inspiron 1500, and Windows won't start either (which leads me to believe that it's a hardware problem). Googling 'DRDY' error gives a lot of links that says it's something to do with hardy. Are you running Hardy as well?

    Here's a link that might help: http://ge.ubuntuforums.com/showthread.php?t=812562

    I don't know how my laptop could be damaged, I'd left it in my room, and the power got drained off, and it wouldn't start normally anymore.

    Please do let me know if you've had a similar problem.
    I have a similar error. The link you referred is not working.

  5. #5
    Join Date
    Oct 2007
    Location
    England
    Beans
    96
    Distro
    Kubuntu 7.10 Gutsy Gibbon

    Re: hdd error {DRDY err}

    Quote Originally Posted by ciyo65 View Post
    I have a similar error. The link you referred is not working.
    I'm afraid I can't help you here,

    In my case, I managed to boot using Ubuntu (it took about 20 minutes to boot up) and then copy the files I needed. I then called Dell support and found out that the computer had crashed 2 days out of warranty, I don't know if it's standard procedure, but I managed to get a new HDD delivered the next day.

    I'm convinced it's a hardware problem, although not aware if it can be fixed. I wish you luck!

  6. #6
    Join Date
    Jan 2008
    Beans
    6

    Arrow Re: hdd error {DRDY err}

    I had a similar problem so I'm not sure if this will help you.

    I downloaded and burnt the live cd, SystemRescueCD although any live cd with the right tools should work.

    Then run:
    e2fsck -f -c -v /dev/sda1

    substituting /dev/sda1 with your device with the error.

    This will force a check of the drive even if fsck believes the drive is ok.

    For this and more tips see http://linux.chrissweeney.co.uk/

  7. #7
    Join Date
    Apr 2008
    Beans
    4

    Re: hdd error {DRDY err}

    I too had a similar error. The last thing I had changed was with Firefox-Mozilla, and I suspected that was the cause. My trusty Ubuntu network guru insisted I need a new hard drive. This old laptop is 5 years old!

    Until I have the chance for further investigation I have completely removed Firefox from the system.

    Hmmmm. So far everything is working...
    Maybe it wasn't the hard-drive after all.

  8. #8
    Join Date
    Apr 2008
    Beans
    4

    Re: hdd error {DRDY err}

    I had some free time this morning, so I took another look at my hard-drive. Sure enough there were some bad-blocks.

    Like Chris-man said in the previous post, it's so much easier to fix than replace.

    Boot from Live CD. Do not mount hard-drive!

    ubuntu@ubuntu:/etc$ sudo e2fsck -c /dev/sda5
    e2fsck 1.41.3 (12-Oct-2008 )
    Checking for bad blocks (read-only test): done
    /dev/sda5: Updating bad block inode.
    Pass 1: Checking inodes, blocks, and sizes

    -----
    -----

    /dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/sda5: 234203/843648 files (2.6% non-contiguous), 1278754/1684809 blocks

    I had to run it twice and deleted rather than fix a few files that I kept note of. I think this is so much better than replacing the hard-drive right now!

  9. #9
    Join Date
    May 2006
    Beans
    12

    Re: hdd error {DRDY err}

    I have been suffering from a similar problem over the last year or so. I have a Maxtor 6V160E0 (150GB) drive in a (soft) raid1 array with a Maxtor 6Y160M0 (160GB) drive (leaving 10GB unallocated). Every month or so, the system would go progressively slower until the 6V160E0 dropped out of the array. I didn't worry too much, because the error was associated with a read operation, the active mirror was clean and I could add the bad drive back into the array fairly easily.

    After upgrading to the 2.6.24-23 kernel, the system became less stable and the drive wouldn't stay active for more than a week, so I had to diagnose the problem properly.

    I found https://bugs.launchpad.net/ubuntu/+s...ux/+bug/228540, and added pci=nomsi to my boot kernel options, but (as expected) it made no difference because I was running a kernel that should have been fixed.

    I then downloaded and ran the seagate/maxtor SeaTools linux diagnostics. Many of the options will not work with Maxtor disks, but "sudo ./st -G /dev/sg1" failed consistently in the last 10% of the drive. Of course, the drive is out of warranty...

    I found a very useful tutorial:
    http://howtoforge.org/how-to-resize-...nk-and-grow-p4, although some of the commands were out of date. I found another tutorial:
    http://ubuntuforums.org/showthread.php?t=726724, which helped with the syntax of some of the commands. Given the danger involved, I was particularly worried about the inconsistent unit sizes and defaults of each kind of command.

    I disconnected the faulty drive and worked on the good drive, which was already larger. I needed to remap the good drive so that when it was mirrored onto the bad drive, the faulty sectors would never be used.

    First, I shrank the ext3 filesystem to 90% of its original size, thus leaving the bad sectors unallocated. (Note: I used gparted initially, but after shrinking the filesystem, it immediately re-grew it to fill the logical volume!). Next, I shrank the logical volume to slightly larger than the file system size (to be certain that I didn't truncate anything important). Then, I shrank the physical volume (to slightly larger again), and finally reduced the raid volume size.

    My nerves gave out and so I did not delete and reallocate a smaller partition. My disk now had a raid volume that only filled the lower 90% of the physical partition, which seemed to be good enough to me.

    I rebooted from the good drive, which worked fine. Then I added the faulty drive back into the raid array. After 5 days, the system is still running at full speed and there have been no more DRDY errors logged.

    I conclude that my disk drive is faulty, but in a way that is difficult to predict. When reading one of the faulty sectors, a retryable error is reported. The disk seems to have tried to move the data to an alternate track because too many read errors occurred on the original sector, but a write error occured during the copy operation. The original data was still OK, but it would need many successive reads to obtain the data. Obviously, the impact to the system depended entirely on what kind of file had been written to the faulty sector.

  10. #10
    Join Date
    Aug 2006
    Beans
    9

    Re: hdd error {DRDY err}

    I had the same problem. It started to show the DRDY ERR messages during boot after my laptop took a 3 1/2 ft dive. Things got progressively worse over a few days and yesterday I bought a new HDD to replace it. I think that's your best bet if you're seeing this error.

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

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