Com apple diskmanagement disenter ошибка 49244 - Исправление ошибок и поиск оптимальных решений проблем

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

ask a new question.

After updating my imac to macOS Catalina it will not show my external hard drive. The drive is recognized on the disk utility but when I try to mount it I got the following message «Could not mount “TOSHIBA EXT”. (com.apple.DiskManagement.disenter error 49244.)». How can I fix this issue?

Posted on Oct 11, 2019 3:23 PM

5 replies

Question marked as
★
Helpful

Oct 16, 2019 5:51 AM in response to luisr1031

I solved the problem by install the trial 15 days tuxera license

Question marked as
★
Helpful

Oct 18, 2019 6:44 PM in response to claus237

Hi,

In utilities, the hard drive was greyed out. I can’t mount my new hard drive. I just keep getting the error.

I’ll take it back to the store and see what they can do.

Question marked as
★
Helpful

Oct 16, 2019 6:20 AM in response to maminyana

I’ve reinstalled Tuxera, and the problem is been solved!

Question marked as
★
Helpful

Oct 16, 2019 9:23 AM in response to yeison208

And what will happen when your free trial expires?

Question marked as
★
Helpful

Nov 14, 2019 9:30 AM in response to luisr1031

Après la mise à jour de mon imac vers macOS Catalina, mon disque dur externe ne s’affiche pas. Le lecteur est reconnu sur l’utilitaire de disque, mais lorsque j’essaie de le monter, le message suivant «Impossible de monter» Backup». (Erreur 49244 de com.apple.DiskManagement.disenter). Comment puis-je résoudre ce problème?

35 replies

Oct 22, 2019 12:13 AM in response to rogerh@mac.com

tout fonctionne depuis la mise à jour de tuxera,

since the update of Tuxera it’s OK for me

Oct 25, 2019 3:19 AM in response to yeison208

Tuxera Works perfectly so far. Had bought the previous version in 2015. Bought a new license key just now.

Oct 25, 2019 7:13 AM in response to luisr1031

Same issue is happening on my MacBook Air Mid-2015. But it is not mounting anything, not even update nor any other download image (DMG file). External disks nor Time Machine either.

Does any one got any answer for that? Tuxera didn’t worked as well.

Workaround I am using is downloading in other machine, extract file do disk and copy using AirDrop, but is it not a solution.

Thanks.

Oct 30, 2019 2:27 PM in response to NickZaven

I am having major issues with spinning external hard drives after installing Catalina. I’ve had 2 hard drives die and a 3rd is now failing to mount.

Oct 30, 2019 3:10 PM in response to maminyana

You need special software to be able got access and use an NTFS volume. A system upgrade will remove that software so you’ll need to reinstall it.

Nov 2, 2019 10:20 AM in response to luisr1031

(com.apple.DiskManagement.disenter error 0.) In my case.

Is there a way to make my WD Mybook work again also on Catalina MBPro 2019? Strangest thing is that i have same model Mybook at office and it works fine with Catalina on Imac (27 late 2013) Both hdd’s are xFat and was working perfect before catalina update.

Nov 11, 2019 6:24 AM in response to luisr1031

Have similar error after updating macOS Catalonia. What should I do to rectify it. Have 4Tb of files in my external hard disk and it is not mounting.

Nov 13, 2019 6:40 PM in response to luisr1031

UPDATED YOUR TUXERA DISK MANAGER

I had the same error today. When I upgraded to the new macOS Catalina, Tuxera Disk Manager was outdated and needed to be manually updated (it doesn’t happen automatically like most other apps). Once I updated Tuxera, I was able to mount all my external hard drives.

Question marked as
★
Helpful

Nov 14, 2019 9:30 AM in response to luisr1031

Dec 10, 2019 11:03 PM in response to luisr1031

I have the exact same issue… except its with my Macbook’s internal SSD… yeah.

Happened sometime roughly after I upgraded my mac to MacOS Catalina. One day, I decide to restart my mac, and then next thing you know it can’t find it’s boot drive. Question mark icon on a blinking folder when I try to boot up.

I would really like to just be able to mount my internal SSD again so I can access my data normally, but for now I am stuck booting off of an external drive with MacOS Catalina installed, using 3rd party data recovery software to try and save some of my data before I will probably inevitably have to format the SSD and start over again.

Any known fixes to mount my internal APFS drive? Its not even recognized as a boot drive when in recovery mode… Thinking this is more serious than I’m making it out to be!

Dec 20, 2019 5:24 PM in response to luisr1031

I got same issue while i was copying boot image suddenly remove usb from mac. thereafter mac doesn’t recognise my usb even i format usb using windows machine. so I clearly read error message so then I realised partition table has issue. to fix that I used below resolution

plug usb and open terminal with diskutil list ( in my case it was dev/disk2
re-partition whole disk with «diskutil eraseDisk JHFS+ UntitledUFS diskN» (diskN is your disk number my case it was disk2)

mac Os Catalina and mac book pro 2018 version

Thanks

Damith

Jan 6, 2020 10:38 AM in response to luisr1031

Jan 17, 2020 11:37 AM in response to maminyana

How did you reinstall this? Did you buy the Tuxera software?

Disk Management disenter error 49244

Источник

I have a fairly new LaCie d2 4TB hard drive (roughly one year old). Some days ago it wouldn’t show up anymore and now I looked into the issue.

In disk utility the disk is unmounted. When hitting «mount» I get this error:

(com.apple.DiskManagement.disenter-error 49244.)

When trying to repair the disk I get the exit code 8 and

Invalid node structure (8, 0) Invalid B-tree node size (8, 0)

I also have Bootcamp installed and Windows can see the drive; it seems normal to me there. But it is formatted as Mac OS Extended so Windows can’t do anything with it. Do you have any idea what I can do other than reformat?

I read the in a different post that you can try the repair process in the terminal or boot into windows and eject the drive properly (yet, Windows isn’t even mounting a Mac OS Extended journaled drive, so how should I unmount it. Also a normal shutdown should do this job, too, and I have done that multiple times in both macOS and Windows). I have tried the terminal commands from the mentioned post, the only interesting part is, when using the sudo fsck_hfs -r -d /dev/disk5s2 command I get this error, where it also shows error 7.

** /dev/rdisk5s2
    Using cacheBlockSize=32K cacheTotalBlock=65536 cacheSize=2097152K.
   Executing fsck_hfs (version hfs-522.100.5).
** Checking Journaled HFS Plus volume.
   The volume name is X-d2
hfs_swap_BTNode: offsets 1 and 0 out of order (0x0000, 0x0000)
   Invalid node structure
(8, 0)
   Invalid B-tree node size
(8, 0)
** The volume X-d2 could not be verified completely.
    volume check failed with error 7 
    volume type is pure HFS+ 
    primary MDB is at block 0 0x00 
    alternate MDB is at block 0 0x00 
    primary VHB is at block 2 0x02 
    alternate VHB is at block 7813365342 0x1d1b67e5e 
    sector size = 512 0x200 
    VolumeObject flags = 0x07 
    total sectors for volume = 7813365344 0x1d1b67e60 
    total sectors for embedded volume = 0 0x00 
    CheckHFS returned -1317, fsmodified = 0

(The files are backed up, so it would be ok to reformat, but I would prefer being able to repair it)

I would be very happy for any answers. Thank you!

Источник

I have a fairly new LaCie d2 4TB hard drive (roughly one year old). Some days ago it wouldn’t show up anymore and now I looked into the issue.

In disk utility the disk is unmounted. When hitting «mount» I get this error:

(com.apple.DiskManagement.disenter-error 49244.)

When trying to repair the disk I get the exit code 8 and

Invalid node structure (8, 0) Invalid B-tree node size (8, 0)

** /dev/rdisk5s2
    Using cacheBlockSize=32K cacheTotalBlock=65536 cacheSize=2097152K.
   Executing fsck_hfs (version hfs-522.100.5).
** Checking Journaled HFS Plus volume.
   The volume name is X-d2
hfs_swap_BTNode: offsets 1 and 0 out of order (0x0000, 0x0000)
   Invalid node structure
(8, 0)
   Invalid B-tree node size
(8, 0)
** The volume X-d2 could not be verified completely.
    volume check failed with error 7 
    volume type is pure HFS+ 
    primary MDB is at block 0 0x00 
    alternate MDB is at block 0 0x00 
    primary VHB is at block 2 0x02 
    alternate VHB is at block 7813365342 0x1d1b67e5e 
    sector size = 512 0x200 
    VolumeObject flags = 0x07 
    total sectors for volume = 7813365344 0x1d1b67e60 
    total sectors for embedded volume = 0 0x00 
    CheckHFS returned -1317, fsmodified = 0

(The files are backed up, so it would be ok to reformat, but I would prefer being able to repair it)

I would be very happy for any answers. Thank you!

Источник

What Is Error 49244?

Many users have reported Error 49244 to appear each time when they connect an external SSD drive to their Mac, running the latest version. The main problem with this error is that it holds the process of the connection and stops it completely from happening.

Read this post to learn more about what is this error and what it does on your Mac and what you can do to fix it for free.

On this page:

What Is Error 49244?Error 49244 DetailsError 49244 – What Are Its SymptomsIs Error 49244 Dangerous?Error 49244 – How to Fix It?Alternative Fixes

Error 49244 Details

Name	Error 49244, also known as com.apple.DiskManagement.disenter error 49244
Type	Runtime / Compatibility Error
Short Description	The error says that an external drive has incompatible partition, which cannot be read.
Symptoms	A pop-up stating the error and its number – “Disk Management disenter error 49244“.
Program	MacOS
Fix Tool	Try this fix to repair your Mac from errors and optimise system performance: Download SpyHunter

Error 49244 – What Are Its Symptoms

Error 49244 is a typical compatibility runtime error and belongs to the same type of errors as the Error -1426, Error Code 1309 and Error Code 101.

Victims have posted on Apple’s Community Forums noticing this error with the following complaints:

error 49244
I tried to connect a SSD external hard drive, it is recognized by Mac OS Monterey but impossible to activate and thus format or partition. ???

error message disenter error 49244

Other side effects of seeing the Disk Management disenter error 49244 on your Mac may also be:

Internet speed starts slowing down.
Your device may behave erratically.
Some of your other apps or external drives connected may stop functioning.

This is a runtime error that most likely is related to the compatibility of your Mac with external drives. Seeing it does not necessarily mean that your Mac has a virus. However, it is recommended to do a checkup using a professional anti-malware software, due to the possibility of some malware modifying your compatibility permissions and partitions.

Is Error 49244 Dangerous?

This error belongs to the category of runtime / compatibility errors, and as such, it doesn’t seem to be related to a more severe issue.

Error 49244 – How to Fix It?

Below we have quoted several different methods, which are possible fixes according to support. Be advised to backup all your files on your external drive from a safe device before applying those steps.

According to the experts on forums, the most upvoted solutions that are reportedly working to fix the com.apple.DiskManagement.disenter error 49244 are the following:

Error 49244 Fix #1:

Open Disk Utility tool and click on Show All Devices.
Select your external drive and then check if are able to erase and re-format the drive using GUID / APFS partition map.
Erase or reformat the drive.

Error 49244 Fix #2

Plug in your device.
Open your Terminal after which navigate to dev/{your disk number or name}
Type “diskutil eraseDisk JHFS+ UntitledUFS disk(Your disk number)” to repartition the whole disk.

Alternative Fixes

If these fixes do not work, you can try the general fixes that are designed to help you deal with most runtime errors for macOS, located below:

Step 1: Close any apps or programs that may be in conflict.

When you get errors, like this one, often conflicting apps may be the case. Below, you can find the solutions for closing conflicting apps for Windows and macOS:

Go to Activity Monitor, mark any processes you believe are suspicious and close them by clicking the “X” button on top left above them.

After you have done this fix, you should observe if this error will show up again if you start and stop a specific process.

Step 2: Update and Re-install Any Software You Believe is Problematic.

Go to Applications and drag the icon of your program to Bin to uninstall it. For macOS, you can go to your AppStore and click on the “Updates” tab to check if any applications are out of date.

Step 3: Install the latest updates of your OS.

Go to System Preferences – Software Update and check for a newer macOS version. You will see a button to install it and Upgrade if its available.

Step 4: Scan your Mac for errors and optimise it automatically.

If you have tried most of the fixes, but you keep getting error messages, then the best advice to go for is to make sure and check your computer for:

Viruses.
Tracking cookies and other pesky and harmful objects.
Problematic files.
Unwanted software.
Adware.
Browser Hijackers.
Other errors that may be slowing it down.

You can do all of this by running an automatic scan of your computer using a professional anti-malware software. Such an advanced tool is created by cybersecurity and tech experts and is guaranteed to help detect and delete any malicious files and whatever may be causing errors and optimise your computer to make it fast again:

Spy Hunter scanner will only detect the problem. If you want the issue to be automatically removed, you need to purchase the full version of the anti-malware tool.Find Out More About SpyHunter Anti-Malware Tool / How to Uninstall SpyHunter

Mac Errors – Frequently Asked Questions

What are Mac Errors?

Mac errors are faulty problems of macOS. They are different types, affecting various programs running on your Mac.

Since macOS is frequently updated, it is easier to fix such errors, due to the way this operating system is constructed.

What Do Mac Error Codes Mean?

Error Codes on Mac are how your macOS explains the different types of problems that can occur on it. The number of the Mac Error code pops up on your screen, and it shows you the error with some explanatory text to help you fix it.

These error codes exist for both small and bigger problems, and in some cases, they can mean that there is a significant issue with your device.

Why Do I See Errors On My Mac?

The reasons may vary. These can be due to a badly written code, faulty software, external app modifying your app, incompatibility, problems with the resources required to run the app, and even a Mac malware infection.

What Types of Mac Errors Exist?

Just like with Windows devices, there are some general error types with Mac as well, including:

Runtime Errors – when you execute a program and it fails due to badly written code, incompatibility with the program and web servers or other problems, like malware.
Logic Errors – something in the logic makes the program fail to return results.
Arithmetic Errors – a type of logic error, which involves miscalculation due to an erroneous configuration or code that does not fit the same logic as the system reads it.
Resource Errors – when your device does not meet the resources required to run a program or if the program is coded faulty, so it requires more resources than necessary.
Interface Errors – when there is a difference between what an app is meant to do and what it actually does.
Compilation Errors – when the compiler of a software fails to turn complicated code into a simple language, understandable by your Mac.

Which are The Most Common Mac Errors?

According to different sources and online forums, the most commonly encountered errors on Mac carry the following codes:

Error Code 36 – when Finder fails to read or write a file on your Mac.
Error Code 41 – caused by malware, outdated software or corrupted files and directories.
Error Code 50 – when you fail to copy and paste a file onto another drive, like USB or an external SSD or HDD.
Error Code 2003F – it shows up when you try reinstalling your macOS in Recovery Mode. Possible causes include bad sectors in the hard disk, malware, etc.

What to Do If I See a Mac Error?

If you see an error on your Mac, your first job is to check the meaning of it. Then, you can see reputable forums, like Apple Discussions or SensorsTechForum in order to find different types of fixes for the problem.

How to Stop Getting Mac Errors?

You cannot. As long as there are people writing the code, there will always be the human error factor. However, there are several measures that you can take in order to significantly reduce the chance of getting a Mac Error:

Check and update your Mac and your Apps (if possible) to the latest version on a daily basis.
Install a relevant and reputable anti-malware for Mac.
Install an optimizer for your Mac, which will keep all your apps updated, remove junk software, and improve your Mac’s health.
Only install apps from trusted sources.

Ventsislav Krastev

Ventsislav is a cybersecurity expert at SensorsTechForum since 2015. He has been researching, covering, helping victims with the latest malware infections plus testing and reviewing software and the newest tech developments. Having graduated Marketing as well, Ventsislav also has passion for learning new shifts and innovations in cybersecurity that become game changers. After studying Value Chain Management, Network Administration and Computer Administration of System Applications, he found his true calling within the cybersecrurity industry and is a strong believer in the education of every user towards online safety and security.

«File System Check Exit Code 8» — Disk wont repair

I’m not sure where this question should be posted. I’ve got a 3 tb Western Digital My Book Studio external drive that I use for backups. I bought it in July. I’ve got a 2 tb partition that I use for Time Machine and a 1 tb partition that holds old photos/music files. Last night, I started…

forums.macrumors.com

thanks. have you ever worked with a data recovery specialist? Can you recommend one?
[automerge]1593354549[/automerge]
PS: get this error message when I try to run disk first aid (in disk util):

Running First Aid on “5V” (disk2s2)

Repairing file system.
Volume is already unmounted.
Performing fsck_hfs -fy -x /dev/rdisk2s2
Checking Journaled HFS Plus volume.
Invalid B-tree node size
The volume could not be verified completely.
File system check exit code is 8.
Restoring the original state found as unmounted.
File system verify or repair failed. : (-69845)

Operation failed…

If the drive is formatted in HFS+, a product like DiskWarrior can more then likely correct the issue. DiskWarrior has been a staple for me for years. It works great on HFS+ formatted drives. It is not free though.

ALSOFT — Makers of DiskWarrior.

DiskWarrior is a utility program designed from the ground up with a totally different approach to preventing and resolving directory damage.

www.alsoft.com

update: yes, I tried DISKWARRIOR — and yes, it seems to have worked! so far, so good. Totally worth the $130 it cost.

thanks for all suggestions!

update: yes, I tried DISKWARRIOR — and yes, it seems to have worked! so far, so good. Totally worth the $130 it cost.

thanks for all suggestions!

w

I have been using DiskWarrior since OS X 10.2. It has saved my system many many times. I am glad it worked.

update: yes, I tried DISKWARRIOR — and yes, it seems to have worked! so far, so good. Totally worth the $130 it cost.

Now make your 3-2-3 backups!

Источник

Replies

First, thanks for this fix — I’ve been having issues with my ExFAT-formatted 5tb external drive on Catalina and this has been super helpful!

This time, though, even after running First Aid in Disk Utility, the drive is still registering as Read-Only, which I’m not sure how to fix! Anyone have any suggestions or have experience with this? The drive does have about 1.5 TB of data on it, and it hasn’t completely backed up to my cloud storage yet, so ideally not anything that requires reformatting (fingers crossed)

The quickest way to sort out problematic exfat drives I’ve found is to mount them in a windows environment (either in a virtual machine or on actual windows computer) and repair them from there. Disk first aid takes a loooong time on larger drives.

Thankyou @jkrosado and @calif94577. It worked out but without hitting the enter button, magic! Also the exfat formatted LA CIE 5GB drive worked on BigSur before then after upgrading to Monterrey it didn’t show up.

I tried that command on the Terminal, the ‘First Aid’ option on Disk Utility said everything was OK and then same Could not mount drive error, I restarted , tried it few times, same error. Dont ask me why but what worked was Logging Out my Mac user and logging again with the same user, super weird. There’s defo some bug on Monterey and the external drives / Time Capsule Mac application…

Hi everyone! I have followed the steps and Disk Utility is running first AID. I have got a SEAGATE 2TB ExFat formatted…but first AID is running «Checking file system hierarchy.» and it has done so for 24 hours…is that normal for a 2TB? I am tempted to quit it….

«Restoring the original state found as unmounted» is the last line I get after running a successful First Aid in Disk Utility after doing the Mount / sudo pkill -f fsc combination. I feel like I’m in an endless loop. Trying to remount a 9TB Raid5 OWD FireWire External Physical Volume • Mac OS Extended (Journaled) on my 27″ iMac (2019) after it was mistakenly shut down w/o ejecting. Have gotten errors 0, 49153 and 49244 after various attempts. I haven’t lost hope due to the successful First Aid reports but getting tired of seeing the drive put back unmounted after every attempt. This is a critical drive for my biz.Any help appreciated. Thanks in advance.

Hi there, My external HDD (LaCie Rugged 4 TB, MacOS Extended (Journaled) formatted) doesn’t show up on the desktop. It is visible in Disk Utility but I can’t repair it. The system returns «com.apple.DiskManagement.disenter error 49244.».

Multiline

Running First Aid on “DISKNAME_1” (disk6s2)

Checking file system and repairing if necessary and if possible.
Volume is already unmounted.
Performing fsck_hfs -fy -x /dev/rdisk6s2
Executing fsck_hfs (version hfs-583.100.10).
Checking Journaled HFS Plus volume.
Invalid B-tree node size
The volume could not be verified completely.
File system check exit code is 8.
Restoring the original state found as unmounted.
File system verify or repair failed. : (-69845)

Operation failed…

BlockQuote

I ran «sudo pkill -f fsck» with no recognizable effect yet. Is there anything to add ahead of this prompt in order to address the non-visible Drive ?
Does anyone have any hints how to fix this issue ?

@calif94577 : «sudo pkill -f fsc» or «sudo pkill -f fsck» ? (I entered the k-version and didn’t get the «2 error pop ups». Am I missing anything ?
Thanks to all contributors and to you @jkrosado as well

I’m on MacOS Monterey 12.5.

thanks so much @jkrosado for saving my wedding photos, i am so appreciative

I’ve pressed mount then in terminal typed in sudo pkill-f fsck.
once I press enter I get underneath password: with a key in a box.
Still won’t mount the usb 😩
Any help would be appreciated

Thank you so much @jkrosado, you saved 4TB of photos and a lot of head aches

I had the same issue and eventualy after a couple of «repair» tries, the disk mounted.

Thank you very much for everyone here, fortunately I didn’t need to try some other solution.

BUT I WAS WONDERING, should I be worried for the future of this drive? Could this be an indication of imminent permanent failure?

Thank you very much!!!

none of those work for me…..I got that WD drive — 1TB..

To remedy the issue I simply hit ‘repair disc’ about four times it still wouldn’t amount, so I ejected the unmounted disk and it showed a mounted icon before it finally ejected. I power cycled the machine and it was mounted.

Non of these worked for me :-/
Was hoping calif94577 way would work, but no…

Источник