[SERVER-36320] I am unable to access my Mongo DB due to an improper shutdown. My coworker recently went through this and I am copying in description what he advised for me to do, let me know if there is anything else I need to provide. Created: 26/Jul/18  Updated: 29/Oct/19  Resolved: 27/Aug/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Victor Garcia Assignee: Nick Brewer
Resolution: Incomplete Votes: 0
Labels: envns, rpns, rpo, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File WiredTiger.turtle     File WiredTiger.wt     File repair-attempt.tar.gz    
Operating System: ALL
Participants:

 Description   

I just recently ran into the issue of a corrupt Lair database due to an improper shutdown. The cause, indicated by the error, was a corrupted WiredTiger.wt file. The fix for this is to submit a JIRA ticket to the guys over at mongodb (https://jira.mongodb.org/) explaining your issue, a copy of the stack trace, and a copy of your WiredTiger.wt and WiredTiger.turtle files. They sent over the fixed versions of the files shortly after (1 hour).

This led to a successful repair and the recovery of all of my lair data!



 Comments   
Comment by Victor Garcia [ 29/Oct/19 ]

Done. Thanks! Issue is WT-5205.

Comment by Kelsey Schubert [ 29/Oct/19 ]

migvic3, would you please open a new ticket and reference this one?

Thanks,
Kelsey

Comment by Victor Garcia [ 29/Oct/19 ]

Hello,

 

My files have corrupted after I lost power. Issue is same as the above which I submitted last year. Would I need a new ticket or can I work off of this one?

Comment by Nick Brewer [ 20/Aug/18 ]

migvic3 Since we haven't heard back from you, I'm going to close this ticket. If you have a moment to provide the information requested previously, it would greatly assist in better tracking this issue.

Thanks,
Nick

Comment by Nick Brewer [ 03/Aug/18 ]

migvic3 Checking in to see if the repair attempt resolved this for you. If you have a moment to answer the platform / version questions, it would assist in better tracking this issue.

Thanks,
Nick

Comment by Nick Brewer [ 27/Jul/18 ]

migvic3 I've attached the files after a repair attempt. Would you please extract these files, substitute them for the current ones in your $dbpath, and let us know if it resolves the issue?

Additionally, I'd like to confirm the following:

  • The operating system and version on which the mongod was running
  • The MongoDB version in use at the time
  • The underlying cause of the crash (power failure, disk corruption, etc)
  • The environment (native, virtualized, container)

Thanks,
Nick

repair-attempt.tar.gz

Generated at Thu Feb 08 04:42:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.