oneRd wrote:
Do I have any advantage in terms of processing time if I keep the amount of space in use on my test drive at minimum or what matters is the total disk's space?
The question was intended in case of logical recovery software use. I answer this question myself: no. Software don’t make distinction between meaningful information and empty space. They will process the whole disk space or partition.
Hello everyone!! After a several days of duly “sector by sector” search I have finally understood now what a terminal log is
![drunk :druunk:](./images/smilies/alc.gif)
looking back at my last posts I feel a bit like Neo being uploaded with entire “domains” of new knowledge in a very short time-span. I must say I have really enjoyed the binge-reading and come to appreciate even more your hard work in this field.
According to my last checkups: the drive appears in the BIOS, it does not appear in Windows 10, it shows up in Lubuntu as unknown or unmountable and it does appears on terminal if I type lsblk
Attachment:
rte.png [ 81.39 KiB | Viewed 19550 times ]
My plan: first doing a very quick sortie with the TTL adapter (since a bought it) and see what do I get back in the terminal and post it here. Wait for your advice. Assuming there is still hope I will try next to image the drive using ddrescue or HDDSuperClone.
Quote:
.... power the drive on with the terminal connected and POST the LOG that the drive output to TTL/terminal software at power up ... Goes without saying open the terminal first and power the drive later.
Spildit has been clear on how to connect the drive through TTL, but how and when do I turn the drive off? It is safe to just power off the drive once It has delivered all information on terminal?
That said:
I've been reading multiple times all major guides around about ddrescue and the HDDSuperClone manual. I would like to understand if my drive’s condition needs a particular setup for HDDSuperClone (maybe the author could help with this) that is not available on the free version nor on ddrescue. I have read ddrescue standard setup for recovery can be further improved with some tweaks like direct access the drive with the --idirect call and the skipping function.
It could help to know how data are arranged; the drive is half full. Also fragmentation should be reasonably low as I did defragmentation not so long previous the failure with very little changes (using mostly to browse internet and working on a few docs and pics). Is that safe to assume data are all stored together?
I've read I could use ddrutility and partclone to extract the MFT from NTFS partitions and save time but I would rather avoid it if the drive conditions turned out to be stable - I do not know how serious it is not being able to get the SMART parameter in Victoria. I've always treated my HDDs as if they contained nitroglycerine therefore I know mine has never suffered any trauma of sort. I do not know if that is enough to guarantee a not damaged platter(s) or head(s).
It is a lot of questions but at least now you know we can have a more constructive conversation.
Thanks for you time