Using Disk Warrior... "speed reduced by disk malfunction:1

Discussion in 'iMac' started by danmc00, Nov 30, 2011.

  1. danmc00 macrumors regular

    Oct 29, 2009
    I purchased disk warrior today to try to save my 27" iMac. I am running the program now and it says " speed reduced by disk malfunction:1"

    Has anyone ran into this? It has been saying this for about 20 minutes now with no progress.

    Any ideas?
  2. wessew macrumors member

    Feb 4, 2010
  3. smithrh macrumors 68020


    Feb 28, 2009
    Diskwarrior can take a LONG LONG time (hours upon hours).

    Let it run to completion. As noted, it's complaining that it's being slowed down by a disk malfunction (probably why you're running DW right now!)...

    Let it run.

    I've been in the same scenario, it did finally finish overnight but it recovered just about everything so I could get it to a backup disk, then replace the bad disk.
  4. danmc00 thread starter macrumors regular

    Oct 29, 2009
    Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

    On disk malfunction 629 now. So this means the drive is bad? I have a 1TB HD in my 27" iMac. Which drive would you recommend replacing it with? Ive done some research about replacing the drive on my own and it kind of scares me to take it all apart.
  5. Vikz macrumors regular


    Nov 13, 2007
    San Juan, Puerto Rico
    Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3)

    When I worked at apple the rule of thumb with disk warrior was after #15 format the drive and replace. Your not going to be able to save it so I hope you got everything backed up
  6. derbothaus macrumors 601


    Jul 17, 2010
    Disk is bad. Buy a new one. It will cost you a fortune right now unfortunately if you don't have a spare lying around. as everyone else stated let DW run and get anything you can off the HDD.
  7. danmc00 thread starter macrumors regular

    Oct 29, 2009
    I am working on getting a replacement drive but I am still running disk warrior. It's been running for 5 days now. 2,237 now. Should I give up on trying to recover data?
  8. flynz4 macrumors 68040

    Aug 9, 2009
    Portland, OR
    How current is your most recent backup?

  9. danmc00 thread starter macrumors regular

    Oct 29, 2009
    Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A405 Safari/7534.48.3)

    Last backup was Oct 11th. I wanted to get some pics and iTunes stuff that were downloaded after that.
  10. cl-user, Jun 1, 2012
    Last edited: Jun 1, 2012

    cl-user macrumors regular

    Dec 16, 2009
    danmc00 did you ever get anything back using DiskWarrior?
    I'm on 22,627 and still grinding.
    Yes new (1 week old) Hitachi 3TB enterprise (HUA723030ALA640) may be dead ... (I don't need warnings or to told I should have backup!).
    but I wouldn't be trying to salvage something is it wasn't irreplaceable.

    Beyond a specialist company, anyone have any ideas for recovery?
    Diskwarrior has been running for several days uninterrupted. Huge numbers of console logs in the form:

    12/6/1 5:29:34 PM [0x0-0x51051].com.alsoft.diskwarrior[570] DiskWarrior App: disk3s2: Read I/O error for block range 224049 to 224049

    Oddly, this disk is in 2 partitions. The other partition runs OK, hence I am hoping the media itself is actually OK.

    BTW Alsoft say: ---------------------------

    The message "speed reduced by disk malfunction" means there is a problem reading data from the disk due to a disk malfunction.

    As long as the mouse cursor still moves during step 5, then the computer did not hang or freeze. DiskWarrior is still working on reading the directory of the disk.

    Such slowdowns are usually the result of having bad blocks on the media. DiskWarrior is having trouble reading data from the locations on disk where the directory structures are stored.

    You will also notice that an error count is kept at the end of the message. This feedback allows you to see that DiskWarrior is still working on reading data from the drive.

    NOTE: This count does not increase at a regualr interval as disk errors are not distributed evenly across a drive.

    Please let DiskWarrior run for as long as it takes. This can take quite a few hours but should eventually complete. On rare occasions, it might even be necessary to run this for a day or two.
  11. fastlanephil macrumors 65816


    Nov 17, 2007
    I had a bad 10 GB HD in an iBook and as I remember and I let DW run over night. It was finished by the morning. Yes, it could be working for a long time.
  12. ilaird macrumors newbie


    Mar 19, 2016
    Given this description, I am guessing that DW is just retrying repeatedly until it gets a good read of a block, then moving on to the next block. So far it's only reporting 3 bad blocks, a third of a way through a 4 TB drive, which like specific damaged blocks (power outages are not rare here in Florida, so a bad write is pretty easy to imagine) so I'll just let it keep running overnight and see what happens.

  13. nambuccaheadsau macrumors 68000


    Oct 19, 2007
    Nambucca Heads Australia
    The last post was five years ago so I guess they drive was repaced.

Share This Page

12 November 30, 2011