Recovering an HD with a Bad Sector/Bad Partition Problem

Disk Drill for Mac and Windows – Help Center Forums General Recovering an HD with a Bad Sector/Bad Partition Problem

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

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

    eadwired
    Participant

    I am trying to recover a 200Gb HD with a bad sector/bad partition problem. It was a used a primary disk in a WinXP OS, suddenly it crashed and cannot be booted again. I just bought an accessory SATA to USB as to connect to another unit and recover files.

    I wonder I cannot see any of the 3 partitions it had before, all of them NTFS formatted. I can just see it as the whole drive, so I had no choice but just deep scanned it, at first it was normal and waited for some hours. When I woke up my MBP was already frozen, so I have to manually restart it. I am now trying to have a second attempt.

    I was wondering if Disk Drill can help this case of mine or is there anything that I am missing from the procedure.

    Thanks!

    #4660

    mynameisJR
    Participant

    Disk Drill can surely help. To tell more about freezing, have a look at our troubleshooting instruction: /help/troubleshooting-basics/

    These logs will be able to explain what happened.

    #4661

    eadwired
    Participant

    Hi tried to check logs but it seems weird my HDisk seems to be disconnected when it is in deepscan..

    From console:
    1/27/11 11:04:28 PM Error opening file system in partition at offset 0 Disk Drill[1056]
    1/27/11 11:04:28 PM Using it as RAW Disk Drill[1056]
    1/27/11 11:04:28 PM Found filesystem raw, offset 0, size 200049647616 Disk Drill[1056]
    1/27/11 11:04:28 PM Volume: /dev/disk1s1 (Files2) mounted: not mounted Disk Drill[1056]

    From Diskdrill.log:
    2011-01-27 23:04:27.755 Disk Drill[1056:1acb] Error determining system volume, trying file systems
    2011-01-27 23:04:28.057 Disk Drill[1056:1acb] Error opening file system in partition at offset 0
    2011-01-27 23:04:28.057 Disk Drill[1056:1acb] Using it as RAW
    2011-01-27 23:04:28.057 Disk Drill[1056:1acb] Found filesystem raw, offset 0, size 200049647616
    2011-01-27 23:04:28.060 Disk Drill[1056:1acb] Volume: /dev/disk1s1 (Files2) mounted: not mounted
    2011-01-27 23:04:28.480 Disk Drill[1056:207] /dev/disk0
    2011-01-27 23:04:28.480 Disk Drill[1056:207] /dev/disk1

    From Recovery Vault log:
    I:2011-01-27T22:30:08 Disk disk1s1 mounted.
    I:2011-01-27T22:30:08 Disk disk1s2 mounted.
    I:2011-01-27T22:30:08 Disk disk1 appeared.
    W:2011-01-27T22:30:08 Disk disk1 is not monitored. No volume path.
    I:2011-01-27T22:30:08 RV opens device /dev/disk1, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T22:30:08 RV opens device /dev/rdisk1s1, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T22:30:08 RV opens device /dev/rdisk1s2, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T22:30:09 Disk disk1s1 appeared.
    I:2011-01-27T22:30:09 RV opens device /dev/rdisk1s1, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T22:30:10 Disk disk1s2 appeared.
    I:2011-01-27T22:30:11 RV opens device /dev/rdisk1s2, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T22:56:18 Disk disk2s5 disappeared.
    I:2011-01-27T22:56:18 Disk disk2s3 disappeared.
    I:2011-01-27T22:56:18 Disk disk2s1 disappeared.
    I:2011-01-27T22:56:18 Disk disk2 disappeared.
    I:2011-01-27T22:58:50 Disk disk1s1 unmounted.
    I:2011-01-27T22:58:50 Disk disk1s2 unmounted.
    I:2011-01-27T22:58:53 Disk disk1s2 disappeared.
    I:2011-01-27T22:58:53 Disk disk1s2 appeared.
    W:2011-01-27T22:58:53 Disk disk1s2 is not monitored. No volume path.
    I:2011-01-27T22:58:55 Disk disk1s1 unmounted.
    I:2011-01-27T22:58:57 Disk disk1s1 unmounted.
    I:2011-01-27T22:59:00 Disk disk1s1 unmounted.
    I:2011-01-27T22:59:03 Disk disk1s1 unmounted.
    I:2011-01-27T22:59:05 Disk disk1s1 unmounted.
    I:2011-01-27T22:59:06 Disk disk1s1 disappeared.
    I:2011-01-27T22:59:06 Disk disk1s1 appeared.
    W:2011-01-27T22:59:06 Disk disk1s1 is not monitored. No volume path.
    I:2011-01-27T22:59:08 Disk disk1 disappeared.
    I:2011-01-27T22:59:08 Disk disk1s2 disappeared.
    I:2011-01-27T22:59:08 Disk disk1s1 disappeared.
    I:2011-01-27T23:04:27 Disk disk1s3 mounted.
    I:2011-01-27T23:04:27 Disk disk1s3 appeared.
    W:2011-01-27T23:04:27 Disk disk1s3 is not monitored. Unknown file system type.
    I:2011-01-27T23:04:27 Disk disk1 appeared.
    W:2011-01-27T23:04:27 Disk disk1 is not monitored. No volume path.
    I:2011-01-27T23:04:27 Disk disk1s5 mounted.
    I:2011-01-27T23:04:27 Disk disk1s1 mounted.
    I:2011-01-27T23:04:27 RV opens device /dev/rdisk1s3, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T23:04:27 RV opens device /dev/disk1, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T23:04:28 Disk disk1s5 appeared.
    W:2011-01-27T23:04:28 Disk disk1s5 is not monitored. Unknown file system type.
    I:2011-01-27T23:04:28 RV opens device /dev/rdisk1s5, flags:0, mode:0, fd:14, errno:2.
    I:2011-01-27T23:08:05 Disk disk1s1 appeared.
    W:2011-01-27T23:08:05 Disk disk1s1 is not monitored. Unknown file system type.
    I:2011-01-27T23:08:05 RV opens device /dev/rdisk1s1, flags:0, mode:0, fd:14, errno:2.

    #4666

    mynameisJR
    Participant

    So, the drive unmounts when scanning right? Seems like it happens in Mac OS when there are bad blocks found. We are working on fixing this, but it really seems to be a “by design” behavior.

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

You must be logged in to reply to this topic.