You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
NVME drives partition map seems to be broken. I am unable to erase/wipe the disk.
I tried:
diskutil verifyDisk /dev/disk4
diskutil unmountDisk disk4
dd if=/dev/zero of=/dev/disk2 bs=100m count=10
sudo diskutil repairDisk /dev/disk4
and I get: Error repairing map: Device error (83)
I would really like to try and repair this NVME SSD, as it's 7.68TB and costs a lot of $$$.
Thank you for any advice/pointers.
Mac Studio, macOS 13.4
A Reasonable non-zero size/capacity says the drive is not dead.
But its current partition scheme is 'unsupported' (or hopelessly corrupted) and child count is zero indicating there is nothing usable on that drive in its current state.
You can try to repair the device, but I do not expect success.
Select the DEVICE by its manufacturer-give name and ERASE. defaults should be GUID partition map, APFS volume, and a name you like.
NB> If it refuses to erase, pretend the screen says "are you sure" instead of whatever message it actually says, and Immediately invoke ERASE again. (This sometimes happens with foreign file systems that may contain data, and the Mac is trying to protect them.)
A Reasonable non-zero size/capacity says the drive is not dead.
But its current partition scheme is 'unsupported' (or hopelessly corrupted) and child count is zero indicating there is nothing usable on that drive in its current state.
You can try to repair the device, but I do not expect success.
Select the DEVICE by its manufacturer-give name and ERASE. defaults should be GUID partition map, APFS volume, and a name you like.
NB> If it refuses to erase, pretend the screen says "are you sure" instead of whatever message it actually says, and Immediately invoke ERASE again. (This sometimes happens with foreign file systems that may contain data, and the Mac is trying to protect them.)
There is no need to use to complex Terminal commands.
In Disk Utility, be sure that you set View menu to "show all devices":
in my example above, my NVMe drive is shown by its immutable manufacturer-given device-name, SHGP31-10... , and can be completely repaired, INCLUDING top-level partition scheme.
If it does not come clean, the entire Device will have to be ERASED. Just erasing the MacOS volume is useless against partition corruption.
If you used any Windows utilities that referenced the physical drive, they are completely likely to clobber the partition map. Windows is not a pleasant guest.
If you have any third-party disk Utilities installed, these are a problem because they leave the drive as a Windows New Technology File System drive, (NTFS, the W is silent) then simulate a MacOS volume structure on top of that to "save you the trouble of erasing". Instead you have untold aggravation later for a number of reasons, and the drive is not accessible unless/until the third-party utilities are loaded -- so drive is not accessible for Recovery.
If the status is the same as you posted before, partition map not supported and child count zero, the drive has likely failed and you should contact the drive-maker for a replacement under warranty.
Many drives have date-codes that make the process easier -- you may not need tedious proof-of-purchase documentation if within the expected life of the drive.
A simple failure of one block in the directory can not cause a failure like this. Since drives of all kinds were first made, a drive controller sets aside spare blocks to be substituted for any blocks that test bad in the factory or later in the field. Supplying new data allows the controller to substitute a spare block for any that have tested bad, and the drive continues to be perfectly usable.
This drive has experienced some sort of non-trivial failure. Send it back for a replacement under warranty.
Try not to let the drive-maker jerk you around, tell you you need to check it under Windows, or other impossible hurdles. Tell them to send you a drive that works, and THEY can figure out what the issue is.
I have show all devices enabled. First aid seems to run fine, but erase partition fails every time.
Tried running erase two times in a row, each time, same error below. :/
Hmm….at this point, I would try erasing and formatting the drive Ex- Fat on a windows machine, then bring it back to the Mac and see if it will format APFS/GUID Partition Map.
In the end I ended up doing an RMA, looks like the drive has some manufacturing defect/issue, so will probably get a new drive. Luckily all my data was backed up elsewhere.
Corrupted SSD / Partition map
