Date: Wed, 11 Oct 2023 11:23:56 +0100 From: void <void@f-m.fm> To: freebsd-arm@freebsd.org Subject: Re: unable to boot latest 14-stable Message-ID: <ZSZ3vATEEGO3N8-T@int21h> In-Reply-To: <ZSZotIDLHZE1SzwL@int21h> References: <ZSXPnTXAdSJYrBDX@int21h> <841CA663-55E0-4EAD-B700-66DC884B50FA@yahoo.com> <ZSZotIDLHZE1SzwL@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 11, 2023 at 10:19:48AM +0100, void wrote:
>Do you think the following might allow the system to boot:
>
>1. get 14-stable beta5 and on another freebsd box, mount its msdos partition
>with mdconfig -f
>
>2. unplug the usb3 disk from the rpi, plug it into the freebsd box,
>do the same as [1]
>
>3. copy the contents of [1] into [2]
>
>I'm worried the process might clobber something GELI needs though,
>rendering the zpool/disk permanently inaccessible.
Following this process allowed it to boot. GELI wasn't clobbered.
The daemon menu defaults to "5. Cons: Video" so this must be changed to
make the serial console fully work again.
The issue, seemingly, wasn't one with the zpool itself, or unknown features.
After getting it to boot:
# zpool status -v
pool: zroot
state: ONLINE
scan: scrub repaired 0B in 01:20:01 with 0 errors on Sun Oct 1 22:09:40 2023
config:
NAME STATE READ WRITE CKSUM
zroot ONLINE 0 0 0
da0p3.eli ONLINE 0 0 0
errors: No known data errors
I've saved onto another machine the problematic msdos partition contents
so I can try and work out what's going on.
--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZSZ3vATEEGO3N8-T>