This message was deleted.

Hi! I think you are running into two different errors, the error log in the first picture does not mean anything and can be ignored (i put up https://github.com/rancher/elemental-toolkit/pull/1857 to not run partx on a file that is not a device).

Thanks for replying. I am running below command: qemu-system-x86_64 -m 4096 -hda disk.qcow2 -bios /usr/share/qemu/ovmf-x86_64.bin -nographic

Hmm, that looks standard.. are you building an expandable disk image? also, what version of the toolkit are you using?

yes I expanded it using dd if=build/elemental-disk.raw of=somedisk.img bs=4M conv=notrunc then converted it in qcow2 using qemu-img convert -f raw -O qcow2 somedisk.img disk.qcow2. I am using elemental toolkit v1.1.0

Okay, what command did you use to build the disk?

sweta@localhost:~/elemental-toolkit> sudo docker images REPOSITORY TAG IMAGE ID CREATED SIZE local/elemental-toolkit v0.0.1-g cb4d8017fa7f 2 hours ago 426MB local/elemental-green v0.0.1-g 0f77a2d4fb6f 6 hours ago 722MB <none> <none> 528072fb6b42 6 hours ago 571MB sweta@localhost:~/elemental-toolkit> sudo docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd)/build:/build -v $(pwd)/manifest.yaml:/manifest.yaml --entrypoint /usr/bin/elemental docker.io/local/elemental-green:v0.0.1-g --debug build-disk --config-dir / -n elemental --local --squash-no-compression -o /build docker.io/local/elemental-green:v0.0.1-g

Do you have any config in manifest.yaml for the build disk spec?

I used the same manifest example as in git discussion

disk:
  unprivileged: true
  expandable: true
  recovery-system:
    fs: squashfs
  type: raw

Pretty weird that it wants to boot into active.. It should by default boot into the recovery image and try to expand the active/passive images and persistent partition...

Yes. Let me try

great, then it should run a reset and reboot into the active image..

so, if I use the raw image generated by build-disk is it expected then should I select the recovery option then elemental one . Then run elemental install cloudinit for elemental setup? Is it the expected behaviour?

The expected behaviour is that grub should boot by default into Elemental recovery on first boot, then run elemental reset to expand the system images and reboot into Elemental (the active image), without any user interaction..