My Postgres service is unable to mount its persistent volume. Two consecutive deployments since May 11 have failed with the same pattern: the container gets stuck in a volume mount loop with exponential backoff and never starts. The volume exists and contains ~220MB of data, but the mount operation never completes.

Service Details:

• Service ID: 93007053-92ae-4f78-92a8-6881eb3fca04
• Service Name: Postgres
• Volume ID: b55740b6-1740-48db-bc84-d86c9af6528a
• Volume Name: postgres-volume
• Volume Size: 5GB
• Data in volume: ~220MB

Failed Deployments:

• Deployment ID: b2cb7efa-dfe4-4183-8254-11cbb86b3483 (May 12, 2026)
• Previous deployment (May 11, 2026)

Last Successful Deployment: April 26, 2026

Issue: The container repeatedly attempts to mount the volume with exponential backoff intervals, then stops. No Postgres process ever starts. Configuration, image, and resources are unchanged from the last successful deployment. This appears to be an infrastructure-level volume attachment issue.

Request: Please investigate the volume attachment mechanism on the infrastructure side.