Can't attach volume to machine

Questions / Help
,
1

Hi everyone,
I attempted an update, but a migration went wrong, so I rolled back to a previous commit and tried redeploying. I scaled machine count to 0 and then attempted to scale back up, but I kept encountering errors related to volume attachment. .

Eventually, I managed to scale up, but new volumes were created, and my primary volume vol_grnoqel12j13p9ev with crucial data is not attached to any machine. The attached image shows the current volume status. I need this volume because my prod data I there, I’m using pocketbase. Need a way to get back to this data.

I tried to do this command, but I keep getting the same error for every action I might try with this volume.

fly machines clone 185e647c177d18 --attach-volume vol_grnoqel12j13p9ev

Cloning Machine 185e647c177d18 into region ams
Attaching existing volume vol_grnoqel12j13p9ev
Provisioning a new Machine with image …
Error: failed to launch VM: insufficient resources to create new machine with existing volume ‘vol_grnoqel12j13p9ev’ (Request ID: 01J47JGQYT8M4WR31NF06W8VQV-otp)

2

Hi Rubin,

This is happening because the host server you’re trying to connect to has the creation of new Fly Machines disabled. To get around this, fork your Fly Volume (so that it contains the same data) and then scale up from the forked Volume. This would be done in two steps:

fly volumes fork --app <YOUR_APP_NAME> 185e647c177d18
fly machines clone 185e647c177d18 --attach-volume <THE_VOL_ID_FROM_PREVIOUS_STEP>

When you’re satisfied, you can delete the old volume.

Let me know how this works out for you.

3

Thanks for your reply, I managed to create a cloned volume and attach it to a machine. However, the clone volume has the same migration error that initially caused the build to fail initially. Now locally I have resolved this error, however, I cannot update the prod because I keep getting the same error preventing me from releasing an update. I am not sure if it is safe to delete the old, original volume: vol_grnoqel12j13p9ev. I just don’t want to lose my data.

I either need a solution how to successfully push and update for this bug, or a way to ssh to the server volume. Currently, I can’t because it is stopped.

Thank you!

Error: error creating a new machine: failed to launch VM: insufficient resources to create new machine with existing volume ‘vol_grnoqel12j13p9ev’ (Request ID: 01J47SGM0D7DHT4QHDGWWF6YWY-otp) (Trace ID: 2cb0d770856a4c9583559d056aa815b6)

4

If you know how to resolve this error from the shell, you can get a shell on your Fly Machine with fly ssh console. The Machine does have to be running first. If your error causes your Machine to reboot in a loop, you may have to first run a deploy where experimental.exec is set to sleep infinity or something similar in your fly.toml. That way the Fly Machine will boot, and do nothing, and then you can ssh in and do your fix manually.

5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.