Major - P3 After an unexpected shutdown, mongodb does not start properly.
I have tried the --repair run with mongo:3.2 and mongo:3.6, But no use.
Here is the console log:
2018-06-13T06:32:41.085+0000 I CONTROL [initandlisten] MongoDB starting : pid=13 port=27017 dbpath=/data/db 64-bit host=029732e706f2
2018-06-13T06:32:41.085+0000 I CONTROL [initandlisten] db version v3.2.20
2018-06-13T06:32:41.085+0000 I CONTROL [initandlisten] git version: a7a144f40b70bfe290906eb33ff2714933544af8
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1t 3 May 2016
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] allocator: tcmalloc
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] modules: none
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] build environment:
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] distmod: debian81
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] distarch: x86_64
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] target_arch: x86_64
2018-06-13T06:32:41.086+0000 I CONTROL [initandlisten] options: \{ repair: true }
2018-06-13T06:32:41.110+0000 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-06-13T06:32:41.110+0000 I STORAGE [initandlisten] Detected WT journal files. Running recovery from last checkpoint.
2018-06-13T06:32:41.110+0000 I STORAGE [initandlisten] journal to nojournal transition config: create,cache_size=46G,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),verbose=(recovery_progress),
2018-06-13T06:32:41.121+0000 E STORAGE [initandlisten] WiredTiger (-31802) [1528871561:121395][13:0x147775671cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2018-06-13T06:32:41.121+0000 E STORAGE [initandlisten] WiredTiger (0) [1528871561:121444][13:0x147775671cc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2018-06-13T06:32:41.121+0000 E STORAGE [initandlisten] WiredTiger (0) [1528871561:121455][13:0x147775671cc0], 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
2018-06-13T06:32:41.121+0000 E STORAGE [initandlisten] WiredTiger (0) [1528871561:121469][13:0x147775671cc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2018-06-13T06:32:41.122+0000 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2018-06-13T06:32:41.122+0000 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2018-06-13T06:32:41.122+0000 I CONTROL [initandlisten] dbexit: rc: 100