taken from a home video

#retro #retrocomputing #chkdsk

I don’t want to leave this system and boot into #Windows. Not even for a second. #Arch + #Gnome are so stress-free, and everything just works.
#chkdsk
Recovered nicely. A few days of alternating #chkdsk and #robocopy and successfully got everything off.
Of course.
#chkdsk

Frage an die #WindowsBubble / #ITBubble:

Der eine #Windows10 #Laptop lief, zumindest vorhin, etwas SEHR langsam, sodass ich zu zwei Not-Neustarts greifen musste...

Ist das ein kritischer #NTFS -Fehler, der mir mit #checkdisk ausgegeben wurde? Hat es evtl einen Zusammenhang mit den Hängern? Und reicht es hier wirklich aus, mit admin-cmd "chkdsk C: /f /r" auszuführen?

Gerne RT. Danke!

#chkdsk #error #Bug #cmd #Windows #RECHNER #sysadmin

The #microSD card in my phone has gotten corrupted.

My (dusty) Windows7 laptop says the disk format is exFat and that the disk is now good.
Pretty sure the Android phone wants Fat32, so how did it ever work in the phone?
Used #FreeFileSync to backup the card's files to a laptop. But some files not transferable.
Used #chkdsk but AOK there.

Hours taken by this #TrashyTech so far?
Three? Five? Getting other things done but ....

So now trying #DiskDrill.

#ConsumingIn2024

Facing the "Disk Does Not Have Enough Space to Replace Bad Clusters" error? Try running the CHKDSK utility with the "/r" parameter to scan and repair bad sectors, ensuring sufficient free space on your disk. Consider freeing up space by deleting unnecessary files or transferring them to an external storage device.

https://www.stellarinfo.com/blog/disk-does-not-have-enough-space-to-replace-bad-clusters/

#DiskError #CHKDSK #DataRecovery

Methods to Fix the "Disk Does Not Have Enough Space to Replace Bad Clusters" Error | Stellar

While running CHKDSK, if you see the Disk Does Not Have Enough Space to Replace Bad Clusters error, recover your data & replace the drive.

Stellar Data Recovery Blog
3 Modi per Usare la Funzionalità Chkdsk #howto #diy #Chkdsk
Yup corrupt AF. And for extra irony 5 directories reported are all for *technology* podcasts. And our old #CHKDSK friend the "100 percent completed"
...except after an hour it isn't. The 'progress' dots are gradually going more to the right but I guess at this pace it's going to be an all-nighter. Still looks like it will be helpful, have used this technique in the past with good results

@danderson @tychotithonus @jernej__s
#ntfs

Does anyone here understand this?

I was copying my #ArchLinux Home drive to an NTFS USB hard drive via Beyond Compare. When it got down to .cache/Thumbnails, it began counting up millions of files and more GB than would fit on the drive. I killed the copy. In Linux I was able to delete most of the files it had already copied, but a few triggered the impossible counts. Curious, I connected the drive to an old Win 10 machine which saw a similar mess. I ran #chkdsk /r for ~4 hours, and the corrupted files were gone. But some of the found.000/dir0000.chk files it made were as corrupt as the originals, I can't delete them. I can copy them to a different drive, but that copies all the items that seemed to be deleted from the previous drive. I can seem to delete most of them again...

This is now happening on Linux native drives, so I doubt my USB drive or Linux vs. NTFS is the problem. Is there some way to see what is happening and delete the corrupt chkdsk files?