Skip to content
Still failing after the rollback: pre-deploy rejected with "no volume attached" (volume attached, never detached)
daniemagic
OP

a month ago

Our deploys are still failing after the rollback announced at 20:47 UTC today (Oct 6).

Setup: one service in us-east4 with a volume attached at /data and a pre-deploy command. The volume is mounted in the currently running deployment. Nothing was detached and no settings were changed.

Timeline (UTC, Oct 6):

17:52 last successful deploy.

18:47 first failure; every deploy since has failed the same way.

21:57 and 22:40: retries after the rollback announcement also failed.

Each one fails at "Deploy > Pre deploy command" within 1-2 seconds, after a successful build, with no deploy logs:

"This deployment expects a volume mounted at /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."

Latest failed deployment ID: ea8d2fd7-ff61-4b2b-977a-9e1fc50f7f30

Is the rollback complete for us-east4, and is there anything we need to do on our side beyond redeploying?

Solved

5 Replies

jonathanluckett

a month ago

same issue here, the only way to fix is to delete the volume, create a new one, and re-attach.... which is not a good solution if you are live.


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


daniemagic
OP

a month ago

dang I wonder what happened


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


anshullaikar

a month ago

I created a rescue service - connected the volume to it via CLI & migrated all the data out to S3 for now.

@Railway team I am never using volumes again for sure. Can't use railway for serious projects like this - thankfully this was an internal service.


hackvhilzan

a month ago

Same issue here. Project "Zarabots", service "Zarabot" (production, EU West). Volume "zarabot-volume" attached at /data. A deployment at ~12:05 UTC today succeeded; since ~20:03 UTC every deployment fails at "Pre deploy command" with the same "expects a volume mounted at /data, but the service has no volume attached" error. No config changes on our side.


chandrika
EMPLOYEE

a month ago

Hey! Thanks for the detailed report. This was caused by a recent change on our side, and we've now rolled it back. Deploys with a volume and a pre-deploy command should go through again, so please redeploy and your volume will be mounted as usual. Your volume and its data weren't affected.

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

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


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


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...