imaging hdd doesn't return files in their proper folders ?

[raven4d]

hello all .

i have used ddrescue to image wd5000aaks-22v1a0 that has some bad sectors .

the first 10 gigas were imaged succesfully then i had to jump over 2 giga to start from the 12th giga untill the end .

the thing is when mounting the image using OSFMount and doing a scan using r-studio , tons of files appear but in raw recovery , all files sorted by their extention .

imaging the first sectors of the original drive should have gathered the MBR and MFTs right ? so files should appear in their original folders , not like an ordinary raw recovery .

[raven4d]

the drive/data has no value and for testing purposes only

[lcoughey]

When you skipped ahead, did you skip ahead on both the source and destination drive?

ddrescue -i 12G -o 12G [source] [destination] [log]

[raven4d]

When you skipped ahead, did you skip ahead on both the source and destination drive?

ddrescue -i 12G -o 12G [source] [destination] [log]

thank you for that notice .
i am using the following

ddrescue -n -f -i 12G /dev/sda1 /dev/sdb1 log

shouldn't the output file automatically follow the input one ?
not using the -o flag should have done the problem ?

[lcoughey]

When you skipped ahead, did you skip ahead on both the source and destination drive?

ddrescue -i 12G -o 12G [source] [destination] [log]

thank you for that notice .
i am using the following

ddrescue -n -f -i 12G /dev/sda1 /dev/sdb1 log

shouldn't the output file automatically follow the input one ?
not using the -o flag should have done the problem ?

It should work, in theory, but I never take the risk. After thinking about it for a bit, it would be helpful to know the file system that is on the drive. The missing 2GB could very well be enough to cause file system corruption.

[raven4d]

sorry , i've skipped that , it's ntfs formatted drive