[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-ddrescue] Having trouble mounting ddrescue image

From: lonestarshack
Subject: Re: [Bug-ddrescue] Having trouble mounting ddrescue image
Date: Sun, 6 Feb 2011 18:46:29 -0800 (PST)

First of all Ian...Thank you for explaining a few things to me. It cleared up
a lot of misunderstandings that I had about the correct way to use ddrescue.
I took your suggestion and it appears I was able to save about half the
drive after letting it run for a really long time. However, now I can't seem
to figure out how to mount the image. I believe I am using the correct
offset and everything. Any thoughts? 

address@hidden gw_bak]# losetup -r /dev/loop0 gw_r1.img
address@hidden gw_bak]# fdisk -lu /dev/loop0

Disk /dev/loop0: 54.3 GB, 54288610304 bytes
255 heads, 63 sectors/track, 6600 cylinders, total 106032442 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xedaaedaa

      Device Boot      Start         End      Blocks   Id  System
/dev/loop0p1   *    14346045   195350399    90502177+   7  HPFS/NTFS
/dev/loop0p2              63    14346044     7172991    b  W95 FAT32

Partition table entries are not in disk order
address@hidden gw_bak]# losetup -r /dev/loop1 -o 7345175040 gw_r1.img
address@hidden gw_bak]# mkdir /mnt/gwimg 2>/dev/null
address@hidden gw_bak]# mount -t ntfs /dev/loop1 /mnt/gwimg
NTFS signature is missing.
Failed to sync device /dev/loop1: Input/output error
Failed to mount '/dev/loop1': Invalid argument
The device '/dev/loop1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
address@hidden gw_bak]# 

Ian Oliver-2 wrote:
> In article <address@hidden>, Lonestarshack wrote:
>> The drive automounted once it was discovered and then I was able to
>> run ddrescue on just the main NTFS partition that was on the drive.
> You're much better running ddrescue without the drive mounted. The OS
> tends to 
> keeps accessing the drive, particularly if it's retrying bad sectors, and
> this 
> just makes life harder for ddrescue. ddrescue hits the device directly, 
> doesn't need the drive to be mounted, so unmount it.
>> I DID
>> NOT run ddresuce on the entire drive; just the NTFS partition I want to
>> recover.
> Sensible, but can make it harder to restore to a new drive.
>> Due to problems with the hard drive, sometimes the drive would
>> unmount on its own. At that point, ddrescue would stop.
> Sounds like the drive is having serious problems. Is it attached via SATA
> or 
> USB? I've had problems with USB connected drives in the past as the error 
> handling on USB seems iffy with some bridges.
>> So, since I was
>> using the log file option, I simply reattached the drive, it automounted,
>> and I continued with creating the image.
> As soon as the OS mounts the drive, unmount it. Even this didn't work for
> me 
> once, and I ended up using a Puppy Linux LiveCD as this doesn't touch
> drives 
> until you tell it to.
>> Now, no
>> matter what I try to do, I can't seem to get this drive to mount. Here's
>> an
>> fdisk output on the image which doesn't look good to begin with. Any
>> thoughts from the ddrescue wizards out there?
>> address@hidden internal]# losetup -r /dev/loop0 01.img
>> address@hidden internal]# fdisk -lu /dev/loop0
> The loop mount looks right, but fdisk won't work on just a partition: it
> needs 
> to see a partition table.
> Your options are,
> 1) Image the whole disk, fdisk will work, losetup will need an offset to
> the 
> right partition if you're to mount it.
> 2) Image just one partition, losetup won't need an offset, fdisk won't
> work. 
> This is your case.
> # Command line: ddrescue --verbose --no-split /dev/sdd1
> /media/9edd991c-2497-4f92-aa86-bf6ccf9ddb1d/01.img
> /media/9edd991c-2497-4f92-aa86-bf6ccf9ddb1d/01.log
> # current_pos  current_status
> 0x3B1840000     +
> #      pos        size  status
> 0x00000000  0x3B1828000  +
> 0x3B1828000  0x00000200  -
> 0x3B1828200  0x00017E00  /
> Why --no-split? Your image is far from complete as you have huge unsplit
> areas 
> as ddrescue hasn't been doing any splitting or retrying.
> Try again with the options "-d -r 4" for direct mode with a few retries.
> Try 
> and stop your OS so much as breathing on the drive during the process.
> Regards
> Ian
> _______________________________________________
> Bug-ddrescue mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-ddrescue

View this message in context: 
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]