On 02/24/2022 10:29 am, Alexander Motin wrote:
On 24.02.2022 10:57, Larry Rosenman wrote:
On 02/23/2022 9:27 pm, Larry Rosenman wrote:
It crashes just after root mount (this is the boot pool and only pool
on the system),
seeL
https://www.lerctr.org/~ler/14-BOOT-Crash.png
Where do I go from here?
I see 2 ways: 1) Since it is only an assertion and 13 is working (so
far), you may just build 14 kernel without INVARIANTS option and later
recreate the pool when you have time. 2) You may treat it as metadata
corruption: import pool read-only and evacuate the data. If you have
recent enough snapshots you may be able to easily replicate the pool
with all the settings to some other disk. ZIL is not replicated, so
corruptions there should not be a problem. If there are no snapshots,
then either copy on file level, or you may be able to create snapshot
for replication in 13 (on 14 without INVARIANTS), importing pool
read-write.
Ugh. The box is a 6 disk R710, and all 6 disks are in the pool.
I do have a FreeNAS box with enough space to copy the data out. There
ARE snaps of MOST filesystems that are taken regularly.
The 13 I'm booting from is the 13 memstick image.
There are ~70 filesystems (IIRC) with poudriere, ports, et al.
I'm not sure how to build the 14 kernel from the 13 booted box.
Ideas? Methods?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
