[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-ddrescue] bug
From: |
sel janka |
Subject: |
[Bug-ddrescue] bug |
Date: |
Sun, 25 Oct 2015 15:06:03 +0200 |
p{padding:0;margin:0;}hii think there is a bug in the 1.20 version (or maybe
all, dunno) - when the usb stick unmounts itself(dont know why), the scanning
process will still go on, but it will not warn the user nor will it write any
more mapfile. so when you discover that it hasn't written any log, you will
have to start from the position where the log file was last written (like 16
hours ago...)P.S. - and maybe it should also start the fourth phase((Fourth
phase; Retrying)) in reverse, so it might have better luck getting the data?
(as it is already retrying).and maybe even print some information on the screen
about how much has been retried already? i think it only showed the error size
while doing the retry phase (and i had to stop it because it hadnt written any
log file - so now i dont know how much did it actually retry already...)and is
the scanning any good if the Reallocated Sector Count and End-to-End Error
SMART values are already very low? maybe even add some more information about
when is it ok to run the ddrescue app and when it would damage the disk... (if
it would?)thanks
- [Bug-ddrescue] bug,
sel janka <=