2 months ago
We canceled a query with an INSERT and the database crashed and the log indicated the database needed to be resized and possible data corruption. We tried to resize the volume to 1 GB and then to 5GB, but no luck getting it to repair itself.
We then detached the current volume and attached a new one to it, but it's still not starting up. Logs attached. Please help! Very much appreciated.
Attachments
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Hey! The volume resize you applied didn't fully propagate to the underlying storage, which is why your database kept crash-looping even after resizing. We've gone ahead and corrected this on your end.
You should now see the full 5 GB of disk space available after redeploying.
We've also shipped a fix to prevent this from happening on future volume resizes.
Status changed to Awaiting User Response Railway • about 2 months ago
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