Re:_New_kernel_doesn’t_recognize_ufs_gpt_roo t_filesystem
- In reply to: Chris : "Re:_New_kernel_doesn’t_recognize_ufs_gpt_roo t_filesystem"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 20 Apr 2025 06:17:17 UTC
On 2025-04-19 22:23, Chris wrote: > On 2025-04-19 20:36, Warner Losh wrote: >> On Sat, Apr 19, 2025, 8:51 PM Chris <bsd-lists@bsdforge.com> wrote: >> >>> Finally got a build world/kernel to complete. Following a >>> installkernel with a boot -s resulted in the inability >>> to mount root (/dev/gpt/FBSD15) >>> It’s a ufs2 filesystem. I booted the 15-CURRENT >>> usb stick. It recognized it. I performed fsck on >>> it. No errors. >>> An attempt to mount it from the new kernel at boot is: >>> Mounting from ufs:/dev/gpt/FBSD15 failed with error 19. >>> >>> Can anyone suggest the best way forward please? >>> >> >> 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.? Of course not. I have GEOM_LABEL in my kernconf. FWIW old vs. new kernel indicates I gained +acpi_sbl_wmi.ko +bnxt_re.ko +dummymbuf.ko +gpioaei.ko +if_iwx.ko +if_mtw.ko +if_rtw89.ko +mac_do.ko +p9fs.ko +snd_dummy.ko +umb.ko +virtio_p9fs.ko +wlan_gcmp.ko and this was removed. No, root is not on gvinum -geom_vinum.ko > >> What does '?' at >> mountroot> prompt say? > nadda, nothing. > >> 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. > > Thanks! > > --Chris >> >> Warner >> >> Thanks. >>> >>> —-Chris -- sent from hardware written from and running on FreeBSD