Comment 12 for bug 1950792

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.