I have been having this issue with my two Western Digital external HDDs (exFAT formatted) since I upgraded my MacBook Air M1 to Sonoma, but I could find two workarounds and one fix (not ideal, but seems to be working). As this laptop suffers from scarce USB-C ports, I have been connecting these drives via a Baseus 6-in-One USB hub.
I recommend you who still can't access your external drives to try one of these and see how they work for you.
It seems that MacOS actually had unknown issues mounting the drives. The system does acknowledge there's a drive inserted in one of its USB ports, but isn't mounting the drives immediately as it should.
Workaround #1: case you have a Windows machine laying around, plug your device to it. Windows will give an alert saying 'the unity is damaged. Do you want to repair it?'. Accept the scan. It can take some time, depending on your drive size. My 2TB unit takes around 10 minutes. My 5TB one takes around 30. Can be still faster than workaround #2, depending on your drive size
Workaround #2: for whatever the reason, as soon as MacOS gives up mounting the drive, it begins a scanning proccess running in the background (which you can watch by typing 'ps aux | grep fsck' at the Terminal). My Terminal gives me two lines as the answer, and one of them ends with '/dev/rdisk4s1' (rdisk4s1 is probably the drive id, yours can be different) - that line contains the exact time count of that scanning proccess.
When this background scan finishes, the drive will mount. It might take a lot of time. My 5TB drive takes almost one hour until it mounts. But in the end it will and you can use your drive as usual.
Both these workarounds aren't practical if you work with your Mac. But feel free to try. If they worked for me, chances are they'll work for you too.
Now, the fix. This one did it for me for good:
- Apple Icon > System Settings. At 'Privacy & Security' tab, look for 'Allow Accessories to Connect'. Set it to 'Automatically when unlocked'. Try connecting the drive again. Should work.
Good luck!
And please, Apple, solve this next update! This is just too frustrating.