Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-34392

file:WiredTiger.wt, connection: WiredTiger.wt: encountered an illegal file format or internal value

    • Linux


      We had a major power outage and it knocked down our mongo db running in docker as part of a stack. Now it won't come back up. Mongo had it's own volume mounted to /data/db.

      At first I took the stack down created and ran a temporary container mounted to the same volume to see if I could repair the data. I ran the "mongod --repair --dbpath /data/db" and nothing, It was still saying "file:WiredTiger.wt, connection: read checksum error for 4096B block at offset 12288: block header checksum of 1843462872 doesn't match expected checksum of 1205067277".

      I also ran this command "mongod --repair --dbpath /data/db --storageEngine wiredTiger"...same thing.

      I then went as far as to restore the data from a backup that we had done the day prior of the volume used to store the mongo data. When I deployed the stack again (fresh containers, etc.) and I check the logs that the server is outputting...still the same issue.

      Please advise/help as I thought that restoring from the backup if anything would of fixed it but still nothing. I'm attaching the stdout of the repair command as well as the regular log of the server while running (or trying to anyways). I just don't understand why the backup restore isn't working as the backup was done before the outage therefor it shouldn't be corrupted.

      Please help me recover the db as it's very important. Much appreciation and thanks.
      Frank Perez

        1. logfile_while_running.txt
          10 kB
        2. output_of_repair_command.txt
          8 kB
        3. repair_attempt.tar.gz
          44 kB
        4. WiredTiger.turtle
          1.0 kB
        5. WiredTiger.wt
          796 kB

            kelsey.schubert@mongodb.com Kelsey Schubert
            frankp Frank Perez
            0 Vote for this issue
            4 Start watching this issue