It did not work for me. In my case, I found that the installed Volume was renamed to "--" and the installation script stopped. After that the Volume was damaged and I had to erase it with Disk Utility. I suspect that the error does not come from the script itself but happened prior to run the script. Some process was messing with the installed Volume.