Com apple diskmanagement disenter ошибка 49217

Boot into Safe Mode according to Start up your Mac in safe mode — Apple Support and test to see if the problem persists. Reboot normally and test again.

NOTE: Safe Mode boot can take up to 3 — 5 minutes as it’s doing the following; 

• Verifies your startup disk and attempts to repair directory issues, if needed

• Loads only required kernel extensions (prevents 3rd party kernel/extensions from loading)

• Prevents Startup Items and Login Items from opening automatically

• Disables user-installed fonts 

• Deletes font caches, kernel cache, and other system cache files

The Safe Mode boot is totally benign and a good first fix attempt to try for many problems.

How was the WD My Passport drive formatted?

Did it come with some software that you installed?

Have you installed or run any «cleaning», «optimizing», «speed-up» or anti-virus apps on your Mac?

My mac mini 2012 suddenly couldn’t boot this morning.
It looks like the main volume (with everything) is unmounted, for some reason.

When I try to mount it in Recovery Mode, I get a com.apple.DiskManagement.disenter (error 49217).
I can’t find anything very helpful online.

‘First Aid’ on ‘Container disk1’ fails with one or more volumes are mounted.
I can’t unmount √ because disk is in use.

‘First Aid’ on the OCZ-AGILITY drive itself is successful, with no problems.

I can’t reinstall Catalina (using the recovery menu), because You may not install to this volume because it is not mounted.

I have a newer 2020 Mac Mini M1, and a PC to try and sort this out.

How do you mount an unwilling drive?

Using external drives gives users many different ways to manage data. For example, it is easy and convenient to transfer, share, and backup files from your Mac with an external hard drive. But, you may encounter an issue when the disk is not mounting, and you can’t access your data. Find out what “com.apple.DiskManagement.disenter error 0” on Mac means and get working solutions to fix it for good.

Usually, external drives mount automatically when you connect them to your Mac. Once connected, you can see the disk on your Desktop and in Finder and can easily access its content. You can also mount the drive manually using Disk Utility. In most cases, this step is quick and easy. 

Unfortunately, sometimes you may end up getting the “com.apple.DiskManagement.disenter error 0” on your Mac. Instead of 0, you may see different numbers in the error message. For example, it can show “com.apple.DiskManagement.disenter error 49223” or “com.apple.DiskManagement.disenter error 49221” or something similar. All of these messages mean that there is an issue with macOS or that external hard drive. So due to that error message, your system can’t mount the drive and can’t access its content.

There are some basic steps to try before hopping on to more complicated instructions when fixing “com.apple.DiskManagement.disenter error 0” on Mac. For example, the error message could be caused by a temporary system glitch, and even a simple restart may fix the situation.

To restart Mac:

1. Click on the Apple sign at the top left corner of your screen.
2. Choose “Restart” in the drop-down menu.

If this didn’t help, make sure to check the formatting of your hard drive. This is especially relevant if you have previously used the drive on Windows on Linux machines. Not all file system formats are compatible with macOS. This means that Mac won’t be able to mound the disk and access its files. 

File system formats supported by macOS:

• APFS (for macOS 10.13 and higher)
• HFS+ (for macOS 10.12 and earlier)
• FAT
• exFAT
• NTFS (read-only)

You will need to reformat the drive if you identify that it is currently set up under a file system that is not supported by Mac.

Pro tip: Reformatting the hard drive erases all the data stored on it. Make sure to create a backup or use Stellar Data Recovery Software to easily restore any kind of lost files.

You may also get “com.apple.DiskManagement.disenter error 0” on Mac if you used it previously on Windows, even if the format is compatible. For example, this could happen due to the difference in the allocation unit sizes (block sizes) between Windows and Mac. 

4 Solutions to Fix “com.apple.DiskManagement.disenter error 0”

Restarting your Mac and checking the file format can be helpful, but it might not be enough in some cases. Move on to more advanced instructions, if the basic troubleshooting steps didn’t help with the “com.apple.DiskManagement.disenter error 0” on Mac. Below we provide four different methods to address the issue and get it fixed.

Solution 1: Check for Connectivity Problems

A proper physical connection of your external hard drive plays an important part in the mounting process. Make sure to check the cable and the correct work of the USB port before moving forward to the next steps. To do this, unplug and then plug back the drive. You can also try to connect it with a different cable or plug it into another USB port on your Mac. These easy tricks should help with the “com.apple.DiskManagement.disenter error 0” if the issue is related to connectivity problems. 

Solution 2: Use First Aid to Check for Errors

First Aid is a handy tool you can find in Disk Utility. It allows to check and repair system errors related to directory structure and formatting. It is recommended to run a First Aid scan when you encounter the “com.apple.DiskManagement.disenter error 0” error message in Disk Utility. 

To use First Aid: 

1. Open Disk Utility from Applications > Utilities.
2. Choose an unmounted drive from the list on the left. 
3. Click on First Aid and then click on Run.

Once the process is done, you can access a detailed report. Make sure to address the issues if First Aid finds any errors during the scan. 

Solution 3: Mount the Disk in Terminal

The Terminal app is a command line that allows you to control your Mac and perform various changes to your system. This powerful tool allows you to access any macOS settings and run commands with administrative privileges. So you might be able to mount the disk with Terminal even when you see “com.apple.DiskManagement.disenter error 0” in Disk Utility. 

To mount the disk in Terminal:

1. Open the Terminal app. 
2. Type diskutil list to see all drives that are connected to Mac. 
3. Type diskutil mount /dev/disk1s2 and press Return.

Make sure to replace disk1s2 with the name of the unmountable drive. You can find out its name in the Identifier column by running the first command.

Solution 4: Reformat the Unmountable Disk

Reformatting the hard drive is the last step you should try, if nothing else works to fix “com.apple.DiskManagement.disenter error 0”. Reformatting helps with most disk problems as it erases everything on it and makes it as brand new. The downside of this solution is that you also lose all the data stored on it. 

Use a reliable recovery tool to prevent data loss on your external hard drive. With the help of Stellar Data Recovery Software, you can restore files from inaccessible, unmounted, and even damaged drives. Using the software before performing reformatting is recommended to make sure all your files are safe. But the advantage of Stellar Data Recovery is that you can recover files even if you have already formatted the drive.

Conclusion

Getting “com.apple.DiskManagement.disenter error 0” can become an unexpected bombshell when you are trying to mount the drive in Disk Utility. But it shouldn’t become a reason to stop you from using your external storage. With a few simple solutions provided in this article, you should be able to mount the disk and access its content back again. 

Read more articles:

• Fix the “Disk Utility’s First Aid Repairing Process has Failed” Error
• macOS Recovery Mode and How to Use it

Catalina update messed up my external hard drive. I now have a half-encrypted APFS partition with more than 20 years of all my data archives, and it won’t mount. Please help!

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

$ 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)

$ 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)

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

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.

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

Hello everyone,

I’m having a little issue with mounting my external hard drive lately. I’ve tried quite a few methods in hope of getting it to work again, but so far, no luck. I hope someone can help me solve this issue, or those who have the same problem may also share your insights.

My external hard drive was working fine about a week ago. But one day, I ejected the hard drive and the icon disappeared, so I thought it was safe to unplug it. When I did, it said the hard drive was not properly removed. It still works fine when I use it the next day, but the same thing happened. It said the drive was not properly removed after I ejected the drive, waited for the icon to disappear, and then unplugged the drive. After that, it never works again, and the attached images are the info I got when I tried to mount or run first aid on this drive.

Please help & thank you in advance!

Computer: 27″ iMac — MacOS Monterey

External Hard Drive: WD_Black 4TB. APFS encrypted