No, and it is not up to me to fix it. It is something with how UFS Explorer works. It will not likely get fixed unless the makers of UFS Explorer want the integration to work.
But what is the issue? One disk starts being cloned into a file and a virtual disk device and later one app reads zero out of the sdv or doesnt read anything (as we cannot tell what UFS explorer thinks?) I can suggest some issues - like the UFSexplorer instead of reading from start also tries to read the end of a disk, like some gpt copy or other super copies, or it reaches out of the current scope of a disk? In windows it could be another assumption that UFSexp tries to open a file in RW mode whereas you cannot do it in windows if the file is already in write mode opened in another app but you can easily do it in linux OS. It also can fail looking for some special /dev/sdv disk-like parameters eg. size of the disk, sector size and so on and fails to do it on a virtual kernel drive and shows all zeroes due to some programming error. BTW what is UFSexplorer for? Like listing any FS structures? UFS afair is a Deeveedee filesystem.
It's unclear from this video what are values of defect map. The software aborts partition detection immediately after it detects first defect block. In this case the software "doesn't know" that defect is emulated by a third-party software. The reason for this should be obvious. There were no "real" requests to adopt the software to be used with HDDSuperClone so there are no any special workarounds to support defects emulation. Linux software version doesn't have any reason to open drive for "write", even for SCSI access (unlike Windows, that requires "write" mode to enable SCSI pass-through). Readign of disk tails is required to support GPT (main copy is located at end of disk) and to support different RAID metadata.
Hope ufs can working 😢
Ever figure out what's causing it?
No, and it is not up to me to fix it. It is something with how UFS Explorer works. It will not likely get fixed unless the makers of UFS Explorer want the integration to work.
But what is the issue? One disk starts being cloned into a file and a virtual disk device and later one app reads zero out of the sdv or doesnt read anything (as we cannot tell what UFS explorer thinks?) I can suggest some issues - like the UFSexplorer instead of reading from start also tries to read the end of a disk, like some gpt copy or other super copies, or it reaches out of the current scope of a disk? In windows it could be another assumption that UFSexp tries to open a file in RW mode whereas you cannot do it in windows if the file is already in write mode opened in another app but you can easily do it in linux OS. It also can fail looking for some special /dev/sdv disk-like parameters eg. size of the disk, sector size and so on and fails to do it on a virtual kernel drive and shows all zeroes due to some programming error.
BTW what is UFSexplorer for? Like listing any FS structures? UFS afair is a Deeveedee filesystem.
It's unclear from this video what are values of defect map. The software aborts partition detection immediately after it detects first defect block. In this case the software "doesn't know" that defect is emulated by a third-party software. The reason for this should be obvious.
There were no "real" requests to adopt the software to be used with HDDSuperClone so there are no any special workarounds to support defects emulation.
Linux software version doesn't have any reason to open drive for "write", even for SCSI access (unlike Windows, that requires "write" mode to enable SCSI pass-through).
Readign of disk tails is required to support GPT (main copy is located at end of disk) and to support different RAID metadata.