[SERVER-33011] unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error Created: 30/Jan/18 Updated: 27/Jul/18 Resolved: 30/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Fabio Vedovelli | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | envns, rns, rpu, trcf, wtc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Hello Support Team! I need your help. I am trying to start Mongod on Ubuntu 14.04 but it looks like Wired Tiger is having troubles reading the data. Start right after moving db's data directory to another partition. The full output is
I am sending the two files usually attached to similar tickets I've found online. Thanks a lot for your help, Fabio Vedovelli |
| Comments |
| Comment by Fabio Vedovelli [ 31/Jan/18 ] |
|
Hello Mark! I understand that. That's very unfortunate. Do you recommend any professional service that might help us recover the data? I'm just wondering if that is even possible. You know: this data is valuable to our company. I thanks you very much for your help and quick replies, Best regards, Fabio Vedovelli |
| Comment by Mark Agarunov [ 30/Jan/18 ] |
|
Hello vedovelli, Unfortunately, this error indicates that there was corruption on the disk, most often cause by a faulty storage layer. In this situation, our best recommendation would be to resync the affected node or restore from a backup if possible. To prevent this type of problem in the future please take note of the following guidelines to help mitigate any issues related to unreliable storage layers or server failures.
Thanks, |
| Comment by Fabio Vedovelli [ 30/Jan/18 ] |
|
@mark.agarunov Thanks for the quick reply! I tried but still no success. This time a different message. Please see this link https://pastebin.com/pzUZWpLu Your help is much appreciated! Fabio Vedovelli |
| Comment by Mark Agarunov [ 30/Jan/18 ] |
|
Hello vedovelli, Thank you for your report. I've attached a repair attempt of the files you provided. Please extract these files and replace them in your $dbpath and let us know if it resolves the issue. If you are still seeing errors after replacing these files, please provide the complete logs from the affected node(s) so that we can further investigate. Thanks, |