The workaround for me was booting into NetBSD 8 first, which usually was followed by successful boot into current branch... I also added a small hack in thread of the bug, which should help to avoid crashes in general. However, if it is reproducible in your setup which probably is seems to be quite different from mine, maybe this bug should have a bit more attention from devs as well. I wonder if nobody else is hitting this issue with multiple hard drives on current branch?
On Fri, May 31, 2019 at 6:13 PM Andrius V <[email protected]> wrote: > > I think it's a duplicate of my reported bug: 54217, though in my case > I do have two disks. > > On Fri, May 31, 2019 at 5:53 PM John D. Baker <[email protected]> > wrote: > > > > PR kern/54253 > > > > -- > > |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X > > |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSD FreeBSD > > | X No HTML/proprietary data in email. BSD just sits there and works! > > |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
