Would you please look at this bug on maas discourse ?
It seems that lxd vm does not see second disk.
This was tracked down to that user running LXD 4.0.x which does not support block custom volumes. As a result, MAAS was actually allocating a filesystem volume, which then correctly did not show up as a block device (disk).
LXD is behaving as intended, MAAS needs to add a check on their side to only let the user create additional disks if on a LXD release which supports it.
1 Like