Thank you for attaching the dmesg to the list. I don't know what
additional info the developers might need to assist you. But how about
/var/log/messages ? Maybe grep for sd0 and sd1?
They might want the whole file, just like dmesg. Here are snippets from
my amd64 system that for you might give them info about what was
happening when that command froze the kernel. (I assume that's why
Ctrl-C and Ctrl-D didn't work for you.) Mine boots fine.
----
May 28 18:51:34 om /bsd: sd1 at scsibus1 targ 1 lun 0: <ATA, GOFATOO
128GB SS, SBFM> naa.0000000000000000
May 28 18:51:34 om /bsd: sd1: 122104MB, 512 bytes/sector, 250069680
sectors, thin
May 28 18:51:34 om /bsd: sd2 at scsibus3 targ 1 lun 0: <OPENBSD, SR
CRYPTO, 006>
May 28 18:51:34 om /bsd: sd2: 121844MB, 512 bytes/sector, 249536575 sectors
May 28 18:51:34 om /bsd: root on sd2a (1f09625bb349f8d6.a) swap on sd2b
dump on sd2b
May 28 18:51:34 om savecore: /dev/sd2b: Device not configured
----
Do you have the ability to console into your arm64 computer from another
system? And save yourself the USB transfer each time?
Committers: any further ideas to help him?
On 5/28/25 3:18 AM, BESSOT Jean-Michel wrote:
-------- Message transféré --------
Sujet : Re: bioctl block on arm64
Date : Tue, 27 May 2025 16:23:22 +0200
De : BESSOT Jean-Michel <[email protected]>
Pour : Kevin Williams <[email protected]>
Hello
Here the dmesg from the bsd.rd on usbkey (snapshot problematic).
Bye
Le 5/26/25 à 20:30, Kevin Williams a écrit :
Hi Jean-Michel,
Thank you for posting to bugs@
For the developers to better assist you, please attach a full dmesg
of the arm64 system, using single-user mode or the OpenBSD installer
if necessary.
On 5/25/25 6:14 AM, BESSOT Jean-Michel wrote:
Hello
I tried to upgrade my computer with the last snapshot image and I am
blocked with a problem. I can not mount my encrypted dd.
Here the problem.
I do the usual sh MAKEDEV sd0 and I run bioctl -c C -l /dev/sd0a
softraid0. Here the problem, the bioctl command wait for something.
It does not tell
it wait for a password and I do not know what it wait and it is not
the password. Crtl C and Ctrl D do not work to end the command and
get back the shell.
Bye
