• superweeniehutjrs@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    2
    ·
    13 days ago

    The “fix” once moved my entire windows folder into some kind of lost and found bin. It was years ago so I don’t remember the details. I had to move the files back by recovery command prompt. At least IT gave me the bitlocker key. That whole process sucked

    • the_crotch
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      12 days ago

      It didn’t move anything. The filesystem got corrupted and that directory was erroneously marked as unused space, which is probably why you were running chkdsk in the first place. Lost and found is the correct place to put files recovered this way because chkdsk doesn’t know where they’re supposed to go. Fsck does the same thing and in fact lost+found is a default directory on most (all?) unices

        • the_crotch
          link
          fedilink
          arrow-up
          3
          ·
          12 days ago

          So it tried to warn you that the filesystem was fucky and you ignored it

          • superweeniehutjrs@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            11 days ago

            It failed to fix itself. Yes, I “ignored” it for a few days as I had no time to sit for it to check the drive - when I was ignoring the prompt it was still working. It would have broken itself earlier, and I would have been even more screwed. And no policies for backup were allowed by IT, other than a couple files on OneDrive.