Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: USB device not recognised (after failing to turn it bootable)

Hi,


I have a MacBook Pro (15-inch, 2017) running macOS 10.13.1 (17B48) and it can detect most USB devices successfully. However, I was busy creating two bootable USBs, which failed.

Now, my MacBook no longer shows these two USB at all, while I would like to completely wipe them and try again. It does still recognise other USBs.


It does not recognise the USBs as connected in Disk Utility (or via terminal diskutil list) but it does show up in System Information under USB devices (see difference in attached screenshots). Console shows up these entries after connecting the USB.

default 10:23:07.671863 +0100 kernel 013780.672233 SSP1@00100000: AppleUSBHostPort::forcePowerGated: kPowerStateSuspended completed with 0xe00002d6 after 1036ms

default 10:23:07.671886 +0100 kernel 013780.672261 SSP2@00200000: AppleUSBHostPort::forcePowerGated: kPowerStateSuspended completed with 0xe00002d6 after 1036ms

default 10:23:09.443934 +0100 kernel remove_purgatory_entry:6011: error 2 removing purgatory entry 3/0x2003f789a-dead for ino 8594094234

default 10:23:09.443959 +0100 kernel cleanup_purgatory_dir:16649: *** Cleaning purgatory removed 1 entries but found 1 BAD entries

default 10:23:20.356843 +0100 icdd #ICDebug - 23:{ICWiredBrowser.m} (USB Device first match)

default 10:23:20.357615 +0100 icdd #ICDebug - 388:{ICWiredBrowser.m} (10 USB Descriptions Managed)

default 10:23:20.358440 +0100 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add Mass Storage Device - 0x0/0x0/0x0 - 0x14400000 - ICDeviceDescriptionSUQuery)

default 10:23:20.407702 +0100 icdd #ICDebug - 215:{ICResourceManager.m} (00000000-0000-0000-0000-0000058F1234|Mass Storage Device|MANUFACTURER:Alcor Micro;MODEL:Mass Storage Device|SW=FALSE|)

default 10:23:20.408124 +0100 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add Mass Storage Device - 0x0/0x0/0x0 - 0x14400000 - ICDeviceDescriptionAdded)

default 10:23:20.408925 +0100 Backup and Sync #ICInfo - 506:{ICMasterDeviceBrowser.m} (Processing: Bonjour Devices:(0) && Local Devices:(0))

default 10:23:20.409082 +0100 Preview #ICInfo - 506:{ICMasterDeviceBrowser.m} (Processing: Bonjour Devices:(0) && Local Devices:(0))

default 10:23:20.420366 +0100 kernel USBMSC Identifier (non-unique): 0x58f 0x1234 0x1

default 10:23:20.424630 +0100 icdd #ICDebug - 37:{ICWiredBrowser.m} (USB Interface first match)

default 10:23:20.425442 +0100 icdd #ICDebug - 388:{ICWiredBrowser.m} (11 USB Descriptions Managed)

default 10:23:20.427079 +0100 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add Mass Storage Device - 0x8/0x6/0x50 - 0x14400000 - ICDeviceDescriptionSUQuery)

default 10:23:20.427113 +0100 icdd #ICDebug - 215:{ICResourceManager.m} (00000000-0000-0000-0000-0000058F1234|Mass Storage Device|(null)|SW=FALSE|)

default 10:23:20.428213 +0100 icdd #ICDebug - 457:{ICDDMessageCenter.m} (+Add Mass Storage Device - 0x8/0x6/0x50 - 0x14400000 - ICDeviceDescriptionUndefined)

default 10:23:20.428819 +0100 Backup and Sync #ICInfo - 506:{ICMasterDeviceBrowser.m} (Processing: Bonjour Devices:(0) && Local Devices:(0))

default 10:23:20.428941 +0100 Preview #ICInfo - 506:{ICMasterDeviceBrowser.m} (Processing: Bonjour Devices:(0) && Local Devices:(0))

default 10:23:20.554682 +0100 trustd could not enable test hierarchy: no UAT pinning preferences set

Is there any possibility of (detecting and) just wiping/resetting this USB via my MacBook?

Note: I do connect them via a USB A > USB C sitecom adapter, but it hasn't resulted in any problems before (or with other, non-failed-bootable USBs), it seems unlikely to me that this would be the cause.

Kind regards,

Isaiah van Hunen

User uploaded fileUser uploaded file

MacBook Pro TouchBar and Touch ID, macOS High Sierra (10.13.1), null

Posted on

Reply

There’s more to the conversation

Read all replies

Page content loaded

Nov 14, 2017 7:02 AM in response to tjk In response to tjk

Not on another Mac, no, but I have on a Windows computer. Windows did list the USB, but was unable to format it "First insert the drive" - it was just confused and couldn't read/write properly. My assumption always was that you can always 'hard-erase/format' a USB and get it working again, but apparently these are bricked beyond repair>

Nov 14, 2017 7:02 AM

Reply Helpful
User profile for user: IsaiahvanHunen

Question: USB device not recognised (after failing to turn it bootable)