File's and folder got corrupted / no access

[LeoLUG]

Hi , I have a problem, not sure if it can maybe have to do with Everything,

My laptop came with 500mb M.2 SSD drive, and I added to it also a 2tb 2.5 SSD,
Lately, some times by trying to open a folder or a file from the 2nd drive (2tb) [14 months old], I got a msg that it's not possible to reach the folder,
Sometimes I got also a msg form Windows there is a problem with the drive, and by fixing I got some recovered files; and sometimes just by restarting windows it turn back to normal.

It never happens to me by browsing folders with TC or Explorer,
Can that be a problem caused by Everything? (I see something similar here)

[therube]

> Can that be a problem caused by Everything?

In general, I would think not.
(You could run ShellExView [but that too is really a different situation] & see if anything there might stand out to you, or if you're loading anything odd in there.)

> I see something similar here

That sure is an oddity.
(Not sure just why or how a context-menu item even causes corruption? Perhaps by the [odd] fact that the particular handler is being fired at an unexpected time?)

> not possible to reach the folder

Anything "special" with the particular folder? Really long length? A system folder that you may not have normal access to?
Could the 2 TB be asleep, & not responding in time, so Windows generates an error message?

> 14 months old

All drives fail. Could be DOA or anytime thereafter.


What version of Everything?
Are you using the Everything Service or running as Administrator?

My thought would be a drive issue.
Check its "SMART" status (with something like, CrystalDiskInfo).
And run CHKDSK (&/or drive manufacturers utility) on it.

[LeoLUG]

I'm using Everything 1.4.1.1001, and using the Everything Service
It happen for me, on different folders, folder with personal files,
really possible it have to do with the drive.
here is the smart status. (don't know what that mean, is it good?)

[raccoon]

here is the smart status. (don't know what that mean, is it good?)

The only thing that's striking to me is the Power On Hours and Power On Count. It just can't be accurate.

By those measurements, 777 hours and 2460 power cycles, it says your drive has only been at operating ready (SSD is always on) for 777 hours which is a scant 32 days, and for an average of only 19 minutes at a time.

What COULD be going on is that you have your Windows Power Settings (or BIOS settings) configured to sleep the drive after 10~15 minutes of idle, even though it's an SSD drive which should never be slept. If the drive is always put to sleep, practically every time you access a file, then it stands to reason there is going to be an access delay for the drive to wake up and the file system to synchronize with Windows. This delay could be causing Everything to hit Access Time-out Errors when attempting to access files.

This is all a little reaching, but that's my intuition. I would intuit further that because it's an SSD drive, Windows doesn't expect it to be asleep, so maybe your BIOS is responsible for the naughty business. Older systems aren't terribly SSD-aware nor optimized.

[LeoLUG]

Thanks for the detailed answer,
The Power Settings is set to turn of Hard Disk after 20 min, I should change it to Never ?

Can that be the reason to corrupt files from that drive?

[froggie]

@raccoon has it right, you should set power off to Never.

SSDs use times of low activity to reorganize the data internally. Cutting off power that often may possibly be causing an issue.

Also, never defrag a SSD - it just causes extra wear and shortens its life.

What version of Windows are you running?

[LeoLUG]

thanks.
I never did defrag with this drive.
Windows is installed on the M.2 SSD, with that one i didn't had the problem.

Edition Windows 10 Home
Version 20H2
Installed on ‎27/‎11/‎2020
OS build 19042.685
Experience Windows Feature Experience Pack 120.2212.551.0

[froggie]

Actually Windows 10 is SSD aware and I believe the power off setting should not effect it.

We are a bit off topic for Everthing support, but I wonder if there is something about the way the additional SDD was installed that is causing your problems. Since this is a Laptop, is the disk external - USB connected or is it installed some other way?

[LeoLUG]

Right, it seems to be off topic.
It is internal. and for 7 months i didn't had any problem with it.

[void]

Everything does not write to your volumes, it only reads.

However, reading the volume might be causing the issue indirectly.

The SMART data looks fine, it could be a bad NTFS directory listing, please try checking your drive for errors:

• Please backup anything important on your drive before checking it for errors.
• In Windows Explorer, right click your drive and click Properties.
• Click the Tools tab.
• Click Check now...
• Click Start
• If prompted to schedule a scan on the next restart, click Yes.

[NotNull]

please try checking your drive for errors:

Better wait a couple of days with that, until the fix for this has landed on your machine.

What stood out to me is the enormous amount of data that is written to this disk: 11128 GB in 777 hours. That is 14 GB per hour. *Every* hour.
That is a lot, especially for a non-system disk.

In the long run this will not be a serious problem, as most SSD's are guaranteed to >100 TB writes. And hat will take you more than 10 years.
But it is a lot of writes ...

My guess is that some specific program writes a lot of data to your D:-drive. And this program does not play nice. If you are downloading a lot (bittorents, etc), take a good look at the configuration of the software to let it write to disk less often (disable sparse files and keep larger chunks in memory before writing to disk).

[LeoLUG]

don't see any reason why the write on the disk is so much.
It was for a cupule of months on an other laptop as the system disk, but even that.

I use the drive a lot to copy stuff from it to HDD drive, i copied around 80 X 1TB from the SSD > external HDD usb connected - but that's is only read.

[NotNull]

Hard to tell from a distance. Even for a system disk, it is a lot of writes.

Some wild guesses:

• Are you running virtual machines from that disk?
• Are any of these files - with a recent date - on your D:-drive?
  (Search in Everything for
  D: hiberfil.sys | pagefile.sys | swapfile.sys
  )
  You might have a (very) aggressive power-down/hibernate schedule. Typically those files are stored on your system disk, btw

But even then, that would not explain the numbers you are seeing.
One thing is (quite) certain: it isn't Everything as Everything only writes to disk when you exit it completely (all "magic" happens in RAM).


But instead of guessing, better take look at what is going on on your system:
Start task manager ==> go to the Performance tab ==> Open Resource Monitor (see bottom) ==> select Disk tab

[void]

Are you using file-based virtual memory on this SSD?

Opening a handle to a raw volume will cause file-based virtual memory to be allocated on disk.
Everything will open a handle to your raw volumes to monitor changes to your file system.

To check disk activity:

• In the Resource Monitor (Start -> Resource Monitor)
• Click the Disk tab
• Expand Disk Activity
• What image is writing to your disk?

[raccoon]

I know it's still off topic, but I'd like him to explore his system BIOS to make sure that it's not set to turn off harddrives after N minutes. The BIOS might just be following orders even though it's an SSD drive. And I'd still turn off the Windows Power Settings HDD sleep for good luck.

I'm putting just over 1 TB per month through my secondary SSD, but I'm certain I'd be capable of 10 TB per month with the right workflow / motivation. (Sure hope it lasts more than 100 TB lifespan. Samsung EVOs have never done me wrong. Avoid QVOs.)

[LeoLUG]

Don't have any of this files -

D: hiberfil.sys | pagefile.sys | swapfile.sys

- on D: (btw, everything related: to search for it only on D, search need to be:

D: hiberfil.sys | D: pagefile.sys | D: swapfile.sys

).

I realized I have a program running from this drive, but doesn't supposed do write on it too much, the programmer will double check it.

Didn't find on the BIOS this settings, will check again.

[LeoLUG]

Now a Everything related question...
What's the reason everything is writing on the drive, by every search?

See on this video recorded https://www.dropbox.com/s/kqzpx9qngpduh ... 2.wmv?dl=0

[void]

Thanks for the video.

I only see a few KBs of reads (no writes from Everything.exe -Unless I'm missing something?)

This is most likely icons or shell extension related.
What type of file is shown in the File column? (you can resize the File column header to make it larger), eg: is it an ico file?

Please try sorting by Write (B/Sec) descending by clicking the Write (B/Sec) column header.

[LeoLUG]

the write by the SYSTEM was on the same folder as the everything was reading, and you right, it's not a lot of reading,
I tried now again, but it doesn't did the same thing ...