I am not sure on this being an actual bug or even edge case deemed not interesting to yours truly, however when last it is then please accept my humble applogies for any noice created ...
I am running OpenBSD 7.8 GENERIC.MP#54 installed on a USB ... (Sandisk Cruzer Blade 16GB)) since my microserver gen 10 plus has this option on the mainboard and one can save a sata slot in the bays. In case my expectancy and knowledge is here at fault I will try to solve my issue with a pci adapter to mvme and install and run OpenBSD from there. Problem occurs with several hardware setups used to perform USB installs ... I create per faq an OpenBSD bootable USB using the install78.img I also have an emptied USB , bootable and fat, to perform the install on (Cruzer) When I boot my OpenBSD install USB , I can all install and setup on the new USB , I also use the encryption setup with passphrase. The install goes true all the steps, however after the creation of the nodes, it hangs multiple minutes long on relinking Uniqe kernel ... then offers messages that disk is full and kernel relinking has failed. Proceeds to asking if to want to reboot. However the failure message about relinking the kernel stays there after every reboot and also when all patches from syspatch have been applied ... so completly up to date with these plus 25 patches ... The error message from /usr/share/relink/kernel/GENERIC.MP/relink.log states following : (SHA256) ok make: don't know how to make new bsd Stop in /usr/share/relink/kernel/GENERIC.MP The feedback I am hoping for is : - has this all to do with "bad practice" installing OS on an USB, since in old liturature there have been rants on the net .. so stupid me of wanting this solution .. - can I then savely presume these issues wont happen on a nvme install, correct ? - can this situation be considered an actual bug or is it an edge case and wont ever be solved ? Kindest regards for understanding my request for support and knowledge, eelco vitalis
