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

On 2025-04-21 00:23, Gary Jennejohn wrote:
> On Sun, 20 Apr 2025 12:19:45 -0700
> Chris <bsd-lists@bsdforge.com> wrote:
> 
>> On 2025-04-20 01:15, Dag-Erling Smørgrav wrote:
>> > Chris <bsd-lists@bsdforge.com> writes:
>> >> Warner Losh <imp@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
>> 
> 
> Removing ctl might be a problem since it supports:
> 	/sys/conf/files:cam/ctl/ctl_nvme_all.c
> 	/sys/conf/files:cam/ctl/ctl_nvme_cmd_table.c
> and you have nvme in your kernel config files.
> 
> But I'm not sure about that since I don't have nvme in my config file.
> 
>> > - The contents of `/var/run/dmesg.boot` after booting the old kernel
>> https://bitpit.us/kern/dmesg.boot
>> 
> 
> A diff of the new and old /var/run/dmesg.boot files might be useful.
Indeed.  But I'm not sure how I might obtain one. Since the new kernel
can't find a drive to write to. :)
I guess I could take a movie. But that'd be hell to transcribe. Any way
to redirect the console to a remote host without having much of a system
yet available?

Thanks for the hint, Gary.

--Chris
> 
> [SNIP]

-- 
sent from hardware written from and running on FreeBSD