This is a hardware issue, no OS can fix this.
this post was submitted on 08 Nov 2024
52 points (77.1% liked)
Software Gore
5371 readers
4 users here now
Welcome to /c/SoftwareGore!
This is a community where you can poke fun at nasty software. This community is your go-to destination to look at the most cringe-worthy and facepalm-inducing moments of software gone wrong. Whether it's a user interface that defies all logic, a crash that leaves you in disbelief, silly bugs or glitches that make you go crazy, or an error message that feels like it was written by an unpaid intern, this is the place to see them all!
Remember to read the rules before you make a post or comment!
Community Rules - Click to expand
These rules are subject to change at any time with or without prior notice. (last updated: 7th December 2023 - Introduction of Rule 11 with one sub-rule prohibiting posting of AI content)
- This community is a part of the Lemmy.world instance. You must follow its Code of Conduct (https://mastodon.world/about).
- Please keep all discussions in English. This makes communication and moderation much easier.
- Only post content that's appropriate to this community. Inappropriate posts will be removed.
- NSFW content of any kind is not allowed in this community.
- Do not create duplicate posts or comments. Such duplicated content will be removed. This also includes spamming.
- Do not repost media that has already been posted in the last 30 days. Such reposts will be deleted. Non-original content and reposts from external websites are allowed.
- Absolutely no discussion regarding politics are allowed. There are plenty of other places to voice your opinions, but fights regarding your political opinion is the last thing needed in this community.
- Keep all discussions civil and lighthearted.
- Do not promote harmful activities.
- Don't be a bigot.
- Hate speech, harassment or discrimination based on one's race, ethnicity, gender, sexuality, religion, beliefs or any other identity is strictly disallowed. Everyone is welcome and encouraged to discuss in this community.
- The moderators retain the right to remove any post or comment and ban users/bots that do not necessarily violate these rules if deemed necessary.
- At last, use common sense. If you think you shouldn't say something to a person in real life, then don't say it here.
- Community specific rules:
- Posts that contain any AI-related content as the main focus (for example: AI “hallucinations”, repeated words or phrases, different than expected responses, etc.) will be removed. (polled)
You should also check out these awesome communities!
- Tech Support: For all your tech support needs! (partnered)
- Hardware Gore: Same as Software Gore, but for broken hardware.
- DiWHY - Questioning why some things exist...
- Perfect Fit: For things that perfectly and satisfyingly fit into each other!
founded 2 years ago
MODERATORS
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?
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.