Actions
Bug #15538
closedRAM disks trigger boot failure warning when using ZFS
Start date:
Due date:
% Done:
0%
Estimated time:
Release Notes:
Force Exclusion
Affected Plus Version:
24.08
Affected Architecture:
Description
Upgrades from 24.03 to 24.08-dev builds fail at first boot after rebooting into the new BE for the upgrade.
Root mount waiting for: usbus1 CAM ugen1.2: <Generic Ultra Fast Media> at usbus1 umass0 on uhub1 umass0: <Generic Ultra Fast Media, class 0/0, rev 2.00/1.98, addr 1> on usbus1 Root mount waiting for: da da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: <Generic Ultra HS-COMBO 1.98> Removable Direct Access SCSI device da0: Serial Number 000000225001 da0: 40.000MB/s transfers da0: 14952MB (30621696 512 byte sectors) da0: quirks=0x2<NO_6_BYTE> Configuring crash dumps... Using /dev/da0p3 for dump device. /dev/gpt/efiboot0: FILESYSTEM CLEAN; SKIPPING CHECKS Filesystems are clean, continuing... Mounting filesystems... Mounting ZFS boot environment...done. Unmounting ZFS volume pfSense/tmp at /tmp for RAM disk... done. Unmounting ZFS volume pfSense/var/tmp at /var/tmp for RAM disk... done. Unmounting ZFS volume pfSense/var/log at /var/log for RAM disk... done. Unmounting ZFS volume pfSense/var/empty at /var/empty for RAM disk... done. Unmounting ZFS volume pfSense/var/db at /var/db for RAM disk... done. Unmounting ZFS volume pfSense/var/cache at /var/cache for RAM disk... done. Unmounting ZFS volume pfSense/var at /var for RAM disk... done. Setting up memory disks... done. Mounting ZFS boot environment...done. Restoring contents of RAM disk store... done. mount: /var/run: No such file or directory *** SYSTEM BOOT FAILURE *** System will reboot in 60 seconds...
Tested: 24.08.a.20240603.0600
Updated by Steve Wheeler 6 months ago
This actually fails the same way if you enable RAM disks after upgrading.
Updated by Jim Pingle 6 months ago
- Subject changed from 24.08 upgrades fail when running RAM disks in ZFS to RAM disks trigger boot failure warning when using ZFS
Actions