[SERVER-42758] My database could not be started after the server was unexpectedly powered off Created: 12/Aug/19  Updated: 20/Aug/21  Resolved: 20/Aug/21

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

Type: Bug Priority: Major - P3
Reporter: godstory wang Assignee: Kelsey Schubert
Resolution: Incomplete Votes: 0
Labels: wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 6.5


Attachments: File WiredTiger.turtle     File WiredTiger.wt     File repair_attempt.tar.gz    
Participants:

 Description   

My database could not be started after the server was unexpectedly powered off. I use repair option to start but not success.

 

2019-08-12T12:42:48.450+0800 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=5564M,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),,log=(enabled=false),
2019-08-12T12:42:48.466+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1565584968:466157][4145:0x7f0c5a035dc0], file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 311296: block header checksum of 2017101102 doesn't match expected checksum of 3148123505
2019-08-12T12:42:48.466+0800 E STORAGE  [initandlisten] WiredTiger error (0) [1565584968:466237][4145:0x7f0c5a035dc0], file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value
2019-08-12T12:42:48.466+0800 E STORAGE  [initandlisten] WiredTiger error (-31804) [1565584968:466257][4145:0x7f0c5a035dc0], file:WiredTiger.wt, connection: the process must exit and restart: WT_PANIC: WiredTiger library panic
2019-08-12T12:42:48.466+0800 I -        [initandlisten] Fatal Assertion 28558 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 365
2019-08-12T12:42:48.466+0800 I -        [initandlisten]***aborting after fassert() failure



 Comments   
Comment by Kelsey Schubert [ 15/Aug/19 ]

haha_x2002@126.com, this error message leads us to suspect some form of physical corruption. Our ability to determine the source of this corruption depends greatly on your ability to provide:

  1. The logs for the affected node, including before, leading up to, and after the first sign of corruption.
  2. A description of the underlying storage mechanism in use, including details like:
    1. What file system and/or volume management system is in use?
    2. Is data storage locally attached or network-attached?
    3. Are disks RAIDed and if so how?
    4. Are disks SSDs or HDDs?
  3. A description of your backup method, if any.
  4. A description of your disks have been recently checked for integrity?
  5. A history of the deployment, including:
    1. a timeline of version changes
    2. a timeline of hardware upgrade/downgrade cycles or configuration changes
    3. a timeline of disaster recovery or backup restoration activities
    4. a timeline of any manipulations of the underlying database files, including copies or moves, and information about whether mongod was running during each manipulation.

I've attached a repair attempt of the files you provided as repair_attempt.tar.gz . Please extract these files, replace them in your $dbpath, and let us know if it resolves the issue.

Kind regards,
Kelsey

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