invalid bootorder: device 'scsi0' does not exist'

[SebTardif]

Got this using any any of the two kind of TrueNAS and same version you had in the script... I didn't modify the script at all.

TrueNAS-13.0-U5.3.iso: OK
~
update VM 108: -efidisk0 local-lvm:0,format=qcow2,efitype=4m,pre-enrolled-keys=0,size=528K
unsupported format 'qcow2' at /usr/share/perl5/PVE/Storage/LvmThinPlugin.pm line 87.
update VM 108: -scsi0 file=local-lvm:32,format=qcow2,iothread=1 -scsihw virtio-scsi-single
unsupported format 'qcow2' at /usr/share/perl5/PVE/Storage/LvmThinPlugin.pm line 87.
update VM 108: -ide2 media=cdrom,file=none
update VM 108: -ide2 media=cdrom,file=local:iso/TrueNAS-13.0-U5.3.iso
update VM 108: -boot order=ide2;scsi0
invalid bootorder: device 'scsi0' does not exist'

Convert VM to template? (y/n) 

Then we can see no harddrive and boot order start with network...

Then I manually added harddrive and boot with harddrive before ISO, then it boot.

[roib20]

Thank you for reporting this issue. I will look into this soon, unfortunately my Proxmox server crashed just as I tried looking into this. I understand you got it to work manually so that's great!

However I would avoid using the current versions of TrueNAS due to a nasty ZFS bug. See here for information about this bug and affected TrueNAS CORE versions: https://www.truenas.com/community/threads/silent-corruption-with-openzfs-ongoing-discussion-and-testing.114390/

I am personally waiting for TrueNAS to update their versions before updating my script.

[bengkelgawai]

This happened for me, because creating VM Disks via script was failed. For me, this was because I didn't allow VM Disks in "local" but chose "local" as storage. Maybe different cause for others, but disk creation via script to the chosen storage should be successful