Com apple diskmanagement disenter ошибка 49223

В этом руководстве мы покажем вам различные способы исправления ошибки Diskmanagement.disenter с кодами ошибок 119930868, 119930872, 49218, 49223, 0 и т. д. Многие пользователи выразили обеспокоенность тем, что не могут подключить внешние жесткие диски к своему Mac. . Эта проблема не зависит от ОС, о ней сообщалось в Big Sur, Monterey и даже Ventura.

Ошибка Mac Diskmanagement.disenter

Всякий раз, когда они пытаются смонтировать диск с помощью Дисковой утилиты, они приветствовал с ошибкой Diskmanagement.disenter вместе с одним из следующих кодов ошибок 119930868, 119930872, 49218, 49223, 0 и т. д. Невозможность доступа пользователей к данным на отключенном внешнем жестком диске доставляет им массу неудобств. Если вы тоже находитесь в одной лодке, то это руководство поможет вам. Следите за исправлениями.

Ошибка Mac Diskmanagement.disenter

Рекомендуется попробовать каждый из нижеперечисленных обходных путей, а затем посмотреть, какой из них приводит к успеху. Итак, имея это в виду, давайте начнем. Droidwin и его участники не будут нести ответственность в случае термоядерной войны, если ваш будильник не разбудит вас, или если что-то случится с вашим Mac и данными, выполнив следующие шаги.

ИСПРАВЛЕНИЕ 1. Завершение процесса fsck

Одна из наиболее распространенных причин этой ошибки может быть связана с тем, что «fsck» может держать ее в заложниках. Поэтому вам придется убить этот процесс и повторить попытку монтирования диска. Вот как это можно сделать:

  1. Для начала запустите Терминал и Дисковую утилиту.
  2. Затем попробуйте смонтировать диск и сразу переключитесь на Терминал.
  3. Теперь выполните следующую команду в окне терминала: sudo pkill -f fsck
  4. Диск смонтируется в режиме только для чтения. Теперь вы можете восстановить его с помощью программы «Первая помощь» в Дисковой утилите.
  5. Ремонт займет время. После этого это должно исправить ошибку Diskmanagement.disenter.

ИСПРАВЛЕНИЕ 2: использование терминала

  1. Для начала загрузите Mac в режим восстановления, как указано ниже: Apple Silicon: нажмите и удерживайте кнопку питания, пока не появится «Загрузка параметров запуска». Затем выберите Функции > Продолжить. Intel: перезагрузите Mac и одновременно нажмите и удерживайте сочетание клавиш Command+R.
  2. Затем нажмите «Утилиты» и выберите «Терминал». Теперь введите следующую команду: diskutil list

    Ошибка Mac Diskmanagement.disenter

  3. Появится список всех дисков. Запишите идентификатор тома вашего диска [such as disk3s1].
  4. Наконец, выполните приведенную ниже команду [replace diskX with your volume identifier].diskutil repairVolume/diskX
  5. Проверьте, исправляет ли он ошибку Diskmanagement.disenter 119930868, 119930872, 49218, 49223, 0.

ИСПРАВЛЕНИЕ 3. Изменение размера выделяемого диска

Некоторые старые Mac не смогут смонтировать диск, если размер выделения больше 1024. Поэтому, чтобы решить эту проблему, перейдите на компьютер с Windows или Linux (или используйте виртуальную машину) и переформатируйте диск в ExFAT и выберите 1024 как размер выделения. Теперь попробуйте установить его на свой Mac, и на этот раз вы не получите никаких кодов ошибок.

Вот и все. Это были три метода, которые должны помочь вам исправить ошибку Diskmanagement.disenter с кодами ошибок 119930868, 119930872, 49218, 49223, 0 и т. д. Если у вас есть какие-либо вопросы относительно вышеупомянутых шагов, сообщите нам об этом в комментариях. Мы вернемся к вам с решением в ближайшее время.

О главном редакторе

Looks like no one’s replied in a while. To start the conversation again, simply

ask a new question.

Could not mount “Seagate”. (com.apple.DiskManagement.disenter error 49223.) message

Im new with MacBooks so thank you for any help. Im trying to mount my hard drive but I’m getting this message- Could not mount “Seagate”. (com.apple.DiskManagement.disenter error 49223.)

I ran the first aid in the disk utilities and it runs and says operation successful. But it still won’t mount.

MacBook Air 13″,

macOS 10.15

Posted on Oct 27, 2019 11:49 AM

Similar questions

  • Could not mount Seagate4 : ( com.apple.DiskManagement.disenter error 0. )
    I too am getting the window: Could not mount
    «Seagate 4 Drive»
    ( com.apple.DiskManagement.disenter error 0. )

    Anyone find out a solution ? Thanks !!

    [Email Edited by Moderator]

    271
    3

  • can’t mount external hard disk or usb drive
    This is the error message when I clicked ‘mount’ in the disk utility, hope someone could help.
    Could not mount “Ted_16”. (com.apple.DiskManagement.disenter error -119930872.)

    On another macbook, the same disk works, so i am sure it’s not the disk itself that has the issue.
    I have tried run first aid, still cannot mount. then, I erased it, still got the same error message.

    752
    4

  • External hard drive won’t mount after power blip
    After a momentary power interruption this morning, my external hard drive (on which I have a Time Machine backup) does not mount and does not appear in Finder. (It is a LaCie 2TB USB drive.) The device is recognized in System Information and Disk Utility, but an attempt to mount it in Disk Utility returns this error message:

    Could not mount “disk2s2”. (com.apple.DiskManagement.disenter error -119930868.)

    I have tried First Aid in Disk Utility but it fails. Restarting the computer did not help either.

    I have a Mac Mini (Late 2014) running MacOS Big Sur Ver. 11.6.2.

    Any suggestions would be appreciated. Thank you!

    966
    4

1 reply


Question marked as

Helpful

Dec 29, 2019 12:09 PM in response to Krakalaka

My 5 TB external harddrive is powered via external power supply and the Mac can’t use it, so I assume Mac and harddvie are just not working together for an unknown reason.

30 replies

Dec 21, 2019 11:45 AM in response to unnsteinngardars

unnsteinngardars wrote:

It is not a Catalina thing, I have a Seagate Backup Plus Hub drive that was formatted as exFAT on a windows computer and will not mount on a mac and gives me the exact same error as this thread. And it started to happen on my mac before Catalina and also was an issue on another mac with a mac os Sierra.

Windows can format the drive using different block sizes some of which macOS does not recognize. Backup any files on this drive and use the Mac’s Disk Utility to erase the drive as GUID partition and ExFAT. You need to erase the physical drive so you may need to click on «View» within Disk Utility and select «Show all devices» before the physical drive appears in the left pane of Disk Utility. This should allow the drive to be used on both Windows & Mac.

When you say Seagate Software, are you referring to the Paragon or something else?

I’ve never used the Seagate external drives or their proprietary software, so I am not sure what is included. Did you run a Seagate app which was included on or with the drive? If so uninstall it using the included uninstaller or by following Seagate’s instructions. I know Paragon software is sometimes included with the Seagate software to allow writing to NTFS volumes.

If you downloaded the Paragon software separately, then yes uninstall it according to the developer’s instructions since it is not needed on a Mac unless you need to write to an NTFS volume or access a Linux file system.

Dec 23, 2019 8:59 AM in response to HWTech

Yes I was referring to paragon software. Here’s what I know:

  1. I have a seagate drive I’ve used for a few years now. When I bought it, it would only mount as read-only on my Mac. I installed the Paragon software and it worked fine after that.
  2. I have backed up 100+ GB of data to that drive over those years
  3. I updated to Catalina. The seagate drive would no longer work, mounting as read-only. I updated the Paragon software and the drive worked fine. Just as before, I don’t have to do anything, as it mounts automatically when I plug it into my mac.

It continues to work fine now. I understand from other posts that this won’t work for everyone, but I can’t comment on those posts. I’m just passing on what I did. I don’t worry about disk formats or Mac vs. PC, I’m just a guy using a disk drive for backups.

-dave

Dec 23, 2019 1:42 PM in response to dchura7734

dchura7734 wrote:

1. Yes I was referring to paragon software. Here’s what I know:

I have a seagate drive I’ve used for a few years now. When I bought it, it would only mount as read-only on my Mac. I installed the Paragon software and it worked fine after that.

2. I have backed up 100+ GB of data to that drive over those years

3. I updated to Catalina. The seagate drive would no longer work, mounting as read-only. I updated the Paragon software and the drive worked fine. Just as before, I don’t have to do anything, as it mounts automatically when I plug it into my mac.

It continues to work fine now. I understand from other posts that this won’t work for everyone, but I can’t comment on those posts. I’m just passing on what I did. I don’t worry about disk formats or Mac vs. PC, I’m just a guy using a disk drive for backups.

-dave

Unless you are using an external drive for access with both Mac & Windows you should always use macOS Disk Utility to erase the drive as GUID partition and MacOS Extended (Journaled) so that only macOS is managing the drive using a native macOS file system. If a drive needs to be shared between Mac & Windows, then erasing the drive as ExFAT on a Mac using Disk Utility is an acceptable alternative since both macOS & Windows support read+write ExFAT file system (it must be erased on a Mac since Windows may format ExFAT with options currently incompatible with macOS).

Third party software is not needed to use an external drive on a Mac unless you want to use the built-in hardware encryption feature found on some external SSD drives. Third party software usually ends up causing issues at some point, but especially during system updates or upgrades. Plus access to the drive may become lost if the proprietary third party software is no longer supported.

Unfortunately this is a Windows only world when it comes to third party hardware so hardware manufacturers default everything to work with a Windows system which means many external drives are shipped using the Windows NTFS file system. It is always best to use the operating system’s built-in native file systems whenever possible to reduce the risk of problems and compatibility issues.

Just something to consider and I hope this information may help others.

Dec 26, 2019 9:39 AM in response to HWTech

Yep I agree its lousy advice. I guess some people should think before offering any advice and consider whether their advice is actually helpful.

Dec 28, 2019 12:26 PM in response to Krakalaka

I have read the whole thread and now concluded this is on Apple, not Seagate.

I bought the Seagate drive before Catalina. After installing the Paragon driver, from Seagate, everything worked. When I upgraded to Catalina, I needed to install a newer version (64-bit). Then it continued to work. A week ago, it stopped working on one of my computers. But it continued to work on the other. Before I triage, the other computer auto-upgraded itself to a newer Catalina. Now both computers stopped working for the drive.

I uninstalled Seagate’s paragon driver, the disk mounts but read-only. I reinstalled the previously working driver (same version) and the problem reproduced.

I guess Apple may claim the Paragon driver is now incompatible with one of the later Catalina patches and I will accept that. The point is still that Apple’s patch broke the driver, not the other way around.

I now have a 5TB drive that is basically useless.

Guess Seagate, Paragon, or Apple need to do something.

[Edited by Moderator]

Dec 28, 2019 8:13 PM in response to sin-yaw

sin-yaw wrote:

I have read the whole thread and now concluded this is on Apple, not Seagate.

I bought the Seagate drive before Catalina. After installing the Paragon driver, from Seagate, everything worked. When I upgraded to Catalina, I needed to install a newer version (64-bit). Then it continued to work. A week ago, it stopped working on one of my computers. But it continued to work on the other. Before I triage, the other computer auto-upgraded itself to a newer Catalina. Now both computers stopped working for the drive.

I uninstalled Seagate’s paragon driver, the disk mounts but read-only. I reinstalled the previously working driver (same version) and the problem reproduced.

I guess Apple may claim the Paragon driver is now incompatible with one of the later Catalina patches and I will accept that. The point is still that Apple’s patch broke the driver, not the other way around.

I now have a 5TB drive that is basically useless.

Guess Seagate, Paragon, or Apple need to do something.

[Edited by Moderator]

And so many other users in this thread have blasted me for recommending people not to use the proprietary software which ships with external drives! Seems I might know what I’m talking about!

You cannot expect Apple to make sure every piece of third party software works in macOS. It is up to the hardware manufacturers to update their third party software. It is the way it has ALWAYS been. It is the same for Windows & Linux systems as well. If you have an issue with a third party app provided by the drive manufacturer, then contact the manufacturer of your external drive for support and to complain about not having a timely software update to the app.

You do have options here. You can report the issue to Seagate and wait for an update to their app. Or you can transfer everything from the now read-only external drive to another drive or computer. Then erase the external drive using Disk Utility. Erase the drive as GUID partition and MacOS Extended (Journaled) if you will only be using it on Macs. Or if you will be using the drive with Windows as well, then erase it as GUID partition and exFAT using Disk Utility. If you erase it as exFAT on Windows, then macOS may not be able to read the drive. Once the external drive has been erased using Disk Utility, then you can transfer all the files back to the external drive.

Dec 28, 2019 8:36 PM in response to HWTech

stay friendly, be happy. we are not in the 1980’s anymore where any manufacturer made his own thing and almost nothing did fit well together. I personally refuse to use third party tools only to access well known, simple devices. to buy any harddrive in the next shop and use it without trouble should be no magic anymore today. not even when using an apple computer …

Dec 28, 2019 10:12 PM in response to HWTech

I have been an OS developers for decades and, in general, agree with you that the manufacturer must ultimately bear the responsibility to make things work.

In this case, however, it was working and got broken by a minor OS patch. Therefore, the patch failed the regression tests against the vendors.

Nearly all OS vendors maintain a large lab and developed a comprehensive regression test suite to prevent things like this from happening. Simply, what was working should continue so. Either Apple did not find such failure, didn’t warn Seagate on this failure, or expect a different relationship than what us customers expect. Probably Apple expects Seagate to test against all patches on its own and remedy any issue. From what I read from Seagate’s website, they appeared completely oblivious to this failure.

Apple must manage its ecosystem as a platform vendor. Your reply basically stated that Apple bears no responsibility. It’s either Seagate’s or customer’s problem. That attitude is really disappointing.

The industry is saying that «Apple is becoming Microsoft faster than Microsoft becoming Apple.» Remember that consumers have choices. Being arrogant will hurt you.

Dec 28, 2019 10:18 PM in response to HWTech

Just search this error message on the internet and count how many customers encountered the same problem. This is not isolated to Seagate. Catalina is not reliable. Fix it.

Dec 29, 2019 4:49 AM in response to HWTech

Thank you for all of your replies to my question. Here is a bit more updated information on my situation.

I have 2 external hard drives that are formatted the same. They both work when connected to my windows computer. The Samsung 1tb hd works when I connect to my Mac and it is powered by a wall plug. The seagate 6tb hd shows up but won’t mount, I can verify it using paragon software and is powered by the usb cable. I’ve tried using paragon software(old version/updated version), it still didn’t work.

I have both hard drives full so I can’t just reformat the seagate. Is there any chance that it could be because the hard drive isn’t getting enough power from the Mac book? Or does the seagate hd and Mac just not play nice together?


Question marked as

Helpful

Dec 29, 2019 12:09 PM in response to Krakalaka

My 5 TB external harddrive is powered via external power supply and the Mac can’t use it, so I assume Mac and harddvie are just not working together for an unknown reason.

Dec 29, 2019 4:19 PM in response to Krakalaka

Krakalaka wrote:

I have 2 external hard drives that are formatted the same. They both work when connected to my windows computer. The Samsung 1tb hd works when I connect to my Mac and it is powered by a wall plug. The seagate 6tb hd shows up but won’t mount, I can verify it using paragon software and is powered by the usb cable. I’ve tried using paragon software(old version/updated version), it still didn’t work.

That is one of the dangers of using a non-native macOS file system and relying on third party software to manage the drive. You may need to contact Seagate for support.

What file system is used on your 6TB drive? macOS should be able to mount an NTFS file system in read-only mode. If the drive is formatted as exFAT, then the exFAT format may be using block sizes which macOS cannot understand. To use an exFAT drive with both Mac & Windows you need to format the drive on the Mac using Disk Utility.

I have both hard drives full so I can’t just reformat the seagate. Is there any chance that it could be because the hard drive isn’t getting enough power from the Mac book? Or does the seagate hd and Mac just not play nice together?

Try using a powered USB3 hub with UASP support to connect the hard drive. This may help provide any extra power plus it will act as a buffer between the devices. Does the 6TB drive come with its own power supply or special double USB cable/dongle? Years ago I did encounter a drive enclosure which would not work on a Mac, so there is always a possibility of hardware incompatibility, but by using third party software the situation becomes more complicated. I think a 6TB drive will need extra power to work either with a double USB connector or its own power adapter.

Have you disconnected all other external devices from your Mac when trying to access the 6TB drive? Is your laptop using its power adapter?

Have you tried booting into Safe Mode to see if the 6TB drive can be mounted as read-only if it is formatted as NTFS?

Has this 6TB drive ever worked on this Mac? Do you see the drive (or the drive’s controller) show up under the USB section of the Apple System Profiler? You can access this by Option-clicking on the Apple menu and selecting the first option (System Information?).

Maybe your drive is physically failing. You may be able to check the health of the external hard drive on Windows by using GSmartControl (portable app available requiring no installation). GSmartControl also has a method to run a drive’s internal self diagnostics. There is no guarantee this information can be accessed since some external drive’s USB controllers block the necessary communication. Maybe your Seagate software on Windows can access this information or even test the physical drive. Feel free to post the GSmartControl report for the drive here using the «Additional Text» icon which looks like a piece of paper.

If the external drives are not backup drives, then I hope you have backup copies of all the data stored on your external drives.

Dec 29, 2019 4:26 PM in response to HWTech

I think we have already clarified that this issue is not related to third party tools and also appears when you are not using them. I haven’t expected there to be that much guys defending Apple at all cost by lacking any helpful information why in nearly 2020 a harddrive bought in the next store should not be able to be used without any hassle with any modern operating system.

Dec 29, 2019 5:33 PM in response to Imobisac

Imobisac wrote:

I think we have already clarified that this issue is not related to third party tools and also appears when you are not using them. I haven’t expected there to be that much guys defending Apple at all cost by lacking any helpful information why in nearly 2020 a harddrive bought in the next store should not be able to be used without any hassle with any modern operating system.

I am far from an Apple fan. I’ve been strongly opposed to the direction Apple has been going for years now and yes Apple does make some pretty stupid decisions. I personally do not purchase Apple’s computers, but am forced to use them for work. Apple is really a closed system where you do it Apple’s way or you will experience difficulties. Same thing if you do something which Apple did expect.

If you search these forums you will see so many threads where updating or removing third party drive management software solved so many of the users’ external hard drive problems.

Yes there can be hardware incompatibilities, but it is hard to identify the hardware issues when some people are unable to erase the drive to test without the third party software being involved. Some of the users posting here with problems may need to contact a local Apple hardware expert to physically examine their computer & drives to see what the source of their individual problem is. You also never get the complete story or system setup from people posting here so we are always working with incomplete information and many unknowns so there could be other factors involved such as security or AV software, etc. Like I said in my last post a 5TB+ drive may require extra power.

Many hardware vendors only pay lip service to macOS compatibility because unfortunately we live in a Windows centric world which is why most of these drives come pre-formatted for Windows with NTFS. Like Linux users Mac users need to research products and carefully choose & configure those products. Mac users do need to understand the hardware more than their Windows counterparts because a Mac user usually needs to do more to make hardware work properly. Mac users do have an option of purchasing guaranteed & tested products from an Apple friendly vendor such as OWC. If Mac users purchase off the shelf items at a regular store, then the Mac user will need to deal with possible incompatibilities. You know nothing of compatibility issues until you try to find Linux compatible hardware or Linux compatible firmware updaters. While Mac users are second class citizens in the tech world, Linux users are treated like the plague by hardware manufacturers. I agree it would be so nice if everyone would agree to standards and then properly implement those standards, but everyone including Apple takes shortcuts.

Dec 29, 2019 5:39 PM in response to HWTech

I was lucky and able to store my backup somewehre else so I connected my 5 TB harddrive with the Mac and made it ExFAT GUID. The harddrive itself is brand new and working okay on both Windows and Mac this way. Nethertheless I remember «strange» things like going into the next shop and find «special» hardware like harddrives with a MacOS compatible sign attached to. For those who are not too familar with re-formatting/partitioning that thing themself. ^^

Could not mount “Seagate”. (com.apple.DiskManagement.disenter error 49223.) message

Many users have been voicing their concern that they aren’t able to mount their external hard drives to their Mac. This issue comes independent of the OS and has been reported across Monterey, Big Sur, and even Ventura. When the user are trying the mount the disk using the Disk Utility, they’re getting the Mac Diskmanagement.Disenter Error with one of these error codes – 119930868, 49218, 119930872, 49223, 0, etc.

Follow us on Telegram

The inability to access data on the unmounted external hard drive has been causing a great deal of inconvenience to the users. If you’re in the same boat, then this guide will be of great help to you. In this guide, you will get to know how to fix Diskmanagement.Disenter Enter 119930868, 49218, 49223, 0, etc.

Mac users have reported encountering the com.apple.DiskManagement.disenter error -119930868 when attempting to mount their Macintosh HD (disk0s2) in Disk Utility after upgrading to macOS Big Sur. This error prevents access to the drive, causing significant issues for those who have installed macOS on that drive. This error is not new, but its recent occurrence suggests a connection to the Big Sur upgrade. The causes and solutions for this error are not specified in the given text.

Method 1: Kill the fsck process

Fix Mac Diskmanagement.Disenter Error 119930868, 49218, 49223

  • To start off, launch Terminal and Disc Utility
  • After that, try to mount the disk and straightaway switch to Terminal
  • Then, execute the following command in the terminal window –

sudo pkill –f fsck

  • The disk will now mount in read-only mode
  • You can now repair it by using First Aid in Disk Utility
  • Wait patiently as repairing could take time
  • Once it is done, it will fix the errors

Method 2: By using Terminal

  • To start off, boot your Mac to Recovery Mode
  • Press and hold the power button until the Loading Startup Options appear -> Select Options -> Continue
  • After that, click Utilities and choose Terminal
  • Type in the following command –
diskutil list
  • It’ll bring a list of all disks
  • Note down the disk’s volume identifier
  • Lastly, execute the following command (replace diskX with the volume identifier that you noted above)
diskutil repairVolume/diskX

Method 3: Make changes to the Disk Allocation Size

Some older Macs will struggle to mount the drive if the allocation size is larger than 1024. For resolving this, you should head over to a Windows or Linux machine and reformat the drive in ExFAT. Then, choose “1024” as the allocation size. Now, you should try to mount it on your Mac and this time, you won’t be getting any error codes.

Conclusion

In short, the com.apple.DiskManagement.disenter error can be a frustrating problem for Mac users who have upgraded to MacOS Big Sur. Although the causes of the error are not specified, there are possible solutions that can be tried before resorting to wiping the drive and reinstalling MacOS. If all other options have been exhausted and there is no important data on the drive, or it has been successfully recovered, wiping and reinstalling MacOS in recovery mode may be the most effective solution. Remember to always back up your data before attempting any troubleshooting steps. Thank you for reading this guide, and please feel free to share your thoughts and experiences in the comment section down below the article.

Aviral Sharma

Aviral Sharma is a talented and passionate writer who has been using words to express his thoughts ever since he learnt how to hold a pen. He is passionate about outer space, history, sports and most importantly technology. Aviral is a regular writer for rootmygalaxy.net and has been getting better by the day.

I have created a Bootcamp partition but when I try to mount it using Disk Utility I get the following error «Could not mount “BOOTCAMP”. (com.apple.DiskManagement.disenter error 49223.)

I am using Parallels and it fails to start the VM and I believe that this is the reason

Currently, I use build 19A501i

Any help, would be greatly appreciated

Replies

Today I installed build 19A512f

By default the Bootcamp partition is not mounted

When I try to run Parallels desktop 14.1.3 it just crashes

With Disk Utility I mount the Bootcamp volume and it mounts Ok

I run again Parallels desktop 14.1.3 and it crashes again and bootcamp is now unmounted

By removing and reinstalling Parallels the issue was solved

Try checking /Library/Filesystems for any leftover files from other NTFS applications. I solved mine by deleting .fs file from iboysoft after I uninstalled the NTFS software.

Contents

  • What Is “com.apple.DiskManagement.disenter Error 0”? 
  • Steps before Fixing “com.apple.DiskManagement.disenter Error 0”
  • 4 Solutions to Fix “com.apple.DiskManagement.disenter error 0”
  • Conclusion

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.
Apple Logo > Restart Mac
Apple Logo > Restart Mac

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.
Disk Utility > Run First Aid
Disk Utility > Run First Aid

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.
Terminal > type diskutil mount /dev/disk1s2
Terminal > type diskutil mount /dev/disk1s2

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.

Stellar Data Recovery > Select What To Recover
Stellar Data Recovery > Select What To Recover

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

About The Author

Ruslana Lishchuk

Ruslana is a tech content writer whose true passion is finding out about everything Mac-related. She specializes in creating macOS guides and tips & tricks. In her spare time, you’ll find her doing yoga or discovering local coffee shops in search of the best filter coffee.

com.apple.diskmanagement.disenter error

Ruslana Lishchuk

Ruslana is a tech content writer whose true passion is finding out about everything Mac-related. She specializes in creating macOS guides and tips & tricks. In her spare time, you’ll find her doing yoga or discovering local coffee shops in search of the best filter coffee.

Did you get a com.apple.diskmanagement.disenter error when you tried to mount your external hard drive on Mac? This indicates a problem with either your external hard drive or macOS. Unfortunately, either case may lead to data loss – but don’t lose hope!

In this article, we’ll explore the possible reasons we encounter DiskManagement Distenter 49135 and how to fix it (without losing your data), as well as other common disk errors. Read on.
Need to recover data from the drive? Go to data recovery section ⤵

When you plug in your external hard drive, the system mounts it and makes its contents viewable in Finder. If it doesn’t show up there, you should still see it in Disk Utility (Finder > Applications > Utilities) where you can also attempt to mount it.

But there are cases when your external hard drive won’t mount, even using Disk Utility. In this scenario, you’ll probably encounter an error that says “Could not mount *name of the drive*”(com.apple.DiskManagement.disenter error 49513).

Several factors could lead to this problem. You may have an incompatible file system. Or, you may be using a Mac Superdrive while running macOS Catalina. Beyond those common reasons, error 49153 may occur simply due to malware, bugs, issues while resizing partitions and interference from local Time Machine backups.

Don’t worry – we’ll show you how to get rid of this pesky error in the next section.

How to Fix com.apple.diskmanagement.disenter error 49153?

There are several ways to address this specific error code, but most fixes can potentially harm your data. We suggest opening your external hard drive in read only mode and copying your files to a separate storage device or to the cloud.

To set your drive to read only mode, right-click your drive > Get Info and scroll down to Sharing and Permissions. Set your user’s privilege to Read only.

Method #1: Connect Your Drive to Another Mac

Disk Utility errors can be caused by either your drive or your Mac. To figure out which methods to try first, connect your drive to another Mac or even a PC. If your drive doesn’t work on other machines, then the problem likely lies with your drive.

If it works on another Mac, then your Mac might be experiencing glitches due to a faulty update or other issue. If it works on a PC, then it’s likely a formatting problem – we wrote more about that in the section of this article that covers other common DiskManagement Disenter errors.

Method #2: Restart your Mac

A temporary bug or glitch may have simply gotten macOS stuck while it attempted to recognize your drive. You may also have a lot of apps running in the background using up the resources macOS needs to properly recognize and mount your drive.

To get your system going, a simple restart might solve the problem. This will automatically close all running apps and reboot the operating system.

Method #3: Use First Aid in Disk Utility

First Aid is a useful tool that finds and repairs disk errors – specifically, it scans the drive and its partitions for issues related to its structure and formatting. These may prevent your drive from properly mounting.

Fortunately, First Aid is a feature of the Disk Utility app, which can recognize unmountable drives or partitions. To repair your drive using First Aid:

Step 1.Launch Disk Utility (Finder > Applications > Utilities).Disk utility icon in Finder

Step 2.Select your drive from the left sidebar, then click the First Aid button at the top of the window.First aid icon in Disk Utility

Step 3.In the dialogue box that appears, click Run.Run button in Disk Utility dialog

Step 4.Wait for the process to finish. Then, manually mount your hard drive in Disk Utility by selecting your drive or volume in the left sidebar and clicking the Mount button.Mount button in Disk Utility

Method #4: Use the fsck Command in Single User Mode

Your external hard drive may not be mounting because of a file system issue. To resolve this problem, you can use Mac’s File System Check command or FSCK through Single User Mode. Here’s how:

Step 1.Enter Single User Mode. To do so, restart your Mac. As soon as it starts to reboot, press and hold the Power button and the CMD + S keys at the same time.

Step 2.You’ll know that you’ve successfully booted into Single User Mode when you see a window that looks like the Terminal app. Once the white text stops appearing, type the following command and hit Return.

/sbin/fsck -fy

Step 3.Once the process is complete, type reboot. This will command your Mac to restart itself.

If you remove your hard drive before ejecting it from Mac, fsck will automatically scan and repair it the next time you use it. This could potentially take a long time, which makes your drive unmountable. To deal with this, force quit the fsck command (Open the Activity Monitor > search fsck > click the x button).

Method #5: Disable Time Machine

Time Machine is a Mac built-in tool that regularly backs up your data, usually automatically. It works well, but on bad days, it can cause the operating system to get stuck while preparing your backup drive. Try disabling Time Machine to free your drive from this process and hopefully allow it to get mounted.

To disable Time Machine, open its settings window by launching System Preferences > Time Machine.

Time machine icon in System Preferences window

Then, untick the box beside the Back Up Automatically setting.Back up automatically button in Time Machine

Method #6: Delete Time Machine snapshots using Terminal

Deleting Time Machine snapshots from your Mac may also resolve this disk utility error. Learn how to do it using the Terminal app by following the steps below:

Step 1.Launch Terminal (Finder > Applications > Utilities > Terminal).Terminal app in Finder

Step 2.The first command we’ll execute will list all locally stored Time Machine snapshots. Type the following command and hit Return:

Tmutil listlocalsnapshots /

listlocalsnapshots command in Terminal

Step 3.Type the following command and hit Return:

Tmutil thinlocalsnapshots /99999999999999

thinlocalsnapshots command in Terminal

Step 4.Keep using the tmutil listlocalsnaphots and tmutil thinlocalsnapshots commands to make sure you delete all your snapshots.

Method #7: Format Your Drive

If all the above methods failed to get rid of the disk errors, your last resort is to format the drive. As we’ve already discussed earlier, formatting your drive will wipe the disk – including errors, viruses, corruption, and unfortunately, your data. We suggest copying your files to a secure location first.

To transfer your files safely, set your drive to read only mode first. To do this, read our pro tip in the introduction of this section.

Fortunately, formatting your drive on Mac is very easy thanks to the Disk Utility app. First, launch Disk Utility (Finder > Applications) and select your drive from the left sidebar. Then, click the Erase button on the top of the window.Erase button in disk utility window

In the dialogue box that appears, name your drive and select a format. If you will only be using your drive with Mac computers, choose APFS. Otherwise, we suggest exFAT for maximum compatibility. Select GUID Partition Map for its scheme, then click Erase to proceed with the format.Erase dialog in Disk Utility

Other Types of DiskManagement Disenter Error

Aside from DiskManagement Disenter Error 49153, there are other DiskManagement Disenter errors that you may encounter that are represented by different codes. Below, we’ve listed the most common ones along with their solutions:

  • DiskManagement Disenter Error 49223. An exFAT hard drive that’s been formatted using Windows can cause this error when connected to a Mac, as macOS doesn’t support all the storage block sizes available on Windows. This incompatibility makes MacOS unable to recognize and mount the drive.If you want to use this drive on both Mac and Windows, you need to format it using Mac (but first, back up your data!). If you intend to use it solely on Mac, we suggest formatting it to Apple-based APFS.
  • DiskManagement Disenter Error 49221.This error is caused by a glitch in the security updates 2021-003 and 2022-003. After the update, you’ve probably tried to mount a NTFS hard drive in Disk Utility when you got this error. To fix this, reinstall macOS or use a third-party software to mount your NTFS drive.
  • DiskManagement Disenter Error 49244. This error often appears when you try to mount your hard drive in Disk Utility while running macOS Catalina. You can use third-party software to mount your drive. If that doesn’t work, you need to format your drive to APFS (again, don’t forget to create a backup!).
  • DiskManagement Disenter Error 49218. You might get this error when you remove a hard drive without proper ejection while using macOS Monterey. This error may also be caused by bugs from macOS Monterey itself.To fix it, (1) execute the sudo pkill -f command in the Terminal app, (2) execute the fsck /dev/disk_user_id/ command in single user mode, and finally (3) execute the mount -f /dev/disk_user_id/ command. Remember to replace “disk_user_id” with your disk’s identifier (diskutil list). To boot into single user mode, follow the first instruction in Method #4. If your drive still fails to work after this fix, you may need to format it.
  • DiskManagement Disenter Error 49180. This error occurs when there’s a raw partition on the drive, which can happen if you connect an APFS drive to an old Mac or if something went wrong while you were shrinking your partition. You have two ways to address this error: (1) resize the external hard drive using Terminal or (2) format the hard drive altogether.

What to Do If You’d Lost Data After DiskManagement Disenter Error?

Disk Utility errors always have the potential to cause data loss and there’s no guarantee that your files will remain intact after fixing them. The safest and most efficient way to restore data caused by disk errors is to use data recovery software.

Data recovery software can restore files regardless of format – it will even work if you decided to format your drive due to the errors. For this article, we’ll be using a tool called Disk Drill. It’s easy to use and works with most disk formats, and it can restore data even from non-mounting drives. Here’s how to use it:

Disk Drill Basic for Mac does not offer free recovery. However, you can back up and preview your files for free. There are free data recovery solutions available on the internet, but they each have their own limitations – your mileage may vary.

Step 1.Download and install Disk Drill for Mac.

Step 2.Launch Disk Drill (Finder > Applications > Disk Drill).

Disk Drill in Finder

Step 3.Select your drive from the middle pane and click Search for lost data.Drive selection window in Disk Drill

Step 4.Wait for the scan to finish, then click Review found items.scan results in disk drill

Step 5.Use the search bar to filter the results by name or by file extension, or use the left sidebar. You can also hover your mouse pointer beside any file to enable preview.Preview window in Disk Drill

Step 6.Use the boxes in the left-most column to select the files you want to restore, then click Recover.file selection window in Disk Drill

Step 7.Select a location on your non-malfunctioning drive to save the recovered files. Then, click OK.destination folder selection dialog in disk drill

Conclusion

Bluntly, disk utility errors are inevitable. Buggy system updates, improper ejection, power surges, and other factors beyond the user’s control can cause one or multiple disk errors. Not only can these errors cause data loss by themselves, but the process of actually fixing them can also harm your files. The best you can do is to routinely back up your files to avoid the worst consequences of these errors.

Если ваш Macintosh HD (disk0s2) не может быть смонтирован с помощью Дисковой утилиты, это означает, что где-то что-то не так и ваш Mac не включается. Несколько пользователей Mac, которые обновились до macOS Big Sur, жаловались на получение ошибки com.apple.DiskManagement.disenter -119930868 при установке своих жестких дисков. Невозможность смонтировать свои диски означает невозможность доступа к этому диску. Это создает огромную проблему, особенно для тех, кто решил установить macOS на этот диск.

com.apple.DiskManagement.disenter error -119930868 не является новой ошибкой, потому что пользователи Mac также сталкивались с ней в более ранних версиях macOS. Однако появление этой ошибки на этот раз означает, что она связана с недавним обновлением до macOS Big Sur.

Что вызывает ошибку com.apple.DiskManagement.disenter -119930868 и как успешно смонтировать ехать без этой ошибки? Если вас интересуют эти вопросы, читайте дальше, чтобы узнать больше.

Что такое Com.apple.DiskManagement.disenter Ошибка -119930868?

Когда вы подключаете внешний жесткий диск к Mac, он обычно отображается на рабочем столе, в Finder и в Дисковой утилите. Но бывают случаи, когда внешний диск не отображается ни в одном из этих мест, и данные на немонтируемом внешнем жестком диске становятся недоступными. Когда пользователи сталкиваются с этой проблемой, самый простой способ решить эту проблему — установить диск вручную. К сожалению, несколько пользователей сообщали об ошибке com.apple.DiskManagement.disenter -119930868 всякий раз, когда они пытались подключить внешний диск с помощью Дисковой утилиты или Терминала.

В некоторых случаях диск уже смонтирован, но невидимый. В других случаях ошибка диска появляется независимо от того, какое действие пользователь пытается выполнить с диском — будь то форматирование, монтирование или стирание.

Полное сообщение об ошибке гласит:

Не удалось смонтировать «имя диска».
(ошибка com.apple.DiskManagement.disenter -119930868)

Что вызывает ошибку Com.apple.DiskManagement.disenter -119930868?

Если не удается смонтировать жесткий диск и появляется ошибка com.apple.DiskManagement.disenter -119930868, это может быть вызвано одной из следующих причин:

  • Повреждение файловой системы. Файловая система отвечает за организацию и хранение данных на диске. Если файловая система Macintosh HD повреждена, основная файловая таблица будет затронута напрямую, поэтому Mac не сможет подключить диск.
  • Вирусные атаки. Возможно, ваша система Mac или Macintosh HD подверглась атаке вируса или вредоносного ПО, что привело к повреждению данных. Тогда ваш Mac также не сможет смонтировать Macintosh HD.
  • Файл каталога поврежден. Файлы каталога содержат файлы записей разделенных томов. Таким образом, если какой-либо файл каталога окажется поврежденным, Mac не сможет получить местоположение размера тома, описание содержимого тома и другую информацию о томе, не говоря уже о монтировании диска.
  • Сбои Дисковой утилиты. Проблема с подключением Macintosh HD также может быть вызвана сбоями Дисковой утилиты.
  • Неисправности системы. К системным сбоям относятся сбои в работе машины и ошибки операционной системы. В случае сбоя операционной системы Mac она не может подключить ни один диск.

Как решить ошибку com.apple.DiskManagement.disenter -119930868

Прежде чем приступить к исправлению этой ошибки, вот контрольный список, который вы При подключении жесткого диска необходимо учитывать следующее:

  • Повторно подключите разъем USB или адаптер, чтобы он плотно прилегал к жесткому диску.
  • Подключите жесткий диск к другому USB-порту или другой Mac.
  • Замените USB-кабель или адаптер, если вы подозреваете, что он поврежден.
  • Подключите img к внешнему источнику питания, если он требуется для жесткого диска.
  • Проверьте светодиод, чтобы убедиться, что устройство хранения включено и работает.
  • Замените жесткий диск другим корпусом, если вы считаете, что он неисправен.

Также рекомендуется запустить сканирование вашего компьютера с помощью надежной антивирусной программы, чтобы убедиться, что ошибка не вызвана заражением вредоносным ПО.

После того, как вы выполнили контрольный список и ошибка по-прежнему появляется, затем выполните следующие действия.

Исправление №1: измените настройки macOS.

Убедитесь, что Finder предпочитает показывать внешние диски на рабочем столе или в Finder. Для этого:

  • Откройте Finder из Dock . В верхней строке меню выберите Finder & gt; Настройки.
  • В окне настроек Finder перейдите на вкладку Общие .
  • В разделе Показать эти элементы на рабочем столе установите флажок Внешние диски . На вашем рабочем столе появится значок внешнего жесткого диска.
  • Перейдите на вкладку Боковая панель . В разделе Местоположения установите флажок Внешние диски . На боковой панели Finder теперь будет отображаться внешний жесткий диск.
  • Вам также необходимо убедиться, что в меню View Disk Utility выбран параметр «Показать все устройства».

  • Нажмите Command + Клавиша пробела открывает Spotlight
  • Введите дисковую утилиту и нажмите Return , чтобы открыть Дисковую утилиту.
  • Щелкните меню «Просмотр» в верхнем левом углу Дисковой утилиты и выберите Показать все устройства . На боковой панели вашей Дисковой утилиты теперь должен отображаться внешний жесткий диск.
  • Исправление №2: сброс настроек прошивки Mac.

    Чтобы сбросить NVRAM (энергонезависимую RAM) & amp; PRAM (ОЗУ параметров):

  • Перезагрузите Mac, затем сразу нажмите и удерживайте клавиши Option + Command + P + R , пока не услышите второй сигнал.
  • Выполните сброс SMC (Контроллер управления системой) на вашем Mac, следуя приведенным ниже инструкциям:
    • Для iMac, Mac Pro / mini или ноутбука со съемным аккумулятором: отсоедините кабель питания или выньте аккумулятор, затем нажмите и удерживайте кнопку питания в течение 5 секунд.
    • Для MacBook Air, MacBook Pro или MacBook с несъемным аккумулятором: нажмите и удерживайте кнопку Shift + Control + Option + Power . в течение 10 секунд.
  • Исправление №3: Восстановите диск с помощью Дисковой утилиты.

    Если ваш компьютер Mac не загружается, вы можете загрузить Mac в режиме восстановления macOS, а затем восстановить размонтированный Macintosh HD (disk0s2).

    Выполните следующие действия, чтобы восстановить размонтированный Macintosh с помощью Дисковой утилиты:

  • Включите Mac, нажав кнопку питания.
  • Нажмите и удерживайте клавиши Command + R сразу после звукового сигнала запуска. Удерживайте клавиши, пока не увидите логотип Apple, вращающийся глобус или другой экран запуска. Запуск завершен, когда вы увидите окно «Утилиты macOS».
  • Выберите Дисковая утилита и нажмите Продолжить
  • Выберите отключенный Macintosh HD (disk0s2) на левой боковой панели окна Дисковой утилиты.
  • Нажмите Первая помощь на панели инструментов окна Дисковой утилиты.
  • Нажмите Выполнить , чтобы проверить и исправить ошибки файловой системы.
  • Дождитесь завершения процедуры. Если вы получили сообщение об успешном завершении, перезагрузите Mac и посмотрите, можно ли загрузить Mac.
  • Если в сообщении говорится, что дисковая утилита не может восстановить диск, перейдите к следующему решению.

    Исправление №4: исправить Macintosh HD через терминал.

    Если Дисковая утилита перестала восстанавливать Macintosh HD в macOS, вы можете попытаться исправить это с помощью терминала.

  • Загрузите свой Mac в Recovery Mode.
  • Нажмите Утилиты в строке меню и выберите Терминал в раскрывающемся списке.
  • Введите список diskutil . Здесь будут перечислены доступные тома.
  • Проверьте идентификатор тома в появившейся таблице. (Например, disk 2s1)
  • Введите diskutil repairVolume / disk 2s1 . (Замените диск 2s1 идентификатором тома вашего Macintosh HD)
  • Исправление №5: Восстановление из резервной копии Time Machine.

    Если у вас есть резервная копия Time Machine, вы можете восстановить резервную копию и исправить отключенный Macintosh HD ( disk0s2).

  • Загрузите Mac в режиме восстановления macOS.
  • Выберите Дисковая утилита и нажмите Продолжить .
  • Выберите Macintosh HD (disk0s2) и нажмите Стереть .
  • Перед стиранием убедитесь, что вы не потеряете данные.
  • Вернитесь в окно Утилиты macOS.
  • Выберите Восстановить из резервной копии Time Machine и нажмите Продолжить.
  • Выберите свой Диск резервной копии Time Machine в качестве образа восстановления и нажмите «Продолжить».
  • Выберите резервную копию и затем нажмите «Продолжить».
  • Выберите жесткий диск в качестве места назначения для восстановления, а затем нажмите Восстановить , чтобы продолжить.
  • Перезагрузите компьютер Mac, когда восстановление будет завершено.
  • Если все остальное не поможет , сотрите диск и переустановите macOS.

    Если нет важных данных или вы успешно восстановили потерянные данные, вы можете стереть диск и переустановить macOS, используя режим восстановления. Выберите Дисковую утилиту, выберите свой диск и сотрите его. Вернитесь в главное окно и нажмите «Переустановить macOS». Имейте в виду, что это должен быть ваш последний вариант. Надеюсь, это должно устранить ошибку com.apple.DiskManagement.disenter -119930868 и решить проблему с диском.


    01, 2023




    I attached a brand new Seagate USB SSD drive (Backup Plus Slim) to a MacBook Pro running 10.15.2. It mounted the first time, I could see it in Finder, and was able to run the Mac start up program on the drive. However this did not seem to work, so I disconnected the drive. I thought I ejected it properly but not absolutely sure.

    Then when I plugged it in again, I could not see it in Finder. I also tried on a Mac mini running 10.14.6 but could not see it in Finder either. Back on the MacBook Pro, I tried Disk Utility. It found the disk, but it was greyed out and not mounted. When I tried to mount it, I saw the following error:

    Could not mount “disk2s2”. (com.apple.DiskManagement.disenter error -119930868.)
    

    Doing a search on Google, I found this discussion, which indicates it is a Catalina problem. I could not see any useful answer.

    I have tried waiting for hours for it to fix itself and rebooting my machine, but it appears that the disk has become damaged. How do I fix this?

    I attached a brand new Seagate USB SSD drive (Backup Plus Slim) to a MacBook Pro running 10.15.2. It mounted the first time, I could see it in Finder, and was able to run the Mac start up program on the drive. However this did not seem to work, so I disconnected the drive. I thought I ejected it properly but not absolutely sure.

    Then when I plugged it in again, I could not see it in Finder. I also tried on a Mac mini running 10.14.6 but could not see it in Finder either. Back on the MacBook Pro, I tried Disk Utility. It found the disk, but it was greyed out and not mounted. When I tried to mount it, I saw the following error:

    Could not mount “disk2s2”. (com.apple.DiskManagement.disenter error -119930868.)
    

    Doing a search on Google, I found this discussion, which indicates it is a Catalina problem. I could not see any useful answer.

    I have tried waiting for hours for it to fix itself and rebooting my machine, but it appears that the disk has become damaged. How do I fix this?

    When your Macintosh HD (disk0s2) cannot be mounted in Disk Utility, it means that there is something wrong somewhere and your Mac won’t turn on. Several Mac users who have upgraded to macOS Big Sur have complained of getting the com.apple.DiskManagement.disenter error -119930868 when mounting their hard drives. Not being able to mount their drives means not being able to access that drive. This poses a huge issue especially for those who decided to install macOS on that drive.

    com.apple.DiskManagement.disenter error -119930868 is not a new error because Mac users have also encountered this in earlier versions of macOS. However, the occurrence of this error this time means that it is related to the recent upgrade to macOS Big Sur.

    What causes the com.apple.DiskManagement.disenter error -119930868 and how do you successfully mount your drive without getting this error? If you’re wondering about these questions, then read on to find out more.

    What is Com.apple.DiskManagement.disenter Error -119930868?

    When you connect an external hard drive on your Mac, it usually shows up on the Desktop, Finder, and Disk Utility. But there are times when the external drive doesn’t appear on any of these places and the data inside the unmounted external hard drive becomes inaccessible. When users encounter this issue, the easiest way to resolve this is by mounting the drive manually. Unfortunately, several users have reported getting the com.apple.DiskManagement.disenter error -119930868 whenever they try to mount the external drive using Disk Utility or the Terminal.

    In some cases, the drive is already mounted but not visible. In other instances, the disk error appears no matter what action the user is trying to perform on the drive — whether it’s formatting, mounting, or erasing.

    The complete error message reads:

    Could not mount “disk name”.
    (com.apple.DiskManagement.disenter error -119930868)

    What Causes Com.apple.DiskManagement.disenter Error -119930868?

    If you can’t mount your hard drive and the com.apple.DiskManagement.disenter error -119930868 appears, it could be due to any of the following reasons:

    • File system damage. File system is responsible for how data is organized and stored in a drive. If the file system of the Macintosh HD is corrupted, the master file table will be impacted in a direct manner so the Mac won’t mount the drive.
    • Virus attacks. Perhaps, your Mac system or the Macintosh HD is attacked by virus or malware, resulting in data corruption. Then your Mac won’t mount the Macintosh HD, either.
    • Catalog file corruption. Catalog files contain the record files of partitioned volumes. So if any catalog file becomes corrupt, the Mac won’t be able to get volume size location, description of volume content and other volume information, let alone mount the drive.
    • Disk Utility failures The Macintosh HD not mounted issue may be caused by Disk Utility faults, too.
    • System malfunctions. System malfunctions include machine malfunctions and operating system errors. If the Mac operating system crashes, it cannot mount any drive.

    How to Solve com.apple.DiskManagement.disenter Error -119930868

    Before you proceed with fixing this error, here is a checklist you need to consider when connecting your hard drive:

    • Reconnect the USB connector or adapter to fit the hard drive snugly.
    • Connect the hard drive to a different USB port or a different Mac.
    • Replace the USB cable or adapter in case you suspect it to be damaged.
    • Connect to an external power source if the hard drive requires one.
    • Check the LED light to ensure the storage device is powered on and working.
    • Swap the hard drive with a different case if you presume it to be faulty.

    It is also recommended that you run a scan of your computer using a reliable antivirus program to make sure that the error is not being caused by a malware infection.

    Once you’ve gone through the checklist and the error still appears, then proceed with the steps below.

    Fix #1: Change macOS Settings.

    Ensure Finder’s preference to show external disks on Desktop or Finder is enabled. To do this:

    1. Open Finder from Dock. From the top Menu Bar, go to Finder > Preferences.
    2. On the Finder Preferences window, click the General tab.
    3. Under the Show these items on the Desktop section, select the External disks checkbox. Your Desktop will now show the external hard drive icon.
    4. Click the Sidebar tab. Under the Locations section, select the External disks checkbox. Your Finder sidebar will now show the external hard drive.

    You also need to ensure Disk Utility’s View menu has the “Show All Devices” option selected.

    1. Press Command + Space Bar keys to open Spotlight.
    2. Type disk utility and hit Return to open Disk Utility.
    3. Click the View menu located at the top left corner of Disk Utility and select Show All Devices. Your Disk Utility’s sidebar should now show the external hard drive.

    Fix #2: Reset Mac Firmware Settings.

    To reset NVRAM (Non-volatile RAM) & PRAM (Parameter RAM):

    1. Restart Mac then immediately press and hold Option + Command + P + R keys until you hear a second chime.
    2. Reset SMC (System Management Controller) on your Mac by using the instructions below:
      • For iMac, Mac Pro/mini, or laptop with a removable battery—detach the power cable or take out the battery then press and hold the Power button for 5 seconds.
      • For MacBook Air, MacBook Pro, or MacBook with non-removable battery—press and hold Shift + Control + Option + Power Button for 10 seconds.

    Fix #3: Repair Disk with Disk Utility.

    If your Mac computer won’t boot, you can boot your Mac into macOS Recovery mode and then repair unmounted Macintosh HD (disk0s2).

    Follow these steps to repair unmounted Macintosh with Disk Utility:

    1. Turn on your Mac by pressing the Power button.
    2. Press and hold down Command+R keys immediately upon hearing the startup chime. Hold down the keys until you see the Apple logo, a spinning globe or other startup screen. Startup is complete when you see the macOS Utilities window.
    3. Select Disk Utility and click Continue.
    4. Select the unmounted Macintosh HD (disk0s2) from the left sidebar of Disk Utility window.
    5. Click First Aid in the toolbar of the Disk Utility window.
    6. Click Run to check and repair file system errors.
    7. Wait until the procedure is completed. If you get a message saying success, restart your Mac and see if your Mac can be booted.

    If a message says that the disk utility cannot repair the disk, go to the next solution.

    Fix #4: Fix Macintosh HD via Terminal.

    If Disk Utility stopped repairing Macintosh HD in macOS, you can then try to fix it with Terminal.

    1. Boot your Mac into Recovery Mode.
    2. Click Utilities from the menu bar and select Terminal from the drop-down list.
    3. Enter diskutil list. This will list out the available volumes.
    4. Check the volume identifier from the table that appears. (For example disk 2s1)
    5. Enter diskutil repairVolume/disk 2s1. (Replace disk 2s1 with the volume identifier of your Macintosh HD)

    Fix #5: Restore from a Time Machine Backup.

    If you have a Time Machine backup, you can restore the backup and fix unmounted Macintosh HD (disk0s2).

    1. Boot your Mac into macOS Recovery mode.
    2. Select Disk Utility and click Continue.
    3. Select Macintosh HD (disk0s2) and click Erase.
    4. Before erasing, make sure you don’t lose any data.
    5. Return to macOS Utilities window.
    6. Select Restore from Time Machine Backup and click Continue.
    7. Select your Time Machine backup disk as the restore source and then click Continue.
    8. Select a backup and then click Continue.
    9. Select the hard disk as the restore destination and then click Restore to continue.
    10. Restart your Mac computer when the restore is done.

    If all else fails, erase the drive and reinstall macOS.

    If there is no important data or you have recovered lost data successfully, you can erase the drive and reinstall macOS instead using Recovery mode. Choose Disk Utility, select your drive and erase it. Go back to the main window and click Reinstall macOS. Keep in mind that this should be your last option. Hopefully this should resolve the com.apple.DiskManagement.disenter error -119930868 and fix your disk problem.

    Vicrey Dharmdas | Author Softwaretested.com

    Vic is a certified gadget freak who feels the need to surround himself with cutting-edge technology. And this passion has helped him a lot in creating content that informs and guides users on using and troubleshooting the latest technology. He is an avid researcher who is always hungry for the latest news and updates on the most cutting-edge technology.

    Vic is the one in charge of keeping our website running smoothly and efficiently, to make sure that our readers have a wonderful experience while visiting the website. He’s good at troubleshooting errors and fixing Windows issues that come up either when playing games or working on the computer. 

    Looks like no one’s replied in a while. To start the conversation again, simply

    ask a new question.

    An external disk refuses to mount, com.apple.DiskManagement.disenter error -119930868.

    What causes this particular error and what can I do to mount this drive or retrieve the data from it?

    iMac Line (2012 and Later)

    Posted on Oct 9, 2019 3:22 AM

    Similar questions

    • External Disk Won’t Mount with Apple’s Big Sur Operating System
      I get this error message: com.apple.DiskManagement.disenter error 49153
      How can I resolve it?

      1005
      6

    • Could not mount “disk2s2”. (com.apple.DiskManagement.disenter error -119930868.)
      Dear, I got this message trying to mount an MSDOS FAT32 external usb stick that has files I want to work on from a windows computer.
      I also tried to look for similar issues but the error wasn’t even the same actually I could not find nowhere that error number.

      Why does not work?
      what I need to do?
      thanks

      772
      2

    • can’t mount USB flash drive
      how do i fix this error Could not mount “disk3s2”. (com.apple.DiskManagement.disenter error -119930868.) need a help pliz

      123
      1

    7 replies


    Question marked as

    Helpful

    Dec 16, 2019 2:10 AM in response to mhicks

    Ok so its been a week since i pressed the «i have this problem too button»

    i spent most of my days not being able to write on the disk only read it and last night i tried to repair the disk again in disk utility. it didnt seem to do anything but this morning i noticed it finished the process and i pressed mount and it worked.

    Sharing & permissions changed to » you have custom access». what i want to say is ease us and tuxera didnt do anything or the western digital discovery. The only thing that worked was my patience.


    Question marked as

    Helpful

    Oct 29, 2019 7:03 PM in response to mhicks

    Open Activity monitor and forse quit there fsck_ext. Will solve issuer.


    Question marked as

    Helpful

    Oct 19, 2019 6:53 AM in response to chuck_3rd

    This doesn’t really help. I don’t want to lose all the info I have on my external drive. You’ve made it sound like it’s the drive issue but it’s really with how the new Catalina update is working to read these drives. Please provide a better fix. I need drive access without reformatting & it’s worked fine up till the latest update.


    Question marked as

    Helpful

    Oct 23, 2019 11:36 AM in response to mhicks

    On my system, I just have to wait for some time till I can mount my external drive (SD, for example).

    Seems like Catalina runs fsck on them if they were not safely removed last time.

    Drive mounts itself after it’s checked for errors. It just takes time.


    Question marked as

    Helpful

    Oct 25, 2019 1:42 AM in response to chuck_3rd

    I’m having a similar issue — «com.apple.DiskManagement.disenter error 0.» since the Catalina upgrade.

    I’ve a partitioned 2Tb drive — half I drag & drop files to, the other half is for Time Machine. I have another disc that I use as a backup for the files/data but not as Time Machine.

    My partition for dragging files into mounts but the Time Machine partition won’t. It wt was last seen in action trying to backup a few days ago but announced it had insufficient space.

    An ideas?

    I’ll also post on a Time Machine forum


    Question marked as

    Helpful

    Oct 30, 2019 5:45 AM in response to mac1317

    The only solution I could find was to install Tuxera. This suggestion was posted on a similar Q as the solution & it worked for me. Microsoft NTFS for Mac by Tuxera 2019


    Question marked as

    Helpful

    Oct 19, 2019 6:52 PM in response to mhicks

    I recently purchased a new IMac and upgraded it to Catalina. BIG mistake!! I have this same problem and it will not mount any external hard drives. These drives all still work fine on my old macBook running Mojave 10.14.1. This problem started when I Accidentally unplugged a drive and didn’t trash the icon first. Another problem is Disk Utility and some other programs will not respond to a QUIT command. The only way to get them to quit is to force quit them. I assume you will have a fix soon???

    273 replies

    Nov 12, 2019 9:29 AM in response to mhicks

    Have the same issue with my external drive on my MacBook Pro

    com.apple.DiskManagement.disenter error -119930868

    The drive cannot be mounted in OS Catalina (10.15.1), drive is APFS 3TB HDD. Disk Utility shows it greyed out and if I try to mount it I get that error.

    I tried to plug this drive in my friend’s iMac with Mojave 10.14.6- it works just fine! Does anyone know how to make it work with Catalina?

    Nov 13, 2019 5:33 AM in response to roman127

    This is really interesting..I did a bit of investigating myself. Seems like while Catalina starts, codes like «fsck -fy» would be running in the background to determine if a drive is mounting or not. I wonder if something is missing in those codes that disallowing some external disks be read (My HD is Seagate — 3TB — NTFS) or there is a link between Catalina’s security code that sends a signal to your antivirus software saying that, the drive is a virus and should not be mounted. I suspects that because I formatted my Mac and it was under OS X Lion, whenever I plugged my HD in, a window of my antivirus popped up and said «blocked autorun.inf because it was infected with INF: Autorun-BH(Wm)» and I am back to Catalina with the same computer, there is no message when I plug in my HD. Yet, my drive is grey out from the list. All of my other WD drives are ok in Catalina.

    Nov 15, 2019 8:39 AM in response to mhicks

    My Lacie 2TB portable hard drive suddenly couldn’t be mounted on my Macbook Pro (Running Catalina) after it shut down because of low battery power. When I restarted… nothing. I tried to mount it on my MacPro, (High Sierra), same thing and I freaked.

    After reading here that all I had to do to restore it, is wait, I didn’t think it could be that easy… but it was. It took about an hour, leaving the drive connected before the computer could mount the drive. All is good.

    Nov 15, 2019 9:33 AM in response to dhbaker

    Now I wonder what affected that @dhbaker. I mean, one second it is working and after the update, it has to take an hour to recover the drive. I have a few 3TB drives and they are all mounted quickly (all WDs). I found out that Lacie is owned by Seagate and so they use Seagate’s drive. The drive I could not mount is a Seagate! coincident?

    Nov 15, 2019 9:51 AM in response to BiilCanada

    My drive is also Seagate! Probably it’s a Seagate thing? I tried to leave it over night- it didn’t mount ( other drives I have are WDs and they mount ok.

    Nov 15, 2019 10:07 AM in response to roman127

    @roman127 right…even though I called the apple support and they claimed it is something to do with my drive. They said they could send me to Seagate support. I didnt think it was anything to do with Seagate but I tried going through Seagate’s website. It looks like they have a data recovery app called pixel8 and it could read my drive, just wouldnt mount but it discovers the files I have in the drive. It will cost $99US for a year of subscription to recover my HD. I wonder why they came up with this software pixel8. I also found out that Seagate does not have a lot of support on Mac side. On PC side they have firmwares and softwares. So I am not sure what the problem between Seagate and Apple is, not supporting each other. For customers, we are in the middle and cant get our problems solved.

    Nov 15, 2019 10:23 AM in response to BiilCanada

    So I think I will also contact Apple Support regarding this issue. But I have really strong argument here- my Seagate drive mounts and works ok with Mojave, so they won’t be able to tell me that this is the problem with my drive.

    Nov 15, 2019 5:01 PM in response to roman127

    Excellent. Great idea @roman127. I need to reverse back to Mojave and see if it would work. It is a pain because I just got back to Catalina from X Lion. I think I will try a time machine method to backup this computer.

    Nov 16, 2019 5:51 AM in response to roman127

    The only solution I could find after much research was to download Tuxera. Now I can access my external drive quickly like before.

    Nov 16, 2019 6:13 PM in response to BiilCanada

    As unsettling as this is, it’s good to know it’s not just me having this issue.. hopefully at some point a fix can be found!

    -Cleo

    Nov 16, 2019 9:04 PM in response to Composercleo

    Apple must fix this and soon or the future of OSX will be compromised.

    Nov 20, 2019 2:44 PM in response to mhicks

    OK, first off I’m quite a junior when it comes to Mac’s. However I got this issue resolved. I did the the convert to APFS system as it seemed to be the «smart» thing to do. However the drive showed out grey. I couldn’t mount or erase or restore, just nothing. I believed that in the conversion the drive would be partitioned. It was not. After a call to Apple Care they determined they didn’t know what the problem was either. After the call I tried the partition option. Problem fixed in 10 seconds. I don’t know if that’s the issue but it worked for me. Good luck!

    Nov 22, 2019 4:25 AM in response to mac1317

    That saved my bacon!! Thanks very much, worked like a charm

    Nov 23, 2019 7:18 AM in response to BiilCanada

    Running OS Catalina on a new MacBook Pro. I just had a drive fail on me (WD 2TB) after mounting quickly for the past 24 hrs. Did not eject it manually — literally the drive unmounted itself while I was adding a Word document to it for backup. Other drives I own work fine (WD and Seagate), I could open the drive great on a windows PC, and a recovery app found the documents while loaded onto the problem Mac. The fsck command was not running in background, per activity monitor. So now I’m recovering my recovery drive on a second backup until this temper tantrum fixes itself.

    I don’t think it’s just a Seagate thing, this definitely seems like a Catalina thing.

    An external disk refuses to mount, com.apple.DiskManagement.disenter error -119930868.

    В этом руководстве мы покажем вам различные способы исправления ошибки Diskmanagement.disenter с кодами ошибок 119930868, 119930872, 49218, 49223, 0 и т. д. Многие пользователи выразили обеспокоенность тем, что не могут подключить внешние жесткие диски к своему Mac. . Эта проблема не зависит от ОС, о ней сообщалось в Big Sur, Monterey и даже Ventura.

    Всякий раз, когда они пытаются смонтировать диск с помощью Дисковой утилиты, они приветствовал с ошибкой Diskmanagement.disenter вместе с одним из следующих кодов ошибок 119930868, 119930872, 49218, 49223, 0 и т. д. Невозможность доступа пользователей к данным на отключенном внешнем жестком диске доставляет им массу неудобств. Если вы тоже находитесь в одной лодке, то это руководство поможет вам. Следите за исправлениями.

    Рекомендуется попробовать каждый из нижеперечисленных обходных путей, а затем посмотреть, какой из них приводит к успеху. Итак, имея это в виду, давайте начнем. Droidwin и его участники не будут нести ответственность в случае термоядерной войны, если ваш будильник не разбудит вас, или если что-то случится с вашим Mac и данными, выполнив следующие шаги.

    ИСПРАВЛЕНИЕ 1. Завершение процесса fsck

    Одна из наиболее распространенных причин этой ошибки может быть связана с тем, что «fsck» может держать ее в заложниках. Поэтому вам придется убить этот процесс и повторить попытку монтирования диска. Вот как это можно сделать:

    1. Для начала запустите Терминал и Дисковую утилиту.
    2. Затем попробуйте смонтировать диск и сразу переключитесь на Терминал.
    3. Теперь выполните следующую команду в окне терминала: sudo pkill -f fsck
    4. Диск смонтируется в режиме только для чтения. Теперь вы можете восстановить его с помощью программы «Первая помощь» в Дисковой утилите.
    5. Ремонт займет время. После этого это должно исправить ошибку Diskmanagement.disenter.

    ИСПРАВЛЕНИЕ 2: использование терминала

    1. Для начала загрузите Mac в режим восстановления, как указано ниже: Apple Silicon: нажмите и удерживайте кнопку питания, пока не появится «Загрузка параметров запуска». Затем выберите Функции > Продолжить. Intel: перезагрузите Mac и одновременно нажмите и удерживайте сочетание клавиш Command+R.
    2. Затем нажмите «Утилиты» и выберите «Терминал». Теперь введите следующую команду: diskutil list
    3. Появится список всех дисков. Запишите идентификатор тома вашего диска [such as disk3s1].
    4. Наконец, выполните приведенную ниже команду [replace diskX with your volume identifier].diskutil repairVolume/diskX
    5. Проверьте, исправляет ли он ошибку Diskmanagement.disenter 119930868, 119930872, 49218, 49223, 0.

    ИСПРАВЛЕНИЕ 3. Изменение размера выделяемого диска

    Некоторые старые Mac не смогут смонтировать диск, если размер выделения больше 1024. Поэтому, чтобы решить эту проблему, перейдите на компьютер с Windows или Linux (или используйте виртуальную машину) и переформатируйте диск в ExFAT и выберите 1024 как размер выделения. Теперь попробуйте установить его на свой Mac, и на этот раз вы не получите никаких кодов ошибок.

    Вот и все. Это были три метода, которые должны помочь вам исправить ошибку Diskmanagement.disenter с кодами ошибок 119930868, 119930872, 49218, 49223, 0 и т. д. Если у вас есть какие-либо вопросы относительно вышеупомянутых шагов, сообщите нам об этом в комментариях. Мы вернемся к вам с решением в ближайшее время.

    О главном редакторе

    LeoElicker

    LeoElicker

    Joined
    Mar 31, 2020
    Messages
    2
    Motherboard

    X79

    CPU

    I7-3930K

    Graphics

    RX 570

    • #1

    What’s up guys, I hope you all are fine.

    I’m having some trouble while trying to mount my Sata HDD on the Disk Manager, before installing the OS (This disk was previously on my MacBook Pro, but I’ve swapped for a SSD).

    I’ve previously installed Windows on it, but have cleaned it to NTFS. At the Disk Manager utility, before installing, I’ve managed to, apparently, erase it to macOS Journaling, which is the Apple recommended format for new installations (found an article on help section).

    So, the disk have unmounted itself and now I was not able to mount it anymore. When I try to mount, format ou even part the disk, I’ve got a different error. In mounting the disk case, the error is (com.apple.DiskManagement.disenter error -119930868) and I’m stuck at that.

    Can someone help me?

    Thanks!

    LeoElicker

    LeoElicker

    Joined
    Mar 31, 2020
    Messages
    2
    Motherboard

    X79

    CPU

    I7-3930K

    Graphics

    RX 570

    • #2

    Well, I solved this question myself a few minutes after posting.

    What I was trying to do is to erase just one part of the disk, not the entire (didn’t knew that this was possible).

    So, if anyone get stuck at that, just go to View->Show All Devices and the erase your disk from the root.

    That’s it, thanks!

    mindkindness

    mindkindness

    Joined
    Jul 25, 2020
    Messages
    3
    Motherboard

    motherboard OR system make & model # > See Rules!

    CPU

    Intel> Need model # > See Rules!

    Graphics

    Radeon Pro 555X

    Mac
    1. MacBook Pro
    • #3

    Hello.
    My system disk (taken out of the disabled iMac) is not mounting.
    It contains softwares that I need to recover. I cannot format it.
    (Note: my Time Machine disk crashed shortly before this problem.)
    I have the error:
    (error -119930868 in com.apple.DiskManagement.dissenter.) Unable to mount «disk6s2».
    How did you solve the problem?
    Thank you !
    [Catalina 10.15.6 (19G73)]

    Last edited: Jul 25, 2020

    • #4

    How did you solve the problem?

    See Post #2.

    So, if anyone get stuck at that, just go to View->Show All Devices and the erase your disk from the root.

    mindkindness

    mindkindness

    Joined
    Jul 25, 2020
    Messages
    3
    Motherboard

    motherboard OR system make & model # > See Rules!

    CPU

    Intel> Need model # > See Rules!

    Graphics

    Radeon Pro 555X

    Mac
    1. MacBook Pro
    • #5

    Thank you.
    I must not make a mistake. The softwares to be recovered is essential and expensive.
    I get in «disk user»:
    «Show all devices» =
    > JMicron Generic DISK03 Media (selectable, SOS = good, GUID partition table with 2TB)
    > disk6s2 (in gray)
    How to erase the root while keeping the rest safe?

    mindkindness

    mindkindness

    Joined
    Jul 25, 2020
    Messages
    3
    Motherboard

    motherboard OR system make & model # > See Rules!

    CPU

    Intel> Need model # > See Rules!

    Graphics

    Radeon Pro 555X

    Mac
    1. MacBook Pro
    • #6

    Thank you Pilgrim-Moderator.
    How to «erase your disk from the root» without risking the rest of the contents of the disk? Procedures ?
    Only select JMIcron and click «Delete»?
    Thank you.

    • #7

    How to «erase your disk from the root» without risking the rest of the contents of the disk?

    If your objective is to preserve data then my advice to you would be to not erase anything.
    Disconnect the drive.

    Install the OS on a new disk and then connect the damaged disk to recover data.
    If this fails then there are professional data recovery specialists available who can recover your data for a fee.

    Replies

    Nevermind, figured it out myself

    Arguably, «figured it out myself» is not a very helpful answer to a situation like this, as people looking for answers reach a dead end.

    Anyways, if your disk happens to be ExFAT, and you remember improperly removing the disk the last time you used it, chances are, fsck is holding it hostage (metaphorically, of course). fsck is trying to repair the disk, but it will stall forever, so you want to launch Disk Utility, and the Terminal. Try to mount the disk, and switch to Terminal and write sudo pkill -f fsck. The disk will mount in read-only mode, and from there, you can repair it with First Aid in Disk Utility. This won’t work for non-ExFat drives, as macOS manages them differently.

    This solved my problem thanks. Just a note to future users, the repair took a really long time for my 5TB drive. Be patient.

    This happened for me on a Big Sur MacOS, clicking the ‘First Aid’ option in Disk Utility kept giving me this same error. What ended up working for me was restarting my laptop, then continuously trying ‘First Aid’ until one time it suddenly didn’t give me the error, and after waiting about 20minutes the drive mounted properly. I don’t think I did anything differently other than trying over and over again.

    Thank you for posting the fix. It worked and saved my years of work


    Vishnu
    https://www.YinandYang.studio

    Just to note to @jkrosado instructions: it worked with Mac OS Extended drive format too.

    @jkrosado tysm!! it worked for me and saved me from panicking due to all my homework and software I need for my classes in that hard drive

    This still isn’t working for me. I don’t understand what this «and the Terminal» means. When I try to mount my drive, the error that is the title of the forum comes up and it appears I am at a dead end. I tried to repair the drive, and it seemed to do something (with a bunch of green check marks) saying it was fixed, but it still won’t open or be recognized by my finder or desktop. If anyone is able to walk me through this, I would be very appreciative.

    I also got this working on my HFS+ drive. Worked exactly the same as an ExFAT not sure what the technical background on this is but for those wondering.

    Thanks @jkrosado
    Your answer was helpful.
    Drive should be ExFAT and it worked after killing process and first aid.

    What about Mac OS Plus drives ? How can I solve it?

    I am inserting external Drives but they are not showing up. I went to disk utility and I tried First Aid and then mounting and I keep on getting «could not mount «New Volume». (com.apple.diskmanagement.disenter [error -119930872.)]
    error message. I tried it with multiple drives and in multiple user profiles on the same Mac. Any help is appreciated.

    Thanks

    Replies

    I am having the same issue. I get the message: Could not mount “New Volume”. (com.apple.DiskManagement.disenter error -119930878.). It initially worked but when I moved some files from my machine to make room for Monterey update, I am getting this message. So many important files are in this drive and I haven’t seen anything that could be of help anywhere else. Let me know if you get it to work and I will if I do on my end.

    Good luck!.

    same issue here. Very problematic. I am certain it is not a problem with the hard drive. all 5 of my drives are doing the same thing — same error code. Just started recently. Apple broke something and needs to fix

    Am seeing same issue when am trying to connect external hardisk, is there any resolution to this issue ? am on Mac Monterey version.

    I got this error when trying to use a USB 3.1 HD plugged into a USB-C docking station on my MacBook Pro. When I tried on a Mac Mini with its own USB Type-A ports, the drive mounted happily. Makes me think the error could be a problem with the adapter.

    The «fix» for me is log out the existing user and then log right back in, same user, no changes. The drives appear in finder and disk util and work as expected.

    I spent an hour+ with Apple support and their answers were to «repair the drive», «run first aid», and «reinstall the OS». Starting in recovery mode, the drives show up and are mounted. As soon as I restart normally, the same issue…drives are unable to be mounted.
    I am not sure why the process of logging out and back in and booting into recovery mode can’t illuminate what might be the issue.

    Log out and back in…drives visible and usable. But every time you disconnect the drives you have to do the same thing in order to mount them.

    I am inserting external Drives but they are not showing up. I went to disk utility and I tried First Aid and then mounting and I keep on getting «could not mount «New Volume». (com.apple.diskmanagement.disenter [error -119930872.)]
    error message. I tried it with multiple drives and in multiple user profiles on the same Mac. Any help is appreciated.

    Thanks

    Replies

    I am having the same issue. I get the message: Could not mount “New Volume”. (com.apple.DiskManagement.disenter error -119930878.). It initially worked but when I moved some files from my machine to make room for Monterey update, I am getting this message. So many important files are in this drive and I haven’t seen anything that could be of help anywhere else. Let me know if you get it to work and I will if I do on my end.

    Good luck!.

    same issue here. Very problematic. I am certain it is not a problem with the hard drive. all 5 of my drives are doing the same thing — same error code. Just started recently. Apple broke something and needs to fix

    Am seeing same issue when am trying to connect external hardisk, is there any resolution to this issue ? am on Mac Monterey version.

    I got this error when trying to use a USB 3.1 HD plugged into a USB-C docking station on my MacBook Pro. When I tried on a Mac Mini with its own USB Type-A ports, the drive mounted happily. Makes me think the error could be a problem with the adapter.

    The «fix» for me is log out the existing user and then log right back in, same user, no changes. The drives appear in finder and disk util and work as expected.

    I spent an hour+ with Apple support and their answers were to «repair the drive», «run first aid», and «reinstall the OS». Starting in recovery mode, the drives show up and are mounted. As soon as I restart normally, the same issue…drives are unable to be mounted.
    I am not sure why the process of logging out and back in and booting into recovery mode can’t illuminate what might be the issue.

    Log out and back in…drives visible and usable. But every time you disconnect the drives you have to do the same thing in order to mount them.

    Понравилась статья? Поделить с друзьями:
  • Codesys ошибка при чтении целевой платформы
  • Codesys ошибка 3611 неверная директория компиляции
  • Codeblocks ошибка при запуске приложения 0xc000007b
  • Codeblocks выдает ошибку при запуске
  • Code net apex legends ошибка