Thanks MAJ for your detailed answers! Will try to support you with feedback. All issues so far are just cosmetically, my System is working 100% now - REALLY happy about this (sleep is so cool!)
That's a feature, not a bug. Seriously, it's normal.
The bootloader is going to list/show all the helper partitions you can boot from. A RAID or FUSION drive will have, at minimum, two helper partitions and that's what you are seeing. The helper partitions are the actual partitions that contain the booting files, like the booter, kexts/kext cache/kernel cache, boot plist, DSDT, etc. The Finder will ignore them, as they don't contain user files.
Thanks you so I know this is normal. Seems like I can't hide the second helper partition via chameleon though...
Okay, two things:
1. You should only be able to choose ONE install target for the Fusion drive. So, that is working correctly.
2. The two "Fusion HD" showing up in the plist editor is a bug. The one with "(Fusion Drive)" should be the correct one.
Now, this is what I'd like to fix. However, it's really hard to script in support for a Fusion drive when you don't have one. So, getting feedback, like this one, really helps. If you can provide me your install log, that will be even more helpful. (#15 View logs; #6 Copy all logs to desktop; zip and send to digital (underscore) dreamer (at) mac (dot) com)
Please see e-mail.
The "Boot OSX" partition is the default name of the helper partition.
The script should be placing/installing the same /Extra files at the root directory of each helper partition.
If this is not happening, you will not be able to boot from that helper partition when you select it at the bootloader screen.
Let me know if you are experiencing issues here and provide your install log.
This happens correctly. However, I wonder if /Extra also needs to be on the main Fusion Drive partition I can see in finder? (It is present there) As far as I understand, only boot helper partitions are relevant for boot.
Not sure I understand exactly what you are experiencing here. Can you elaborate on this further? What do you mean by 'installing correctly when not changing install target?' And, are you getting the "no OS installed" error on a drive that has the OS installed?
Please see mail. It seems to be possible to install to a wrong "ghost" target drive after "changing target". Now, that I now duplicate partitions in chameleon are correct behavior, it's not really relevant anymore.
For a Fusion drive setup, yes. Is that not happening?
If you are able to boot your Fusion drive setup, then the UUID is doing its job pointing the booter on the helper partition to the partition where the OS is installed.
What do you mean by creating a boot-UUID flag, but not applying the UUID? Note that UUIDs are used for different purposes. In this case, the boot UUID is used to identify the drive the OS is located on and should boot to. This is not to be confused with the Platform UUID, which is a unique identifier for your system.
Please, see mail.
Kind regards and thank you for all the support. Hackinstaller already achieved 99.9% perfection for me