Info

Hi, I'm using MongoDB 3.4. We are unable to start with the backup files of /data/db. As per the documentation, tried to repair DB with the following command but same error persists. mongod --repair --dbpath /db-path I have attached the log file.

Top User Comments

thomas.schubert commented on Thu, 25 Oct 2018 19:41:54 +0000: Hi yuvaraj We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, Kelsey nick.brewer commented on Wed, 26 Sep 2018 17:15:10 +0000: yuvaraj We'd like to take a closer look at what might be causing the repair to fail. Would it be possible for you to archive (tar or zip) and upload your entire dbpath directory? You can upload this information our secure portal - information shared there is only available to MongoDB employees, and is automatically removed after a period of time. Thanks, -Nick nick.brewer commented on Wed, 26 Sep 2018 14:40:59 +0000: yuvaraj Did you try booting from the same dbpath with your 3.4 installation after running the nightly build with --repair? Thanks, -Nick yuvaraj commented on Wed, 26 Sep 2018 07:18:40 +0000: Tried as per your comment. Here's the log : 2018-09-26T11:35:11.109+0530 I CONTROL [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none' 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] MongoDB starting : pid=24960 port=27017 dbpath=C:\Program Files\MongoDB\Server\4-nightly-build\db-data 64-bit host=CHETPDT017 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] db version v4.0.2-143-g7ea530946f 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] git version: 7ea530946fa7880364d88c8d8b6026bbc9ffa48c 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] allocator: tcmalloc 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] modules: none 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] build environment: 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] distmod: 2008plus-ssl 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] distarch: x86_64 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] target_arch: x86_64 2018-09-26T11:35:11.443+0530 I CONTROL [initandlisten] options: { repair: true, storage: { dbPath: "C:\Program Files\MongoDB\Server\4-nightly-build\db-data" } } 2018-09-26T11:35:11.443+0530 W STORAGE [initandlisten] Detected unclean shutdown - C:\Program Files\MongoDB\Server\4-nightly-build\db-data\mongod.lock is not empty. 2018-09-26T11:35:11.491+0530 I STORAGE [initandlisten] Detected data files in C:\Program Files\MongoDB\Server\4-nightly-build\db-data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2018-09-26T11:35:11.491+0530 W STORAGE [initandlisten] Recovering data from the last clean checkpoint. 2018-09-26T11:35:11.491+0530 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=3539M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress), 2018-09-26T11:35:11.636+0530 E STORAGE [initandlisten] WiredTiger error (-31803) [1537941911:635986][24960:140710473720144], txn-recover: __wt_txn_recover, 723: Recovery failed: WT_NOTFOUND: item not found Raw: [1537941911:635986][24960:140710473720144], txn-recover: __wt_txn_recover, 723: Recovery failed: WT_NOTFOUND: item not found 2018-09-26T11:35:12.004+0530 E STORAGE [initandlisten] WiredTiger error (-31803) [1537941912:4016][24960:140710473720144], txn-recover: __wt_txn_recover, 723: Recovery failed: WT_NOTFOUND: item not found Raw: [1537941912:4016][24960:140710473720144], txn-recover: __wt_txn_recover, 723: Recovery failed: WT_NOTFOUND: item not found 2018-09-26T11:35:12.315+0530 E STORAGE [initandlisten] WiredTiger error (-31803) [1537941912:315015][24960:140710473720144], txn-recover: __wt_txn_recover, 723: Recovery failed: WT_NOTFOUND: item not found Raw: [1537941912:315015][24960:140710473720144], txn-recover: __wt_txn_recover, 723: Recovery failed: WT_NOTFOUND: item not found 2018-09-26T11:35:12.351+0530 W STORAGE [initandlisten] Failed to start up WiredTiger under any compatibility version. 2018-09-26T11:35:12.351+0530 F STORAGE [initandlisten] Reason: -31803: WT_NOTFOUND: item not found 2018-09-26T11:35:12.351+0530 F - [initandlisten] Fatal Assertion 28595 at src\mongo\db\storage\wiredtiger\wiredtiger_kv_engine.cpp 645 2018-09-26T11:35:12.351+0530 F - [initandlisten] ***aborting after fassert() failure nick.brewer commented on Tue, 25 Sep 2018 22:34:45 +0000: yuvaraj Thanks for the additional details. I'm actually going to suggest a different repair process for you, which involves making use of some recently introduced updates to the {{ mongod --repair}} option. Important: Before you start this process, take a backup of your dbpath via a manual copy of the directory, or a filesystem snapshot. Download and untar the latest MongoDB 4.0 nightly release From the unpacked directory, run mongod --repair, and point it to your dbpath: bin\mongod.exe --repair --dbpath \path\to\corrupted\dbpath Once the repair completes, stop the 4.0 nightly mongod, and then start your regular 3.4 installation as you normally would. -Nick yuvaraj commented on Tue, 25 Sep 2018 13:03:06 +0000: Hey Nick, I have attached 2 files. The cause of the corruption (disk / filesystem failure, unexpected shutdown, etc) - It is raw data took from Folder level Backup. The platform (virtual machine, container, native hardware) - Virtual Machine nick.brewer commented on Tue, 25 Sep 2018 12:58:13 +0000: yuvaraj Thanks for your report. If you upload the WiredTiger.turtle and WiredTiger.wt files from your dbpath, we can attempt to repair them for you. We'll need to confirm: The cause of the corruption (disk / filesystem failure, unexpected shutdown, etc) The platform (virtual machine, container, native hardware) Thanks, -Nick

Steps to Reproduce