It looks like I have a 128 partition and it is still too small:
/dev/sda3 130571808 2336148 121576820 2% /
/dev/sda1 112596 51680 51744 50% /boot
128MB enough even with the slightly larger kernel 6.6.2 there must be an other reason.
The boot partition is now 512MB because newer xfstools cannot format smaller partitions anymore.
2 Likes
I expanded the root partition from 256 to 512, but the problem persists.
At least disk space is not the reason.
What error messages are occurring in the bootlog?
It looks like the problem is related to Proxmox’s VirtIO SCSI driver.
Booting with an IDE or SATA driver works.
1 Like
i have the same problem
my ipfires are running on vmware esx
i changed the /boot partion to 256mb and tryed to update again.
at the reboot the system hangs. it looks like ipfire does not see the root partion
the /boot has more than 200mb free space this could not be the problem
2 posts were merged into an existing topic: Upgrade to 181 hangs - no WebGUI
Did you now which config/module proxmox use?
The drivers are from Virtio - KVM
This is lspci and /sys from a VM with IPFire 180:
00:03.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon
00:04.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG
00:05.0 SCSI storage controller: Red Hat, Inc. Virtio SCSI
00:12.0 Ethernet controller: Red Hat, Inc. Virtio network device
00:13.0 Ethernet controller: Red Hat, Inc. Virtio network device
/sys/bus/virtio/drivers_autoprobe
/sys/bus/virtio/drivers_probe
/sys/bus/virtio/drivers
/sys/bus/virtio/drivers/virtio_rng
/sys/bus/virtio/drivers/virtio_rng/uevent
/sys/bus/virtio/drivers/virtio_rng/virtio1
/sys/bus/virtio/drivers/virtio_rng/bind
/sys/bus/virtio/drivers/virtio_rng/unbind
/sys/bus/virtio/drivers/virtio_console
/sys/bus/virtio/drivers/virtio_console/uevent
/sys/bus/virtio/drivers/virtio_console/bind
/sys/bus/virtio/drivers/virtio_console/unbind
/sys/bus/virtio/drivers/virtio_balloon
/sys/bus/virtio/drivers/virtio_balloon/uevent
/sys/bus/virtio/drivers/virtio_balloon/bind
/sys/bus/virtio/drivers/virtio_balloon/unbind
/sys/bus/virtio/drivers/virtio_balloon/virtio0
/sys/bus/virtio/drivers/virtio_balloon/module
/sys/bus/virtio/drivers/virtio_scsi
/sys/bus/virtio/drivers/virtio_scsi/uevent
/sys/bus/virtio/drivers/virtio_scsi/bind
/sys/bus/virtio/drivers/virtio_scsi/virtio2
/sys/bus/virtio/drivers/virtio_scsi/unbind
/sys/bus/virtio/drivers/virtio_scsi/module
/sys/bus/virtio/drivers/virtio_rproc_serial
/sys/bus/virtio/drivers/virtio_rproc_serial/uevent
/sys/bus/virtio/drivers/virtio_rproc_serial/bind
/sys/bus/virtio/drivers/virtio_rproc_serial/unbind
/sys/bus/virtio/drivers/virtio_net
/sys/bus/virtio/drivers/virtio_net/uevent
/sys/bus/virtio/drivers/virtio_net/bind
/sys/bus/virtio/drivers/virtio_net/virtio4
/sys/bus/virtio/drivers/virtio_net/unbind
/sys/bus/virtio/drivers/virtio_net/module
/sys/bus/virtio/drivers/virtio_net/virtio3
The module is present in core181:
[root@helena ~]# modinfo virtio_scsi
filename: /lib/modules/6.1.61-ipfire/kernel/drivers/scsi/virtio_scsi.ko.xz
license: GPL
description: Virtio SCSI HBA driver
srcversion: C99A4F98EB531464CD29DAB
alias: virtio:d00000008v*
depends:
retpoline: Y
intree: Y
name: virtio_scsi
vermagic: 6.1.61-ipfire SMP preempt mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 37:A5:1A:DA:24:57:A4:11:39:D4:C3:0C:9C:8E:74:BC:D5:5E:40:F9
sig_hashalgo: sha512
signature: 30:64:02:30:18:DE:40:AE:BA:16:14:BE:53:9C:C8:2E:AB:08:36:77:
D3:ED:84:A1:28:3A:7B:8A:9A:0A:14:7A:9C:80:8D:38:97:8B:5B:01:
5C:32:6C:ED:11:1E:EC:E5:C7:65:28:5D:02:30:4C:E2:70:A8:5B:6F:
78:2E:F3:10:D4:AB:83:7D:4E:59:F7:FC:70:82:73:16:41:E1:1E:5F:
47:1B:1A:AB:85:05:30:6B:F4:7C:37:F0:97:F9:16:A7:51:1C:77:29:
FD:62
I have to check if it is in the initrd and has matching udev rules.
Same problem here, also by changing the virto scsi i got the error and its impossible to start the firewall. is there in the backround help or is it like it seems that no one of the devs cares about it?
It seems I also had to do a manual reboot, just adding my 2 cents here.
Other that that I do not think I have any other problems
I did some test with my backup firewalls. They are virtual machines on vmware esx 6.7
The Problem still exists on older installations. I expanded the /boot partition up to 256MB but the Problem still exist.
In the log is a Dracut warning that the root disk does not exist.
In dracut shell I can not see or mount any disks, only the (virtual) CD-Rom drive.
One of my ipfire VMs is installed in summer 2023, there the update wokrd without problems. The configuration of the VM is the same like the other that do not work
Have you tried “modprobe virtio_scsi” before you try to mount the disk?
i triedd “modprobe mptsas”
after this i can see the Disks.
I cannot reproduce this on kvm and proxmox 8.1.3. I have tested all storage/scsi options. But i have seen that one udev rule file is missing in the initrd.
Can someone with a virtualizer and snapshots try to run
ln -s false /bin/loginctl
and then run the update to core181 if this resolve the problem?
IPFire is 179 and I run “ln -s false /bin/loginctl” followed by an upgrade to 182.
Unfortunately, nothing changed, still Dracut error.
modprobe virtio_scsi on dracut shows that the driver is present and the drive is shown.
I tried to upgrade an old IPFire 180 to 181 on a fresh Proxmox 8.1, but IPFire won’t boot.
I tried to upgrade a fresh IPFire 180 to 181 and it worked.
So there may be something old in IPFire that is not present in a new IPFire that is causing the error.