com.apple.DiskManagement.disenter error -119930868 on external drive

Hi,

Hope you are all fine !

I had a problem on several disk due to bad unmounting caused by Caldigit TS4.

The TS4 has/had problem managing hard drives and sleep of the computer… The problem appeared on internal drives pugged into a OWC Dock.

The dock is TB2 with Apple TB2 to TB3 pugged into the Caldigit TS4.

One of the drives is a 4TB Seagate Exos Enterprise that is brand new and I'm almost sure I formatted it in APFS when using it for the first time. The other/s are 2TB or 3TB but almost sure at that time I was using HFS.

The drives are seen But no way to SOS… This particular 4 TB drive seems to respond mechanically well, like spinning when tryning to acces, going to sleep…And is brand new…

After reading a few (many actually ;) ) pages on Apple forums I've found, I've tried the diskutil way on terminal… but having some problem with syntax, sometimes it worked sometimes I think I'm not writing correctly so it does nothing…

If I understand well this error

com.apple.DiskManagement.disenter error -119930868

Is a directory problem.

A long time ago I used Disk Warrior a lot in the G4/G5 age ;) But it seems it doesn't handle APFS…

I've run a scan with Stellar Recovery and this software seems to see all my files… The Hard drive seemed to act normally during all the process… But it seems it doesn't just rebuild the directory and will recover all the files and put them like video in video folder…pictures in picture folder… so I'll have my files but a great mess…

I've also tried rhe FSCK command…but didn't undertood enough to get something good…

So my question are :

  • As the data seems to be there and the drive still working fine, is there a way to make Mac Os or a software rebuild the directory like Disk Warrior used to do. And not just back uping the files a la Stellar recovery.
  • Could someone make a comprehensive diskutil / fsck tutorial for noobs ;)
  • After the fix , if successful … should I throw this drive away or the prob is only a Mac OS bug…
  • Can the adapted TB2 to TB3 add source of problem ?

Can the adapted TB2 to TB3 ON Caldigit TB port add source of problem ?

  • AFPS is still recommanded for external HD
  • Could someone explain those DiskManagement.disenter error

Best

.V

Replies

Hi, Nobody there ;) ?

It seems that those DiskManagement.disenter error xxxxx has popped up a lot in various situations…@ various people…

THX

.V

Still working on that problem… Here what I've found with Terminal :

% diskutil list external /dev/disk4 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *4.0 TB disk4 1: EFI ⁨EFI⁩ 209.7 MB disk4s1 2: Apple_APFS ⁨⁩ 4.0 TB disk4s2

% diskutil verifyVolume disk4s2 Started file system verification on disk4s2 Error: -69564: Unable to find an APFS Container Reference

sudo fsck_apfs -n -x /dev/disk4s2 0000: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0400: 482b 0004 8000 6000 4846 534a 0000 15d6 |H.......HFSJ....| 0410: dca8 c8eb dfe3 533d 0000 0000 dca8 accb |......S.........| 0420: 0000 0eaa 0000 008a 0000 2000 15d4 6636 |..............f6| 0430: 00f7 a7d0 04ae 004e 0001 0000 0001 0000 |.......N........| 0440: 0000 237c 0001 88ea 0000 0000 0000 0001 |................| 0450: 0000 0000 0000 0000 0000 0000 0000 0000 |................| 0460: 0000 0000 0000 0000 9d19 222d 3940 63cd |............9.c.| 0470: 0000 0000 02ba a000 02ba a000 0000 15d5 |................| 0480: 0000 0001 0000 15d5 0000 0000 0000 0000 |................| 0490: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 04c0: 0000 0000 0100 0000 0100 0000 0000 0800 |................| 04d0: 0000 85d7 0000 0800 0000 0000 0000 0000 |................| 04e0: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0510: 0000 0000 1520 0000 1520 0000 0000 a900 |................| 0520: 0007 d0d7 0000 a900 0000 0000 0000 0000 |................| 0530: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0560: 0000 0000 1520 0000 1520 0000 0000 a900 |................| 0570: 0000 8dd7 0000 a900 0000 0000 0000 0000 |................| 0580: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0ff0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

<plist version="1.0"> <dict> <key>fsck_msg_type</key> <string>ERROR</string> <key>fsck_verbosity</key> <integer>1</integer> <key>fsck_msg_number</key> <integer>0</integer> <key>fsck_msg_string</key> <string>error: Device does not contain a valid APFS container.</string> </dict> </plist>

sudo fsck_apfs /dev/disk4s2 0000: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0400: 482b 0004 8000 6000 4846 534a 0000 15d6 |H.......HFSJ....| 0410: dca8 c8eb dfe3 533d 0000 0000 dca8 accb |......S.........| 0420: 0000 0eaa 0000 008a 0000 2000 15d4 6636 |..............f6| 0430: 00f7 a7d0 04ae 004e 0001 0000 0001 0000 |.......N........| 0440: 0000 237c 0001 88ea 0000 0000 0000 0001 |................| 0450: 0000 0000 0000 0000 0000 0000 0000 0000 |................| 0460: 0000 0000 0000 0000 9d19 222d 3940 63cd |............9.c.| 0470: 0000 0000 02ba a000 02ba a000 0000 15d5 |................| 0480: 0000 0001 0000 15d5 0000 0000 0000 0000 |................| 0490: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 04c0: 0000 0000 0100 0000 0100 0000 0000 0800 |................| 04d0: 0000 85d7 0000 0800 0000 0000 0000 0000 |................| 04e0: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0510: 0000 0000 1520 0000 1520 0000 0000 a900 |................| 0520: 0007 d0d7 0000 a900 0000 0000 0000 0000 |................| 0530: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0560: 0000 0000 1520 0000 1520 0000 0000 a900 |................| 0570: 0000 8dd7 0000 a900 0000 0000 0000 0000 |................| 0580: 0000 0000 0000 0000 0000 0000 0000 0000 |................| . . . 0ff0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

error: Device does not contain a valid APFS container.

I am encountering the same error. The drive has been working perfectly and now randomly won't mount. Did you ever manage to solve this?