I try not to interrupt a rescue that is spitting out data unless I have a 
really good reason to do so.

There's lots you can do without writing to the image, though.  If you mount the 
image as read-only then you can attempt to read some files from it right now, 
on-the-fly, without writing to it with Testdisk.  But I certainly would not try 
to repair the filesystem at this point.



--- On Sun, 6/14/09, Ken A Scott <[email protected]> wrote:

From: Ken A Scott <[email protected]>
Subject: Re: [Bug-ddrescue] Testdisk sees what ddrescue does not
To: [email protected]
Received: Sunday, June 14, 2009, 3:06 PM


#yiv827113499 
{padding:1ex;margin:0px;font-family:sans-serif;font-size:small;}#yiv827113499 
a[href]{}#yiv827113499 blockquote{margin:0;border-left:2px solid 
#144fae;padding-left:1em;}#yiv827113499 blockquote 
blockquote{border-color:#006312;}#yiv827113499 blockquote blockquote 
blockquote{border-color:#540000;}


Hi guys,
Thanks for the help and encouragement.  The imaging of the drive is going well 
(saved ~45 Gb so far with less 1% errors and clipping along at about 1MB per 
sec after I added -c 64 and -d qualifiers to ddrescue) .  Given that the entire 
drive 250GB was not close to full the question is can I stop ddrescue at some 
point, make a copy of what I have so far, and perform testdisk, fsck, and mount 
etc. to that copy?
I know that would cost me whatever data might have been spread out into the 
last unimaged portion of the original NTFS partition but would it even work?
 
In other words, can effective repairs be performed on a image of a portion of a 
NTFS  partition?
 
Even if this idea is faulty I can always resume the ddrescue where I left off. 
Thanks
Ken
 
On Sun, 14 Jun 2009 09:30 -0700, "andrew zajac" <[email protected]> wrote:


    
        
            It's far from useless.  You can image the drive and mount the 
partition on the image using an offset.

            

            Assuming you imaged the drive (sdb) to a file named "image" in the 
current directory, you can do:

            

            mkdir mnt

            sudo mount -t ntfs -o r,loop,offset=32256 file mnt


            See here for more details:

            
https://help.ubuntu.com/community/DataRecovery#Mounting%20partitions%20on%20the%20image

            

            

            --- On Fri, 6/12/09, Ken A Scott <[email protected]> wrote:

            

            From: Ken A Scott <[email protected]>

            Subject: [Bug-ddrescue] Testdisk sees what ddrescue does not

            To: [email protected]

            Received: Friday, June 12, 2009, 2:45 PM

            

            #yiv827113499 #yiv267214611 
{padding:1ex;margin:0px;font-family:sans-serif;font-size:small;}#yiv827113499 
#yiv267214611 a[href]{}#yiv827113499 #yiv267214611 
blockquote{margin:0;border-left:2px solid 
#144fae;padding-left:1em;}#yiv827113499 #yiv267214611 blockquote 
blockquote{border-color:#006312;}#yiv827113499 #yiv267214611 blockquote 
blockquote blockquote{border-color:#540000;}
            
            I have a troubled disk which won't mount in Linux (or boot up to XP 
which is what it is).  The 'testdisk' utility correctly indentifies the 
partitions
            (a large 233GB NTFS Windows partition and a small 11GB recovery 
partition =>  total size 250GB)
            and can show actual files on on the windows partition but can't 
write the partition table to the disk.  ddrescue 1.2-1.3 (on a MEPIS system) 
with the following command    $ddrescue --no-split  /dev/sdb1  imagefile logfile
            says
            'cannot open input file:No such file or directory'
             
            Since cat /proc/partitions shows a sdb entry  '8  16   244198584'  
I was able to start the above command with just
            $ddrescue --no-split  /dev/sdb  imagefile logfile
            but I'm not sure if it is useful (since I know there to be actually 
two partitions there).
             
            Any advice?
            Thanks in advance!
            Ken
             
            
            -- 
  Ken A Scott
  [email protected]

            
            

            -----Inline Attachment Follows-----

            

            _______________________________________________

            Bug-ddrescue mailing list

            [email protected]

            http://lists.gnu.org/mailman/listinfo/bug-ddrescue
            
        
    




The new Internet Explorer® 8 - Faster, safer, easier.  Optimized for Yahoo! Get 
it Now for Free!

-- 
  Ken A Scott
  [email protected]


-----Inline Attachment Follows-----

_______________________________________________
Bug-ddrescue mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-ddrescue



      __________________________________________________________________
Make your browsing faster, safer, and easier with the new Internet Explorer® 8. 
Optimized for Yahoo! Get it Now for Free! at 
http://downloads.yahoo.com/ca/internetexplorer/
_______________________________________________
Bug-ddrescue mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-ddrescue

Reply via email to