[SERVER-60703] file:WiredTiger.wt, connection: WiredTiger.turtle: encountered an illegal file format or internal value Created: 14/Oct/21  Updated: 18/Oct/21  Resolved: 18/Oct/21

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

Type: Bug Priority: Major - P3
Reporter: HongRu Bai Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

hello,
My data is corrupted, there is no backup or replset due to mistake, I request help according to the instructions of Server-19815.

thanks!



 Comments   
Comment by Edwin Zhou [ 18/Oct/21 ]

Hi north.bai@foxmail.com,

Thank you for the update and we're happy to hear that --repair on MongoDB v4.0.27 was able to resolve your corruption!

To avoid a problem like this in the future, it is our strong recommendation to:

Best,
Edwin

Comment by HongRu Bai [ 16/Oct/21 ]

Thank you for your help.

I finally fixed my data using v4.0.27 --repair as suggested.

Thank you very much.

Comment by Edwin Zhou [ 15/Oct/21 ]

Hi north.bai@foxmail.com,

MongoDB v3.2 reached end of life in September of 2018. But we can provide limited guidance on this issue.

This error message leads us to suspect some form of physical corruption.
Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. Please try mongod --repair using the latest version of MongoDB.

In the event that a --repair operation is unsuccessful, then please also provide:

  • The logs leading up to the first occurrence of any issue
  • The logs of the repair operation.
  • The logs of any attempt to start mongod after the repair operation completed.

Best,
Edwin

Comment by HongRu Bai [ 14/Oct/21 ]

Affects Version/s: 3.2.6
Component/s: WiredTiger

Generated at Thu Feb 08 05:50:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.