Major - P3 Hi,
Today I faced the problem that many already reported. The server crashed and the database is corrupted. I can't bring it up to normal.
I've tried to start mongod with --repair ... nothing...
How can I recover from this? I can see from many posts that you guys generate the repaired files and then we can start mongod. But really, how can we recover from this problem wtihout opening a ticket or depending on someone to fix the checksum at the WiredTiger file?
I am attaching the files for analysis... BTW, I utilise --directoryperdb at my mongod instance.
– LOGS
2018-04-29T18:37:03.912-0300 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=493M,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), 2018-04-29T18:37:04.330-0300 E STORAGE [initandlisten] WiredTiger error (0) [1525037824:330136][1126:0x7f34f3033cc0], file:WiredTiger.wt, WT_CURSOR.next: read checksum error for 16384B block at offset 643072: block header checksum of 4091829093 doesn't match expected checksum of 2132028001 2018-04-29T18:37:04.330-0300 E STORAGE [initandlisten] WiredTiger error (0) [1525037824:330189][1126:0x7f34f3033cc0], file:WiredTiger.wt, WT_CURSOR.next: WiredTiger.wt: encountered an illegal file format or internal value 2018-04-29T18:37:04.330-0300 E STORAGE [initandlisten] WiredTiger error (-31804) [1525037824:330199][1126:0x7f34f3033cc0], file:WiredTiger.wt, WT_CURSOR.next: the process must exit and restart: WT_PANIC: WiredTiger library panic 2018-04-29T18:37:04.330-0300 I - [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 361