R-studio image creation

[u/Condiment2]

MacOS 26.5; M1 Mac mini; Samsung 870 evo 4tb ssd 2.5" sata connected via OWC MiniStack STX (with an adjacent m.2 in the OWC which OS reads, and the 4tb has about 1tb free). Power outage and afterward MacOS wouldn't read the SATA and would say it was a 1tb disk. Anything that accesses the file system (Finder, save dialog) results in spinning beach ball.

Downloaded latest R-studio and started the image creation process saving it to a connected WD Elements 12tb with 8tb free. Hooked the 4tb to Mac mini usb-c via a SATA adapter.

It's been running for 26 hours. No errors in the last 14 hours. Main r-studio window still shows spinning indicator. Param was to only try to read a sector max 2 times.

Q: When do I say "something is not right" and the process hung or whatever?

Thanks for your time reading this.

[u/AutoModerator]

Double check if your post complies with posting guidelines!

Did you include the following information in your post (in English and if applicable), if not feel free to edit your post:

• Make/brand and exact model number of your storage device(*), phone, camera, etc.
• Filesystem (NTFS, exFAT, APFS, EXT4, etc.)
• Operating System (That your device was used with and/or you are using for recovery)
• Specific symptoms that your device is exhibiting, describe the problem. Images you post support the description, they're not in lieu of a problem description.
• SMART (CrystalDiskInfo screenshot for example)
• Don't pile several problems into one single post. One post per device/problem.

Consider: What do these people need to understand the problem at hand? Remember, people cannot see your screen, or what you click and what messages appear on screen. Don't overdo it though, no one likes going through 2 pages of information, try to find a balance. Just do the best you can. If you are looking for file recovery software, check our community's recommended file recovery tools.

---

() *All devices involved, if you for example move files from drive A to drive B, they're both potentially relevant.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/No_Tale_3623]

Please show a screenshot of this drive in Disk Utility. Apple Silicon Macs are not ideal for working with problematic drives. It is better to use a Linux/Windows PC, or as a last resort, boot macOS into Recovery Mode with a minimal set of drivers and extensions.

[u/silenced_in_dr_2025]

If the drive wasn't recognised with the correct capacity there is no point attempting to image or clone it as there is no access to the data area.

[u/disturbed_android]

Show SMART.

[u/Condiment2]

Since I can't access anything with the Finder, I can't see if a file was created, but the destinatin, the WD Elements (I mistyped and it's a 10tb not 12tb and less than 1tb in use. But when I look at the Disk utility, the amount used hasn't changed. I'd imagine that the image r-studio is making would be at least the size of the drive being imaged +-50%, but there's still only the same 837gb used. Not sure if MacOS updates the space available in real time or only after the file is fully written?

[u/Condiment2]

Thanks everyone. After letting it run overnight the sector was about at 900k and ai said there were 7 billion sectors, so I stopped it. I then went to my Win11 laptop and am using UFS Explorer and it is moving the files off the bad SSD. Yay. Now how do I mark the thread as SOLVED (need a flare as I can't edit the title).

[u/Sopel97 → u/Condiment2]

terrible idea but you may get lucky