Hello! This is a bug that I discovered by mistake.
If you have an installation on an encrypted disk or partition and you do detach the encrypted drive by accident (as I did bioctl -d sd0) or you mount the disk or partition on a different system and also detach it the original install will not boot. This is the error that it will show open(hd0a:/etc/boot.conf): Invalid argument boot> cannot open hd0a:/etc/random.seed: Invalid argument booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try /bsd If you do boot sr0a:/bsd, it will ask for the passphrase and it will start booting but then it will hang. softraid0 at root scsibus2 at softraid0: 256 targets panic: root device (3312a...) not found Stopped at db_enter+0x10: popq %rbp TID PID UID PRFLAGS PFLAGS CPU COMMAND * 0 0 0 0x10000 0x2000 0k swapper panic(ffffff81dff....) at panic+0x12a setroot(ffff80......) at setroot+0xdeb disconf(1b21..) at diskconf+0x185 main(0,0,0,0,0,ffff80..) at main+0x500 end trace frame: 0x0, count:10https://www.openbsd.org/ddb.html describes the minimum info required in bug reports. Insufficient info makes it difficult to find and fix bugs. ddb{0}> The solution is to use a rescue system and 'installboot sd2' (where sd2 is the attached encrypted partition). Steps to get the error: 1. attach an encrypted disk (partition) with an OpenBSD installation on it, let's say sd1a --- "bioctl -c C -l sd1a softraid0" --- you will get the new sd2 2. detach the sd2 "bioctl -d sd2" 3. The OpenBSD will no longer boot. Hope I was clear enough and this it is really a bug.
