New Volume Was Created but not by Me

I noticed my machine was rolling in an attempt to start, but failing to boot. As I started looking into the logs, I noticed a change - there’s a new volume that had been created several days ago, and the prior one is pending_destroy. I didn’t create the new one, so I’m assuming it was an automatic thing. Unfortunately, because the machine won’t mount the Docker image I’m using (Ghost for my blog), I’m unable to debug or even retrieve my data, and it appears that my whole blog is about to be deleted permanently.

I tried the config override with ‘sleep inf’ just to get it mounted, but no luck (see log below). Anyone have any other suggestions on how I can recover?

2025-08-18T15:11:14.176 proxy[1781954b4d7589] dfw [info] Starting machine

2025-08-18T15:11:14.298 app[1781954b4d7589] dfw [info] 2025-08-18T15:11:14.298170770 [01K2YVC8NJMW2XHQED4NBY6ABR:main] Running Firecracker v1.12.1

2025-08-18T15:11:14.298 app[1781954b4d7589] dfw [info] 2025-08-18T15:11:14.298331192 [01K2YVC8NJMW2XHQED4NBY6ABR:main] Listening on API socket (“/fc.sock”).

2025-08-18T15:11:15.135 app[1781954b4d7589] dfw [info] INFO Starting init (commit: 34faef9)…

2025-08-18T15:11:15.218 app[1781954b4d7589] dfw [info] INFO Checking filesystem on /var/lib/ghost/content

2025-08-18T15:11:15.221 app[1781954b4d7589] dfw [info] /dev/vdc: clean, 707/195840 files, 43946/785408 blocks

2025-08-18T15:11:15.222 app[1781954b4d7589] dfw [info] INFO Mounting /dev/vdc at /var/lib/ghost/content w/ uid: 0, gid: 0 and chmod 0755

2025-08-18T15:11:15.245 app[1781954b4d7589] dfw [info] INFO Resized /var/lib/ghost/content to 3217031168 bytes

2025-08-18T15:11:15.252 app[1781954b4d7589] dfw [info] INFO Preparing to run: `docker-entrypoint.sh sleep inf` as root

2025-08-18T15:11:15.254 app[1781954b4d7589] dfw [info] INFO [fly api proxy] listening at /.fly/api

2025-08-18T15:11:15.272 runner[1781954b4d7589] dfw [info] Machine started in 1.09s

2025-08-18T15:11:15.273 proxy[1781954b4d7589] dfw [info] machine started in 1.097591423s

2025-08-18T15:11:15.508 app[1781954b4d7589] dfw [info] 2025/08/18 15:11:15 INFO SSH listening listen_address=[fdaa:0:e83e:a7b:9f67:3c6c:50b1:2]:22

2025-08-18T15:11:20.599 proxy[1781954b4d7589] dfw [info] waiting for machine to be reachable on 0.0.0.0:2368 (waited 5.326121216s so far)

2025-08-18T15:11:23.631 proxy[1781954b4d7589] dfw [error] [PR03] could not find a good candidate within 1 attempts at load balancing. last error: [PM05] failed to connect to machine: gave up after 15 attempts (in 8.331761415s)

And right after I posted this, I managed to solve the issue (or at least get it running again). I simply repushed my fly.toml with a ‘fly deploy’ and everything worked itself out.

Sharing for future seekers…

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