March 1st, 2020, 11:06
March 1st, 2020, 16:33
March 1st, 2020, 16:59
June 5th, 2020, 14:58
June 5th, 2020, 21:23
June 5th, 2020, 23:05
June 5th, 2020, 23:53
maximus wrote:I see the bug in the Linux version where it completely locks up on bad sectors has not been fixed
June 6th, 2020, 0:18
June 8th, 2020, 12:07
michael chiklis wrote:Wooow, seem to be very promising this update.
Very good job
Unfortunately i don't have Deepspar but i own MRT which all we hate due the way how File Explorer behavies when extracting files.
MRT can't separate properly BAD files from GOOD files becuse it drops the bads one all in single folder (without original folder structure).
This means that many files get renamed, so is near to impossible (very difficult) understanding from which folders are those coming from.
Is UFS able to separate good files from bad files and drop them in a folder (ex called DAMAGED) with original folder structure of source drive?
Will in future UFS support MRT as Deepspar?
MRT staff doesn't want to listen their customer, they will never fix this and other heavy bugs, especially in File Explorer.
It is very annoing that we can't generate a proper list of bad files to send to ours customer, maybe UFS staff can overcome easily to this very annoing mrt shortcoming.
I hope so
June 8th, 2020, 22:43
June 9th, 2020, 9:35
Amarbir[CDR-Labs] wrote:Dr Kiev ,
Is This Feature For Recovery Explorer Also ?
June 9th, 2020, 11:43
Iurii wrote:Amarbir[CDR-Labs] wrote:Dr Kiev ,
Is This Feature For Recovery Explorer Also ?
Not all, only part of them.
Recovery Explorer products are a cheaper and simpler alternative to UFS Explorer products starting from version 7.0. UFS Explorer is intended for data recovery professionals, while the Recovery Explorer audience is experienced users and system administrators.
June 9th, 2020, 13:06
maximus wrote:Here is the short version without me going back through exact steps because it is late here for me.
- software edition (with version); Latest version of UFS Explorer Pro 8.0 (Linux) downloaded a couple hours before this post.
- OS edition; Ubuntu 18.04.4
- hard drive connection type; SATA, and also as a generic block device through HDDSuperClone.
- sequence of actions you did (with all parameters). While exploring the file system of the NTFS partition on the drive, when expanding a certain folder the program will lock up indefinitely.
The Windows version does not have this issue, it only happens with the Linux version.
There are bad sectors in the MFT on the drive, which is likely causing the issue.
When using the generic block device through HDDSuperClone, I can see that it ends up in an endless loop trying to read a bad sector (or block). It will not stop trying to read the bad sector (block), the program must be terminated.
June 9th, 2020, 13:43
Iurii wrote:maximus wrote:Here is the short version without me going back through exact steps because it is late here for me.
- software edition (with version); Latest version of UFS Explorer Pro 8.0 (Linux) downloaded a couple hours before this post.
- OS edition; Ubuntu 18.04.4
- hard drive connection type; SATA, and also as a generic block device through HDDSuperClone.
- sequence of actions you did (with all parameters). While exploring the file system of the NTFS partition on the drive, when expanding a certain folder the program will lock up indefinitely.
The Windows version does not have this issue, it only happens with the Linux version.
There are bad sectors in the MFT on the drive, which is likely causing the issue.
When using the generic block device through HDDSuperClone, I can see that it ends up in an endless loop trying to read a bad sector (or block). It will not stop trying to read the bad sector (block), the program must be terminated.
Please read article https://www.ufsexplorer.com/blog/work-w ... -drive.php
It describe our recommendation how to use our software.
June 9th, 2020, 14:48
DR-Kiev wrote:michael chiklis wrote:Wooow, seem to be very promising this update.
Very good job
Unfortunately i don't have Deepspar but i own MRT which all we hate due the way how File Explorer behavies when extracting files.
MRT can't separate properly BAD files from GOOD files becuse it drops the bads one all in single folder (without original folder structure).
This means that many files get renamed, so is near to impossible (very difficult) understanding from which folders are those coming from.
Is UFS able to separate good files from bad files and drop them in a folder (ex called DAMAGED) with original folder structure of source drive?
Will in future UFS support MRT as Deepspar?
MRT staff doesn't want to listen their customer, they will never fix this and other heavy bugs, especially in File Explorer.
It is very annoing that we can't generate a proper list of bad files to send to ours customer, maybe UFS staff can overcome easily to this very annoing mrt shortcoming.
I hope so
All you need to put pattern to bad-blocks areas with MRT, mount that drive to system , run UFS Pro, acivate feature of bad-block recognition by pattern and start saving data in advanced mode separating good/corrupted files . All folders hierarchy will be kept, bad files you will find in separate folder (problem), same like in Pc3k DE .
June 12th, 2020, 22:27
maximus wrote:Iurii wrote:maximus wrote:Here is the short version without me going back through exact steps because it is late here for me.
- software edition (with version); Latest version of UFS Explorer Pro 8.0 (Linux) downloaded a couple hours before this post.
- OS edition; Ubuntu 18.04.4
- hard drive connection type; SATA, and also as a generic block device through HDDSuperClone.
- sequence of actions you did (with all parameters). While exploring the file system of the NTFS partition on the drive, when expanding a certain folder the program will lock up indefinitely.
The Windows version does not have this issue, it only happens with the Linux version.
There are bad sectors in the MFT on the drive, which is likely causing the issue.
When using the generic block device through HDDSuperClone, I can see that it ends up in an endless loop trying to read a bad sector (or block). It will not stop trying to read the bad sector (block), the program must be terminated.
Please read article https://www.ufsexplorer.com/blog/work-w ... -drive.php
It describe our recommendation how to use our software.
I have replied to your PM and am offering TeamViewer access to a computer for a technician to view the issue. I am trying to give level 2-3 information about a software bug in the Linux version, but I feel I am only getting level 1 support replies. The Linux version gets stuck in an infinite loop trying to read a bad sector. Hopefully a TeamViewer session will help a technician see the issue.
June 13th, 2020, 6:35
So the only reply I have got is to use the advanced SCSI connection method, which does bypass the issue (except with Recovery Explorer because that is not an available option). The issue is being blamed on an internal read issue, which is not the case. So I made a video to demonstrate the issue, since it will never get fixed because no one cares about a bug in the Linux version.
https://youtu.be/Sy5kk84urFc
June 13th, 2020, 8:48
maximus wrote:maximus wrote:Iurii wrote:maximus wrote:Here is the short version without me going back through exact steps because it is late here for me.
- software edition (with version); Latest version of UFS Explorer Pro 8.0 (Linux) downloaded a couple hours before this post.
- OS edition; Ubuntu 18.04.4
- hard drive connection type; SATA, and also as a generic block device through HDDSuperClone.
- sequence of actions you did (with all parameters). While exploring the file system of the NTFS partition on the drive, when expanding a certain folder the program will lock up indefinitely.
The Windows version does not have this issue, it only happens with the Linux version.
There are bad sectors in the MFT on the drive, which is likely causing the issue.
When using the generic block device through HDDSuperClone, I can see that it ends up in an endless loop trying to read a bad sector (or block). It will not stop trying to read the bad sector (block), the program must be terminated.
Please read article https://www.ufsexplorer.com/blog/work-w ... -drive.php
It describe our recommendation how to use our software.
I have replied to your PM and am offering TeamViewer access to a computer for a technician to view the issue. I am trying to give level 2-3 information about a software bug in the Linux version, but I feel I am only getting level 1 support replies. The Linux version gets stuck in an infinite loop trying to read a bad sector. Hopefully a TeamViewer session will help a technician see the issue.
So the only reply I have got is to use the advanced SCSI connection method, which does bypass the issue (except with Recovery Explorer because that is not an available option). The issue is being blamed on an internal read issue, which is not the case. So I made a video to demonstrate the issue, since it will never get fixed because no one cares about a bug in the Linux version.
https://youtu.be/Sy5kk84urFc
June 13th, 2020, 10:28
Iurii wrote:So the only reply I have got is to use the advanced SCSI connection method, which does bypass the issue (except with Recovery Explorer because that is not an available option). The issue is being blamed on an internal read issue, which is not the case. So I made a video to demonstrate the issue, since it will never get fixed because no one cares about a bug in the Linux version.
https://youtu.be/Sy5kk84urFc
We are working on this problem. We will let you know when bug will be fixed.
June 13th, 2020, 18:06
Amarbir[CDR-Labs] wrote:Iurii wrote:So the only reply I have got is to use the advanced SCSI connection method, which does bypass the issue (except with Recovery Explorer because that is not an available option). The issue is being blamed on an internal read issue, which is not the case. So I made a video to demonstrate the issue, since it will never get fixed because no one cares about a bug in the Linux version.
https://youtu.be/Sy5kk84urFc
We are working on this problem. We will let you know when bug will be fixed.
Well,
When a developer of a tool reports a bug ,a developer on the other side should be speaking to him ,Why is this because some level of tech exchange is bound to happen ,Maximus is a awesome developer and researcher and if a low end tech guys speaks to him i would say its a insult ,So speak to him and try and solve the issue ,Using hddsuperclone and Recovery explorer or UFS Explorer should be a deadly combo for peeps who understand it .
PS : Maximus Keep Up The Good Work Buddie ....
Powered by phpBB © phpBB Group.