Does not recognise any drive on Mac OS X El Capitan #46
Comments
|
What filesystem is your usb thumbdrive formatted as? If it's ntfs, it will not be listed (if I recall correctly). This issue is discussed further here. |
|
That was indeed the issue. After formatting to fat32 I can now select the disk. Thanks |
|
@Joris-van-der-Wel you should close this although it would be better if the system notified the user somehow rather than just loading an empty list |
|
How exactly do you you format to fat32 in El Capitan? Disk Utility provides FAT and ExFat as options, but no fat32. |
|
I think I just used windows to format it (when I got home) |
|
Yes, that was also the only thing what worked for me finally, after I tried many times different formatting methods with diskutil and Disk Utility app on mac. |
|
I've formatted the USB stick as FAT32 in my Windows env, however I still cannot get it to be detected in unetbootin on mac. Is there an older version that you used, or the latest? |
|
@timrettop are you certain it's formatted as FAT32, not exFAT or so? anyhow, if you are certain it is actually formatted as FAT32, you could try the targetdrive option as described at https://sourceforge.net/p/unetbootin/wiki/commands/ so once you have determined which drive you want (run (replacing /dev/disk2s1 with the USB drive) |
|
This is still an issue. I am using OSX El Capitan (10.11.6) and I have tried formatting my USB thumb drive using Disk Util and Windows itself as FAT32. The drive is not appearing in the list. When attempting to run UNetbootin from the command line, the GUI launches and the same problem occurs. |
|
In actual fact, the following command seems to be doing something What I am trying to do is create a bootable usb so I can install Windows 8.1 on my Intel NUC 6i5YSK. ... and it seems UNetbootin has hung having extracted 506 of 2096 files. |
|
This Yosemite Disk Utility patched to work on El Capitan helped with me: http://www.insanelymac.com/forum/files/file/480-disk-utility-patched-v2 Apparently the El Capitan Disk Utility FAT-formatting does something Unetbootin doesn't like. |
|
I was able to get the USB installer disk made but when I booted into it, I couldn't get the installer to work. There could be hundreds of reasons why this was happening. What I ended up doing was using bootcamp assistant on an older iMac, where you can create a USB install from a Windows 8.1 iso and it worked perfectly. |
|
I figured out if you rename the USB stick to |
|
Mahdisadjadi Dude you just helped me out. I was really frustrated, trying to figure out why unetbootin would not recognize a USB drive I am formatting to use for an ESX5.0 install (testing legacy VMs..ugh) and your steps were the ONLY ones that worked, after trying dozens. |
|
@Mahdisadjadi holy smokes, that worked for me too. wth? Thanks for the tip! |
|
I would argue this issue should be re-opened. I can confirm that formatting as FAT32 on Windows 10 did NOT make the drive recognizable. Only following the instructions in #46 (comment) solved the issue. |
|
New issue filed @crw. |
|
@crw , @Mahdisadjadi , do you guys still have the USB drives you used for this? Can you confirm that if they are NOT named with "FAT" or "Microsoft" in the drive name, they do not appear on the drop down menu for unetbootin? If they do not appear, could you please run and paste the results of the commands "diskutil list" and "system_profiler SPStorageDataType" in Terminal? I'm trying to figure out if there is an alternative to the way that unetbootin currently determines whether a drive is FAT formatted on Macs that would address your issues. |
|
Confirmed that renaming the same USB to "FUBAR" made it not show up in the list. I renamed the drive FAT32 before running the following commands. I hope this helps! |
|
This is helpful. I think I coded up a fix, but I'm having trouble with the build process of the app, so I'm going to need to do some more digging - may take a few days. Once I do get it built, I may ask you to test it out (since I can't reproduce the issue myself and will only be able to test a happy path situation). |
|
@michaelqyee what issue are you having with the build process? do the instructions at https://sourceforge.net/p/unetbootin/wiki/compile/ not work? (I updated the OSX build section with the version of Qt I use for static builds, as qt4's default installer doesn't work on some newer versions of OSX) |
|
@gkovacs I'll preface this by saying I have never built a Mac application before, so some of this experience is conflated with my own inexperience. I was following the Statically Linked Version instructions for Mac OSX on the link that you provided. Because I'm running on El Capitan, I wasn't able to install qt-mac-carbon-opensource-4.7.2.dmg, so I instead used Homebrew (brew install qt4). I modified the qmake-mac and build-mac scripts to reference the qt libraries installed by Homebrew, and when I ran the ./build-mac script, it threw warnings about creating objects that had conflicting versions (10.5 vs 10.7). I then modified g++-macx.conf to change the -mmacosx-version-min flag to 10.7 instead of 10.5, which eliminated those warnings. After that, the build ran successfully without errors, but the application created was recognized as incomplete. I think this is because the actual executable isn't created for me: This is the build output (after increasing the verbosity of g++): I will go ahead and revert everything except for my changes and try again with the version of Qt you provided, but please let me know if you see anything awry with my approach. |
|
@michaelqyee yeah don't use homebrew's version of qt4 because the builds it creates aren't statically linked (ie, they won't run on systems that don't have Qt4 installed). I believe I actually use the g++ from XCode's Command Line Tools not the one installed by homebrew, I suspect that might be the issue. I updated the build instructions again on the wiki, hopefully those instructions should work? |
|
@gkovacs sorry for the delay. I had some issues with the qt archive you provided; my computer was complaining about the object files not being compiled for the correct processor type (i386 vs x86_64), so I deleted all of the object files and recompiled. During the make step, though, I realized that the Makefiles for the WebKit stuff never got remade. Do you have any tips on how to regenerate those Makefiles (e.g., qt4-mac/src/3rdparty/webkit/Source/Makefile.WebKit)? At first glance, it doesn't seem to be connected to the configure script in the qt4-mac directory, but I could be wrong. |
|
I formated my usb stick with Disk Utility to |
|
@gkovacs I'm still having trouble with the build process - I'm unable to create the qt4 artifacts. I could just submit the code changes I have without testing, but that seems irresponsible. Are you opposed to changing to qt5? I can try it out to see if it helps; the process seems to be fairly straightforward: https://wiki.qt.io/Transition_from_Qt_4.x_to_Qt5. |
|
@gkovacs This is still an issue. You need to change the name of the USB stick to "FAT32", then it will be recognized by unetbootin. This issue should not be marked as "closed". |
|
This issue still affects the official build, unetbootin-mac-625.dmg, available from the UNetbootin web site homepage. On OS X 10.11.6 (El Capitan) UNetbootin 625 did not recognize my FAT32, GUID scheme flash drive until I renamed that drive "FAT32". |
|
Works for me, tried it with MBR (probably works with guid too according to comments above) partitions and MS-DOS (FAT) for the USB device from the OS X Disk Utility, this formats the partition as FAT32. Also, the partition name has to be in upper case. After that the USB device shows up in unetbootin for OS X (Sierra, 10.12.2). Tested with unetbootin-mac-625.dmg. |
|
Worth noting that ExFAT is detected fine as long as I use GUID partition map. |
|
I reformatted my drive with Disk Utility (MS-DOS (FAT) with GUID scheme) and for good measure renamed the disk "FAT32", but I had to restart UNetbootin in order for the disk to be recognized. |
|
renaming the disk "FAT32" worked for me as well. |
1 similar comment
|
renaming the disk "FAT32" worked for me as well. |
|
Following @Mahdisadjadi's advice fails with error message "could not open device" and corrupts my USB on macOS Sierra 10.12.4. Formatting to exFAT with GUID scheme and all-caps name worked for me |
|
Yeah, "FAT32" does the trick! 🎉 |
|
I was having trouble with same thing.Even though I formatted so many times, problem still persisted. Then I tried complete Format on my USB in FAT32 mode (DONOT QUICK FORMAT). After that everything worked perfectly but yeah @Mahdisadjadi`s renaming does work too. |
|
I've made countless tries based on the suggestions above with microSD card inserted into Mac's internal card reader. No success at all. After using External USB card reader unetbootin 647 finally found the drive. |
|
Internal card readers show themselves differently than external ones. Internal ones actually present themselves as card readers ( |
|
I created an internal partition on my macbook 2016 with FAT32 format, but it was not recognized in unetbootin, even it was named to "FAT32". How can I get it to work? |
|
@supersugerlo you can use the targetdrive option if you know which drive letter it is https://github.com/unetbootin/unetbootin/wiki/commands#targetdrive it doesn't show the internal drives intentionally in the dropdown menu to ensure that people don't accidentally nuke their bootcamp installs |
|
I've tried out all of above suggestions here to recognise the USB in Unetbootin (inc. naming USB "FAT32", GUID scheme and erasing as MS-DOS FAT) in my mac OS 10.10.5 but none work. As a non technical user I'm confused by https://github.com/unetbootin/unetbootin/wiki/commands#targetdrive |
|
I also tried doing this on Windows10 machine but couldn't get it to work there either. |
|
As @Eugenius73094 said, in OSx 10.10.5 it won't detect the drive even if the stick is renamed to FAT32. What did work for me though was launching unetbootin from the command line and specifying the target drive by parameter, something like this: /Users/kperdomo/Desktop/unetbootin.app/Contents/MacOS/unetbootin installtype=USB targetdrive=/dev/disk2s2 where /dev/disk2s2 is the stick's device name |
|
I am using OSx 10.11.6, El Capitan, and only @kperdomo's command line parameter passing worked for me, none of the others did. |
|
I think if you name your drive "External FAT", you'll be able to see your external drive. I submitted a pull request that I believe will fix this here: 5759172 |
|
Using "External", with ExFAT has been the only method I have been able to get working.
|
and others
The drive list remains empty. Mounting / Unmounting the thumbdrive (before launching unetbootin) does not make a difference.
The text was updated successfully, but these errors were encountered: