Skip to content
Pre-deploy fails: 'expects a volume mounted at /app/data' but volume IS attached
mkoyan333
OP

a month ago

Hi Railway team,

Every deploy of our backend service now fails at the pre-deploy step, before our pre-deploy command (prisma migrate deploy) even runs, with:

"This deployment expects a volume mounted at /app/data, but the service has no volume attached. Railway did not create the container: it would have run without the volume, and data written there is lost on the next deploy. Attach a volume at /app/data, or remove the mount, and deploy again."

But the volume IS attached:

  • Canvas shows backend-volume under the backend service; volume settings show Mount Path /app/data.

railway volume list reports: backend-volume, Attached to: backend, Mount path: /app/data, 92MB used, Status: Ready.

  • No volume changes were made; Activity shows only variable changes.

Details:

  • Project: aurumflow (54e4b800-2216-4275-b178-bfe6aa78188a), environment production, service backend (f62da7d0-6e19-4a70-9a5c-69922ec90b22), region us-west2, Dockerfile build.
  • Failed deployments: 262d1457-4460-47cb-93b4-b039e9502728 (2026-10-06 19:10 UTC) and 6917b070-b639-4543-b547-d8e128961d27 (2026-10-06 20:00 UTC). Build succeeds both times.
  • Last successful deploy with the same volume setup: 3e082656-d446-466c-957c-40f5d1141552 (2026-10-06 17:11 UTC) — still serving traffic.
  • Your Diagnose tool reports "Infrastructure Error": the service config lists the volume at /app/data but the platform reported none attached.
  • Possibly related: the project also has an orphaned volume postgres-volume-WQHG (Attached to: N/A, mount /var/lib/postgresql/data) left from a deleted service.

Could you please check the volume attachment for this service on your side? Please do NOT delete or recreate backend-volume — it holds data. We're blocked from shipping a release until this is fixed.

Thanks!

Solved

8 Replies

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


ramchandra-st

a month ago

We are getting same issues atm. Railway team please fix this soon.


ramchandra-st

a month ago

But -> https://status.railway.com/ is green, I would expect those outage there if possible :)


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.

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 1 month ago


Anonymous

a month ago

Can you please let us know when this is fixed? We are unable to deploy due to this issue.


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


kingmoc

a month ago

We’re seeing the same pre-deploy failure: Railway reports no volume attached at /data, although the dashboard and API show the volume attached and READY. Both our GitHub deployment retry and a direct Railway redeploy returned the same error. The previous backend deployment is still running, and we haven’t changed or removed the volume.

Thanks for identifying the Railway-side change. Has the rollback completed, and is it safe to retry the failed deployment now?


hackvhilzan

a month ago

Thanks for the quick fix! Confirming it's working again on our side: deployments for service "Zarabot" (project Zarabots, production, EU West) now go through with the volume mounted at /data as usual. Nothing was detached or deployed without the volume in the meantime, so no data recovery needed. Appreciate the help!


chandrika
EMPLOYEE

a month ago

Hey! The rollback is out, and deploys with a volume and a pre-deploy command should go through again. Please redeploy and your volume will be mounted as usual.

Sorry for the disruption, and let us know if anything still fails.


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


ikethaler

a month ago

Working, thank you


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


Status changed to Solved sam-a • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...