Reuse old volume in new machine after "irrepairable hardware damage"

,
41

And now I have this list of volumes

➜ fly vol list
ID                   	STATE  	NAME        	SIZE	REGION	ZONE	ENCRYPTED	ATTACHED VM   	CREATED AT
vol_n0l9vl2ddz8r635d*	created	sig_sgt_data	1GB 	ams   	f6b7	true     	              	1 year ago    	
vol_vppoe3mgn552qzwv 	created	sig_sgt_data	1GB 	ams   	7ef4	true     	              	1 month ago   	
vol_4qynyk60n20w9o6v 	created	sig_sgt_data	1GB 	ams   	759e	true     	              	1 minute ago  	
vol_vg7p7m8wye7kz3pv 	created	sig_sgt_data	1GB 	ams   	759e	true     	185e64eb449148	37 seconds ago	

* These volumes' hosts could not be reached.
42

That really is a fresh volume…

I think you might have hit a fly scale bug here, to be honest. I will poke through the source code a little.

In the meantime, so you can have your data back, how about the following alternative approach?

$ fly m stop  185e64eb449148  # and any other machines in the app
$ fly m clone 185e64eb449148 --attach-volume vol_4qynyk60n20w9o6v

You should see an explicit Attaching existing volume message, as it operates.

(You can delete the older machine(s) once you’re satisfied that this newest one does in fact have the restored volume.)

43

Ohh! I got my data back! :slight_smile:

Thank you!

1 Like
44

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