TheGleaner

Yes that is basically what I found before I went with unraid, those that did not have a driver error with my system anyways(ethernet is a reasonably important thing to have working). I figured $120 was a decent price at the time to save time. But even then I debated on it as $120 and soon $240 can go a long ways elsewhere, far enough that it may be worth trading perpetual savings for time and frustration with the lack of a helpful community.

To a degree yes, for what I use it for anyways. Before unraid I looked very hard at, what was at the time, free and true nas, along with OMV, snap raid and a few others, the last being proxmox, but since the others had a driver error of some type or another and/or a completely worthless community, I ended up here with my first generation, one generation old, AMD EPYC. Do I want to move? No. Do I want to split up everything into its own place? No. Will I if a subscription is added? Yes. Do I know where I'm going if the worst case scenario happens? No, but now is a good time to start looking, even if it turns out to be a waste of time in the end, rather than later, trying to beat a deadline. I regularly do look for other alternative software, such as my current search for a replacement for TubeArchivist, but I did not figure I would have to look for another OS, again. Lesson learned, I guess.

17 days later we need an official clarification, again.

I'm on unraid due to the one time cost and the community. Given the bugs and issues I've had, I would be leaving in search for something different if a subscription does happen. I would not have even considered unraid if it did have a subscription. Seeing how alot of it is run by the community now, it definitely does not sit right in any way. Even as we speak here, there are multiple threads on reddit proposing alternatives-on the unraid subreddit. I'm looking for them now as if 7.0 does cost more, especially reoccurring, I see little reason why not to go and try all other big name alternatives, again.

Is today's error. It isn't connecting to anything either.

Is now what I am getting today

Diag: server1-diagnostics-20231031-0256.zip

I am getting the following errors, somewhat randomly: In a red banner across the middle of the screen, when trying to use it. It functions fine, except the banner is in the way. and: and that is all the window shows. Black text on a white background. I recently started getting them under 6.11.5(or whatever the last 6.11 was) but after updating to 6.12.4, and half hoping they would go away, the second error type appeared.

What a disaster that came to be. Unraid connection: they were featured long ago on LTT. That is how I recalled unraid when searching for a nas os. I just had to search through 5 years of garbage to find the video to find the name, however.

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. server1-diagnostics-20230621-0110.zip

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 server1-diagnostics-20230618-0626.zip

server1-diagnostics-20230618-0626.zip

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. HGST_HUH721010ALN604_7JKLGUEC-20230618-0537.txt

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.