bug-ddrescue
[Top][All Lists]
Advanced

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

[Bug-ddrescue] compatibility with ddrescueview + compatibility with ubun


From: Анонимный отправитель
Subject: [Bug-ddrescue] compatibility with ddrescueview + compatibility with ubuntu 16.04 kernel (4.4.0.24)
Date: Tue, 19 Jul 2016 01:13:15 +0300

Hello, Antonio!
I have 2 problems now.
1. Having compiled ddrescue-1.22-pre3 - I get the mapfiles incompatible with 
the ddrescueview because of the presence of parameter "current_pass", which is 
not recognized by ddrescueview. I informed the author of ddrescueview, got no 
answer - and now use a workaround having patched the source code (not to output 
the current_pass value to the mapfile :) ) - and recompiled ddrescue. Now my 
version is compatible with ddrescueview. So, using the new option 
"--mapfile-interval=5,10" I get a suitable visualization with ddrescueview. 
Thanks for that new option very much!
2. For the first time, I used ddrescue 1.17 with Xubuntu 14.04 - direct mode 
worked fine, bad sector sizes were aligned by 512bytes. Then I used versions up 
to 1.20 - worked fine, too.
Now I am using ddrescue 1.22-pre3 (latest) with Lubuntu 16.04 LTS - and 
BAD-sectored areas are aligned by 4096bytes!!! Though, Victoria for Windows in 
PIO-mode sees only 3 BAD sectors in one of the 8-sectored blocks. I wiped them 
3 (had rewritten), then ddrescue successfully read that block!!! The second 
block contained 8 BAD sectors (Victoria could not read them, so I wiped them 
all =8 ). All that were "soft BADs", some touched the system area slightly. 
Later, after having made the full-copy of that disk with ddrescue, the source 
disk was rewritten with DMDE (input and output were the same source disk) and 
fixed with chkdsk. The only valuable thing damaged - was a DOC-file (about 768 
characters). Disk is usable again.
So, I think, the newest Linux kernels (v.4 and above) do not work correctly 
with direct mode, and even do not read physically blocks by 512bytes :(. Does 
anyone know anything about such a kind of problem? Is it caused by the kernel, 
or by ddrescue? I'll try older versions of both kernel and ddrescue soon, and 
report the results to help the development of ddrescue.
3. I am translating the manual into Russian... About 20% complete. Where is the 
translated version better to be sent?

reply via email to

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