Contribute
Register

USB fails to create, ->10.11.4+ Skylake Starter Guide

Status
Not open for further replies.
Joined
Nov 12, 2016
Messages
30
Motherboard
GA-B150M-DS3H
CPU
i3
Graphics
Nvidia + Intel
Mac
  1. MacBook Pro
  2. Mac mini
Classic Mac
  1. PowerBook
Mobile Phone
  1. iOS
Hello,
Trying to follow
10.11.4+ Skylake Starter Guide ---> Multibeast. [AND Unibeast, same thing!]
GA-B150M-DH3, install USB on a Macbook Pro Core Duo running Yosemite.
Ticked Clover UEFI bootmode in Bootloaders.

But USB fails to create with:

Clover EFI installer log - Sun Nov 20 17:49:09 EET 2016
Installer version: v2.3k r3423 EFI bootloader
======================================================
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *256.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS MacBkSSD 255.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *32.0 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS uuu 31.7 GB disk1s2
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *6.8 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_HFS OS X Install ESD 6.5 GB disk2s2
/System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) not loadable (reason unspecified); check the system/kernel logs for errors or try kextutil(8).
mount_msdos: msdos filesystem is not available

ERROR: can't mount ESP partition (disk1s1) !
Check that the partition is well formated in HFS or Fat32.

To format as HFS use command like:
sudo newfs_hfs -v EFI /dev/rdisk1s1
 

Attachments

  • Clover_Install_Log.txt
    1.6 KB · Views: 156
Last edited:
/System/Library/Extensions/msdosfs.kext failed to load - (libkern/kext) not loadable (reason unspecified); check the system/kernel logs for errors or try kextutil(8).
mount_msdos: msdos filesystem is not available

Running in safe mode?
 
No safe mode, just normal Yosemite

Something is damaged with that install then... clearly, it is having trouble loading msdosfs.kext (not available in safe mode).

Without msdosfs.kext, you cannot mount FAT32 partitions such as the EFI partition.
 
Oh, dear... sigh
How do I repair then?
msdosfs.kext is indeed in /System/Library/Extensions....

So ein Mist!

MacBook-Pro-2:Extensions spyros$ sudo kextutil -t msdosfs.kext

Diagnostics for /System/Library/Extensions/msdosfs.kext:
Code Signing Failure: code signature is invalid
ERROR: invalid signature for com.apple.filesystems.msdosfs, will not load
 
Last edited:
Oh, dear... sigh
How do I repair then?
msdosfs.kext is indeed in /System/Library/Extensions....

What is the output of:
Code:
sudo touch /System/Library/Extensions && sudo kextcache -u /
 
sudo touch /System/Library/Extensions && sudo kextcache -u /

msdosfs.kext has invalid signature; omitting.


@#ARGHH W.T.Kext..
 
msdosfs.kext has invalid signature; omitting.


@#ARGHH W.T.Kext..

You patched it, but are not booting with kext-dev-mode=1.
 
You patched it, but are not booting with kext-dev-mode=1.
Not to my knowledge! no patch installed. What do you mean 'not booting'?
How can I boot a MacBook Pro with 'kext-dev-mode=1"?
 
Not to my knowledge! no patch installed. What do you mean 'not booting'?
How can I boot a MacBook Pro with 'kext-dev-mode=1"?

kext-dev-mode=1 is a kernel flag that allows you to use patched/unsigned kexts.
Some kext installer tools see it fit to patch msdosfs.kext without your permission.
On a real Mac, you set kernel flags in nvram (boot-args).
Suggest you restore msdosfs.kext to vanilla if you didn't intend on patching it.
 
Status
Not open for further replies.
Back
Top