Forum rules

Please do not post questions about data recovery cases here (use this forum instead). This forum is for topics on finding new ways to recover data. Accessing firmware, writing programs, reading bits off the platter, recovering data from dust...

Funny thing about STUart is you can actually mount /dev/nbdX as HDD and copy some data from it (very slowly, but most likely safer than "/Ti" and/or "/Tm" commands) and mounting is faster than whole drive imaging (it would take about half a year to download whole 2 TB :-/ in my case the drive was partitioned to 4 partitions and only 2 of them are filled with data - around 26%).

Due to a block based adressing you can just skip any bad sectors and continue to copy the data (although you must do it manually as STUart will crash probably). Download speed is pretty slow - about 34kBps of the filesystem with 460kbps UART. My drive supports up to 1.25 Mbps so maximum speed is probably nearly 100kBps. Up to this date it have worked with only one data retrieval failure (probably UART buffer overrun) and transfer run for several hours.

I'm pretty sure that there are similar functionalities in commercial software, but I'm offering you a GPLed source code (as is). If someone wants to maintain this software, I'm OK with it (after recovering all my files I hope I will never need to use it again ).

Is there a serial command to show the partition offsets in the drive (for the #define START_512 and #define LEN_512)? I've got a NTFS drive with two partitions that won't show in Win Disk Manger or mount in Linux. The drive seem to be responding to /AR and /FD command though. Also, where does the first bit (the Hi Addr 405B8600) come from in "/FD405B8600,,,1040,1,"?

Is there a serial command to show the partition offsets in the drive (for the #define START_512 and #define LEN_512)? I've got a NTFS drive with two partitions that won't show in Win Disk Manger or mount in Linux.

Not sure the controller works with the PC partition table in such a way, the partition table is an operating system thing. LBA devices (AFAIK) provide simple block access from block 0 to <disk_size> - the DOS partition table exists on top of that, as a data structure inside of the MBR (which begins at LBA block #0).

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum