Damaged PSDs since 7.6.13 running

[EppeltFotostudios]

Hello together, since I´ve installed f@h (7.6.13 Client) on two win10 machines (atual Version) - we encountered since this day several damaged PSDs if the client is running in the background (Not all, some. Not depending on the size and not depending on the amount of layers ) We had this problem also on transferring Raw datas (~42mb each ) from a SD-Card from one of this machines via network to the Disk Station )
Means, a lot of work is destroyed … That´s not funny. If there is the possibility that this Problem is caused by the Client I´ll have to stop contributing.

Is it possibile that I get network problems when the Client is runnig on full Speed?

We save on a network drive, a Synology Disk Station with a Raid 6. The drives on this station are all ok - the protocoll of the disk stations shows no defects.
The disk Station is running the actual Firmware.
Best regards Chris

[bruce]

please post the first few pages of FAH's log per the instructions below.

When you did the installation, did you accpept the defaults? If you have a GPU, did you reinstall the drivers from the manufacturer's site?

FAH does not use PSD files, so it's difficult to understand how it could be interacting with them.

Which FAH files did you decide to transfer. Installing the client should have been sufficient withoug transferring anything although it sometimes helps to copy FAH"s config file.

[Joe_H]

If by PSD you mean Portable Storage Device, the client should have no more effect on one than any other software reading and writing files to the device.

Anti-virus scans of F@h work files may trigger false positives on random binary data in the files. If the anti-malware software removes or modifies those files, then corruption within the data folder can occur. We do recommend excluding the F@h work directory from scans.

[EppeltFotostudios]

Hi, thanks for Reply,
PSD means Photoshop document
the anti-Virus the one Microsoft based.
The Installation is as defefault, the graphic driver is actual.
We have this Problem only on files saved to the Network drive (mapped as Network drive z://)
We don´t save any data on the machine itself - for security reasons.
The Problem never happened before - it exist only since the Client is running.
The client is most time running on full power -

[Hopfgeist]

If the connection between running the folding-at-home client at full power and damaged image files is actually there, and not just a coincidence, then that hints at a more fundamental problem. All current operating systems have memory protection, separating applications' main memory and making access to another application's memory impossible. All network traffic has very robust error correction on multiple levels, and persistent errors are extremely rare. If everything works according to specification.

What could be happening is that FAH puts so much stress on the system (typically high temperature) that otherwise marginal hardware components become unstable and generate bit errors. Main memory (RAM) is a prime candidate, and unless you have ECC memory (uncommon on desktop machines), errors are typically not detected and/or corrected.

If you say this happens only on network drives, then the network interface is also a possibility. If you have another program which will also load the system heavily (such as a 3D rendering system, Cinebench comes to mind), try running that and see if the errors still happens. If they do, I would strongly suspect a hardware problem, that only manifests itself under heavy load, often triggered by temperature.


Cheers,
HG

[bruce]

How big is your system's power supply?

[EppeltFotostudios]

Thanks for reply -
on both machines is also Adobe Premiere and Cinema 4d installed - even on Rendering Videos with the Adobe media Encoder in the background we never had this Problem.
With Cinema 4d too.
Testing this problem during work time - sorry, no, it´s paid time And after worktime … . I will check the System temperature on workload. That ´s the only Thing I can do.
Both machines are different, one is a AMD Ryzen based System the other an Intel System. Both are running different graphic adapters by NVidia.
Actually I can´t check the Intel, we are on work - but the Ryzen one has Corsair Memory LPX2. I checked the Corsair Website and I didn´t find a hint wether it ist EEC or NnoEEC Memory. So I believe it ist NonEEC.
The Power Supply is a 850W bequiet - should be enough.
For my self, I believe it is a Network Problem, caused by the Client who is disturbing the Network traffic of other applications. On small account of packages it is no Problem, on saving a photoshop file with 1Gb, it is a Problem. But I´m not a Computer specialist, I´m a photographer
Thanks for your support Christian

[bruce]

on both machines is also Adobe Premiere and Cinema 4d installed - even on Rendering Videos with the Adobe media Encoder in the background we never had this Problem.

Perhaps the problem is whatever you're trying to do with background activities. FAH is specifically designed to use all "unused resources" but I suspect that Adobe is assuming that it can also use background resources and there are none left.

[EppeltFotostudios]

Yes and no, the Adobe Suite uses 80% if available, the mediaencoder is running in the Background using available ressources … but indeed the activity of FAH shouldn´t influence the System even it is running on 100% …

[bruce]

If 100% of the background activity is spent on FAH, there's none left for Adobe. If during the few seconds that it takes to download a new WU, Adobe uses 80%, it's not enough for you to notice.

[PantherX]

Welcome to the F@H Forum EppeltFotostudios,

I currently fold on my GPU and CPU (on 4 CPUs) while running Photoshop and Lightroom without any corruption on several files that I have used.

It seems that Adobe officially recommends to save to local storage and once saved, then transfer it to a NAS: https://helpx.adobe.com/photoshop/kb/ne ... oshop.html
Moreover, it seems that corrupted PSD files on NAS is not a unique issue: https://community.adobe.com/t5/photosho ... 872?page=1

Can you please post the log file? Ensure you include the first 100 lines which will inform us of what the system configuration is and what the client settings are. If you require guidance, please view this topic: viewtopic.php?f=24&t=26036

[Sandman192]

Someone said...

If 100% of the background activity is spent on FAH, there's none left for Adobe.

That's not how it works. You can have 2, 5, or more programs running at 100% at a time and they would all get divided equally to run together. Exp: 2 at 100% will divide each into half the CPU process.
Unless one program priority is set higher than the other then it can be 30/70 or something along the line like that. With 2 programs at 100% and so on.

[Sandman192]

1. He said it happed on 2 different computers. Nice thing having it is on 2 computers (not just 2 but 2 different computer with same problem).
2. He said it never happen before he updated to the new F@H.
3. Anti-virous? I never heard any anti-virous program crupet any file transfers. So I'll strike that one of the list.
4. What power supply you have? Again it worked before he updated F@H.

I really think that is a F@H issue.

[HaloJones]

If these computers are being used for paid work, I would strongly advise not folding on them except outside of work hours. FAH is designed to use all spare capacity and really for home computers.

BTW, do you have written permission to run the software (assuming you are not the business owner)?

[MeeLee]

Unless you are using a MLC SSD as storage device, or Western Digital HDD, data corruption is very unlikely.
Western Digital HDDs are known to fail prematurely, especially in high heat environments.
MLC SSDs are also a cheap way to get higher disk space by putting multiple bits into a single cell.
MLC nowadays mean 4 bits or more. SLC drives are extremely expensive, and come in small sizes usually.
DLC and TLC (two and three bits per cell) are your standard SATA 3 drives of a few years back.
Triple Level Cell SSDs are what you should be aiming at, if you have an SSD drive for storage, as DLC drives are pretty uncommon.
Or, go HDD with Toshiba drives. They've been proven to be the most reliable drives.


Before any data gets corrupted by the CPU, a CPU would need to reach such hot temperatures, that it comes close to it's max rated temperature.
You can download HWMonitor to check your system's temperatures, and compare them to the max temperatures noted in ark.intel.com

Another thing you can do, is check your RAM.
Turn off all background activity, and within Windows, press the 'windows key' + R, and in the run window enter: "mdsched.exe" (without quotation marks).
It'll test your RAM for defects.

There is almost no network activity that FAH uses that could corrupt files.
A much smaller possible reason, would be this:
If you have an Intel CPU with hyperthreading, and assume that your data issue is caused by the Meltdown/Spectre vulnerability, you could patch it, by downloading and installing the correct software patch; however, these patches are known to give near to the same performance penalty as disabling HT all together.
This site should give you the resources you need: https://www.grc.com/inspectre.htm
I would not recommend patching, unless you're absolutely sure this is the reason your files are corrupted because of this.