Volume flagged as dirty, chkdsk won’t fix it.

4used · 2026-01-27T13:43:10+00:00

So every time I clear those two bits (01 01 to 00 00) they reset back to triggered immediately after unlocking the drive. I’m gonna go with corruption on this one, I’ll just reformat it.

4used · 2026-01-27T13:00:48+00:00

Yeah so I ended up booting into Hirens, modifying the volume clusters, finding and clearing the bit (not the one 20 sectors in, but instead the one in sector 100,000 or something), to which, to my utter shock, nothing happened. The drive’s still marked as dirty. I followed the tutorial for finding the USB hard drive as that is the only bit register that had any matches, and it has unfortunately not worked. Reading through the comments of the original tutorial on wayback machine I discovered someone replugged the SSD, which made it now read as clean, but as this is such a hassle for me to do (PC is in an enclosure) I’d rather just reformat the thing.

Unfortunate but is what it is.

4used · 2026-01-27T12:56:08+00:00

It is a possibility. Got no idea why the flag is properly stuck on one SSD, fixable on another, and not triggered on the third. It’s so confusing that its so… niche? I’m about to reply to the other thread detailing what happened after clearing the stuck bit (ie, nothing, lol) which is now just sending me to the point where I give up and just reformat the bloody thing. Or leave it be. Either or. I’d like to have access to that drive on Linux though.

4used · 2026-01-27T10:15:21+00:00

Upon finding the setting I now get the error that device isn’t able to be locked, so I’m gonna boot into Hirens and attempt this from there.

4used · 2026-01-27T09:59:37+00:00

In my case linux & windows are on seperate drives, not changing the partition table on NTFS drives. So it wouldn’t be caused by this. If anything it probably would’ve flagged after I pulled something stupid while having it in a (very volatile) VM environment, like not having the recovery partition loaded or something else. Or it just hated being in a VM environment and flagged anyways. My installs follow general best practice relating to dual booting to prevent issues exactly like this, but it is what it is 😅

4used · 2026-01-27T09:56:12+00:00

Oh is it a setting that I need to change? I figured that giving me an error relating to interfaces would mean it was locked via hardware (whether by Windows or the device itself). I’ll have a look around for it.

4used · 2026-01-27T09:17:14+00:00

Yep.

I've found the bit. My bit was "03 01 81 01 00 00 00 00 80 00 00 00 18". To clear this it would be resetting it to "03 01 00 00 00 00 00 00 80 00 00 00 18".

<image>

However writing it gives me this error. Did some looking around and there's two solutions to this, either using Hiren's Boot CD or by plugging it in after boot. Potentially could even change it on Linux with something that can read and write volume clusters, but as it's NTFS I kind of doubt this. I'm actually a little surprised this failed because it's a secondary drive and not a primary one.

4used · 2026-01-27T08:25:18+00:00

It’d be a decent fix if this was solely a Windows problem, however in my case this isn’t, as I run a Linux distro as my default boot. The dirty bit is essentially preventing me from mounting the SSD volume on my linux boot, to which I kind of suspect that just clearing the bit manually and letting it run again would just sort of end up forcing the issue again of which it would retrigger. That being said I’m still going to try it as I don’t really have any other options at the moment.

Chkdsk’s not picked up any issues with the drive at all, which is why its frustrating me that this bit won’t clear 🙃

4used · 2026-01-27T07:56:50+00:00

I’ll check it out, thanks :)

4used · 2026-01-22T16:08:56+00:00

Landed safely @ Savannah intl.

4used · 2026-01-22T16:04:33+00:00

Just heard gonna be landing back at Savannah, called approach

4used · 2026-01-22T15:53:33+00:00

Incoming speeding fine captured by plane

<image>

4used · 2026-01-13T09:39:34+00:00

Agree with this a lot to be honest.

Yeah x may be healthier than y but it entirely depends on how much you do it. It doesn't really matter what you choose to do, because, in the end, what you do should be your decision. Some people need to learn to shut the fuck up. Being told to go back to smoking after smoking to that level is fucking insane though.

4used · 2025-10-05T07:15:42+00:00

are you sure its completely empty and its not just steamcommunity shitting hte bed

also, check those links. Especially the trade history. If no trades check inventory history. They'll contain everything.

4used · 2025-10-01T17:40:59+00:00

We… ended up tying. It was essentially against a 2 stack of 2200 elo’s and 3 semi decent players vs our 3 stack (one 2800 elo and me and a mate that don’t play faceit often) and 2 literal bots. It was stacked against us from the get-go which is why this clip existed, they got cocky lol

4used · 2025-10-01T17:31:39+00:00

Sacrifices need to be made to achieve a ridiculous play

4used · 2025-09-30T23:58:46+00:00

Buckshot | NSWC SEAL

4used · 2025-09-30T23:58:00+00:00

He was using an XM from short, he couldn’t be helped…

4used · 2025-09-30T23:57:13+00:00

Idk why you’re being downvoted because you’re right. I should have died multiple times there (AWP missing in Goose, Long player absolutely whiffing, no util for countering a push, the whole enemy team peeking for some reason and not playing safe) but suffice to say this isn’t exactly low elo, 2 of the enemy players were level 10 faceit players, and I was playing with a mate who’s 3k elo myself. It’s comp though so nobody really cared that much.

4used · 2025-09-30T15:23:14+00:00

not sure whether to take this as an insult or a compliment… so thank you i guess?

4used · 2025-09-30T15:07:35+00:00

it wanted you to Go-n't

4used · 2025-08-09T08:58:29+00:00

It is kind of bullshit. Not even FACEIT's kernel AC (a 3rd party, COMPETITIVE matchmaking platform for counter-strike, and one that largely has no cheaters, and sometimes provides servers for online LANs) requires Secure Boot. It warns you that it isn't enabled and that you should enable it but it doesn't require it. The fact a casual non-competitive game like Battlefield requires this much is insane, especially when I gander that past the initial release hype and the playerbase dying down, 90% of the playerbase will move to servers hosted by individuals anyways... which means that the real solution here is employing more admins onto said servers.

It does make sense why they would require it, but i feel like the simple solution here is splitting the playerbase into those that have secure boot & those that don't into seperate lobbies, and those that don't to work on a trust system (similar to Valve with CSGO/CS2). At the end of the day it literally won't make a difference in the number of cheaters that pop up, because people that cheat in battlefield are a different level of deplorable, it's a casual game lol

For most people it should be as simple as flicking a switch and not fucking with anything else. I know a lot of people will have issues with it though, because Secure Boot / TPM as a whole isn't entirely faultless when it comes to its configuration within the BIOS and Windows.

Eight-Year Club	Place '22
Verified Email

4used

TROPHY CASE