Search found 321 matches

Go to advanced search

by maximus
Wed Jan 02, 2019 9:29 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

12839 It's the second one :(. I tried different computers and the same issue. I read somewhere on the net that someone has success cloning via USB with ddrescue so I gave it a try. So far 1.7 tb pass with zero skips and errors It should be finished soon I'll let you know if it worked https://imgur....
by maximus
Wed Jan 02, 2019 3:12 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

12874 Well we will have to wait and. It'll few more days to finish. Once it'll finish Ill post here the result and try again to clone it. Happy new year man I just released version 2.1.6. With this version, it will give a message for an unsupported sector size, if that is somehow the case. And the ...
by maximus
Wed Jan 02, 2019 3:03 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

HDDSuperClone version 2.1.6 released.

HDDSuperClone Changelog

version 2.1.6 20190102
* Now shows message for unsupported sector size in the free version
* Fixed a bug where SCSI passthrough could report drive sized changed
by maximus
Tue Jan 01, 2019 8:59 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

Okay, I am looking through the code, and maybe found another possibility for a wrong/changed size error. But as far as I can tell it would still be triggered by a read error of some sort. Hope somehow it is that possible issue, and your recovery is good. EDIT: After further review, the issue may hap...
by maximus
Tue Jan 01, 2019 8:42 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

That output shows it is not because of the sector size. It it recognized as having 512 byte logical and physical sector size to the OS. So that would not be the cause of hddsuperclone reporting the size changed. With that being the case, it goes back to questioning the data recovered. Hopefully it i...
by maximus
Tue Jan 01, 2019 7:40 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

Here is a command you can use to show what sector size the kernel sees from the drive. You should be able to run this command from a new terminal window while ddrescue is running, all it does is list the block devices. lsblk -d -b -o NAME,SIZE,LOG-SEC,PHY-SEC,MODEL Maximus thanks for your reply Wel...
by maximus
Sun Dec 30, 2018 9:25 am
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

Here is a command you can use to show what sector size the kernel sees from the drive. You should be able to run this command from a new terminal window while ddrescue is running, all it does is list the block devices.

Code: Select all

lsblk -d -b -o NAME,SIZE,LOG-SEC,PHY-SEC,MODEL
by maximus
Sun Dec 30, 2018 9:19 am
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

When working with a USB drive using the default auto-passthrough mode, it will try to get the best information from a passthrough ATA identify device command. But when the imaging is started, it uses SCSI passthrough. It could be possible that the ATA data indicated a 512 byte sector size, but the ...
by maximus
Sat Dec 29, 2018 10:31 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

I hope the best for your outcome. If the ddrescue result is good, I do have one possibility that could happen with hddsuperclone. When working with a USB drive using the default auto-passthrough mode, it will try to get the best information from a passthrough ATA identify device command. But when th...
by maximus
Thu Dec 27, 2018 10:38 pm
Forum: HDDSuperClone & HDDSuperTool
Topic: HDDSuperClone
Replies: 388
Views: 64997

HDDSuperClone

Did you try cloning it first with hddsuperclone, then fix the slow issue, and then use the same log file to attempt to resume the cloning? If so, then it would indicate that the original log file had a bad size, and it was stopping you from using it with the drive now showing the correct size, and i...

Go to advanced search