[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: File WiredTiger.turtle     File WiredTiger.wt     File repair-SERVER-33011.tar.gz    
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

2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] MongoDB starting : pid=19451 port=27017 dbpath=/data/db 64-bit host=production
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] db version v3.2.7
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] git version: 4249c1d2b5999ebbf1fdf3bc0e0e3b3ff5c0aaf2
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] allocator: tcmalloc
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] modules: none
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] build environment:
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten]     distmod: ubuntu1404
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten]     distarch: x86_64
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten]     target_arch: x86_64
2018-01-30T18:45:25.744+0100 I CONTROL  [initandlisten] options: {}
2018-01-30T18:45:25.769+0100 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-01-30T18:45:25.769+0100 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-01-30T18:45:25.776+0100 E STORAGE  [initandlisten] WiredTiger (-31802) [1517334325:776898][19451:0x7f902b158cc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2018-01-30T18:45:25.776+0100 E STORAGE  [initandlisten] WiredTiger (0) [1517334325:776951][19451:0x7f902b158cc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2018-01-30T18:45:25.776+0100 E STORAGE  [initandlisten] WiredTiger (0) [1517334325:776964][19451:0x7f902b158cc0], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2018-01-30T18:45:25.776+0100 E STORAGE  [initandlisten] WiredTiger (0) [1517334325:776979][19451:0x7f902b158cc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2018-01-30T18:45:25.777+0100 I -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2018-01-30T18:45:25.777+0100 I STORAGE  [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2018-01-30T18:45:25.777+0100 I CONTROL  [initandlisten] dbexit:  rc: 100

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,
Mark

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,
Mark

Generated at Thu Feb 08 04:32:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.