Com apple diskmanagement disenter ошибка 49217

Similar questions

• External Disk Drive Problem
  com.apple.DiskManagement.disenter error 49153

  1407
  1
  

• External Hard Drive LaCie Not Mounting
  Could not mount “LaCie”. (com.apple.DiskManagement.disenter error -119930878
  

  1113
  2
  

• Disk Management disenter error 49244
  After updating to MacOS 12.4 my external drive will not mount. I get an error message that says «Could not mount “My Passport LHM”. (com.apple.DiskManagement.disenter error 49244.)»

  How do I fix this issue?
  

  1766
  6
  

Machines: 2 Macbook Pros, one 2015 and one 2017.

I was consolidating all my files into archives as I’ve been doing every end of year now. I had to change some partitions around, and then I decided to encrypt the ARCHIVES partition and use the remaining two for time machines.

A few hours later, everything seems to be ok, then suddenly it doesn’t mount any more! I get this error box:

Could not mount “#ARCHIVES”. 
(com.apple.DiskManagement.disenter error 49217.)

I searched a lot, and eventually I think I spotted the problem. The disk must have gotten unplugged or disconnected during the encryption process, and now it’s permanently stuck at 12%.

$ diskutil apfs list:
+-- Container disk3 040F149B-CF0A-4AB4-A419-DA4025B9F2EB
    ====================================================
    APFS Container Reference:     disk3
    Size (Capacity Ceiling):      1000110108672 B (1.0 TB)
    Capacity In Use By Volumes:   639805698048 B (639.8 GB) (64.0% used)
    Capacity Not Allocated:       360304410624 B (360.3 GB) (36.0% free)
    |
    +-< Physical Store disk2s2 A54CE868-A1E6-4FBD-ACA5-3A40676ABC7C
    |   -----------------------------------------------------------
    |   APFS Physical Store Disk:   disk2s2
    |   Size:                       1000110108672 B (1.0 TB)
    |
    +-> Volume disk3s1 6DA2AF20-C71E-3FDA-ABD2-FCB8718C8A9A
        ---------------------------------------------------
        APFS Volume Disk (Role):   disk3s1 (No specific role)
        Name:                      #ARCHIVES (Case-insensitive)
        Mount Point:               Not Mounted
        Capacity Consumed:         639597895680 B (639.6 GB)
        Encryption Progress:       12.0% (Paused) (Unlocked)

Here are a bunch of things I tried:

$ diskutil apfs decryptVolume disk3s1 -user gmiwenht -passphrase ********
Starting background decryption of disk3s1 using crypto user gmiwenht as authorization
Error starting decryption of APFS Volume: Malformed UUID (-69578)


$ diskutil apfs encryptVolume disk3s1 -user gmiwenht -passphrase ********:
The APFS Volume must be mounted in order to be encrypted


$ diskutil mount disk2s2:
Volume on disk2s2 failed to mount because it appears to be
an APFS Physical Store (or is the APFS Container already mounted?)
Note that for this mount operation, Disk Arbitration reports that
the operation is not supported (kDAReturnUnsupported)
See "diskutil apfs list"


$ diskutil mount disk3s1:
Volume on disk3s1 failed to mount
This appears to be an APFS Volume; note that locked APFS volumes
will not mount unless unlocked (e.g. "diskutil apfs unlockVolume")


$ diskutil apfs unlockVolume disk3s1:
Passphrase: ********
Unlocking any cryptographic user on APFS Volume disk3s1
Error unlocking APFS Volume: The given APFS Volume is not locked (-69589)

I ran out of ideas. I tried playing around with Disk Utils too. Here is the info it gives for the drive:

Volume name : #ARCHIVES
Volume type : APFS Volume
BSD device node : disk3s1
File system : APFS (Encrypted)
Connection : USB
Device tree path : IODeviceTree:/PCI0@0/XHC1@14
Writable : No
Is case-sensitive : No
File system UUID : 6DA2AF20-C71E-3FDA-ABD2-FCB8718C8A9A
Volume capacity : 1,000,110,108,672
Owners enabled : No
Is encrypted : Yes
Can be verified : Yes
Can be repaired : Yes
Bootable : No
Journaled : No
Disk number : 3
Partition number : 1
Media name : 
Media type : Generic
Ejectable : Yes
Solid state : No
S.M.A.R.T. status : Not Supported
Parent disks : disk3

I tried running first aid, and it seemed to work!

Running First Aid on “#ARCHIVES” (disk3s1)

Repairing file system.
Volume is already unmounted.
Performing fsck_apfs -y -x /dev/rdisk3s1
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 #ARCHIVES was formatted by hfs_convert (1412.41.1) and last modified by apfs_kext (1412.41.1).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the extent ref tree.
Checking the fsroot tree.
Verifying allocated space.
The volume /dev/rdisk3s1 appears to be OK.
File system check exit code is 0.
Restoring the original state found as unmounted.

Operation successful.

But… when I try to mount it, I still get the same error again:

Could not mount “#ARCHIVES”. 
(com.apple.DiskManagement.disenter error 49217.)

Last but not least, all the search results seem to be getting hogged by this one company called iBoysoft. Their iBoysoft Data Recovery Free software seems to be able to mount the drive and I can see all my files are still inside (phew). But of-course if you want to actually retrieve your data, as opposed to just a scan, then you need a $99 license. EDIT: screenshot

If someone with APFS experience I would be very appreciative. I feel like there’s got to be some command line tricks that iBoysoft uses that will fix it for free. I doubt they invent their own secret sauce so quickly that it’s ready to roll out and fix new bugs literally as they come up.

All my life’s files are on that disk, every single school, uni, and grad school project. Lesson learned: I should back up to more than one disk, but for now I cannot afford to break this hard drive.

TL;DR: You should probably wait a few months before upgrading to Catalina.