Deep scan gets slower and slower the more it progresses…? (1.8)

Disk Drill for Mac and Windows – Help Center Forums Deep Scan Deep scan gets slower and slower the more it progresses…? (1.8)

Tagged: , , ,

This topic contains 3 replies, has 2 voices, and was last updated by  mynameisJR 4 years, 3 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #4393

    Whitecat
    Participant

    Trying to scan an 8GB Transcend Compact Flash card that won’t mount normally. The speed of the scan is getting slower and slower as it progresses. After the first 8 hours or so I think it said it would take around 50 hours to do the whole card – now, after almost 121 hours it’s not even at 50% and it says there are about 131 hours remaining… every time I check it gets worse and worse. Any way to fix this, or does anyone know what’s going on? Results are trickling out… the number of files found is indeed growing so it’s definitely finding things. Just seems unbearably slow, and getting slower! Thanks in advance…

    NB I’m on OSX 10.7.3, latest DD version (Pro), Macbook Pro C2D 3.06 if that matters at all.

    #4940

    mynameisJR
    Participant

    Are you deep-scanning or quick-scanning? It’s also possible that your disk contains a lot of bad blocks (bad sectors). You can check this by pressing the “i” button in the left lower corner near the disk name inside of Disk Drill. Or you can check this information in Console log. Just go to Applications -> Utilities -> Console. You can save your recovery session before doing that.

    #4941

    Whitecat
    Participant

    Deep scanning. If I click that ‘i’ and then click ‘Specify Bad Blocks’ it says there are 128 bad blocks (starting at block 2816). Is that enough to cause the speed issue?

    #4942

    mynameisJR
    Participant

    Hi again, it seems like the bad blocks can cause the longer scan. Other reasons include: another app accessing the memory card while you are scanning it with Disk Drill; it’s also possible that your card-reader (if you are using the one) switched to USB 1.1 mode instead of USB 2.0. In case it’s a USB card-reader in place, try inserting it in a different USB port. Also try extending the specified range of bad blocks for your memory card (128 -> set 256 for example), and rescan.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.