I'm not sure this is the right forum to ask but I have a HP Microserver N54L Gen6 which ran just fine until yesterday with 11.1 (Latest update).
I then updated it to 11.2 which worked flawless, even my encrypted pool worked perfectly after I entered the password. I then started installing the new plugins, deleting the old ones via the legacy UI, did a reboot and my server did not come up again. Everything was perfect. I then had a look and it just hangs there after trying to start from the USB stick (2 of them where its installed) no error nothing just a blinking cursor.
So I decided to start with a fresh install of 11.2, prepared the media according to the manual but when starting from it it gets as far as the bootstrap loader, Revision 1.1 and then just stops there.
The only simialr thread I coudl find is this one: https://forums.freebsd.org/threads/installer-hangs-during-boot-11-1-on-amd.61936/ and a possibly related bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
I tried both USB sticks which were in use and no luck :-( If I don't get any tips I guess I'll have to finally update to a newer system but this was working just fine since 2014 :-(
I then updated it to 11.2 which worked flawless, even my encrypted pool worked perfectly after I entered the password. I then started installing the new plugins, deleting the old ones via the legacy UI, did a reboot and my server did not come up again. Everything was perfect. I then had a look and it just hangs there after trying to start from the USB stick (2 of them where its installed) no error nothing just a blinking cursor.
So I decided to start with a fresh install of 11.2, prepared the media according to the manual but when starting from it it gets as far as the bootstrap loader, Revision 1.1 and then just stops there.
The only simialr thread I coudl find is this one: https://forums.freebsd.org/threads/installer-hangs-during-boot-11-1-on-amd.61936/ and a possibly related bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
I tried both USB sticks which were in use and no luck :-( If I don't get any tips I guess I'll have to finally update to a newer system but this was working just fine since 2014 :-(