Перейти к основному содержанию

Model A1418 / Late 2012 / 2.7 & 2.9 GHz Core i5 or 3.1 GHz Core i7 Processor

212вопросов Показать все

Bootable usb key not showing up.

Dear Community,

Tricky case here that will please the experts and will challenge them.

I bought 2 usb keys that are known to be really fast. 1 is Kingston Data Traveler Max, 256 GB, with write and read speed of respectively 1000/900 Mbs. The other one is Transcend ESD310C 256 GB with similar performance. This last one is a duo (both USB A and USB C) while the first one is only USB A (USB C exists and I have one as well).

The DT Max is sold as a USB pendrive or key, while the ESD310C is sold as an SSD. But I think that both have the same technology. Whatever it means, mac Os sees them as non-removable SSDs and not as removable usb keys.

I can format, partition and create as many bootable volumes as I want with both keys, exactly as I did with a "real" usb key (Sandisk Ultra Dual Drive Pro) and this is working fine, in a nutshell.

Problem is: once this is done and I try to boot on any of these volumes, they are just not showing up. While those on the Sandisk appear as expected.

I also noticed with the DT Max some latences while I was using createinstallmedia command in Terminal that I never face with a standard usb key or even an external SSD (did the test as well with Sandisk Extreme Pro).

It looks like mac Os does not figure out whether it is facing a usb "protocol" or an SSD "protocol" (dunno which term to use here) and result is that I cannot boot on any of those two devices. While I perfectly see and manipulate the content in either Terminal or Disk Utility. I have to admit that this is driving me crazy.

Anyone facing the same kind of issues with similar devices? More important, anyone with at least an explanation and/or, even better, a fix?

Thanks a bunch for your help, buddies.

Update (12/11/23)

Quick update here: I wrote an email to Kingston support explaining the issue. Will try to do the same to Transcend.

Regarding Kingston, other consumers reported same issue with external SSD XS2000 model.

Will update this post upon answer reception if ever.

Update (12/12/23)

Received answer from Transcend: « Apple’s fault ». Great…

Now while driving to the office this morning, was just thinking that the Mac was not able to mount the EFI partition from the usb at startup. Cannot be any other root cause I guess. Question is: why?

I know this little utility called mountEFi on Mac Os, will try to check what’s inside after the bootable creation process. And will check as well if my Ventoy key is visible at least on the boot menu on Mac, as I created it using exFat for the standard partition and considering the VTOYEFI partition is Fat32.

By the way I will check which format the EFI partition created on Mac by the createinstallmedia command is

Just read Wiki page for EFI definition and use, specifically for Mac Os. My assumption here above may not be correct as it is said that bootloader is not stored in the EFI partition… 😕

Отвечено! Посмотреть ответ У меня та же проблема

Это хороший вопрос?

Оценка 2
Добавить комментарий

2 Ответов

Выбранное решение

Epilogue: Kingston answered that the use of their devices as bootable media is not supported…

Probably the reason why I can create as many bootable keys as I want for whatever Windows or Linux distro without an issue. I won’t answer as I am not in charge of educating Kingston Support on their own products.

As expected, macOS cannot see the Ventoy key on boot menu and EFI partition created with createinstallmedia command is empty.

So that’s all folks. As frustrating as it can be I just have to accept that both brands are not reliable in my use case. Would have liked knowing it before buying.


Был ли этот ответ полезен?

Оценка 1
Добавить комментарий
Наиболее полезный ответ

Did you install the needed system files onto the USBs? You need to use the correct macOS the system requires

Был ли этот ответ полезен?

Оценка 2

17 Комментариев:

Yes, of course. I’ve been doing bootable usb keys for mac Os for almost 15 years.


@timbleking - You maybe facing a file system issue. Apple now has two file systems! HFS+ and now APFS. Depending on the given system you may not be able to use the newer APFS volumes.

First make sure the system (in this case a 2012 iMac) is updated to the highest supported version.


Yes Sir, did that already, everything aligned.


@timbleking - I just had a thought did you enable encryption on the system drive that will disable external boot up.


Hum…not as far as I know. And if that was the case, how come it would work with either the Dual Pro and the Extreme, and not with the DT and ESD?


Показать 12 больше комментариев

Добавить комментарий

Добавьте свой ответ

Timbleking будет вечно благодарен.
Просмотр статистики:

За последние 24часов: 0

За последние 7 дней: 1

За последние 30 дней: 4

За всё время: 134