Trying to configure a Debian trixie build via FAI. The FAI server is Debian bookworm and is therefore running version 6.0.3. The FAI server hosts the successful building of bookworm and bullseye. PXE boot is working fine, however, soon after the booting process starts, the install abruptly stops with the following message:
FAI: installation aborted. Hit <ENTER> to obtain a shell reboot with: faireboot or after a logout There are a couple of warning and failed messages that precede this message, but I don't believe they are critical enough to stop the installation: /run/rpcbind not owned by root failed! Starting NFS common utilities: statd Not starting: portmapper is not running ... (warning). Cleaning up temporary files .... startpar: service(s) returned failure: rpcbind ... failed! INIT: Entering runlevel: 2 Using makefile-style concurrent boot in runlevel 2. Starting S.M.A.R.T. daemon: smartd failed! Starting time daemon: chronyd. Starting OpenBSD Secure Shell server: sshd. It would seem that the rpcbind failure would be critical, however, when I exit to a shell, I'm able to see the NFS Mount of the trixie NFSROOT to /run/rootfsbase. What is not mounted is the fai-config. However, if I attempt to mount the fai-config manually, it is successful, so there is not a network connectivity nor access issue to the fai-config. On top of that, if I execute /usr/lib/fai/terminal-wrapper, the FAI install executes, the fai-config is mounted and everything seems to install properly except for grub. When the FAI installation is aborted, it appears that it is so early in the process that there are no logs in /tmp/fai and there are no logs in /var/log related to fai. /var/log/dmesg has a lot of information and at the end has the following message: evm: overlay not supported I was not able to find a way to resolve that issue, if in fact that is the fatal issue causing FAI to exit early. I could really use some assistance in figuring out what's causing FAI to abort so quickly. Thanks, Lone
