Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identical SSD Do Not Show and Raw Corrupted from NTFS SSD Hangs then Crashes #116

Open
Reusaliable opened this issue Feb 2, 2023 · 0 comments

Comments

@Reusaliable
Copy link

Issue 1: Identical SSDs are not shown after source selection.
Issue 2. Can not clone raw corrupted SSD due to 'damaged' file system.

When two identical SSDs are plugged in only one will show within source location then the target does not show at all as it's occupied by source selection.

Samsung EVO 870 1TB in USB C case plugged into left USB C port via USB C cable.
Samsung EVO 870 1TB in USB A case plugged into right USB A port via USB A cable.

Furthermore, one of these SSDs is 'raw corrupted' and the other is blank (partition 1 setup exact same to migrate data). When selecting Redo Backup it hangs on the identifying disks then freezes and crashes after a minute. Likely due to corrupted SSD containing 280 GB but not an accurate file system.

Please see more regarding this case in below link. I'm currently trying to use Redo Rescue to make a bit-bit full identical clone of corrupted SSD. Tried Redo Rescue and Recovery v1.0.4 and Redo Rescue v3.0.2.

Link: https://www.tenforums.com/drivers-hardware/202207-samsung-ssd-2-5-evo-970-raw-corruption-ntfs.html#post2508748

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant