Deeply frustrating. Manual mounting is possible, with DiskManger bypass; but media server remains broken as a result.
Can the update be removed?
sizza64 wrote:
will wait until apple give us a new patch for this bug! thanks again!
I would not expect a fix from Apple since it is the third party vendor & developer who are responsible for making sure their third party app works with macOS. @PachisCruz's post later in this thread even proves that the problem is with the manufacturer's third party driver since after uninstalling the manufacturer's driver and rebooting, @PachisCruz was able to read the NTFS drive which shows that macOS is functioning fine and it is just the manufacturer's driver that has the problem. Of course macOS does not have native built-in write support for NTFS volumes, but at least the NTFS volumes can be read after uninstalling the drive manufacturer's software. See @PachisCruz's specific post I referenced here:
NTFS external drives won't mount after se… - Apple Community
This is why most contributors on these forums recommend against using the manufacturer's proprietary software for managing drives because the proprietary third party drivers may break after a macOS update and users will need to wait until the third party developer fixes the problem (if they even do so). Using a native built-in file system included by default with macOS is always the safest and most reliable option.
Apple has released new update for 10.15.7,this issue has been resolved.
@Hngry_J
the problem was fixed in latest macOS-Patch for catalina. No need for workarounds any more
platinumbob wrote:
I found a work around on Tuxero's website
https://macsupport.tuxera.com/hc/en-gb/articles/4696818610706-Help-I-can-t-mount-NTFS-volumes-on-macOS-Catalina-after-the-latest-update-
This is similar to Paragon.
I just confirmed that this also works with Paragon. Simply replace the path in step 4 with "/Library/Filesystems/ufsd_NTFS.fs/Contents/Resources/mount_ufsd_NTFS." The rest of the commands remain the same. Note that you should replace "ntfs-disk" with the name of the NTFS volume you will be mounting, and be sure to use the correct "diskXsY" you found from "diskutil list."
PachisCruz wrote:
Well, the only thing I have to add is that, unfortunatly the reason I've been using this type of software is because it permitted me to transfer files on both Mac and Pc. I don't know what will hapen when I reformat the drive again.
If you need to share the drive with both macOS and Windows, then make sure to use Disk Utility to erase the whole physical drive as GUID partition and exFAT. Within Disk Utility you may need to click "View" and select "Show All Devices" before the physical drive appears on the left pane of Disk Utility. It is important to use Disk Utility to erase the drive since Windows has many different file allocation sizes that might be used, but macOS is only able to recognize a more limited number of file allocation sizes so a drive formatted as exFAT using Windows may not be readable by a Mac (although technically Windows does allow the selection of various file allocation sizes for some file systems).
1. On my IMac running Catalina 10.15.7, after an update, the error "com.apple.DiskManagement.disenter error 49221" occurred.
2. After a web search for reports of the same problem, I decided to install the Paragon driver "NTFS_for_Mac.dng" and followed the installation instructions, including rebooting the computer.
3. The new driver failed to mount my external drives (SeaGate Backup plus portable drive).
4. I decided to uninstall the new driver.
5. Miracle! Like the donkey that played the flute. After rebooting the IMac, my two external drives appeared fresh and clean on the desktop, perfectly mounted and fully usable.
6. I hope a similar path will help those who cannot access their Seagate external drives.
7. Good luck!
Following the steps below fixed the issue for me. No need to buy any kind of external software.
Using Terminal to mount the disk
As a command-line interface on Mac, Terminal allows you to control your operating system and make some changes. When there's a logical error in the process of mounting, the hard drive refuses to be mounted. But the Terminal can work as a bridge to let you take control of the core of the system and then mount the hard drive via command lines.
Following the steps below fixed the issue for me. No need to buy any kind of external software.
Using Terminal to mount the disk
As a command-line interface on Mac, Terminal allows you to control your operating system and make some changes. When there's a logical error in the process of mounting, the hard drive refuses to be mounted. But the Terminal can work as a bridge to let you take control of the core of the system and then mount the hard drive via command lines.
If you rely on your disk(s) being automounted at startup, and your disk Identifiers aren't going to change, then you can reinstate the auto-mounting if you have some nix skills: keep using the original version of paragon with the original temporary fix: https://kb.paragon-software.com/article/56
then make a shell script out of that, as described at the end of this, similar, fix: https://macsupport.tuxera.com/hc/en-gb/articles/4696818610706-Help-I-can-t-mount-NTFS-volumes-on-macOS-Catalina-after-the-latest-update-
Now automate that shell script so it launches at startup: https://apple.stackexchange.com/questions/290264/run-script-as-root-at-startup-macos-10-12-sierra
you're back to automounting at startup. Works for me.
If you are using Paragon: Take the answer from platinumbob and use the following line at the end with your disk and Volume Name:
sudo /Library/Filesystems/ufsd_ExtFS.fs/Contents/Resources/mount_ufsd_ExtFS -o nodev -o noowners -o nosuid /dev/disk?s? /Volumes/???
sizza64 wrote:
I got Paragon «NTFS for Mac» working on my mac...
That will work too. It still gives you the same potential for temporarily losing access to your data on NTFS volumes after a macOS update though.
Did you check the drive identifiers with:
diskutil list
...and update the mount command in step 4 with your desired drive identifier, e.g., disk2s1?
Out of interest... I logged back in tonight and the drives all mounted (unexpectedly) without any further software or OS updates.
I have tuxera, I found this solution on their website,
I cant figure it out, didnt work with me
dialabrain wrote:
HWTech wrote:
The best solution is to temporarily transfer the data from the NTFS volume to another location…
That could be difficult to do if the drive won't mount.
Yes it could be if the user does not have a backup. Hopefully the user has access to another Mac which was not updated with a similar patch, or they also have access to a Windows system.
sizza64 wrote:
I did the command to mount my ext hd and it was working but... i reboot my mac and forced to do it again 'cause the ext Hd didn't mount again... is this problem happened on «Big» too?
Yes you will need to issue that Terminal mount command each time until the drive manufacturer provides an updated driver.
It is entirely possible Big Sur (possibly even Catalina) can have the same issue if Big Sur received the same "fix" which caused the third party driver to fail in Monterey.
You should do yourself a favor and do what @PachisCruz mentioned in the post just before your post. I highly recommend first transferring (or backing up) the data on the NTFS volume to another location first if you can read the volume just to be safe. Of course it is your computer and you can manage it as you wish.
FWIW, the security update broke Paragon's Microsoft NTFS for Mac. They will need to issue a fix.
NTFS external drives won't mount after security update 2021-003 (com.apple.DiskManagement.disenter error 49221.)
