[root@dcvsl122 mongodb]# docker run -it -v /docker/services/mongodb/db01:/data/db mongo:3.6.23 mongod --repair
2022-03-18T01:44:35.199+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=78ef85a9ea2b
2022-03-18T01:44:35.199+0000 I CONTROL  [initandlisten] db version v3.6.23
2022-03-18T01:44:35.199+0000 I CONTROL  [initandlisten] git version: d352e6a4764659e0d0350ce77279de3c1f243e5c
2022-03-18T01:44:35.199+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
2022-03-18T01:44:35.199+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2022-03-18T01:44:35.199+0000 I CONTROL  [initandlisten] modules: none
2022-03-18T01:44:35.200+0000 I CONTROL  [initandlisten] build environment:
2022-03-18T01:44:35.200+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
2022-03-18T01:44:35.200+0000 I CONTROL  [initandlisten]     distarch: x86_64
2022-03-18T01:44:35.200+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2022-03-18T01:44:35.200+0000 I CONTROL  [initandlisten] options: { net: { bindIpAll: true }, repair: true }
2022-03-18T01:44:35.203+0000 W -        [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
2022-03-18T01:44:35.206+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2022-03-18T01:44:35.207+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
2022-03-18T01:44:35.208+0000 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
2022-03-18T01:44:35.208+0000 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=31620M,cache_overflow=(file_max=0M),session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2022-03-18T01:44:35.823+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1647567875:823824][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 604: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error Raw: [1647567875:823824][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 604: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2022-03-18T01:44:35.823+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1647567875:823889][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 611: WiredTiger has failed to open its metadata Raw: [1647567875:823889][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 611: WiredTiger has failed to open its metadata
2022-03-18T01:44:35.823+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1647567875:823900][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 614: This may be due to the database files being encrypted, being from an older version or due to corruption on disk Raw: [1647567875:823900][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 614: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2022-03-18T01:44:35.823+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1647567875:823928][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 617: You should confirm that you have opened the database with the correct options including all encryption and compression options Raw: [1647567875:823928][1:0x7f2bc0d96a40], file:WiredTiger.wt, connection: __wt_btree_tree_open, 617: You should confirm that you have opened the database with the correct options including all encryption and compression options
2022-03-18T01:44:35.826+0000 F STORAGE  [initandlisten] WiredTiger metadata corruption detected
2022-03-18T01:44:35.826+0000 F STORAGE  [initandlisten] This version of MongoDB is unable to repair this kind of corruption, but version 4.0.3+ may be able to repair it. See http://dochub.mongodb.org/core/repair for more information.
2022-03-18T01:44:35.826+0000 F -        [initandlisten] Fatal Assertion 50944 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 71
2022-03-18T01:44:35.826+0000 F -        [initandlisten] \n\n***aborting after fassert() failure\n\n