Hi,
Thank you for your feeeback.
Also OpenBSD 6.9beta snapshot is crashing when I setup RAID5 with three
"Samsung PRO 860 1TB" SSDs.
OpenBSD obsd69b.it-infra.org 6.9 GENERIC.MP#368 amd64
obsd69b# dmesg | grep -i bios
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdc312018 (61 entries)
bios0: vendor
On Fri, Feb 26, 2021 at 09:54:06PM +, Nicholas Marriott wrote:
> Should be fixed by format.c r1.279. Thanks!
>
Confirmed. I see this fixed while running:
OpenBSD 6.9-beta (GENERIC.MP) #368: Sun Feb 28 21:10:13 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
On 2021-02-27 03:35, Mark Schneider wrote:
Hi,
I face system crash on OpenBSD 6.8 when trying to use softraid RAID5
drive trying to write big files (like 10GBytes) to it.
I can reproduce the error (tested on two different systems with
OpenBSD 6.8 installed on an SSD drive or an USB stick).
https://www.bsdly.net/~peter/20210301/20210301_greyhame_dmesg.boot
and a ls -l / shows that bsd.upgrade is indeed not +x:
[Mon Mar 01 15:39:59] peter@greyhame:~$ ls -l /
total 184140
drwxr-xr-x 2 root wheel 512 Feb 20 07:32 altroot
-rw-r--r-- 1 root wheel 160 Mar 1 10:01 auto_upgrad
://www.bsdly.net/~peter/20210301/20210301_103647.jpg
When it finally proceeded from that point, I caught a glimpse of it at the boot:
prompt with the message
bsd.upgrade is not u+x
but it proceeded to boot anyway.
When I attempted a 'doas sendbug', I got a panic:
"panic: config_detach: forced d
not sure how interested anyone will be in this given that it's hidden
behind allowkmem=1, but posting anyway, I hit this while running procmap:
kernel: protection fault trap, code=0
Stopped at copyout+0x53: repe movsq (%rsi),%es:(%rdi)
ddb{1}> [-- sthen@localhost attached -- Sun Feb
