[SERVER-38854] once mongodb abruptly shutdown, --repair is used (3.6 version). but repair failed too Created: 04/Jan/19  Updated: 11/Jul/19  Resolved: 25/Apr/19

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

Type: Bug Priority: Major - P3
Reporter: Richard Xu Assignee: Danny Hatcher (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows server 2018R2


Attachments: Text File mongod.log    
Operating System: ALL
Participants:

 Description   

while running mongod --dbpath xxxx --repair, the run aborted

the log file is attached. 

 



 Comments   
Comment by Richard Xu [ 11/Jul/19 ]

Please give me a call when you have time, I want to see the options to officially deploy mongodb

Regards

Richard
832 277 0528

Comment by Danny Hatcher (Inactive) [ 28/Feb/19 ]

Hello Richard,

Are you still experiencing this issue?

Thanks,

Danny

Comment by Danny Hatcher (Inactive) [ 31/Jan/19 ]

Hi Richard,

I apologize for the belated response. Are you still unable to start your server? If so, would you be able to try running the --repair using 4.0.5 binaries? We've made a series of large improvements to our repair process in the 4.0 version.

Thank you,

Danny

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