MongoDB production database crashed after storage grow – service not starting and data appears lost
clujball
HOBBYOP
4 months ago
My MongoDB database service crashed suddenly in production.
After noticing storage-related issues, I performed a storage grow operation. Since then, the database service does not start anymore and never connects. All connection attempts fail, and the service remains unavailable.
At this point, it looks like all data may have been lost, as the database does not respond and no collections are accessible.
What I’ve observed so far:
- The crash happened unexpectedly in production
- The issue started after performing a storage grow
- MongoDB does not come back up after the operation
- The service does not accept connections at all
- Data appears to be missing or corrupted
This database is critical for production, so I need urgent help to:
- Understand what went wrong during or after the grow operation
- Determine whether the data can be recovered
- Restore the database service as soon as possible
Please let me know if you need logs, configuration details, or any additional information to investigate further.
1 Replies
Status changed to Awaiting User Response Railway • 4 months ago
Status changed to Closed brody • 4 months ago