After Upgrade to 24.7.8 - faild to boot from zfs

Started by Betarg, November 08, 2024, 09:19:59 PM

Previous topic - Next topic
Hey,

after i upgraded to 24.7.8 my opnsense wont boot anymore. During the boot the loader stucks on mountroot and opnsense wont boot. I think the problem is the new kernel-24.7.8 because when i do on Boot options "boot with old kernel" my firewall booting and work well.

Does anyone has a idea why the boot fails with the new kernel?






Boot the old kernel and please post the output of

zpool get bootfs
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Here is the output:

root@OPNsense:~ # zpool get bootfs
NAME   PROPERTY  VALUE               SOURCE
zroot  bootfs    zroot/ROOT/default  local

Output of

bectl list
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

here is the output:

root@OPNsense:~ # bectl list
BE             Active Mountpoint Space Created
20241026235540 -      -          327M  2024-10-26 23:56
default        NR     /          2.48G 2024-08-06 21:49

Looks good. I am puzzled by that vfs.root.mountfrom variable either in /boot/loader.conf or /boot/loader.conf.local.

That should not be there. But then again it's set to the same dataset as the proper attributes are. So neither should it hurt.

You can try removing it, at the risk of rendering the system unbootable - sorry, no guarantees over the forum. I can only tell you it's weird.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

The new kernel has some new Intel drivers in it. So if it really is the kernel (which you could try by locking the kernel to the 24.7.7 one), I would guess that your specific boot disk driver is no longer working.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

Quote from: Patrick M. Hausen on November 08, 2024, 10:03:47 PM
I am puzzled by that vfs.root.mountfrom variable either in /boot/loader.conf or /boot/loader.conf.local.
...
You can try removing it, at the risk of rendering the system unbootable
there is no vfs.root.mountfrom in my loader.conf and i dont have a loader.conf.local

Quote from: meyergru on November 08, 2024, 10:25:56 PM
The new kernel has some new Intel drivers in it. So if it really is the kernel (which you could try by locking the kernel to the 24.7.7 one), I would guess that your specific boot disk driver is no longer working.
thats a good point.
My system is a NRG Systems IPU618 that has a Intel Core Intel Core i7-1185G7 inside. I am booting from a NVME SSD, so i think the driver could be the problem.

is there any soloution for this? Or should i only boot with the old kernel?

Mounting the root and Intel nic drivers have nothing in common though.

I would rather think drive was ~full with not enough room left to properly installed the kernel - which comes last in the process iirc.

zpool list or df -hT may shed some light here...

November 08, 2024, 10:44:14 PM #9 Last Edit: November 08, 2024, 10:47:06 PM by newsense
Quoteis there any soloution for this? Or should i only boot with the old kernel?

Boot the old kernel, then do these steps -- assuming there's some free space left on the drive.

# bectl create 24.7.6

# opnsense-update -kr 24.7.8

# opnsense-shell reboot




P.S. There was no 24.7.7 kernel

November 08, 2024, 10:56:51 PM #10 Last Edit: November 08, 2024, 11:04:38 PM by Betarg
Quote from: newsense on November 08, 2024, 10:37:26 PM
I would rather think drive was ~full with not enough room left to properly installed the kernel - which comes last in the process iirc.

zpool list or df -hT may shed some light here...
no, i dont have full drive:


root@OPNsense:~ # zpool list
NAME    SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
zroot   456G  2.90G   453G        -         -     2%     0%  1.00x    ONLINE  -


root@OPNsense:~ # df -hT
Filesystem                 Type       Size    Used   Avail Capacity  Mounted on
zroot/ROOT/default         zfs        441G    2.2G    439G     0%    /
devfs                      devfs      1.0K      0B    1.0K     0%    /dev
/dev/gpt/efiboot0          msdosfs    260M    1.3M    259M     1%    /boot/efi
zroot/var/audit            zfs        439G     96K    439G     0%    /var/audit
zroot/usr/src              zfs        439G     96K    439G     0%    /usr/src
zroot/var/tmp              zfs        439G     96K    439G     0%    /var/tmp
zroot/var/crash            zfs        439G     96K    439G     0%    /var/crash
zroot                      zfs        439G     96K    439G     0%    /zroot
zroot/var/mail             zfs        439G    112K    439G     0%    /var/mail
zroot/home                 zfs        439G    144K    439G     0%    /home
zroot/tmp                  zfs        439G    1.6M    439G     0%    /tmp
zroot/usr/ports            zfs        439G     96K    439G     0%    /usr/ports
zroot/var/log              zfs        439G    355M    439G     0%    /var/log
devfs                      devfs      1.0K      0B    1.0K     0%    /var/dhcpd/dev
devfs                      devfs      1.0K      0B    1.0K     0%    /var/unbound/dev
/usr/local/lib/python3.11  nullfs     441G    2.2G    439G     0%    /var/unbound/usr/local/lib/python3.11
/lib                       nullfs     441G    2.2G    439G     0%    /var/unbound/lib


Quote from: newsense on November 08, 2024, 10:44:14 PM

# bectl create 24.7.6

# opnsense-update -kr 24.7.8

# opnsense-shell reboot



thanks, i will try it

Update:
not working, same error again

Then it is not the new kernel.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

updated the kernel again via GUI - System - Firmware - packages - "reinstall"

system downloaded the kernel again, reboot and now i am online. Double check it via reboot and "default" kernel is active.

Now working. And i dont know what was the problem...  :-X


Alternative was for me: reinstall with UFS and restore my backup. But not need anymore.

thanks all for your help  ;D