Re: New kernel doesn’t recognize ufs gpt root filesystem

[Chris]

On 2025-04-20 01:15, Dag-Erling Smørgrav wrote:

Chris <bsd-li...@bsdforge.com> writes:

Warner Losh <i...@bsdimp.com> writes:
> Maybe this is a custom kernel without the label code.
It's an upgrade. It's 15 from ~11 mos ago. Yes a custom kernel. But
I'm using the same kernconf as before. Was label removed from generic
in the last 11 mos.?

Thanks for your reply!

Please share:

- The output of the `what` command on your old (working) kernel

FreeBSD 15.0-CURRENT #1 main-n270118-94b09d388b81-dirty: Mon May 13 12:57:41 PDT 2024

- The output of the `what` command on your new (failing) kernel

FreeBSD 15.0-CURRENT #0 main-n276516-65d8491719bb: Sat Apr 19 17:41:06 PDT 2025

- The kernel configuration file you used to build the new kernel

https://bitpit.us/kern/LENOIP15ND-NEW

here's the old kernconf:
https://bitpit.us/kern/LENOIP15ND-OLD

and here's a convenient diff of them:
https://bitpit.us/kern/LENODIFF

- The contents of `/var/run/dmesg.boot` after booting the old kernel

https://bitpit.us/kern/dmesg.boot

> What does '?' at mountroot> prompt say?
nadda, nothing.

That's hard to believe.  Are there any error messages relating to nvme
prior to the mountroot promopt?  (if necessary, use Scroll Lock followed
by Page Up / Page Down to scroll back on the console).

No. Nothing apparent.
gpart reports a bad label on the 4th slice (OpenBSD). But it's done so
for as long as it's been there and that wouldn't prevent the freebsd slice
from being seen. It's on 2.

> Does one of those work if you add 'ufs:/dev/' to the
> front of each of the geoms listed? Most likely ada0p2 or nda0p2.
Indeed. It's nda0p2. But ufs:/dev/nda0p2 returns the same error 19.
I had to move kernel to kernel.new && kernel.old to kernel to get
here to write this response.

You could have just selected kernel.old from the loader menu (press 'k'
to cycle between available kernels) or prompt (`boot kernel.old`)...

I did this for convenience. I knew I'd need to move things back
before installing world. But as the (new) kern wouldn't boot the system...

I would however advise you to copy kernel.old to kernel.works, as it
will be permanently deleted the next time you install a new kernel
(unless you use `make reinstallkernel` instead of `make installkernel`).

Understood. That's good advice. Thanks.

--Chris

DES

--
sent from hardware written from and running on FreeBSD

0xE512722F.asc
Description: application/pgp-keys