I am having similar problems since updating from 3.0 to the latest release 3.2.6
We mainly use legacy boot (instead of UEFI) and the boot order of all our nodes is set to: 1. Network/PXE 2. harddisk A deployed node would boot PXE and then immediately MAAS tells it (not sure how exactly) to boot from the harddrive instead. This doesn't seem to work anymore with 3.2.6. Instead of booting the node stops with a kernel panic. Error messages I can see on the screen are (nothing in the SOL at this early stage): ``` VFS: Cannot open root device "squash:http://172.17.100.3:5248/images/ubuntu/amd64/ga-20.04/fo"; or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ``` If I set the harddisk as first boot device in the BIOS the node boots okay. Commission of a node works, and new deployments work up to the point where the node would boot into the newly installed OS, then above error prevents it from succeeding. Then I need to manually change the boot order to allow deployment to succeed. Any idea what has changed here from 3.0 to 3.2? What is the recommended boot order for legacy boot now? I suppose nowadays MAAS requests PXE boot via IPMI whenever needed, so hard disk as first boot option should work. But I remember this was not always the case when we started using it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950792 Title: No boot possible - Cannot open root device Status in MAAS: Triaged Status in linux package in Ubuntu: Incomplete Bug description: MaaS cannot boot on my X11DPi-NT and will therefore fail to commission. It will instantly fail after grub. It will fail to boot saying that is not able to open root device. I even tried supplying the squashfs via python on a different port as the url is somehow cut off a bit, but to no avail. The python webserver doesn't even see any connection try. ( custom kernel params: root=squash:http://10.0.33.253:8080/squashfs python webserver: python3 -m http.server 8080) Steps to reproduce: 1. Setup maas ;) 2. Try to commision server 3. See the kernel and initrd download fly by 4. Boom kernel panic Hardware: Supermicro X11DPi-NT with UEFI http Networkboot enabled NIC: Intel X722 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1950792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
