[SERVER-28790] Mongo does not start with current dataset Created: 13/Apr/17  Updated: 13/Aug/18  Resolved: 02/May/17

Status: Closed
Project: Core Server
Component/s: Internal Code, WiredTiger
Affects Version/s: 3.4.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kal Assignee: Kelsey Schubert
Resolution: Done Votes: 0
Labels: envns, rfi, trcf, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2012 R2


Attachments: HTML File WiredTiger     File WiredTiger.basecfg     File WiredTiger.lock     File WiredTiger.turtle     File WiredTiger.wt     Text File mongo.log     File mongod.lock    
Operating System: Windows
Participants:

 Description   

Having used Mongo many times before I am having issues starting up Mongo with a particular dataset.

I have included all wiredtiger files and the mongo log and would really appreciate if you could investigate this isssue asap.



 Comments   
Comment by Kelsey Schubert [ 02/May/17 ]

Hi kal0007,

From your responses, I do not see anything to indicate a bug in the MongoDB server. For MongoDB-related support, please see our Technical Support page.

Thank you,
Thomas

Comment by Kal [ 19/Apr/17 ]

1. The disks are SSD's, we are not using RAID
2. The disk was corrupt, when Windows ran the disk recover, it corrupted the mongo DB files
3. Yes, the same version of MongoDB has been running
4. No I haven't but Windows Recovery may have copied or moved files
5. We don't have any backups
6. See above
7. The file system was check on 13/04/17 when windows ran the recovery.

I can supply you the database files if required as we have a very high profile customer waiting for this fix.

Comment by Mark Agarunov [ 14/Apr/17 ]

Hello kal0007,

I have a few additional questions about data storage and the configuration of your environment to help us understand what's going on here. However, beware in these sorts of situations it can be difficult to understand the cause of the corruption without a straightforward reproduction.

  1. What kind of underlying storage mechanism are you using? Are the storage devices attached locally or over the network? Are the disks SSDs or HDDs? What kind of RAID and/or volume management system are you using?
  2. Would you please check the integrity of your disks?
  3. Has the database always been running this version of MongoDB? If not please describe the upgrade/downgrade cycles the database has been through.
  4. Have you manipulated (copied or moved) the underlying database files? If so, was mongod running?
  5. Have you ever restored this instance from backups?
  6. What method do you use to create backups?
  7. When was the underlying filesystem last check and is it currently marked clean?

Thanks,
Mark

Comment by Mark Agarunov [ 14/Apr/17 ]

Hello kal0007,

Thank you for the report. Unfortunately the error in the logs indicates that there was likely corruption in the underlying storage layer. I would recommend a clean resync from a node that is not affected or restoring from a backup.
Additionally, please consider doing a thorough integrity check of the affected node's disk drives. If the failures continue to persist, you may need to replace them.

Thanks,
Mark

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