[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: |
|
| 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 ***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 ] |
|
Thank you for following up. We're happy to hear that you've been able to solve this issue with --repair. Best, |
| 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 ] |
|
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, |
| Comment by Edwin Zhou [ 03/Nov/21 ] |
|
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:
Best, |