Volume Migration Failed Post-Metal Migration – Risk of Data Loss
therealesttor
HOBBYOP

5 months ago

Hi Railway team,

believe our Postgres service was auto-migrated to Railway Metal, and we're now seeing this error on deploy:

Deployment failed during the pre-deploy process Volume migration failed

Our situation:

  • The volume committee-volume is still active and mounted

  • The region is EU West (Amsterdam) [Metal (NEW)]

  • Grafana and other services are still pulling and writing data, so the old container is functioning

  • We have not redeployed or rolled back yet

  • We've taken a full backup via .sql export

Can you please advise:

  1. Whether this volume can be safely remounted

  2. If a redeploy now would orphan or reset the volume

  3. Whether we can rollback to the pre-migration state manually

Project: Meticulous Creation
Database Image: ghcr.io/railwayapp-templates/postgres-ssl:16
Volume: committee-volume
Status: Data still flowing through other services

Solved

1 Replies

itsrems
EMPLOYEE

5 months ago

Heya, so, your migration failed, and we kept the old deploy up.

I know the UI is a bit confusing but your data is safe; you can redeploy the service, and we'll migrate it at another time.

Sorry for the impact !

Best,

Nico

Status changed to Awaiting User Response Railway • 5 months ago

Railway
BOT

4 months 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 • 4 months ago

Loading...