- Joined
- Nov 3, 2013
- Messages
- 84
- Motherboard
- Ga-Z390-AORUS-PRO
- CPU
- i9-9900K
- Graphics
- RX 580
- Mac
- Mobile Phone
I am getting the same thing" Raid disk" in Chimera for my Yosemite disk. has anyone found a fix for this?
Anyone else getting the "raid" mark on their boot drive?
- Thread starter JoeStorm
- Start date
- Status
- Joined
- Jul 21, 2011
- Messages
- 22
- Motherboard
- Gigabyte Z68X-UD3H-B3 UEFI BIOS
- CPU
- Intel Core i7 2600K
- Graphics
- Intel HD 3000 Integrated
- Mac
- Classic Mac
- Mobile Phone
Still searching for a fix...
Another thread is currently active:
http://www.tonymacx86.com/yosemite-...sd-not-recognized-bootable-after-install.html
Another thread is currently active:
http://www.tonymacx86.com/yosemite-...sd-not-recognized-bootable-after-install.html
- Joined
- Jan 24, 2011
- Messages
- 310
- Motherboard
- GA-Z77-DS3H
- CPU
- i5-3570K
- Graphics
- RX 580
- Mac
- Mobile Phone
any other drives plugged in? I had it too but I had 4 HDD plugged in while upgrading. I unplugged all the SATA's except my SSD, reformatted and installed again and it worked fine. After I did multibeast I plugged other drives in.
Just a heads up since you have SSD.
When you do finally get it going, something might be up with multibeasts trim enabler. I was getting a gray screen on reboot with a circle and a line through it when I install TRIM from multibeast.
Just a heads up since you have SSD.
When you do finally get it going, something might be up with multibeasts trim enabler. I was getting a gray screen on reboot with a circle and a line through it when I install TRIM from multibeast.
- Joined
- Jul 21, 2011
- Messages
- 22
- Motherboard
- Gigabyte Z68X-UD3H-B3 UEFI BIOS
- CPU
- Intel Core i7 2600K
- Graphics
- Intel HD 3000 Integrated
- Mac
- Classic Mac
- Mobile Phone
Only have one SSD drive plugged in.
Thanks for the Trim hint, I normally use Trim Enabler from Cindori software. I will try it as soon as I'm able to boot directly from my SSD.
Thanks for the Trim hint, I normally use Trim Enabler from Cindori software. I will try it as soon as I'm able to boot directly from my SSD.
- Joined
- Jul 21, 2011
- Messages
- 22
- Motherboard
- Gigabyte Z68X-UD3H-B3 UEFI BIOS
- CPU
- Intel Core i7 2600K
- Graphics
- Intel HD 3000 Integrated
- Mac
- Classic Mac
- Mobile Phone
I am now able to boot on the SSD by using the EFI partition for the boot loader and /Extra folder:
http://www.tonymacx86.com/yosemite-...-not-recognized-bootable-after-install-3.html
http://www.tonymacx86.com/yosemite-...-not-recognized-bootable-after-install-3.html
- Joined
- Nov 3, 2013
- Messages
- 84
- Motherboard
- Ga-Z390-AORUS-PRO
- CPU
- i9-9900K
- Graphics
- RX 580
- Mac
- Mobile Phone
Ok i found a way to fix this problem. Install Yosemite as normal. If you get the "Raid" on your Yosemite disk, boot into a working backup disk (assuming you have one). Next make an image of the Yosemite disk. Now erase and repartition the Yosemite drive. Then your going to reimage the Yosemite drive with the image you made earlyer. now boot to the USB Installer drive and you will notice the "Raid" is now gone from the Yosemite drive. Select the Yosemite drive and it will boot up just fine. Then run Multibeast and your done.
- Joined
- Oct 9, 2012
- Messages
- 12
- Motherboard
- ASUS Sabertooth X79 UEFI BIOS v.4608
- CPU
- Intel Core i7-3820 Sandy Bridge-E
- Graphics
- ASUS GeForce GTX-470 1280MB
- Mac
- Classic Mac
- Mobile Phone
Thanks, Bro!
This worked perfectly for me! ***UPDATE***
Installed & configured Clover. iMessage is working perfectly now, and no other issues have arisen.
I don't know why I didn't do this sooner.
Last edited:
- Joined
- Jul 21, 2011
- Messages
- 22
- Motherboard
- Gigabyte Z68X-UD3H-B3 UEFI BIOS
- CPU
- Intel Core i7 2600K
- Graphics
- Intel HD 3000 Integrated
- Mac
- Classic Mac
- Mobile Phone
I've found that you can also "revert" the logical volume and Core Storage using a simple command:
diskutil cs revert UUID
where you replace UUID by your Logical Volume UUID. "diskutil list" will give you the UUID
I'm also running Clover now, pretty much perfect now but I find it a little hard to configure for my Gigabyte Series 6 and the Intel HD 3000, but great once configured correctly!
diskutil cs revert UUID
where you replace UUID by your Logical Volume UUID. "diskutil list" will give you the UUID
I'm also running Clover now, pretty much perfect now but I find it a little hard to configure for my Gigabyte Series 6 and the Intel HD 3000, but great once configured correctly!
- Joined
- Jan 5, 2013
- Messages
- 12
- Motherboard
- GA-Z97N-WIFI
- CPU
- i7-4790K
- Graphics
- GTX 1070
- Mac
- Mobile Phone
Thanks hackbox, this got me past the can't find /System/Library/Kernels/kernel bit
Chief
Chief
- Joined
- Nov 20, 2014
- Messages
- 1
- Motherboard
- I didn't read
- CPU
- the RULES
- Graphics
- so ignore me
Thanks for the revert command. I was bangin my head for a couple hours on this "Missing /System/Library/Kernels/mach_kernel" message. I quadrupal checked my configs. I really like chameleon and want to stick with it. I finally found this thread by looking up "Chameleon raid icon".
I noticed diskutil listing a /dev/disk1 thanks to Core Storage. I dumped the first sector of /dev/disk0s4 and the first 512 bytes (0x200) have been modified by Core Storage. The next 512 bytes are the rest of chameleons boot1h file. I tried to dd boot1h back to /dev/disk0s4. After a reboot it reverted to the Core Storage header.
I even found this awesome forensic white paper outlining GPT and MBR analysis methods. It was the first place I found the GPT header signature structure. http://www.digitalforensics.ch/nikkel09.pdf My thinking was just change a byte for the partition type. I was wrong. "diskutil cs revert /dev/disk1" was much easier. Thanks again.
The Raid icon is still there because Chameleon is picking up the Recovery partition. Looks like I gotta hide this one.
I noticed diskutil listing a /dev/disk1 thanks to Core Storage. I dumped the first sector of /dev/disk0s4 and the first 512 bytes (0x200) have been modified by Core Storage. The next 512 bytes are the rest of chameleons boot1h file. I tried to dd boot1h back to /dev/disk0s4. After a reboot it reverted to the Core Storage header.
I even found this awesome forensic white paper outlining GPT and MBR analysis methods. It was the first place I found the GPT header signature structure. http://www.digitalforensics.ch/nikkel09.pdf My thinking was just change a byte for the partition type. I was wrong. "diskutil cs revert /dev/disk1" was much easier. Thanks again.
The Raid icon is still there because Chameleon is picking up the Recovery partition. Looks like I gotta hide this one.
- Status