- Joined
- Apr 20, 2013
- Messages
- 53
- Motherboard
- Asus P8Z77-V PRO/THUNDERBOLT
- CPU
- Core i7-3770K
- Graphics
- EVGA Nvidia GeForce GT 740 SC
- Mac
- Classic Mac
- Mobile Phone
Hello,
I am using a hackingtosh currently running MAVERICKS to create a USB stick to install EL CAPITAN.
I use for this UNIBEAST 6.0.
I have made severals attempts to create the stick, all successfull from a Unibeast perspective, but providing each time the same result : The USB stick is unable to boot the system (Can't find /mach_kernel).
I searched the site for such issue and notice it is related to a change in chameleon between MAVERICKS and YOSEMITE. However, I am still under MAVERICKS, and the mentionned flag to remove in chameleon.org.plist does not exists in my file.
So I start thinking the issue was not this one.
I restart the USB stick creation process with terminal, Disk Utility and console open to scan what exactly happens during stick creation process. I was able to notice that USB stick is hosting 2 partitions by the end of process, both resulting in a drive poping in Finder : USB and EFI.
I walk through EFI from finder and find the clover structure that should allow proper boot. Therefore, I was thinking the stick was OK. Nevertheless, I switched to Disk Utility to check the USB stick. There, was the difference. Disk Utility is not detecting the EFI volume hosted on USB stick. Worse, when I scanned the USB stick for errors, Disk Utility detected a partition map errors and advise to fix errors.
So I click the Repair button, but then no more EFI volume, and boot prove inefficent, USB stick cannot boot.
Does someone knows about this issue ? Am I the only one to face it ?
Hereunder the log extract from Disk Utility when it detected the partition map error.
I am using a hackingtosh currently running MAVERICKS to create a USB stick to install EL CAPITAN.
I use for this UNIBEAST 6.0.
I have made severals attempts to create the stick, all successfull from a Unibeast perspective, but providing each time the same result : The USB stick is unable to boot the system (Can't find /mach_kernel).
I searched the site for such issue and notice it is related to a change in chameleon between MAVERICKS and YOSEMITE. However, I am still under MAVERICKS, and the mentionned flag to remove in chameleon.org.plist does not exists in my file.
So I start thinking the issue was not this one.
I restart the USB stick creation process with terminal, Disk Utility and console open to scan what exactly happens during stick creation process. I was able to notice that USB stick is hosting 2 partitions by the end of process, both resulting in a drive poping in Finder : USB and EFI.
I walk through EFI from finder and find the clover structure that should allow proper boot. Therefore, I was thinking the stick was OK. Nevertheless, I switched to Disk Utility to check the USB stick. There, was the difference. Disk Utility is not detecting the EFI volume hosted on USB stick. Worse, when I scanned the USB stick for errors, Disk Utility detected a partition map errors and advise to fix errors.
So I click the Repair button, but then no more EFI volume, and boot prove inefficent, USB stick cannot boot.
Does someone knows about this issue ? Am I the only one to face it ?
Hereunder the log extract from Disk Utility when it detected the partition map error.
2015-10-27 21:58:11 +0100: Verifying partition map for “SanDisk Cruzer Blade Media”
2015-10-27 21:58:11 +0100: Starting verification tool:
2015-10-27 21:58:11 +0100: Checking prerequisites
2015-10-27 21:58:11 +0100: Checking the partition list
2015-10-27 21:58:11 +0100: Checking for an EFI system partition
2015-10-27 21:58:11 +0100: Checking the EFI system partition’s size
2015-10-27 21:58:11 +0100: Checking the EFI system partition’s file system
2015-10-27 21:58:11 +0100: Problems were found with the partition map which might prevent booting
2015-10-27 21:58:11 +0100: Error: The partition map needs to be repaired because there’s a problem with the EFI system partition’s file system.
2015-10-27 21:58:11 +0100:
2015-10-27 21:58:11 +0100: : The partition map needs to be repaired because there’s a problem with the EFI system partition’s file system.
2015-10-27 21:58:11 +0100:
2015-10-27 21:58:27 +0100: Verifying and repairing partition map for “SanDisk Cruzer Blade Media”
2015-10-27 21:58:27 +0100: Starting repair tool:
2015-10-27 21:58:27 +0100: Checking prerequisites
2015-10-27 21:58:27 +0100: Checking the partition list
2015-10-27 21:58:27 +0100: Adjusting partition map to fit whole disk as required
2015-10-27 21:58:27 +0100: Checking for an EFI system partition
2015-10-27 21:58:27 +0100: Checking the EFI system partition’s size
2015-10-27 21:58:27 +0100: Checking the EFI system partition’s file system
2015-10-27 21:58:27 +0100: Repairing the EFI system partition’s file system
2015-10-27 21:58:27 +0100: Creating a new EFI system partition
2015-10-27 21:58:29 +0100: Checking all HFS data partition loader spaces
2015-10-27 21:58:29 +0100: Checking booter partitions
2015-10-27 21:58:29 +0100: Reviewing boot support loaders
2015-10-27 21:58:29 +0100: Checking Core Storage Physical Volume partitions
2015-10-27 21:58:29 +0100: Updating Windows boot.ini files as required
2015-10-27 21:58:29 +0100: The partition map has been repaired
2015-10-27 21:58:29 +0100: