Skip to content
Deploys blocked: "expects a volume mounted… but the service has no volume attached" after deprecated-region change
ayylchyql-a11y
OP

a month ago

Service api (project mumisushi, environment production) has volume api-volume (ce565acd-8ed3-4154-b6d4-7051c7cb02fe) mounted at /app/apps/api/uploads.

After the automatic "ignore deprecated regions" change, every deploy fails at the pre-deploy step with:

"This deployment expects a volume mounted at /app/apps/api/uploads, but the service has no volume attached. Railway did not create the container."

  • The volume status is Ready, but its Volume Region field in the volume settings is empty.
  • Deployments 9bcd321a and 7cae1ec0 failed with the original region config (europe-west4).
  • We then manually switched the service region to europe-west4-drams3a, expecting a volume migration. Deployments cb90ad02 and 9f41f94d failed with the same error, and no migration started.
  • The old region can no longer be selected.
  • The currently active deployment (0dc26e44, europe-west4) is healthy. A volume backup was taken on 2026-10-06 21:40.

Please migrate the volume to europe-west4-drams3a, or advise how to proceed without data loss. This is a production service for a restaurant, so we'd like to avoid downtime during opening hours. Thank you!

Update: this looks like the same regression reported today in https://station.railway.com/questions/pre-deploy-rejected-for-missing-data-vo-c998bd1c and https://station.railway.com/questions/production-deploys-failing-no-volume-a-0332725d (it started around 18:50 UTC on 2026-10-06, also in other regions), so it may not be related to the region at all. Our pre-deploy command runs database migrations (prisma migrate deploy), so removing it is not a safe workaround for us.

Solved

6 Replies

Status changed to Awaiting Railway Response Railway • about 2 months ago


chandrika
EMPLOYEE

a month ago

Hey! Thanks for the detailed report. We tracked this down to a recent change on our side and we're rolling it back now. We'll update here once the rollout is done.

Your volume and its data are safe. Once the rollback is out, redeploying should go through with your volume mounted as usual.

If you detached your volume or deployed without it in the meantime, reply here before redeploying and we'll help make sure nothing written since then gets lost.


Status changed to Awaiting User Response Railway • about 2 months ago


chandrika
EMPLOYEE

a month ago

Since the service region was switched to europe-west4-drams3a while you were debugging, please hold off on redeploying until we've confirmed how that change affects your volume.


ayylchyql-a11y
OP

a month ago

Thanks! To answer your question: we never detached the volume. One more retry happened at 20:17 UTC (deployment 89bdf65c), before your message, and it failed with the same error; we haven't redeployed since. The active deployment is still healthy. Could you let us know when it's safe to redeploy? We'd ideally deploy before 10:00 CET tomorrow (before the restaurant opens).


Status changed to Awaiting Railway Response Railway • about 2 months ago


hunterhewitt1

a month ago

Following - Same issue here.


chandrika
EMPLOYEE

a month ago

Hey! Thanks for your patience, and sorry for the wait. The rollback is out, and we've checked the region question: your volume is already in the location that europe-west4-drams3a deploys to, so redeploying won't move it and your uploads stay where they are. You're safe to redeploy whenever suits you before opening. Let us know if anything looks off.


Status changed to Awaiting User Response Railway • about 1 month ago


ayylchyql-a11y
OP

a month ago

Thank you, Chandrika! Just redeployed: the volume is mounted, migrations ran fine and everything is up before opening. Really appreciate the quick fix and the follow-up!


Status changed to Awaiting Railway Response Railway • about 1 month ago


Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...