I have a stuck volume (id: 459cd623-3ddd-4cb1-8750-1945c2d439be) on service telegram-gateway in project 7c7bffbe-890a-4667-8af9-a4dd02d8b02c that is blocking me from mounting a new volume at /opt/data. Current state: - Volume status: isPendingDeletion = true, deletedAt = 2026-07-28T12:29:42Z - Service reports: hasVolume = false - Volume does NOT appear on the project canvas, despite being mounted - The volume's data is fully backed up; losing it is acceptable — I only need the mount point released What I've tried: - `railway volume detach` reports "detached" but the volume remains attached to the service - `railway volume add -m /opt/data` fails with "A volume is already mounted on service telegram-gateway" - Checking the project canvas for a delete/force-delete button — the volume doesn't appear there What I need: Please force-clear this stuck volume so the /opt/data mount is free and I can attach a new persistent volume to telegram-gateway. The volume will auto-delete tomorrow at 1:29 PM, but I need to restore service functionality now.

Volume ID - Railway Central Station

Volume ID

chloedaly

HOBBYOP

2 months ago

I have a stuck volume (id: 459cd623-3ddd-4cb1-8750-1945c2d439be) on service telegram-gateway in project 7c7bffbe-890a-4667-8af9-a4dd02d8b02c that is blocking me from mounting a new volume at /opt/data.

Current state:

Volume status: isPendingDeletion = true, deletedAt = 2026-07-28T12:29:42Z
Service reports: hasVolume = false
Volume does NOT appear on the project canvas, despite being mounted
The volume's data is fully backed up; losing it is acceptable — I only need the mount point released

What I've tried:

railway volume detach reports "detached" but the volume remains attached to the service
railway volume add -m /opt/data fails with "A volume is already mounted on service telegram-gateway"
Checking the project canvas for a delete/force-delete button — the volume doesn't appear there

What I need:

Please force-clear this stuck volume so the /opt/data mount is free and I can attach a new persistent volume to telegram-gateway.

The volume will auto-delete tomorrow at 1:29 PM, but I need to restore service functionality now.

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • 2 months ago

mayori

MODERATOR

2 months ago

(see Mykal response below)

mykal

EMPLOYEE

2 months ago

Hey! just took a look at this for you.

Nothing's stuck, and your data is all good; The volume you named (459cd623) doesn't exist anymore, it finished deleting on July 28.

What's mounted at /opt/data now is a different volume, telegram-gateway-volume, created 14 minutes after the previous one was removed. It's healthy, holding about 2.6 GB, and tonight's deploy mounted it fine. railway volume add -m /opt/data is failing as there's already a working volume there.

Don't use Swap Volume for this. It would detach the volume your data is actually on.

Status changed to Awaiting User Response Railway • 2 months ago

mykal

EMPLOYEE

2 months ago

I do see that your service telegram-gateway is throwing HTTP 404s from Nous Research's API Gateway because a model you've requested isn't in their catalog. That may be causing the deploy to fail on startup

Railway

BOT

2 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 • about 2 months ago

Welcome!