usb – Easy methods to troubleshoot an (HFS+) exterior drive now not being detected by macOS Catalina
I’ve an exterior USB drive that makes use of HFS+ and it labored nice for greater than a yr till a number of days in the past. Final week, I received the error Drive was not ejected correctly … 2 instances. It nonetheless labored nice when it was eliminated and re-plugged to the USB port. I did not do a filesystem test / restore via Disk Utility because it continued to work nice. Now, macOS Catalina simply refuses to detect the drive in any respect.
The troubleshooting I’ve achieved thus far:
- Test in Disk Utility – the drive shouldn’t be proven.
- Test with
diskutil listingcommand in Terminal – the drive would not seem within the listing. - Test in System Data > USB part – the drive is not proven linked.
- Use a distinct USB cable with the disk drive – no change; drive continues to be not detected.
- Test if all of the USB ports work with one other pen drive – all work nice.
- Repeat step 1 to three in Secure Mode – the drive shouldn’t be detected in Secure Mode too.
- Go to Restoration Mode and test with
diskutil listingcommand – the drive is not listed. - Take away all USB units besides keyboard, mouse and the drive – disk nonetheless not detected.
- Reset PRAM – nonetheless no drive detected.
- Reset SMC – nonetheless no drive detected.
- Run
sudo diskutil exercise– no messages generated when drive is plugged and unplugged. - Test in Console. Log when drive is plugged to USB port:
default 21:31:08.504203+0530 icdd Added | [USB][ Game Drive ] ( 0, 0, 0) @ 0x14500000 |
default 21:31:11.798926+0530 kernel Discover – new kext com.apple.driver.usb.AppleUSBHostPlatformProperties, v1.2 matches prelinked kext however cannot decide if executables are the identical (no UUIDs).
default 21:31:11.848612+0530 icdd Inferior | [USB][ Game Drive ] ( 8, 6,50) @ 0x14500000 |
default 21:31:11.845199+0530 kernel USBMSC Identifier (non-unique): 57583832453130394E32544B 0x1058 0x262f 0x5002, 3
default 21:31:53.212439+0530 kernel USB machine 1058262F14500000 – BOT reset accomplished with kIOReturnTimeout.
default 21:31:53.513587+0530 kernel USB machine 1058262F14500000 – might be reset!
default 21:31:54.881092+0530 kernel USB machine 1058262F14500000 – fConsecutiveResetCount = 1.default 21:31:54.883295+0530 icdd [Removed] | [USB][ Game Drive ] ( 0, 0, 0) @ 0x14500000 |
default 21:31:54.883424+0530 icdd [Removed] | [USB][ Game Drive ] ( 8, 6,50) @ 0x14500000 |
default 21:31:54.882997+0530 kernel IOUSBMassStorageResource: dangerous busy depend (0,-1)
Backtrace 0xffffff80009fe8a6 0xffffff7f81a03436 0xffffff8000a2a5de 0xffffff8000a01894 0xffffff8000a0bd87 0xffffff80002c113e 0x0
default 21:31:54.883028+0530 kernel com.apple.iokit.IOUSBMassStorageDriver(157.140.1)[61A8ACED-1488-36C8-9B78-47B81C0653D4]@0xffffff7f81a01000->0xffffff7f81a34fff
default 21:31:54.883050+0530 kernel dependency: com.apple.iokit.IOUSBHostFamily(1.2)[132A3039-5B42-38C4-A6DB-F450EAE64E0C]@0xffffff7f80f7c000
I additionally observed that in the course of the interval when the method icdd says “Added” after which “Eliminated” (after a couple of minutes), VMWare reveals the USB disk drive briefly in its USB listing (even when macOS reveals no traces of it).
What ought to I do subsequent? I haven’t got entry to a different system proper now however I can most likely create a USB Linux stay disk and boot into it to test the drive (however then, I can even should ponder what is the level of utilizing macOS in any respect if I want to show to a different OS …? :).
