Connecting USB-C SSD instantly corrupted it

[eicca]

This might be the biggest idiotic bug I've ever seen. All I did is plug my USB-C SSD into my iphone, transfer some files to it, and now it cannot be written to at all. Not by my Mac, not by my iPhone, not by my iPad. Throws an error every attempt.

I can read files fine, thank goodness, but I'm gonna have to wipe it unless anybody knows of a fix.

The QC at Apple is hilarious when it's not data-destroying, but this is infuriating and unacceptable.

 

[chrfr]

This might be the biggest idiotic bug I've ever seen. All I did is plug my USB-C SSD into my iphone, transfer some files to it, and now it cannot be written to at all. Not by my Mac, not by my iPhone, not by my iPad. Throws an error every attempt.

I can read files fine, thank goodness, but I'm gonna have to wipe it unless anybody knows of a fix.

The QC at Apple is hilarious when it's not data-destroying, but this is infuriating and unacceptable.

What happens when you run First Aid on it in Disk Utility, and what kind of disk is it?

 

[eicca]

First Aid fails with the following:

Running First Aid on “TruePartnerSSD” (disk4s1)

Checking file system and repairing if necessary and if possible.
Volume was successfully unmounted.
Performing fsck_apfs -y -x /dev/rdisk4s1
Checking the container superblock.
Checking the checkpoint with transaction ID 9831.
warning: container has been mounted by APFS version 2235.80.4.0.1, which is newer than 2235.0.13
warning: disabling overallocation repairs by default; use -o to override
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume /dev/rdisk4s1.
Checking the APFS volume superblock.
The volume TruePartnerSSD was formatted by diskmanagementd (2142.120.7) and last modified by apfs_kext (2235.0.13).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
error: (oid 0x123b) apfs_root: btn: invalid o_oid (0x1d49ce)
error: (oid 0x123b) apfs_root: btn: invalid o_xid (0x2664, expected 0x2604)
error: (oid 0x123b) apfs_root: btn: invalid o_type (0x40000002, expected 0x3)
error: (oid 0x123b) apfs_root: btn: invalid o_subtype (0xb, expected 0xe)
error: (oid 0x123b) apfs_root: btn: invalid o_type (0x40000002, expected 0x3)
warning: aborting jobj validations for current fsck pass - trying to repair fsroot tree with invalid nodes
error: btn: oid (1028), xid (9829), type (0x2), subtype (0xe), flags (0x1) level (2)
error: btn: invalid btn_btree.bt_key_count (expected 45306, actual 45343)
error: btn: oid (1028), xid (9829), type (0x2), subtype (0xe), flags (0x1) level (2)
error: btn: invalid btn_btree.bt_node_count (expected 1117, actual 1118)
Checking the extent ref tree.
Verifying volume object map space.
warning: orphan omap mapping found for oid 4667
The volume /dev/rdisk4s1 with UUID 0A69F0F9-5132-4DBF-BC2C-44CDF86ED9F6 was found to be corrupt and needs to be repaired.
Verifying allocated space.
warning: found spaceman free queue tree entry (0x1d49b1+1, xid 9827) which overlaps with existing range (0x1d49b1+2)
warning: found spaceman free queue tree entry (0x1d49a6+1, xid 9829) which overlaps with existing range (0x1d49a5+2)
warning: found spaceman free queue tree entry (0x1d49a8+1, xid 9829) which overlaps with existing range (0x1d49a8+1)
warning: found spaceman free queue tree entry (0x1d49f5+2, xid 9829) which overlaps with existing range (0x1d49f4+2)
warning: found spaceman free queue tree entry (0x1d49fb+1, xid 9829) which overlaps with existing range (0x1d49fb+1)
error: underallocation detected on Main device: (0x1d4ac8+1) bitmap address (0x74aa)
Performing deferred repairs.
error: Unable to perform deferred repairs without full space verification
error: Try running fsck against the entire APFS container instead of a volume
The volume /dev/rdisk4s1 with UUID 0A69F0F9-5132-4DBF-BC2C-44CDF86ED9F6 could not be verified completely.
File system check exit code is 8.
Restoring the original state found as mounted.
File system verify or repair failed. : (-69845)

Operation failed…

Disk is a Samsung SanDisk Extreme USB 3.2 SSD

 

[lostless]

look like the ssd went into failsafe mode. The drive probably went bad and some SSDs go into failsafe mode where you can still read the data, but it will no longer be able to write to it.

 

[DeltaMac]

hmm... Samsung? ...or, SanDisk? Samsung doesn't appear to use the name "Extreme" in a storage device, AFAIK. SanDisk has several using Extreme in the name.

Back up the drive, if you need to... then try to format the drive.

 

[eicca]

SanDisk, you’re right. Duh.

 

[chrfr]

First Aid fails with the following:

Given that the data is retrievable I'd probably just copy it elsewhere then reformat the whole thing, but you should also try to repair the container and the disk, not just the particular volume where your data is: https://support.apple.com/en-us/102611

You want to try repairing volumes, containers, then disks, in that order.
Also some Sandisk Extreme Pros have a severe firmware bug that can cause data loss, so make sure there are no outstanding firmware updates for your particular disk: https://arstechnica.com/gadgets/202...-failing-firmware-fix-for-only-some-promised/
In spite of the article only mentioning the Extreme Pro, the Extreme v2 and WD My Passport SSDs also have a problem and need updates: https://support-en.wd.com/app/firmwareupdate