Both hard drives are not recognized on 2 M1 Macs (M1 Pro Macbook, M1 Mac mini). My goal is for the drives to use NTFS because I also deal with Windows machines. Installed on the macs is Paragon NTFS For Mac M1 Version.
I have determined that the above mentioned app is not the issue. Sometimes, when connecting either drive, one of 2 scenarios occur. Either nothing will happen at all but checking System Report shows the drive under USB with the correct voltage, or I get a message saying the connected drive cannot be read with options to Initialize, Eject, or Ignore. Choosing Initialize opens Disk Utility where the drive is shown. After making sure to enable "Show All Devices", I run First Aid on the SSD and it is successful. However the Erase function fails every time. Most times I get "Wiping volume data to prevent future accidental probing failed. : (-69825)". A few times I get something about an I/O error. This is despite trying different formats (NTFS, APFS, etc).
The firmware is up to date on both drives and security is disabled. The drives run fine under Windows 11. Other troubleshooting steps I have tried:
Uninstall/Reinstall NTFS For Mac
Reboot MacBook Pro
Trying different ports and cables
Connecting SSD to Win11 PC and performing initialize/cleaned using diskpart utility.
Verified that both SSD's can be accessed and used in Windows using NTFS
Attempts using macOS Terminal vs Disk Utility produce the same results. Connecting a USB flash drive works fine on both Mac and Windows. At this point I am led to believe there is either something going on with the drives or macOS Monterey, but I am now at a point where I cannot isolate the problem. Have others experienced this? If so, what worked for you? I'm not sure where to go from here.
I have the same mounting issue with my Samsung SSD T7. It mounted under Big Sur, but with macOS Monterey, it will no longer mount, even when using Disk Utility. (I'm running OS 12.3.1)
I've tried different cables, and USB ports. The issue is obviously a software compatibility or firmware problem.
