Yes, but /dev/vda is rootfs (ephemeral store mounted on /), which is 8Gs and comes for free with every Fly VM.
Persistent store (volumes) are (from what I have observed) virtual block device /dev/vdc (ex).
So, I guess, /data hasn’t been mounted at all… I haven’t used flyctl m update with volumes, may be someone else who has will chime in. You can also choose to run LOG_LEVEL=debug flyctl m update ... to see where the cmd is going wrong.
Kind of started over and launched a new machine first without ports and the volume seem to have mounted correctly. The volume now shows when listing machines and the size is ~1gb and encrypted. Updated the machine to expose the ports and all seems fine now.
@Safinn As you’ve observed, you can’t use m update to change which volume is mounted to a VM (you can use it to change the mount point, though). The UX is in flux, though. (Edit to clarify: afaik you’ll still need to mount the volume at machine creation time.)
Did you get any error from fly m update? I think it will error if you try to update to a different volume if you already had one mounted, but I don’t know if trying to mount one to an already-created volume-less machine is caught by that.
I see, thank you for the information. I didn’t get an error when trying to add a volume to an already volume-less machine but the diff of the config showed that it would add a mount but the details were wrong. I haven’t tried changing volumes once I got one attached.