"unfsckable" meaning in English

{
  "forms": [
    {
      "form": "more unfsckable",
      "tags": [
        "comparative"
      ]
    },
    {
      "form": "most unfsckable",
      "tags": [
        "superlative"
      ]
    }
  ],
  "head_templates": [
    {
      "args": {},
      "expansion": "unfsckable (comparative more unfsckable, superlative most unfsckable)",
      "name": "en-adj"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "adj",
  "senses": [
    {
      "categories": [
        {
          "kind": "other",
          "name": "English entries with incorrect language header",
          "parents": [
            "Entries with incorrect language header",
            "Entry maintenance"
          ],
          "source": "w"
        },
        {
          "kind": "topical",
          "langcode": "en",
          "name": "Computing",
          "orig": "en:Computing",
          "parents": [
            "Technology",
            "All topics",
            "Fundamental"
          ],
          "source": "w"
        }
      ],
      "examples": [
        {
          "ref": "1994 January 17, Deborah Howland, “3.2 crashes”, in comp.sys.next.bugs (Usenet)",
          "text": "I was peacefully running a fairly stock black slab with 3.0 (no kernel servers, in particular) when my external 1.2GB drive flamed out sort of like Mark described, only more so: scores of media errors and bad sectors, crashes, kernel panics, etc. This built up gradually over about 5 days until my system was totally unbootable, unfsckable, and unusable.",
          "type": "quotation"
        },
        {
          "ref": "2003 October 8, Pigeon, “How to kill X?”, in linux.debian.user (Usenet)",
          "text": "I'm a fan of SCSI hard drives, and I like to set up ext3 with an external journal, ie. on a different physical drive, which speeds things up a bit, though at the cost of making your data twice as vulnerable to hard drive failures (if the journal drive dies you're likely to end up with an unfsckable mess on the data drive).",
          "type": "quotation"
        },
        {
          "ref": "2006 April 26, BrianM, “Knoppix is Kneat”, in nz.comp (Usenet)",
          "text": "Linux file system hopelessly corrupted and unfsckable. Despaired of losing all the data accumulated since the last CD backup, but then remembered an old Knoppix CD in the drawer. It detected all the partitions on the hdd, plus my USB stick, enabling a retrieve of my precious data.",
          "type": "quotation"
        }
      ],
      "glosses": [
        "Unable to be repaired with fsck; highly corrupt."
      ],
      "id": "en-unfsckable-en-adj-OwZPKC3-",
      "links": [
        [
          "computing",
          "computing#Noun"
        ],
        [
          "fsck",
          "fsck"
        ],
        [
          "corrupt",
          "corrupt"
        ]
      ],
      "raw_glosses": [
        "(computing, of a filesystem) Unable to be repaired with fsck; highly corrupt."
      ],
      "raw_tags": [
        "of a filesystem"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "sciences"
      ]
    }
  ],
  "word": "unfsckable"
}

{
  "forms": [
    {
      "form": "more unfsckable",
      "tags": [
        "comparative"
      ]
    },
    {
      "form": "most unfsckable",
      "tags": [
        "superlative"
      ]
    }
  ],
  "head_templates": [
    {
      "args": {},
      "expansion": "unfsckable (comparative more unfsckable, superlative most unfsckable)",
      "name": "en-adj"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "adj",
  "senses": [
    {
      "categories": [
        "English adjectives",
        "English entries with incorrect language header",
        "English lemmas",
        "English terms with quotations",
        "en:Computing"
      ],
      "examples": [
        {
          "ref": "1994 January 17, Deborah Howland, “3.2 crashes”, in comp.sys.next.bugs (Usenet)",
          "text": "I was peacefully running a fairly stock black slab with 3.0 (no kernel servers, in particular) when my external 1.2GB drive flamed out sort of like Mark described, only more so: scores of media errors and bad sectors, crashes, kernel panics, etc. This built up gradually over about 5 days until my system was totally unbootable, unfsckable, and unusable.",
          "type": "quotation"
        },
        {
          "ref": "2003 October 8, Pigeon, “How to kill X?”, in linux.debian.user (Usenet)",
          "text": "I'm a fan of SCSI hard drives, and I like to set up ext3 with an external journal, ie. on a different physical drive, which speeds things up a bit, though at the cost of making your data twice as vulnerable to hard drive failures (if the journal drive dies you're likely to end up with an unfsckable mess on the data drive).",
          "type": "quotation"
        },
        {
          "ref": "2006 April 26, BrianM, “Knoppix is Kneat”, in nz.comp (Usenet)",
          "text": "Linux file system hopelessly corrupted and unfsckable. Despaired of losing all the data accumulated since the last CD backup, but then remembered an old Knoppix CD in the drawer. It detected all the partitions on the hdd, plus my USB stick, enabling a retrieve of my precious data.",
          "type": "quotation"
        }
      ],
      "glosses": [
        "Unable to be repaired with fsck; highly corrupt."
      ],
      "links": [
        [
          "computing",
          "computing#Noun"
        ],
        [
          "fsck",
          "fsck"
        ],
        [
          "corrupt",
          "corrupt"
        ]
      ],
      "raw_glosses": [
        "(computing, of a filesystem) Unable to be repaired with fsck; highly corrupt."
      ],
      "raw_tags": [
        "of a filesystem"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "sciences"
      ]
    }
  ],
  "word": "unfsckable"
}