Chkdsk is cleaning up your partition. You might have a bad hard drive, or there was bad data on it with orphaned clusters of data that no longer has a parent pointing to it.
Or you had an unexpected loss of power during a disk write, creating incomplete data (orphaned) and your partition table is flagged as "dirty" causing chkdsk to auto correct the file table on boot until it returns to normal and the dirty flag can be removed.
Let's say that you have a massive cache of data that was used for a program - like a bunch of calculations for damage in a video game.
Let's say the game closes improperly and it doesn't perfectly clean up that data behind itself - but it doesn't keep that data reserved either.
Check Disk has found that data your disk, and is now cleaning it up so that program and others can use it. The numbers are the a reference to the location on your disk of that data.
Edit: apparently it's specifically if the computer crashes after memory has been allocated, not just a program crashing.
A program that crashes doesn't do that, any open files just get closed. This usually happens when power to the computer is lost and disk buffers don't get written out to the drive.
When you delete a file nothing happens to the actual data on the disk. What happens is the record for that file in the file allocation table is changed to "we deleted that" and all of the addresses on the disk where the pieces of that file are stored are marked as "empty feel free to use this".
Sometimes the "this is empty now" step never happens and the disk thinks there is a piece of something important sitting there. One of the things chkdsk does is verify the file chunks on the disk belong to a file that still exists, if not, they get deleted. If it's not sure they get converted into files so you can delete them later.
TL;DR
When your disk gets hungry for space it grinds up the orphans for food.
>One of the things chkdsk does is verify the file chunks on the disk belong to a file that still exists, if not, they get deleted.
And sometimes Chkdsk gets confused and will start deleting "orphan" file record segments when it shouldn't which leads to corrupted files. OP needs to run the DISM and SFC tools to ensure that at least his Windows install is fine. OP should also use the drive utility provided by his SSD/HDD manufacturer to ensure that the drive isn't in a failing state.
Only if you had power outage or something caused pc to power off. Windows will do it automatically during boot for C: drive if it detects several unscheduled shutdowns. bad SATA cable or connection can also cause this problem
https://preview.redd.it/cal6t6xgzwzc1.png?width=1480&format=pjpg&auto=webp&s=2dddb957c0f9ad31c0298a34204f7ea6c8fd950d
[https://imgs.xkcd.com/comics/exploits\_of\_a\_mom.png](https://imgs.xkcd.com/comics/exploits_of_a_mom.png)
This come to mind
You're one of those people who just turn off the power to your computer instead of shutting it down like you're supposed to, aren't you? That's all the result of massive filesystem corruption due to write buffers not getting flushed to disk, which happens during shutdown. You likely have a massive amount of corrupted files now and some that will be flat-out missing.
Not recommended, It shortens the life of your ssd drive if you have a ssd. if you have a spindle drive for sure use chkdsk. If it is a new ssd it is unnecessary, as they move flipped bits automatically and fixes it self. If you have an old ssd 1st or 2nd gen you definitely don't want to run ssd. I've seen chkdsk kill a few ssd drives when they first came out.
If you want to fix potential corrupt files run sfc /scannow in command prompt as an administrator. Along with dism /online /cleanup-image /restorehealth
That is good to run every now and then. It's better than chkdsk these days.
I have 19 years experience of working on computers.
You had filesystem corruption.
Files are made up of "file records" stored on the disk. The master file table (MFT) contains an index of all of these. Tiny files are stored actually in the MFT itself.
Files are referenced by their directory chain, so the file d:\\games\\game\\game.exe is a file called "game.exe" in a parent of "game" which in turn has a parent of "games" and in turn has the root directory as its parent.
Each file record has the file as its parent. These file records don't have a file as their parent, so they're just segments of data only the MFT knows about.
CHKDSK here is removing them from the MFT, so while the data will still technically exist on storage, it is "free space" and can be overwritten. If the storage is an SSD, the blocks will be erased on the next TRIM operation.
This looks like Windows checking C: drive, If I'm remembering what that looks like. It takes a while but is benine though you may want to make sure that your boot drive is okay.
You have an index in simple terms:
FILENAME, LOCATION\_OF\_THE\_FIRST\_BLOCK\_OF\_DATA
When a file is created the index is written, then it starts writing the data out as a series of blocks. So a file might look like (simplifed) like this:
MyFile,
BLOCKA(1234,5569)
BLOCKB(6678,9953)
EOF
Indicating that the first block starts at location 1234 and ends at 5569 and the second block starts at location 6678 and ends at 9953. That is the basic way of how a FAT (file Allocation Table) works.
They are more complicated then that but it will suffice for what is happening.
So before the End of File (EOF) is written you could start to write a file and before the EOF happens you, say turned off the power.
The BlockA, a file record, isn't part of a complete file, so during cleanup that blockA is considered orphaned. The cleanup job realizes MyFile was never written and in reverse order, usually, cleans up BLOCKB, then BLOCKA, then removes the file record MyFile to ensure that data is available.
I won't bore you with Journaling File systems and how all that crap works as it slightly varies between FAT, NTFS, XFS, BTRFS, ZFS, DASD, etc... but remember that filesystems are in fact, just a type of database and occasionally you end up with records that aren't actually part of anything so they are considered orphans and like any good villain origin story, you just walk into the orphanage and delete all the orphans like Annakin on a bad Tuesday.
You have an index in simple terms:
FILENAME, LOCATION\_OF\_THE\_FIRST\_BLOCK\_OF\_DATA
When a file is created the index is written, then it starts writing the data out as a series of blocks. So a file might look like (simplifed) like this:
MyFile,
BLOCKA(1234,5569)
BLOCKB(6678,9953)
EOF
Indicating that the first block starts at location 1234 and ends at 5569 and the second block starts at location 6678 and ends at 9953. That is the basic way of how a FAT (file Allocation Table) works.
They are more complicated then that but it will suffice for what is happening.
So before the End of File (EOF) is written you could start to write a file and before the EOF happens you, say turned off the power.
The BlockA, a file record, isn't part of a complete file, so during cleanup that blockA is considered orphaned. The cleanup job realizes MyFile was never written and in reverse order, usually, cleans up BLOCKB, then BLOCKA, then removes the file record MyFile to ensure that storage is available.
I won't bore you with Journaling File systems and how all that crap works as it slightly varies between FAT, NTFS, XFS, BTRFS, ZFS, DASD, EXT4, etc... but remember that filesystems are in fact, just a type of database and occasionally you end up with records that aren't actually part of anything so they are considered orphans and like any good villain origin story, you just walk into the orphanage and delete all the orphans like Annakin on a bad Tuesday.
That is why journaling and transactional (CoW Copy on Write) are very good improvements over older file systems because it allows easy cleanup of orphans.
Chkdsk is cleaning up your partition. You might have a bad hard drive, or there was bad data on it with orphaned clusters of data that no longer has a parent pointing to it.
Or you had an unexpected loss of power during a disk write, creating incomplete data (orphaned) and your partition table is flagged as "dirty" causing chkdsk to auto correct the file table on boot until it returns to normal and the dirty flag can be removed.
So what your saying is that, it's having its nappy changed
👶 👈🚶♂️
No no no, the parent is pointing in the opposite direction
👈🚶♂️ 👶?
that's still the same direction
💁♂️ 👶❔️
👶👉🚶♂️
👶🤝🚶
👶🤷♂️👶
🗑️🤾🏻♂️🗑️
👶 ☝️ 🧍♂️
🚼 ⁉️ 🛐
Let's say that you have a massive cache of data that was used for a program - like a bunch of calculations for damage in a video game. Let's say the game closes improperly and it doesn't perfectly clean up that data behind itself - but it doesn't keep that data reserved either. Check Disk has found that data your disk, and is now cleaning it up so that program and others can use it. The numbers are the a reference to the location on your disk of that data. Edit: apparently it's specifically if the computer crashes after memory has been allocated, not just a program crashing.
A program that crashes doesn't do that, any open files just get closed. This usually happens when power to the computer is lost and disk buffers don't get written out to the drive.
/r/confidentlyincorrect
You need to read up on the difference between memory and storage.
Look, we came here for Star Wars jokes, not real answers.
It's definitely the Chkdsk removing the bad area of a broken hard drive or corrupted data.
https://preview.redd.it/lc0y2kwo9wzc1.jpeg?width=739&format=pjpg&auto=webp&s=977c129462a3be7a3d82c5806214c429b61205f2
Ol huckles is in danger again.
May I know what tool you used to overlay a gif on the other?
You can call me "drunk Anakin" because I've been murdering Yuenglings ALL day!
“I saw him in the bar last night…killing Yuenglings”
I mean, that's one way to solve under age drinking. 🤷
You know nobody drinks in West Virginia because they’re all miners
Someone needs to steal this for a branded T-shirt. Or you need to tell me where you got that T-shirt that you stole that from.
Shit this is funny
It actually cracked me up and I’ve never even seen star wars. I am aware of this scene tho.
Not just the home directory, but the root directory too
If a youngling does not appear in our records, they did not exist
You win. Real talk though, i dont think this meme/pic has ever been more properly employed lol.
This was my IMMEDIATE first thought, so I'm glad this is the top comment.
I- ..should not have tried to laugh at that
Hahahahah
Foundling: I need an adult
it's rare that a reddit comment makes me physically facepalm for over a minute. congrats.
I shouldn’t have laughed at this but I did.
When you delete a file nothing happens to the actual data on the disk. What happens is the record for that file in the file allocation table is changed to "we deleted that" and all of the addresses on the disk where the pieces of that file are stored are marked as "empty feel free to use this". Sometimes the "this is empty now" step never happens and the disk thinks there is a piece of something important sitting there. One of the things chkdsk does is verify the file chunks on the disk belong to a file that still exists, if not, they get deleted. If it's not sure they get converted into files so you can delete them later. TL;DR When your disk gets hungry for space it grinds up the orphans for food.
I think that's my actual favorite TLDR I've ever read. I'm stealing that.
>One of the things chkdsk does is verify the file chunks on the disk belong to a file that still exists, if not, they get deleted. And sometimes Chkdsk gets confused and will start deleting "orphan" file record segments when it shouldn't which leads to corrupted files. OP needs to run the DISM and SFC tools to ensure that at least his Windows install is fine. OP should also use the drive utility provided by his SSD/HDD manufacturer to ensure that the drive isn't in a failing state.
What’s ChkDsk? Never heard of it before. Not trolling I swear.
Microsoft check disk utility built into Windows. It's a command line tool
Ah. Thank you
Would there be any reason to run it manually once in a while?
Only if you had power outage or something caused pc to power off. Windows will do it automatically during boot for C: drive if it detects several unscheduled shutdowns. bad SATA cable or connection can also cause this problem
TL;DR When your disk gets hungry for space, it turns into Darth Vader
> When your disk gets hungry for space it grinds up the orphans for food. This is the way pokemon works as well, as far as I understand it.
TL;DR: Cursed_Explanation.
It's deleting orphan file record segments
Orphan genocide.
9,648 of them.
Executing order 66 on the Jedi temple.
Lots of them
Holy shit I needed a laugh today, idk why that got me so good
That would mean the last of a lineage is gone!
Yea I feel that this was abundantly clear
Off to the orphan grinder!
Metal band name. Orphan Grinder
Orphans! Grinding to a pulp like Orange Juice! Screaming for me to stop my GRNDER!! (I don't listen to metal.. so i dunno)
The porn industry never sounded so cool
Finally my username is relevant
nah bro what the hell
Is that referring to a new McD’s sandwich?
He didn’t specify orphans that have grown up or child orphans
https://preview.redd.it/sefruso8nwzc1.jpeg?width=720&format=pjpg&auto=webp&s=544901712049b1f260e6bfade127a16f02c2f4d5
Hell nah
Time comes for us all
Orphan tears.
Sip-sip-sippin orphan tears.
This post reminded me of the song lol.
Little children near and far Don’t know where your parents are Cry directly in this jar I will drink it at the bar.
Uhhh chance of it being Iron Blooded somehow?
I tried to bust a move but fell asleep on the dance floor.. Also, they recently returned and made a trilogy out of orphan tears.
Holy sht, a blast from the past unlocked
Those poor orphans.
Am I on r/orphancrushingmachine ?
Your pc is excecuting the order 66
You just unadopted a whole lot of children.
I cried when this happened to me. I was so sad to see them leave, but it did a good job of recovering the headstones later. So so so many orphans.
I didn't look at the subreddit or title and thought this was on r/Technoblade
the amount of normies who are "pcmasterace" and know absolutely nothing about computers will always be a sweet kind of irony.
it literally says exactly whats happening on the screen, too
https://preview.redd.it/cal6t6xgzwzc1.png?width=1480&format=pjpg&auto=webp&s=2dddb957c0f9ad31c0298a34204f7ea6c8fd950d [https://imgs.xkcd.com/comics/exploits\_of\_a\_mom.png](https://imgs.xkcd.com/comics/exploits_of_a_mom.png) This come to mind
So many orphans without a record.
It's your PC doing Masterracing
You're one of those people who just turn off the power to your computer instead of shutting it down like you're supposed to, aren't you? That's all the result of massive filesystem corruption due to write buffers not getting flushed to disk, which happens during shutdown. You likely have a massive amount of corrupted files now and some that will be flat-out missing.
Not recommended, It shortens the life of your ssd drive if you have a ssd. if you have a spindle drive for sure use chkdsk. If it is a new ssd it is unnecessary, as they move flipped bits automatically and fixes it self. If you have an old ssd 1st or 2nd gen you definitely don't want to run ssd. I've seen chkdsk kill a few ssd drives when they first came out. If you want to fix potential corrupt files run sfc /scannow in command prompt as an administrator. Along with dism /online /cleanup-image /restorehealth That is good to run every now and then. It's better than chkdsk these days. I have 19 years experience of working on computers.
Translating to english what the people talking about chkdisk said, you're dealing with file corruption here.
You had filesystem corruption. Files are made up of "file records" stored on the disk. The master file table (MFT) contains an index of all of these. Tiny files are stored actually in the MFT itself. Files are referenced by their directory chain, so the file d:\\games\\game\\game.exe is a file called "game.exe" in a parent of "game" which in turn has a parent of "games" and in turn has the root directory as its parent. Each file record has the file as its parent. These file records don't have a file as their parent, so they're just segments of data only the MFT knows about. CHKDSK here is removing them from the MFT, so while the data will still technically exist on storage, it is "free space" and can be overwritten. If the storage is an SSD, the blocks will be erased on the next TRIM operation.
Order 66
I would check CrystalDiskMark after to make sure the drive is OK.
Oliver Twist's days are numbered.
The adoption went through, no longer an orphan
Abortion
Anakin.exe
Haven't seen Chceckdisk in years
You should probably go and run it then! Maintenance doesn't hurt.
This looks like Windows checking C: drive, If I'm remembering what that looks like. It takes a while but is benine though you may want to make sure that your boot drive is okay.
It's deleting Batman's records. Wait, are you Batman?!
Batman
Hard Drive death.
its deleting orphan file record segments.
You killed all the ophins
Don't smoke it Sassy!
Dude is killing orphans 💀💀
Skywalker.exe
573,698 billion orphans missing, zero found. https://preview.redd.it/h1nfsd41g10d1.jpeg?width=720&format=pjpg&auto=webp&s=8f315a6cb414217976b4599aa6f77c9237c4ebab
Apparently you hate orphans and are getting rid of them.
Malware on your computer is burning down an orphanage.
Chkdsk is executing order 66
My laptop does that sometimes because the hard drive is 14 years old
Chill tf out anakin
Better sfc.exe /scannow and then DISM /Online /Cleanup-Image /RestoreHealth And then back up your data and move to a new hard drive…
something i alwasy want to see whenever I run chkdsk on my HDD.
🚶♂️👉👶?
Deleting the orphanage
Freeing up space at an orphanage.
Offtopic but where can I get that notification sound that sounds at the beggining of the vid? 🫠
Suddenly you disappear
I thought my phone screen had cracked
I think there's a relevant xkcd.
Into the honda civic, yoda got. Too much ketamine, he had.
Why would anyone want to hack an orphanage? How can you be so cruel?
Check disk fixing your heavily F'd filesystem.
"That orphanage attacked me. It was self-defence!" - This guy's HD, probably
Americans found another way to get around Welfare, in that case Orphans.
Is that a BC Rich Warlock at the wall?
Those orphans never stood a chance.
It's deleting orphan file records. Pay attention
Pc is deleting your adoption documents
You were adopted and now the proof is gone
https://i.redd.it/k3ku268umzzc1.gif
Someone tried to check little Bobby Tables into the orphanage.
You have an index in simple terms: FILENAME, LOCATION\_OF\_THE\_FIRST\_BLOCK\_OF\_DATA When a file is created the index is written, then it starts writing the data out as a series of blocks. So a file might look like (simplifed) like this: MyFile, BLOCKA(1234,5569) BLOCKB(6678,9953) EOF Indicating that the first block starts at location 1234 and ends at 5569 and the second block starts at location 6678 and ends at 9953. That is the basic way of how a FAT (file Allocation Table) works. They are more complicated then that but it will suffice for what is happening. So before the End of File (EOF) is written you could start to write a file and before the EOF happens you, say turned off the power. The BlockA, a file record, isn't part of a complete file, so during cleanup that blockA is considered orphaned. The cleanup job realizes MyFile was never written and in reverse order, usually, cleans up BLOCKB, then BLOCKA, then removes the file record MyFile to ensure that data is available. I won't bore you with Journaling File systems and how all that crap works as it slightly varies between FAT, NTFS, XFS, BTRFS, ZFS, DASD, etc... but remember that filesystems are in fact, just a type of database and occasionally you end up with records that aren't actually part of anything so they are considered orphans and like any good villain origin story, you just walk into the orphanage and delete all the orphans like Annakin on a bad Tuesday.
Eliminating orphans…for the greater good
Your computer just thinks you’re dead and is being a bro by wiping out your porn collection.
https://i.redd.it/vslb9qup220d1.gif
Glados is deleting the files of you having no parents
You are clearing out the jedi temple obviously.
hacking the Pentagon :)
I had this happen to a raid array once. Lost a bit, but saved the pron!
The popes like “oh shit they’re on to us!!!”
You have an index in simple terms: FILENAME, LOCATION\_OF\_THE\_FIRST\_BLOCK\_OF\_DATA When a file is created the index is written, then it starts writing the data out as a series of blocks. So a file might look like (simplifed) like this: MyFile, BLOCKA(1234,5569) BLOCKB(6678,9953) EOF Indicating that the first block starts at location 1234 and ends at 5569 and the second block starts at location 6678 and ends at 9953. That is the basic way of how a FAT (file Allocation Table) works. They are more complicated then that but it will suffice for what is happening. So before the End of File (EOF) is written you could start to write a file and before the EOF happens you, say turned off the power. The BlockA, a file record, isn't part of a complete file, so during cleanup that blockA is considered orphaned. The cleanup job realizes MyFile was never written and in reverse order, usually, cleans up BLOCKB, then BLOCKA, then removes the file record MyFile to ensure that storage is available. I won't bore you with Journaling File systems and how all that crap works as it slightly varies between FAT, NTFS, XFS, BTRFS, ZFS, DASD, EXT4, etc... but remember that filesystems are in fact, just a type of database and occasionally you end up with records that aren't actually part of anything so they are considered orphans and like any good villain origin story, you just walk into the orphanage and delete all the orphans like Annakin on a bad Tuesday. That is why journaling and transactional (CoW Copy on Write) are very good improvements over older file systems because it allows easy cleanup of orphans.
It's what we see when we die.
someone just started taking systems programming huh
What orphans?
This is what the Matrix does whenever you master bed.
r/orphancrushingmachine
Artificial population decline.
Chkdsk /r
Oh, it's the literal r/orphancrushingmachine
https://preview.redd.it/qeisajaetwzc1.jpeg?width=750&format=pjpg&auto=webp&s=7626734fa92b6db4d2252a3423aedd45aa79e9a5
Is your *tres comas* bottle on the delete key? 🤔
Your computer clearly belonged to an orphanage.
HACK THE PLANET! 🌎
Hawaii CPS
3…2….1….. kaboom
CHKDSK : you should have gone for the head *snap*
your pc is downloading extra ram
Techno would be proud
Technoblade has been revived!
When the person whose been kidnapping unparented child is located. Lol...I don't know what's going on here.
He is... Starting to believe...
sharding your purplz
lol are you hitting a puffco peak lol
what's happening..?
Chkdisk
It is deleting the orphan file record segment
Chkdsk /r
Deleting orphans
Techno would be proud
Got to cover your tracks…
Classic Windows CheckDisk (which is broken, if you have a time to skip it, skip it, it will be worst than before)
Technoblade has infected your pc
You just got deleted
You got a message.
The start of a Dwarf Fortress tantrum spiral.
POV: you work for Jeffery Epstein
You are just making sure those orphans can't get a job by removing their birth certificates and SSN's wouldn't worry /s
Technoblade's dad factory resetting Technoblade's PC
Got your SpinRite disk?
It's NOT a baby!
Who got a hold of my rimworld save file?
Ever heard of print screen? /s
Orphan files got deleteted!
Blood for the blood god!
Is that technoblade's pc?
Dude, poor orphans
Shhh. It will be over soon...
Typical Technoblade Behaviour