• Honytawk
        link
        fedilink
        English
        arrow-up
        10
        ·
        24 days ago

        An SSD can have good and bad sectors at the same time, dude

      • Boomkop3@reddthat.com
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        16 days ago

        If that’s an hdd, replace it. If that’s an ssd, stop pulling the darn plug and/or holding the power button.

          • Boomkop3@reddthat.com
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            14 days ago

            Either that or you have to make a warranty claim. Although if you’re experiencing instability, or are overclocking you could experience these issues too. Just don’t risk shutting it down busy.

            But you knew that already, right?

  • kboy101222@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    25 days ago

    That’s what happens when a hard drive fails at some point in the boot. It isn’t a windows issue

  • superweeniehutjrs@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    26 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@sh.itjust.works
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      25 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

          • superweeniehutjrs@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            24 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.

  • Anthony [She/Her/They/Them]@lemmy.cif.suOP
    link
    fedilink
    arrow-up
    1
    ·
    14 days ago

    OK, just to clarify a few things, because a lot of people are being smartasses here in the comments:

    1. It’s a relatively new (1-2 Months old) Samsung NVME drive.
    2. I do NOT hold to power button or pull the plug on this machine EVER.
    3. The drive is in prestine conditions. Not a single bad sector. Use the same drive DAILY on Linux and disk utility reports no bad sectors.

    So stop talking nonsense if you don’t know what’s going on.