[SERVER-60821] How to recover from read checksum error Created: 19/Oct/21  Updated: 22/Nov/21  Resolved: 22/Nov/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Dario De Simon Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File WiredTiger     File WiredTiger.turtle     File WiredTiger.wt     File WiredTigerLAS.wt     File _mdb_catalog.wt     File sizeStorer.wt     File storage.bson    
Operating System: ALL
Steps To Reproduce:

The server is installed on hyper-v VM, at the nigth the storage shut down e disconnect the disk, when I reconnect the disk and start the mongo service give me this error

Participants:

 Description   

How I can recover my db from this error:

2021-10-19T19:28:00.268+0200 I STORAGE [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2021-10-19T19:28:00.268+0200 I STORAGE [initandlisten] ** See http://dochub.mongodb.org/core/prodnotes-filesystem
2021-10-19T19:28:00.268+0200 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=7412M,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),
2021-10-19T19:28:04.875+0200 E STORAGE [initandlisten] WiredTiger error (0) [1634664484:875538][11247:0x7f03a47abe80], file:WiredTiger.wt, WT_CURSOR.next: read checksum error for 28672B block at offset 1908736: block header checksum of 1885693284 doesn't match expected checksum of 2855298891
2021-10-19T19:28:04.875+0200 E STORAGE [initandlisten] WiredTiger error (0) [1634664484:875611][11247:0x7f03a47abe80], file:WiredTiger.wt, WT_CURSOR.next: WiredTiger.wt: encountered an illegal file format or internal value
2021-10-19T19:28:04.875+0200 E STORAGE [initandlisten] WiredTiger error (-31804) [1634664484:875620][11247:0x7f03a47abe80], file:WiredTiger.wt, WT_CURSOR.next: the process must exit and restart: WT_PANIC: WiredTiger library panic
2021-10-19T19:28:04.875+0200 I - [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 365
2021-10-19T19:28:04.875+0200 I - [initandlisten]

***aborting after fassert() failure

2021-10-19T19:28:04.900+0200 F - [initandlisten] Got signal: 6 (Aborted).

 



 Comments   
Comment by Edwin Zhou [ 22/Nov/21 ]

Hi dario.desimone@gmail.com,

Thank you for following up. We're happy to hear that you've been able to solve this issue with --repair.

Best,
Edwin

Comment by Dario De Simon [ 21/Nov/21 ]

Hello Edwin,

yes, I've tryed with --repair.

The problem was an error on the storage where are installed the Virtual Machine.

Repaired it, I've rescued all data from disk.

Thanks for interesting.

Best Regards

Comment by Edwin Zhou [ 18/Nov/21 ]

Hi dario.desimone@gmail.com,

We still need additional information to diagnose the problem. If this is still an issue for you, would you please note what version of MongoDB you're using? Are you encountering this issue on a replica set or on a standalone? Have you found success with using mongod --repair using the latest version of MongoDB?

Best,
Edwin

Comment by Edwin Zhou [ 03/Nov/21 ]

Hi dario.desimone@gmail.com,

This error message leads us to suspect some form of corruption. Can you please note what version of MongoDB you're using? Are you encountering this issue on a replica set or on a standalone?

Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath.

The ideal resolution is to perform a clean resync from an unaffected node.

You can also try mongod --repair using the latest version of MongoDB.

In the event that a --repair operation is unsuccessful, then please also provide:

  • The logs leading up to the first occurrence of any issue
  • The logs of the repair operation.
  • The logs of any attempt to start mongod after the repair operation completed.

Best,
Edwin

Generated at Thu Feb 08 05:50:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.