Konnor378

Yes, I was installing drivers from ich777, as far as I remember ITE, realtek and radeon-top. Maybe the speed problem is solved by forcing smb3, because I also have smb3 minimum protocol in ovm, and the file corruption is probably some kind of component incompatibility. I also learnt on another forum that unraid doesn't work well on boards with Marvell controller, I don't remember exactly, and maybe it's my case.

So, I finished testing the hardware and found out that it's not the components, but the unraid itself. Another RAM with ECC did not help. I tried OMV/TrueNas/WinServer2022 systems and on all systems there was no file corruption, moreover even the smb transfer rate on all above systems increased (150-190 MB/s), on unraid it was around 40-50 MB/s. Maybe there is some incompatibility with unraid, but I remember exactly that on version 6.11.... files were fine. I then completely reinstalled unraid with partition cleanup on the flash drive, didn't install any plugins/containers, just created shared folders on the drives, shared via smb, and a day later the files were corrupted again. I now have OMV installed, also running via the same flash drive and the files are fine. Looks like I'll have to wait for newer versions of unraid with a fixed bug to ever get back to it.

In general, on a different RAM card with ECC the problem remains. I will try another OS to rule out incompatibility of my components with unraid

I moved the file from the /tmp folder back to the disc, and it was even more broken than usual. Looks like it's the RAM after all. I'll get new RAM from ecc today and see if the situation changes.

Okay. I'll try copying the test files to /tmp. As for ECC memory, the motherboard supports unbuffered ecc, but the processor is not sure. I have an asus prime a320i-k board and an amd athlon 3000g processor and I'm not sure if the processor supports ecc because I've come across mixed information and I'm not sure if it can work with ecc memory. I also have an assumption that the image from the USB stick through which unraid is launched is corrupted. I don't know if this is true, but on version 6.11.... this never happened. I don't mean to disparage unraid in any way, but I previously had an OMV system with the same configuration and it did save my files, but the excessive crutching and almost constant console work was a bit stressful

The problem still exists. Going to go buy another RAM with ecc tomorrow. I will report the problem in a few days after the tests

Yes, I put the file in read mode and left the other one as is to see the changes, and to rule out other trivial problems, I updated the bios on the motherboard and, following the advice, moved the RAM to a different slot and restricted access to other devices for the time being. We'll see how the files behave.

I will try moving the RAM to a different slot. If there are any changes, I will let you know

The rsync test passed without errors. When I upload the file to the system, the checksums match, but within 1-3 days the file gets corrupted, and after the corruption the checksums are different from the original. The files are static and are not moved anywhere, just stored on the disc. When I ran memtest86 I put the clean test files on the disc and was sure they were intact, and after checking the RAM I found those test files corrupted again, with memtest showing no errors. I also tried reconnecting the RAM though in the same slot, but got corrupted files again

About 30 passes In that case I need to run memtest for a few days or even a week?

I wrote earlier that I ran memtest86+ for 24 hours and didn't get a single error

Yes, I am accessing all the files. I have also copied corrupted files to several computers and in all cases they were corrupted. The checksum was also different from the original one. I'll attach a screenshot of the error if that helps with the solution. The dynamix file integrity plugin also marks files as corrupted

Hi, I ran into a problem with file corruption. It's worth saying straight away that I'm using non-ecc RAM, no cache and no parity disc if that affects anything. I previously thought the btrfs filesystem was to blame, but having changed to xfs and zfs I found out that it's not the filesystem or the drives that are to blame, as this problem is spreading to all drives and even new drives that have only been running for a few hours with a completely clean SMART (specifically bought a brand new cheap drive to check). The zfs and btrfs checks built into the file system do not reveal any problems. I then started checking the RAM with the inbuilt memtest86+ and after 25 hours it showed no errors, all passes were in passed mode, then running the array again I saw that the files recently downloaded before memtest86 had also become corrupted. Maybe it's my unraid upgrade from 6.12.4 to 6.12.6 as I found this problem on 6.12.6. I don't even know what to think or what the problem could be. I don't know if all file types are corrupted, but the exe format is definitely corrupted sooner or later bigshell-diagnostics-20240106-2327.zip