Skip to content
Staging deployment engine cannot resolve existing attached volume — infrastructure-level attachment mismatch
jeffson-bruno
OP

a month ago

Hello Railway Team,

I'm requesting human/staff investigation of an infrastructure-level volume attachment issue in a staging environment.

This issue was previously investigated in the Support AI thread:

Staging volume attachment missing at infrastructure level despite config declaration

The Support AI instructed me to open a new support thread here because the issue requires a Railway team member.

Environment: staging

Service: ordenis-v1.0

Volume: ordenis-v1.0-volume

Volume ID: e843d52c-180d-4ab0-ad54-ae0cbe9e0466

Expected mount path: /app/storage/app/private

Problem

Railway's dashboard, service configuration, and backend attachment records all report that the existing volume is attached to ordenis-v1.0 at /app/storage/app/private.

The volume is ready and contains approximately 83 MB of data.

However, the deployment engine consistently fails during PRE_DEPLOY_COMMAND with:

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

This creates an asymmetric state:

Storage/attachment backend: attached

Deployment engine: attachment not found

Troubleshooting already performed

The exact existing volume mount was re-declared through the Railway Agent using the same volume ID and the same mount path.

The configuration patch was applied and triggered another deployment.

That deployment successfully progressed to the deployment/pre-deploy stage but failed again with the identical no volume attached error.

Therefore, re-declaring the configuration did not repair the infrastructure-level attachment visibility.

The Support AI subsequently confirmed:

  • the existing volume is present;
  • Railway backend records show it attached to the staging service;
  • the mount path is correct;
  • approximately 83 MB of volume data is intact;
  • failed deployments stopped before container creation;
  • no data was written to or removed from the volume;
  • re-declaring the mount again will not resolve the issue;
  • this requires investigation by a Railway team member.

Current impact

ordenis-v1.0 staging application is currently offline because no new deployment can create a container with the expected volume.

PostgreSQL and the scheduler remain online.

Production is unaffected.

Data-safety constraints

Please preserve the existing volume and its data.

Please do not wipe, delete, or replace the volume without discussing it with me first.

Please do not modify the production environment.

I have intentionally not attempted a detach/reattach cycle because Railway's backend reports the existing attachment as valid and the volume contains persistent data.

Could a Railway team member please inspect why the deployment engine cannot resolve/access this attachment even though the storage backend reports it as attached?

If a detach/reattach or another infrastructure-level operation is required, please confirm the exact recommended procedure and its data-preservation implications before I perform it.

Thank you.

Solved

1 Reply

Status changed to Awaiting Railway 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.


Status changed to Awaiting User Response Railway • about 1 month 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...