66 GB of weird undeletable files suddenly appeared

[mlbk]

Hello,

I have been using FFS for quite a long time, it always helps me a lot and I love it.

However, yesterday I discovered 66 GB of weird undeletable files that suddenly appeared on my HDD which I use for backing up my personal data. It looks like the disk or its part got corrupted somehow.

I even suspected FFS, that's why I'd like to ask you if anyone had any similar trouble.

Here is the link with details and "screenshots":

https://answers.microsoft.com/en-us/protect/forum/protect_other-protect_start-windows_10/66-gb-of-weird-files-suddenly-appeared/910a56fe-3c1b-4e0b-ab08-3800188e81bc/

I managed to repair the disk with Microsoft crew. The advisor also suspected the "backup program" but since he apparently does not know FFS, I still do not know the origin of those files.

Could FFS cause something like that? Does anyone of you have any similar experience?

Thank you for help.
Martin

[xCSxXenon]

Definitely not FFS.
Either the drive is starting to go, or something else interfered with the permissions/file table. The fact that you can't delete them, with no error, lends to corruption of the data/drive. Get another backup and run an extended SMART test on the drive with the issue. You could try "chkdsk /f E:" and see if it finds/fixes anything. In my data recovery experience, that issue occurs when the storage controller/firmware is broken.

[therube]

The fact that you can't delete them

Suspect if you went into the directory in question (at a C: prompt - in that directory), a DEL of *.* would squash them.

(If you don't know C: prompts, do not attempt.)

That aside, I'd say your drive (or the connection to, or the box it is in, or...), is bad.

And yes, see what S.M.A.R.T. has to say (followed by CHKDSK) if you feel it is worthwhile...

Yes, that disk is usable

I'd certainly disagree with that - until you've tested things (drive, connection, box, even system RAM) & verified that it is all is indeed good.

Yes it is possible that data on the drive (drive tables or whatnot) simply "got corrupted".
And maybe that the drive is otherwise good, but before I'd trust data to it, I'd verify.