That's why I primarily use Linux...
That's why I primarily use Linux...
21 comments
-
This is a hardware issue, no OS can fix this.
-
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 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?
-
-
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.
21 comments