- Joined
- Sep 9, 2015
- Messages
- 88
- Motherboard
- Asus X299-A
- CPU
- i7-7920X
- Graphics
- VEGA 56
- Mac
- Mobile Phone
That's awesome! Thanks for the fast response! How did you even get to discovering the names for the drives if you couldn't boot with them connected? ;-) I can't remember what mine are titled...
Well firstly I still had my working Yosemite on my SSD and first set up a test 10.11 on "Clubs" volume, which worked.
But secondly, it didn't matter about my RAID and not being able to boot with it plugged in. Before I solved it I just unplugged the 1 drive in the RAID that was causing the issue until I solved it. So it didn't really matter what the names and UUIDs etc of my RAID were, and it doesn't matter about yours either. Turning off 'scanning entries" is the key - that way it will ignore the RAID and not freeze on scanning entries. We're not telling the config.plist what to ignore, we're telling it what to manually add, ie. I only want to see my SSD really and nothing else. Some people use it to add their Windows boot drive as well.
"Clubs" is my backup drive for emergencies so I have that as an entry too.
I don't really know what scanning entries is doing (perhaps searching for EFI partitions or something) given that it still has to be aware of what hard drives ARE there in order to match my manual addition of 'custom entries' but...it works... so I like it haha
Good luck