Data type MongoDB 3.x data capacity gb failure type Server power loss causes WIREDTIGER.WT file corruption Start error detected data files in E:\DTLFolder\MongoDB\dat A created by the ' Wiredtiger ' storage engine, so setting the active storage engine to ' Wiredtiger '. 2018-05-08t16:10:09.755 +0800 I STORAGE [initandlisten] Wiredtiger_open config:create,cache_size=18g,session_max=20000,eviction= ( 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), 2018-05-08t16:10:09.765+0800 E STORAGE [initandlisten] Wiredtiger (0) [1525767009:765885][6772:140729286678224 ], FILE:WIREDTIGER.WT, Connection:read checksum error for 4096B block at offset 24576:block header checksum of 391507870 5 doesn ' t match expected checksum of 3915078719 repair results file After parsing WIREDTIGER.WT does not match the checksum of the boot file store. Manually parse the error message. Complete the recovery. Database launches directly ok This is also the damage caused by a power outage database files not being shut down in time. Remember to check the hardware for non-illegal shutdown sudden power outage.
MongoDB Database Recovery MONGO database failed to start recovering MongoDB database power loss Data recovery
