This post doesn’t benefit me at all but I love how long it is.
Comment on Syncthing alternatives
avidamoeba@lemmy.ca 4 weeks ago
That’s really weird. I’ve been using it for mobile-desktop-server-offsite sync for many years, with transfer sizes over 15TB, over WiFi, cellular, cable, fiber. I’ve never seen data corruption. Conflicts, sometimes. Permission issues, sometimes. Wiping something accidentally, sometimes. It’s even more weird because Syncthing performs computes hash values for the files it manages. I don’t know if it performs hash validation after copying remotely but if not, it can be forced manually which would tell you what’s fucked and be pulled from the source, if it still exists.
zorflieg@lemmy.world 4 weeks ago
avidamoeba@lemmy.ca 4 weeks ago
Let me tell you about diagnosing a reproducible crash on that 5950X system after swapping the RAM with verified good modules, which I only discovered because I decided to warm myself using Folding@home for a couple of cold days while the building was switching the central heating on.
ZeDoTelhado@lemmy.world 4 weeks ago
That is some good info here. My HDD is totally fine (checked it very recently actually), as for the ram last time I checked was ok, but can check again to be sure
avidamoeba@lemmy.ca 4 weeks ago
Check my edit.
ZeDoTelhado@lemmy.world 4 weeks ago
That is some crazy story right there. I do know for a fact that memtest needs multiple passes. But in my case the machine only has 1 stick of ram (used to have 2, one died). I will probably do a memtest overnight and get at you tomorrow.
halcyoncmdr@lemmy.world 4 weeks ago
(used to have 2, one died)
That would make me immediately look to the RAM as the possible source or corruption. If it used to be a matched pair and one stick died, the odds of the other being on its way out are MUCH higher than normal. I would never trust that matched stick.
halcyoncmdr@lemmy.world 4 weeks ago
I thought it was common knowledge that Memtest needed to be run for multiple passes to truly verify there are no issues. Seems that’s one of those things that stopped being passed down in the community over the years. Back when I was first learning about overclocking around 2005 that was emphasized HEAVILY, with the recommendation to run it at least overnight, and a minimum of 10 passes.
avidamoeba@lemmy.ca 4 weeks ago
It’s kind of embarrassing because I used to work as a service technician at a popular computer store in the 2000s and Memtest86+ has been a standard fare of testing. I guess outside of OC, the shorter first pass truly was enough to spot has RAM in the vast majority of cases. Plus multichannel interactions were not nearly as prevalent in the DDR1/2/3 days. I recently installed 4 DIMMS for 128GB on an AM5 machine just to discover that the 5600 RAM only boots at 3600 in a 4-DIMM config, as per AMD’s docs. Could force it higher but without extra adjustment it can’t go beyond 4600 on this machine. Back in the day, different DIMMs, often with different chips worked in 2, 4-DIMM configs so long as they matched their JEDEC spec. backinmyday.gif
halcyoncmdr@lemmy.world 4 weeks ago
Yeah AMD’s memory controllers, especially DDR5 seem to have a lot more difficulty at high speed with 4 slots filled. I used to plan upgrades around populating 2 slots and doubling if needed a few years later, instead now you really need to plan to ignore those slots if you are needing memory performance for things like gaming versus raw capacity.
avidamoeba@lemmy.ca 4 weeks ago
Yeah, I didn’t need 128GB, but as soon as I figured what’s going on with the 4-DIMM config, I ordered another kit to fill what I think I’d need for the lifetime of the system.
NullPointerException@programming.dev 4 weeks ago
The software should inform the user to run atleast 10 passes in the UI