terminal – The disk wasnt ejected as a result of a number of applications could also be utilizing it

MacBook Air m1 8/256

Sequoia 15.1

Exterior nvme ssd Kingston NV2 [SNV2S/1000G], APFS

Ugreen 40gbps ssd enclosure

Connecting on to the laptop computer by included with the enclosure cable

This concern was current earlier than on Sonoma or Ventura, however appeared like 2-3 instances inside 6 months. It didn’t hassle me in any respect. After I up to date to Sequoia I principally haven’t been in a position to eject my drive with out this error.

Im making an attempt to eject from finder sidebar, from areas, from desktop – nothing.

I power give up all purposes – nothing.

Highlight index
At first an error with highlight index induced this, however it mounted itself someplace within the strategy of rebuilding the index after i reinstalled Sequoia from restoration. [I left my macbook to do all its post-update things for 10 hours, it rebuild the index and synchronized everything].

QuickLook
The identical error, now attributable to quicklook processes. Discovered an answer:

1. «lsof | grep /Volumes/drive1».

• If it says one thing about quicklook, I do «killall -9 QuickLookSatellite» or «/usr/bin/killall -KILL QuickLookUIService»

Finder
At this level ive already spent hours coping with this drawback. Discovered the answer – «killall -KILL Finder». It helped.

Restating
Restarting the Macboook with out ejecting the drive. Once I log in and shortly open finder to eject from sidebar I get the error, however then the drive efficiently ejects.

Right now
Right now was totally different as a result of nothing from above helped.

Ive additionally tried:

1. «diskutil unmount /Volumes/drive1»

• terminal says «Quantity drive1 on disk5s1 didn’t unmount»

2. Disk utility mount / unmount button is non-intractable with «Bodily disk», intractable with «Container» and «Quantity». Im urgent unmount on each: Did not unmount “drive1” as a result of it’s at the moment in use.

Some extra information

• Disk Utility First Support didnt discover any points
• There aren’t any different drives related
• Drivedx doesnt present any points with the drive – every thing is 100% besides from temperature, however temperature remains to be okay. There aren’t any error logs.
• when i reconnect the drive after ejecting it, i wait and attempt to eject it once more. typically the drive ejects efficiently the second time, typically it doesn’t. more often than not this error seems when the drive has been related for 10-30-60min or extra.
• earlier than this concern appeared my drive was disconnecting after macbook went to sleep. i suppose the laptop computer simply stops giving it energy. however now even after leaving it sleep for a few hours the drive didnt disconnect. no concept if this has something to do with the difficulty.
• When unable to eject system logs say:

• Kernel – disk5s1: gadget shouldn’t be readable.
• Diskarbitrationd – unmounted disk, id = /dev/disk5s1, ongoing.
• Diskarbitrationd – unmounted disk, id = /dev/disk5s1, failure.
• Diskarbitrationd – unable to unmount /dev/disk5s1 (standing code 0x00000010).
• Kernel – print_unknown_ioctl:17066: disk5s1 unknown ioctl _IOW(‘X’, 2, 48) (0x80305802), pid = 4143

Dont inform me to do that
The ONLY factor that ALWAYS helps is to show off after which bodily disconnect the cable. However doing this tens of instances per day is driving me loopy. I additionally don’t wish to Pressure Eject.

ChatGPT
It helped earlier than. Here’s what it really helpful that i havent tried but. [I have no idea what is single-user mode, sip or disk identifier. If you think i shouldnt do something from this list please tell me].

1. Reboot in single-user mode, then “/sbin/mount -uw /diskutil unmountDisk /dev/disk5”
2. Attempt totally different cable / totally different port
3. Examine and disable SIP: Boot into restoration, then “csrutil standing”, then disable it.
4. Unmount utilizing Disk Identifier: “sudo diskutil unmountDisk power /dev/disk5”
5. Reset NVRAM
6. Join the drive to a different macbook to see if the difficulty is drive-specific

Im not skilled. The whole lot that I’ve tried has been discovered on the web, this discussion board particularly (because of everybody right here btw!), and likewise with ChatGPT.

The principle frustration is: every time i see this error its for a distinct purpose. And i’ve an enormous checklist of troubleshooting steps to undergo EACH TIME to try to repair it. “Simply works” they stated …

When you’ve got any questions, need any additional information or logs, screenshots – please ask, i’ll present something you want.