OK, just to clarify a few things, because a lot of people are being smartasses here in the comments:
- It’s a relatively new (1-2 Months old) Samsung NVME drive.
- I do NOT hold to power button or pull the plug on this machine EVER.
- 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.
This is a hardware issue, no OS can fix this.
I’m literally daily driving the same drive with Ubuntu 24.04. No problems there. This is an OS Problem.
If that’s an hdd, replace it. If that’s an ssd, stop pulling the darn plug and/or holding the power button.
It’s a SSD, but I do not Pull the plug or hold the power button EVER on this machine. Stop thinking you know everything if you have no idea.
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?
An SSD can have good and bad sectors at the same time, dude
That’s what happens when a hard drive fails at some point in the boot. It isn’t a windows issue
It’s an SSD but OK…
Same difference in this case. If the drive is detected to have failed in some way, this is what windows runs at boot
ETA: we’ll get there when we get there
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
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
Windows was able to boot for a week, prompting me every time, until I didn’t manage to skip it one day. Then it bricked itself
So it tried to warn you that the filesystem was fucky and you ignored it
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.
Windows 11 on an IDE drive. You love to see it.
It’s actually on a SSD but ok… A NVME to be exact
Twas but a joke sir
It will take as long as it takes.
You noticed the 1578%, right?
