No bad blocks reported
LINUX based utility for use with gnuddrescue to aid with data recovery
Brought to you by:
maximus57
Menu
▾
▴
when i run the scan it reports no errors found, while dmesg does show me errors. How is this possible or am i doing something wrong?
ddru_ntfsfindbad -V /dev/sdb1 sectors
ddru_ntfsfindbad 1.3 20140608
Reading the logfile into memory...
processed 0 lines out of 1 with 0 errors
Reading boot sector...
Reading mft inode...
total mft fragments=5
total mft size=1443102720 bytes
total inodes=352320
processing inode 352320 of 352320
MFT hard errors=0
--------------------- Dmesg -----------------
[ 1034.646984] end_request: I/O error, dev sdb, sector 1643652104
[ 1037.556974] end_request: I/O error, dev sdb, sector 1643652104
[ 1040.466958] end_request: I/O error, dev sdb, sector 1643652104
[ 1043.390268] end_request: I/O error, dev sdb, sector 1643652104
[ 1046.770297] end_request: I/O error, dev sdb, sector 1643652104
[ 1087.913616] end_request: I/O error, dev sdb, sector 1643652104
[ 1090.816945] end_request: I/O error, dev sdb, sector 1643652104
[ 1093.733619] end_request: I/O error, dev sdb, sector 1643652104
[ 1096.870293] end_request: I/O error, dev sdb, sector 1643652104
[ 1099.880301] end_request: I/O error, dev sdb, sector 1643652104
[ 1102.940269] end_request: I/O error, dev sdb, sector 1643652104
[ 4716.286601] end_request: I/O error, dev sdb, sector 1643652104
[ 4719.193254] end_request: I/O error, dev sdb, sector 1643652104
[ 4722.106580] end_request: I/O error, dev sdb, sector 1643652104
[ 4725.446574] end_request: I/O error, dev sdb, sector 1643652104
[ 4765.356584] end_request: I/O error, dev sdb, sector 1643652104
[ 4768.273243] end_request: I/O error, dev sdb, sector 1643652104
[ 4771.189912] end_request: I/O error, dev sdb, sector 1643652104
[ 4774.289917] end_request: I/O error, dev sdb, sector 1643652104
[ 4777.326581] end_request: I/O error, dev sdb, sector 1643652104
[ 4780.456572] end_request: I/O error, dev sdb, sector 1643652104
[ 8329.992909] end_request: I/O error, dev sdb, sector 1643652104
[ 8332.899560] end_request: I/O error, dev sdb, sector 1643652104
[ 8335.849682] end_request: I/O error, dev sdb, sector 1643652104
[ 8339.076235] end_request: I/O error, dev sdb, sector 1643652104
[ 8379.226262] end_request: I/O error, dev sdb, sector 1643652104
[ 8382.119564] end_request: I/O error, dev sdb, sector 1643652104
[ 8385.062891] end_request: I/O error, dev sdb, sector 1643652104
[ 8388.202908] end_request: I/O error, dev sdb, sector 1643652104
[ 8391.256240] end_request: I/O error, dev sdb, sector 1643652104
[ 8394.299562] end_request: I/O error, dev sdb, sector 1643652104
[11933.815857] end_request: I/O error, dev sdb, sector 1643652104
[11936.722536] end_request: I/O error, dev sdb, sector 1643652104
[11939.665864] end_request: I/O error, dev sdb, sector 1643652104
[11942.899209] end_request: I/O error, dev sdb, sector 1643652104
[11983.425855] end_request: I/O error, dev sdb, sector 1643652104
[11986.342528] end_request: I/O error, dev sdb, sector 1643652104
[11989.282519] end_request: I/O error, dev sdb, sector 1643652104
[11992.435855] end_request: I/O error, dev sdb, sector 1643652104
[11995.479185] end_request: I/O error, dev sdb, sector 1643652104
[11998.569186] end_request: I/O error, dev sdb, sector 1643652104
[15636.692160] end_request: I/O error, dev sdb, sector 1643652104
[15639.585492] end_request: I/O error, dev sdb, sector 1643652104
[15642.525489] end_request: I/O error, dev sdb, sector 1643652104
[15645.818820] end_request: I/O error, dev sdb, sector 1643652104
[15686.138818] end_request: I/O error, dev sdb, sector 1643652104
[15689.045486] end_request: I/O error, dev sdb, sector 1643652104
[15691.995486] end_request: I/O error, dev sdb, sector 1643652104
[15695.082153] end_request: I/O error, dev sdb, sector 1643652104
[15698.138820] end_request: I/O error, dev sdb, sector 1643652104
[15701.182161] end_request: I/O error, dev sdb, sector 1643652104
[15704.122153] end_request: I/O error, dev sdb, sector 1643652104
[16801.172043] end_request: I/O error, dev sdb, sector 2216695304
[16804.098716] end_request: I/O error, dev sdb, sector 2216695304
[16807.032037] end_request: I/O error, dev sdb, sector 2216695304
[16810.325385] end_request: I/O error, dev sdb, sector 2216695304
[16813.512039] end_request: I/O error, dev sdb, sector 2216695304
[16816.548699] end_request: I/O error, dev sdb, sector 2216695304
[16819.475374] end_request: I/O error, dev sdb, sector 2216695304
[19236.081809] end_request: I/O error, dev sdb, sector 1643652104
[19239.078447] end_request: I/O error, dev sdb, sector 1643652104
[19279.485121] end_request: I/O error, dev sdb, sector 1643652104
[19282.485125] end_request: I/O error, dev sdb, sector 1643652104
[19285.518470] end_request: I/O error, dev sdb, sector 1643652104
[19288.501811] end_request: I/O error, dev sdb, sector 1643652104
[19293.941796] end_request: I/O error, dev sdb, sector 2216695304
[19296.845198] end_request: I/O error, dev sdb, sector 2216695304
[19299.768460] end_request: I/O error, dev sdb, sector 2216695304
[19303.218435] end_request: I/O error, dev sdb, sector 2216695304
[19306.425122] end_request: I/O error, dev sdb, sector 2216695304
[19309.471789] end_request: I/O error, dev sdb, sector 2216695304
[19313.478457] end_request: I/O error, dev sdb, sector 2216695312
[19317.965120] end_request: I/O error, dev sdb, sector 2216698064
[19320.875121] end_request: I/O error, dev sdb, sector 2216698064
[19323.808449] end_request: I/O error, dev sdb, sector 2216698064
[19327.068451] end_request: I/O error, dev sdb, sector 2216698064
[19329.978455] end_request: I/O error, dev sdb, sector 2216698064
[19332.928451] end_request: I/O error, dev sdb, sector 2216698064
[19335.955126] end_request: I/O error, dev sdb, sector 2216698064
First let's examine the line "ddru_ntfsfindbad -V /dev/sdb1 sectors"
What is in the file "sectors"? According to the output it processed 0 lines out of 1. So is there only one line in sectors?
Second, and maybe more important, the old ddrutilty (now called ddru_findbad) was able to use actual sector numbers in a file. The new Ddru_ntfsfindbad only works with a ddrescue log format.
Try using ddru_findbad (it is included in the package, type ddru_findbad --help for options). It is older and much slower and not as forgiving, but may work for you. If it does not work then your only option would be to manually convert the sector list to a ddrescue logfile format.
Sorry for any confusion.
i dont have a ddrescue log file, i made a file with a given sector range " 2048 5860532223"
Thats all there is in the file.
(running arch linux) i got an error about fdisk:
Waring! GNU fdisk is not detected!
Therefore GPT partitioned disks will not be able to be processed
and this script may produce errors if trying to do so.
so i did "ln -s /usr/bin/gdisk /usr/bin/gfdisk"
sudo ddru_findbad /dev/sdb1 sectors
Command line input was processed succesfully
ddru_findbad 1.10 20140217
Target = /dev/sdb1
Logfile = sectors
Output base name = results
Sector size = 512
Loop wait time = 2
More info = false
Extra output = false
Quick = true
Quick ntfs = true
Target /dev/sdb1 is detected to be a block device
Neither mmstat or fsstat gave results
The partition table or file system could be corrupt
Cannot determine if target is whole drive or single partition
Last edit: Dr. Snuggels 2014-07-13
Ddrufindbad needs an actual list of bad sectors to work with. A sector range of 2048 5860532223 would mean that all sectors in that range are bad and would be checked, which would take a very very very long time and report all files are bad.
But also ddrufindbad will not work if mmstat or fsstat are unable to give results. This is why I created ddru_ntfsfindbad. It only works with a ddrescue logfile, but it does not rely on 3rd party software to process the NTFS partition (plus it is much faster).
The whole idea behind this is to find out what files are corrupt AFTER performing data recovery on a failing drive, where you would have a log of sectors that were not recoverable.