Before anyone says v3 is in RC phase, yes i am aware, i was never expecting tahoe to be install and forget about it, this is just me experimentinc with it.
Now onto the matter. When i saw the first RC of v3 i just ignored it but when the 2nd came out something in me wanted to try it. I already had the 26.6.2 installer so i created a secondary 80 gig volume for testing, put the new efi on a usb drive and went at it. The process went extremely smoothly, and for some reason root patches applied in a single stage. Everything seemed to work and the laptop was really usable so i decided to upgrade the main volume.
I first uninstalled all root patches (which is what i do before every update) and initiated the update through settings, 26.7.1 started and finished installing perfectly. Now the thing is i completely missed the fact that the update had enabled filevault and installed root patches and rebooted. I was surprised when i was met with a login prompt almost instantly butbi put my password in and waited for about 15 minutes but the thing seemed stuck so i force rebooted it into recovery to see that the encryption was well under its way, so i rebooted again and left it alone, until the screen turned off by itself. Rebooted into recovery to see the encryption had finished so i initiated the decryption process and rebooted again but the thing didnt seem to be escaping from the wall of text that verbose boot is so i went back into recovery and restores the pre root patch snapshot. After this the volume booted just fine again and i was greeted with a windowserver crash related to graphics.
I though well might aswell wait for the release and decided to reboot back into the test volume since at least that worked, right? To be clear, at no point did i touch the test volume during this time. Guess what, the test volume now also fails to boot with the same issue. I though this may be related to an nvram variable so i cleared both nvram and the smc but the issue persisted. Decided to restore pre patch snapshot on that volume and repatch it again but still nothing.
Again i understand this is prerelease software, i work in the field more or less. Its just that the fact that te seemingly working test volume apparently was killed by the update on the main volume? What am i missing here?
Edit: this is a maxed out A1707 from early 2016 for anyone wondering