TheGleaner

So then, as a follow up, for it to show an error, it has to not correct it? I have got it to show errors before on new to me ram...

Archivebox, dev version, with extension, on 6.11.5: why is it filling my docker image file rapidly? As in two weeks and it reads as 40GB according to unRaid.

Just as a general idea, if you throw a new to you stick of ECC ram into your computer/server and unraid starts reporting ECC correction errors upon boot, that stick is the issue, most of the time, correct? If true, why didn't memtest find the issue during a few passes, yet UnRaid does immediately?

What would be recommended for being a redundant type and having at least 18 molex plugs and at least 1600w in an ATX or very close form factor? I currently have an old zippy/emacs 2+1 redundant psu rated at 800w, but I am getting very close to that rating being pulled at startup. I have found I can get what i want from zippy/emacs, but it would be special order through any distributor and they are not very interested in ordering just 1.

Got it to fail now.

Which one?

I have rebooted, but I am trying to get it to do it again right now. Here is this if it means anything

This drive was a parity drive for about 6 months. I bought it used like all the rest then one day it was disabled. It was like it was unplugged. I tried swapping cables, ports, etc, and it would run fine for about a week and then act the same, like it was unplugged. I got a replacement and moved on, yet then it has idled fine since then and I can sit and load/unload with preclear or any other disk testing program most of the time without issue. There have been a few times where it has acted like it was unplugged. It has been running for 6 months or so again without issue so there is no unraid log on it currently. I figured I would ask and see if someone has dealt with similar or had an idea on what else to do or try.

The log is filled with this for days, then its fine for weeks, then it has this again. What exactly does this mean? I only took a look at the log because one drive got kicked off with one error.

I could "understand" some of them closing(well, no I don't but...), but anything related to tech support it shouldn't have even crossed their minds. I do find it odd that any time someone recommends coming here instead of what ever is supposedly the replacement, it gets shot down as "forums aren't good for troubleshooting" yet reddit is a forum. Datahoarder is also a sad thing to lose. If unraid couldn't figure it out, someone over there could.

No. I was meaning I was trying to transfer MBs worth of files to a 2 TB SSD cache drive, but I have not had the issue since I posted. Go figure.

128 currently, will be 1TB eventually as I find enough cheap ram, because why not.

I am having the issue of when trying to transfer from a disk to the cache, some files will not transfer as it says there is not room in the cache, but the cache does have room and the files are small, small enough they could all fit on the cache. version v2021.04.21 (5.6.4) Unraid 6.11.5

Same here

More arrays, as in multiple of the 30ish drive existing type, not break that 30ish into smaller ones.

I recently bought a few used HGST Ultrastar 10TB drives, and one of them was a former IBM Storage solutions drive, that at first had type 2 protection on it. I searched and found a few commands to disable it(I think) but now it still states "LU is fully provisioned" which doesn't seem related, as I have another one with that, but it seems to be fine. The issue I am having, still, with it is it shows as 9.93TB instead of 10 like all the others. With the type 2 protection it was showing 9.9TB. What is still enabled or disabled or what is going on here to get that odd size and how do I get it back to its nameplate capacity of 10TB, like all my other ones? It does show 4096 as the sector size.

I can not seem to get it to do anything much, and when I do, the the same issue as above. It seems very hit and miss for connecting and handshaking.