Skip to content
Deployment validator says attached
/data
volume is missing in staging and production
gogoseang
OP

a month ago

Deployments for my GoGoLOTRO service are failing before the pre-deploy command starts:

This deployment expects a volume mounted at /data, but the service has no volume attached.

However, Railway’s environment state and service configuration both show that the volume exists and is attached at /data.

Staging

  • Service: GoGoLOTRO (65c46ffd-a146-4e6d-8831-443c16802e0d)
  • Environment: staging (fea25ae8-bdb7-4ac2-8cca-3627926df763)
  • Volume: gogolotro-volume (f17a9da2-fc43-475d-8db0-979c3dd359a6)
  • Failed deployments:
    • c89eecbb-dc1a-4775-8c40-8f8a518e1a6e
    • edade193-b067-4a71-bdeb-62064fa4a480

Production is failing with the same validation error:

  • Failed deployment: 28004953-aec0-4cef-b824-9867544a20f9

The build succeeds, but container creation is blocked before the pre-deploy command executes. Previous deployments of the same commit succeeded. The issue appeared in both environments at approximately the same time.

Railway’s diagnostic assistant confirmed that the volume registry and deployment validator appear to disagree. Diagnostic thread:

https://station.railway.com/support/volume-attachment-metadata-mismatch-val-d6f5c0f0

The volume contains persistent ASP.NET data-protection keys. Can a Railway team member repair or refresh the attachment metadata without requiring the volume to be deleted or recreated?

Solved

3 Replies

markwitt1

a month ago

having the same issue


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


reidnotai

a month ago

same issue here as well.


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


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


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.


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...