I'm now trying to migrate it back to see if the disk wants to re-link. I have no idea how long this should normally take but I feel like its taking longer than usual for ~200mb of data.

My fault for trying, I guess. The entire container is no longer available.

Hey there! Thats not supposed to happen. I just flipped the volume state to ready. Would you be alright if i try to deploy it in EU West manually?

Sure thing, go ahead 🫡

Edit: I won't go touch, but the disk seems to now be in Singapore but the container is EU West.
Edit 2: I think me clicking on the postgres service initiated a re-deploy and failed, or the timestamp is just bugged.

It's been down for a bit too long now - would deleting the service and restarting a new one work? Docs says volumes unmount if the service gets removed, but we also can't download the volume ourselves via the dashboard to backup ourselves, so...

Mounting the volume in another postgresql service doesn't seem to work. The deployment starts fine if using another volume.

We're getting this spammed in the logs:
Railway volume not mounted to the correct path, expected /var/lib/postgresql/data but got
Please update the volume mount path to the expected path and redeploy the service

... and in the volume we see Directory that this volume is mounted to in Postgres. /var/lib/postgresql/data

Both are now in the same region.

We restored from a backup - which previously didn't work - and the volume mounted. I guess... resolved?

I'm still not sure what caused it in the first place.

Hmm me neither I'm not quite sure. If you see this again, can you let me know? Want to dive in then