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?