Error Couldn't allocate volume, no disks available (region: dfw, size_gb: 1)

1

There seems to be a persistent problem this morning with deploying new machines/DBs, we’ve gotten a similar message across multiple attempts.

fly pg create --region dfw --vm-size shared-cpu-1x --name pr200-5eeefd3-beacon-db --volume-size 1 --organization beacon --initial-cluster-size 1

results in

Creating postgres cluster pr200-5eeefd3-beacon-db in organization beacon
9
10
11
Launching...⣾ WWWWWWWWWWWWWWW
12
13
Launching...⣽ WWWWWWWWWWWWWWW
14
15
Launching...⣻ WWWWWWWWWWWWWWW
16
17
Launching...⢿ WWWWWWWWWWWWWWW
18
19
Launching...⡿ WWWWWWWWWWWWWWW
20
21
Launching...⣟ Error Couldn't allocate volume, no disks available (region: dfw, size_gb: 1)
2

Hey there,

This problem should be resolved. Can you confirm?

3

Hey @shaun! It looks like I can create a DB but now I see the following when getting to the next step:

fly deploy --region dfw --app pr200-5ebe7aa-beacon -c fly.preview.toml

results in

...
==> Monitoring deployment

v0 is being deployed

1a5211ec: dfw pending
--> v0 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v1 

--> Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/

Error abort

Update: This seems to have been resolved about 3 hours after I posted, around 5pm CT. Thanks!

1 Like