What Does 'Problem With This Drive' Error ACTUALLY Mean?

▼ Time Stamps: ▼
0:00 - Intro
0:33 - How Does It Know There's a "Problem"?
1:49 - An Excellent Thing to See
3:27 - How Does The "Dirty Bit" Get Enabled?
4:44 - Manually Enabling The Dirty bit
5:18 - Seeing The Change For Ourselves
6:00 - The Actual bit
6:26 - Changing The Raw Hex Data
6:50 - Manually Disabling The Dirty Bit
7:16 - How To Avoid the Error
7:52 - If You See the Warning Often
8:27 - What About the Desktop?

▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

[pcpanikMusik]

After 24 years of ignoring this error, finally someone explains it 😂

[gz-kbct]

The worst part about ejecting is when it says the drive is in use but you know for a fact that the drive is NOT in use. At that point everyone just pulls the drive out. This is the most common reason why a usb drive has the dirty bit set.

[RockinRobbins]

I have received over a hundred such error messages over 20 years and have done the scan. Never once has the scan found a problem. It's like the offer to run a Windows analysis of a problem. The analysis NEVER finds the cause or fixes the problem.

[pigable]

I always mock how it says errors were found, scans it then proceeds to tell me that no errors could be found on my USB.

[linuxphile]

That error is also shown when you plug in a drive with a filesystem that Windows doesn't natively recognize, like ext4.

[manstid]

it always make me panic that my data might get corrupt lol

[crjakob]

I always get that when plugging in my external drive

[acetum_]

Bro this happens all the time when using a drive on Windows after using the same drive on Linux. Run the CHDSK and low and behold no errors whatsoever found.

[Wampa]

When I switched to Linux, I kept getting corrupted files on my USB sticks. It took me over a year to realize that copying isn't done when the "cp" command returns or the progress window disappears. The difference between the filesystem and the storage medium, and the importance of syncing, are probably the most obscure things I've encountered.

[nothanks]

thank you for the explanation! its seems like such a simple thing, im baffled why it can't just tell you what happened instead of being as vague and unhelpful as possible.

it's really frustrating how far into the weeds the average Windows user has to go to now just to figure out random little issues like this. i feel like it wasnt always this bad, but maybe im just dumb lol

[Acceleronics]

This comment goes back at least 10 years, and probably more like 15 or 20. I told Windows to proceed with the scan and fix process. When it was done, the USB drive had no files listed in Explorer. There had been lots of files on that drive. From that point on, I never allowed Windows to scan AND fix with a single click. Once bitten, twice shy!

[Monkeymario.]

1:41 Generative AI is getting scary good at text, tho it still struggles it says "YOU FORGOTEN TO EJECT THE DR0VE"

[dr.acula]

This happened a lot to me back when I used to sync my classic iPods with iTunes. Most times I was in a hurry and never bothered to eject the iPod first because I had to run to catch the bus... guess it makes sense now.
Excellent video for us "advanced beginners" casual users :D

[TigerP]

Your Hexpat structure immediately took me back 40 years when I would fix Unix file systems using adb on the raw device.

[rorywalters]

It’s kinda interesting macOS deals with this the other way around. When you unplug a drive without properly ejecting it, instead of telling you to repair the drive next time you plug it in, macOS would tell you immediately: ‘You idiot! Eject before you unplug it!’.

[raphaeloberhummer]

'Don't mess arround when you don't know what you're doing.'
It's a sentense I ignore of the purpose to learn.

[_SJ]

Thanks for explaining this ❤ I also ignore this message always.

[soundspark]

FAT based drives aren't very reliable so the dirty bit tells the OS it should run a scan the next time the drive is mounted.
NTFS rarely goes "dirty" because the journal can be rolled back to put the drive back into a known good configuration.

[Twinsen]

Finally a video that's useful. Do more of these instead of like the last 5 which were useless.

[Suffering]

Interesting to finally hear the explanation on this. I've had this error on multiple drives, even though I always eject them because I'm worried it might do harm if I don't. Even purchased a new drive some years back and it had the error from the first time I plugged it into my PC, lol. From that moment on I knew not to take it too seriously. So I just ignore it now, still ejecting every time, and using my USB drives without problems.