[UPDATE] Well, as no one answered on this post I tried a reset. Of course didn’t work then I even lost internet access interestingly guest wlan started properly.
So I went on the journey of regaining internet access one way or the other. I started flashing medkits of TOS 5.x HBS branch without success. Then I flashed medkit of my old 3.11.22 schnapps backups (yes I always copy them onto a usb stick weekly) with and without info file. Still no luck.
So thought, ok let’s try factory reset. Still no success and still my guest wireless networks were starting with their names & passwords which I really didn’t understand.
At the end I opened the turris and connected it via serial cable. I saw that it had started TOS 5.3 but with lots of errors on startup. I didn’t even have a eth0 or other eth interfaces, it only had br_guest_turris and wlan0, wlan1, etc.
With serial console I was then able to rollback to the schnapps snapshot before the update and now I’m back on 3.11.21 but my big fear is that once 5.3 is beeing distributed automatically it will break in exactly the same way!
What I think had broken the whole thing was that I’m using /dev/sda3 to boot turris (not eMMC) but why did no one of the recovery methods set the boot mode back to eMMC? To my knowledge at least the factory reset should do the trick but apparently I also didn’t switch from the broken ssd install to emmc which probably contained the proper medkit.
My big fear now is of course what will happen when 5.3 gets distributed automatically. Will it again kill my OS beyound repair?
And how do I finally install 5.3 onto ssd (maybe first install on emmc and then copy everything over?)
And does anyone of the mods like pepe or vcunat have any clue why TOS 5.3 upgrade bricked the ssd installation and why factory reset didn’t set boot mode back to eMMC?
These were the things that actually took me hours to get it back working and still not having 5.3 in the end but my family relies on having a properply working router.
So as long as there’s no explanation what happened here I think automatic updates of TOS 5.3 are NOT READY to be distributed yet as the ssd install had absolutely nothing special in configurations apart from some DHCP stuff for an internal samba4 domain which forwarded everything for that domain to the domain controller. But this should not kill the automatic upgrade.