I am commissioning a new machine to my MAAS pool with ubuntu 20.04 image but it turns out to boot into busybox mode (initramfs). The busybox mode does not have fsck command and I have tried to mount the missing proc and sys file but failed to boot as well. I tried to commissioning with Ubuntu 22.04 image and it works fine but I need Ubuntu 20.04 as Ubuntu 22.04 have compatibility issue with my software.
My machine is using NVME Predator SSD GM7000 1TB… I tried to install Ubuntu 20.04 with live CD and it works fine… just the cloud image cannot…
Could any one offer me some help on this? I have been troubleshooting for a week but do not have any idea …
yeaa… it said no init found. Try passing init=bootarg and chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /, execute NEW_INIT, PID must be 1. NEW_ROOT must be a mountpoint.
2023-11-30 18:30:42 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: br0.
2023-11-30 18:30:52 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
2023-11-30 18:31:15 provisioningserver.utils.services: [info] Beaconing process for vnet2 started.
2023-11-30 18:31:15 provisioningserver.utils.services: [info] Beaconing process for vnet1 started.
2023-11-30 18:31:15 provisioningserver.utils.services: [info] Beaconing process for vnet4 started.
2023-11-30 18:31:15 provisioningserver.utils.services: [info] Beaconing process for vnet3 started.
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet2]: tcpdump: vnet2: No such device exists
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet2]: (SIOCGIFHWADDR: No such device)
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet4]: tcpdump: vnet4: No such device exists
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet4]: (SIOCGIFHWADDR: No such device)
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet1]: tcpdump: vnet1: No such device exists
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet1]: (SIOCGIFHWADDR: No such device)
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet3]: tcpdump: vnet3: No such device exists
2023-11-30 18:31:15 provisioningserver.utils.services: [info] observe-beacons[vnet3]: (SIOCGIFHWADDR: No such device)
2023-11-30 18:31:15 provisioningserver.utils.services: [critical] Beaconing process for vnet2 failed.
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.
2023-11-30 18:31:15 provisioningserver.utils.services: [critical] Beaconing process for vnet4 failed.
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.
2023-11-30 18:31:15 provisioningserver.utils.services: [critical] Beaconing process for vnet1 failed.
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.
2023-11-30 18:31:15 provisioningserver.utils.services: [critical] Beaconing process for vnet3 failed.
Traceback (most recent call last):
Failure: twisted.internet.error.ProcessTerminated: A process has ended with a probable error condition: process ended with exit code 3.
Apart from the rackd log, I have capture log before the PXE boot to the initramfs mode.
The last few lines are:
failure: overlayroot: failed to move root away from /root to /media/root-ro
mount: mounting /dev on /root/dev failed: No such file or directory
ipconfig: no device to configure
ipconfig: BOOTIF: SIOCGIFINDEX: No such device
wget: can’t connect to remote host (MAAS IP Address): Network is unreachable
:: mount -t squashfs -o loop ‘/root.tmp.img’ ‘/root.tmp’
/root.tmp.img: Can’t open blockdev
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.Begin: Running /scripts/local-premount …
Btrfs loaded. crc32c=cr32c-intel
Scanning for Btrfs filesystems
done.
It was working when booting with Ubuntu 22.04 image. I have triggered to download the Ubuntu 20.04 image to the MAAS to install but still have the same issue.
I have restarted my rackd controller and the vnet error is not prompting out anymore. The rackd log looks like as below now when I PXE boot that machine:
2023-12-01 10:01:49 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
2023-12-01 10:10:42 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by
2023-12-01 10:10:42 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by
2023-12-01 10:10:43 provisioningserver.rackdservices.tftp: [info] grubx64.efi requested by
2023-12-01 10:10:50 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/command.lst requested by
2023-12-01 10:10:50 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/fs.lst requested by
2023-12-01 10:10:50 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/crypto.lst requested by
2023-12-01 10:10:50 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/terminal.lst requested by
2023-12-01 10:10:50 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg requested by
2023-12-01 10:10:50 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg-58:11:22:ce:07:ec requested by
2023-12-01 10:10:51 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-20.04/focal/stable/boot-kernel requested by
2023-12-01 10:10:52 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-20.04/focal/stable/boot-initrd requested by
2023-12-01 10:11:33 provisioningserver.rackdservices.dhcp_probe_service: [info] Probe for external DHCP servers started on interfaces: br0.
2023-12-01 10:11:43 provisioningserver.rackdservices.dhcp_probe_service: [info] External DHCP probe complete.
2023-12-01 10:12:45 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by
2023-12-01 10:12:45 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by
2023-12-01 10:12:46 provisioningserver.rackdservices.tftp: [info] grubx64.efi requested by
2023-12-01 10:12:54 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/command.lst requested by
2023-12-01 10:12:54 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/fs.lst requested by
2023-12-01 10:12:54 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/crypto.lst requested by
2023-12-01 10:12:54 provisioningserver.rackdservices.tftp: [info] /grub/x86_64-efi/terminal.lst requested by
2023-12-01 10:12:54 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg requested by
2023-12-01 10:12:54 provisioningserver.rackdservices.tftp: [info] /grub/grub.cfg-58:11:22:ce:07:ec requested by
2023-12-01 10:12:54 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-20.04/focal/stable/boot-kernel requested by
2023-12-01 10:12:55 provisioningserver.rackdservices.http: [info] /images/ubuntu/amd64/ga-20.04/focal/stable/boot-initrd requested by
After that it boots to initramfs busy box mode again T.T
I suspect the potential root cause is the image failed to bound to the NIC of my machine.
When I boot with Ubuntu 22.04 image, the eno1 hardware address is available with MACADDRESS mtu 1500 DHCP RARP. However, I receive the cloud-initramfs-dyn-netconf: did no find a nic with MACADDRESS when pxe booting with Ubuntu 20.04
Not sure if Ubuntu 20.04 does not support my UEFI:PXE IPv4 Realtek PCIe 2.5GBE Family Controller…
