bug-ddrescue
[Top][All Lists]
Advanced

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

Re: [Bug-ddrescue] ddrescue - disk 2 disk (ntfs)


From: Al Grant
Subject: Re: [Bug-ddrescue] ddrescue - disk 2 disk (ntfs)
Date: Thu, 16 Jul 2009 15:54:40 -0700 (PDT)

Thanks Andrew, 

That makes perfect sense. I have found after mounting the images (which is
of a NTFS windows drive) that most of the sub directories under C:\Windows
are missing. This is of course far more than 1500Kb of data.

The only way that I can reconcile this is to think that the place that holds
the index of files/directories (FAT table?) is part of whats missing, so
although the error size is small its killed the directories in a indirect
way???

Make any sense?

-Al


andrew zajac-2 wrote:
> 
> It started off this session with 629 different areas with errors which
> totaled 1500 kb of missing data.  So far, it has been able to recover some
> of that missing data.  In doing so, it broke up the error spots.  
> 
> So the areas before and after the newly recovered data now count as
> individual errors - the number of individual error spots goes up while the
> total amount of missing data goes down.
> 
> 
> 
> --- On Thu, 7/16/09, Al Grant <address@hidden> wrote:
> 
> From: Al Grant <address@hidden>
> Subject: Re: [Bug-ddrescue] ddrescue - disk 2 disk (ntfs)
> To: address@hidden
> Received: Thursday, July 16, 2009, 8:13 AM
> 
> 
> Thigns are going well, but I was wondering, here is what I ran for the
> second
> run to get data of the parts of the disk with errors:
> 
> address@hidden:~$ sudo ddrescue -r1 -v /dev/sdb /storage/test.bin testlog
> 
> About to copy 160041 MBytes from /dev/sdb to /storage/test.bin
>     Starting positions: infile = 0 B,  outfile = 0 B
>     Copy block size: 128 hard blocks
> Hard block size: 512 bytes
> Max_retries: 1    Split: yes    Truncate: no
> 
> Press Ctrl-C to interrupt
> Initial status (read from logfile)
> rescued:   160040 MB,  errsize:   1507 kB,  errors:     629
> Current status
> rescued:   160041 MB,  errsize:    757 kB,  current rate:        0 B/s
>    ipos:     4363 MB,   errors:    1480,    average rate:       17 B/s
>    opos:     4363 MB
>                              
> Now if I read this correctly, it read from the log file that after the
> first
> pass there was error size : 1507Kb?
> 
> And if I keep reading it says after the pass with -r1 option it now only
> has
> (it completed) error size : 757Kb?
> 
> This is a reduciton in the total error size - I assume this is good?
> 
> But how can the error size go down, yet errors goes up (from 629 to 1480)?
> 
> Thanks in advance - trying to understand the program better!!
> 
> Cheers
> 
> -Al
> 
> -- 
> View this message in context:
> http://www.nabble.com/ddrescue---disk-2-disk-%28ntfs%29-tp24438174p24515206.html
> Sent from the Gnu - ddrescue mailing list archive at Nabble.com.
> 
> 
> 
> _______________________________________________
> Bug-ddrescue mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-ddrescue
> 
> 
> 
>       __________________________________________________________________
> Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your
> favourite sites. Download it now
> http://ca.toolbar.yahoo.com.
> _______________________________________________
> Bug-ddrescue mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-ddrescue
> 
> 

-- 
View this message in context: 
http://www.nabble.com/ddrescue---disk-2-disk-%28ntfs%29-tp24438174p24525867.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.





reply via email to

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