Contribute
Register

Bizarre SSD drive failure

Status
Not open for further replies.
Joined
Aug 14, 2012
Messages
41
Motherboard
GA-Z87MX-D3H
CPU
i7-4770
Graphics
GTX 980 Ti
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Hello,

I'm having a bit of a bizarre issue with my SSD. The Hackintosh suddenly restarted itself while I was using it, and it won't reboot, the boot bar indicator below the Apple logo just goes a quarter of the way and then it reboots again on an endless loop.

So I removed the SSD and connected it to my MacBook so I could run disk utility or a DiskWarrior scan/rebuild on it, but as soon as the drive is mounted the MacBook crashes!

I tried this on a third Mac, the same thing, as soon as it mounts, it crashes the Mac.

I booted on recovery mode on one of the Macs, plugged in the SSD drive, and it also crashed the mac.

I booted the Hackintosh using an old Sierra clover boot USB I have, the recovery mode doesn't crash, and the drive shows as pictured in the attached screenshot.

SSD-Sierra-Disk-Utility.jpg


The other bizarre part is that I managed to mount the drive on Windows 10 by using 3rd party software that allows mounting Mac filesystems, and I can see all the files and browse them.

When booting up verbose from the Hackintosh I see some APFS related errors but they scroll super fast and I can't find out hjow to get a text dump of that, however, on the other Mac that this SSD crashes, I get the following:

Code:
*** Panic Report ***
panic(cpu 0 caller 0xffffff7f85224093): "kind == NEW && refcnt = -1\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/apfs/apfs-748.67.14/nx/jobj.c:2532
Backtrace (CPU 0), Frame : Return Address
0xffffff9113253830 : 0xffffff8003c6d166
0xffffff9113253880 : 0xffffff8003d95824
0xffffff91132538c0 : 0xffffff8003d87b10
0xffffff9113253940 : 0xffffff8003c1f180
0xffffff9113253960 : 0xffffff8003c6cbdc
0xffffff9113253a90 : 0xffffff8003c6c99c
0xffffff9113253af0 : 0xffffff7f85224093
0xffffff9113253b60 : 0xffffff7f852237a1
0xffffff9113253cf0 : 0xffffff7f851c4cd1
0xffffff9113253e60 : 0xffffff7f852244be
0xffffff9113253f20 : 0xffffff7f8521123a
0xffffff9113253fa0 : 0xffffff8003c1e4f7
      Kernel Extensions in backtrace:
         com.apple.filesystems.apfs(748.51)[8CC12916-78CF-38CC-89BD-490873C400A5]@0xffffff7f851c2000->0xffffff7f852a7fff
            dependency: com.apple.kec.corecrypto(1.0)[CA65BD09-4559-3507-A72B-733ED9110DF1]@0xffffff7f84caf000
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[CA2AB641-FF39-316A-BA4F-5AF561C66AC7]@0xffffff7f850a4000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[F27A8A2A-6662-3608-83BD-415037509E01]@0xffffff7f84646000

BSD process name corresponding to current thread: kernel_task

Any advice on how to repair this unmountable drive?
 
Last edited:
I managed to mount the drive on the MacBook by using Disk Arbitrator (I google how to prevent automatically mount of a USB drive on Mac OS) and I discovered that if I mount the drive on read-only mode it doesn't crash the MacBook, I can browse the files and even do the first aid with disk utility, this is what I'm getting:

Code:
Running First Aid on “Container disk4”

Repairing storage system
Performing fsck_apfs -y -x /dev/disk3s2
Checking the container superblock.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume.
Checking the APFS volume superblock.
The volume Pro SSD was formatted by hfs_convert (748.1.47) and last modified by apfs_kext compiled @ Nov  2 201.
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 2.
error: drec_val object (oid 0x2): invalid type (0)
Snapshot is invalid.
The volume /dev/disk3s2 could not be verified completely.

Operation successful.

Google is not helping much with this error.

The good news is that I managed to mount the EFI partition and backup my clover settings and I will be able to back up all my data but I would love to simply fix the issue with the file system and get back to normal without having to do a full re-install.

Any help?
 
Status
Not open for further replies.
Back
Top