Hello,
I have seen other issues with similar corruption as I'm seeing on my mongo instance. I've attached my wiredtiger files in the hopes that you can repair them as you have others. My server suffered a
Thanks!
2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] MongoDB starting : pid=13877 port=27017 dbpath=/data/db 64-bit host=288259c1abe3 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] db version v3.4.9 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] git version: 876ebee8c7dd0e2d992f36a848ff4dc50ee6603e 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] allocator: tcmalloc 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] modules: none 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] build environment: 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] distmod: debian81 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] distarch: x86_64 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] target_arch: x86_64 2017-10-04T03:57:15.471+0000 I CONTROL [initandlisten] options: {} 2017-10-04T03:57:15.496+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'. 2017-10-04T03:57:15.496+0000 I STORAGE [initandlisten] 2017-10-04T03:57:15.496+0000 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine 2017-10-04T03:57:15.496+0000 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem 2017-10-04T03:57:15.496+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=1459M,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),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0), 2017-10-04T03:57:15.546+0000 E STORAGE [initandlisten] WiredTiger error (-31802) [1507089435:546504][13877:0x7f5e8be59d40], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error 2017-10-04T03:57:15.546+0000 E STORAGE [initandlisten] WiredTiger error (0) [1507089435:546613][13877:0x7f5e8be59d40], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata 2017-10-04T03:57:15.546+0000 E STORAGE [initandlisten] WiredTiger error (0) [1507089435:546637][13877:0x7f5e8be59d40], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk 2017-10-04T03:57:15.546+0000 E STORAGE [initandlisten] WiredTiger error (0) [1507089435:546676][13877:0x7f5e8be59d40], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options 2017-10-04T03:57:15.557+0000 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 269 2017-10-04T03:57:15.572+0000 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating 2017-10-04T03:57:15.572+0000 I NETWORK [initandlisten] shutdown: going to close listening sockets... 2017-10-04T03:57:15.572+0000 I NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock 2017-10-04T03:57:15.572+0000 I NETWORK [initandlisten] shutdown: going to flush diaglog... 2017-10-04T03:57:15.572+0000 I CONTROL [initandlisten] now exiting 2017-10-04T03:57:15.572+0000 I CONTROL [initandlisten] shutting down with code:100