tiny-e

Support section is showing months-old content before current stuff. Sorting seemingly does nothing .

still bashing away at this ☹️. I don't understand why it sees the NIC but won't use it.

Moved from noisy, power hungry dell server to more 'consumer' hardware. The built in NIC on the board is realtek and seems flaky, possibly causing random reboots under unraid. So installed a Intel-based nic. If I boot into Ubuntu on the same machine, all works fine. If I boot into unraid I lose link lights on the NIC, can't seem to get it to work. I have the system booted into Ubuntu right now and am lurking in the discord. Could use some help, Diagnostic zip attached. I'm stuck. :/ Thanks for any help! nimbus-diagnostics-20251005-1131.zip

Here's where I'm at currently. Issue still persists.

I've been stuck here for like a half an hour:

Seeing Lots of iowait.. going to calculate appdata (it was set to Cache--->Array, but switched to cache only yesterday, I ran mover after making the change, but maybe there's an issue?

Thanks -- I Think I'm good, correct?

Problem still exists. 6.12.10. Adding, updating, or re-pulling a container make my system unresponsive. I've tried various things from making sure (I think) that appdata lives only on the cache, switching to file mode in docker (folders also on cache drive), etc. Getting frustrated. Can anyone help? I can upload new diagnostics once my server responds to my requests again...

Thanks for the reply -- It is: ... You know, the cache was originally part of a ZFS pool, and one drive died and I've yet to replace it. Could that be the issue? If so, can I un-pool the cache temporarily until I have a replacement in place?

Nearly a month goes by.... The behavior still exists. As my system is unresponsive as I try to pull a docker container now...

Yeah, I'm not sure what's going on.

Well... tell that to the "wrong disk" message. The array refused to start until I did the hokey pokey described above. Which is why I feel there should be a function for this or some accurate, specific, instructions. I did exactly this *see below* (minus the power down/up as I have hot swap bays) -- Didn't work. Wound up searching / going to the discord (that didn't work either.. but usually does). Finally stumbled across an article somewhere that got me back up and running. To that end, I've spent enough of my life on this issue to last me for awhile. So, take my feedback into consideration --or don't. I'm a relatively happy customer, but if customers take the time to suggest things they'd like to see, I'd at least pretend to care about their feedback.

Search should work. It doesn't. At all. I'm pretty sure the process described in there doesn't work as that's what I initially did. Unraid said "wrong disk" when I tried to assign the new drive parity. I wound up having to stop the array, put the old drive back in, start the array, stop the array, unassign it, put the new drive in, do "new config', ssign the new drive as parity. Piece of cake and totally intuitive. OR there could be a function "Replace/Upgrade Parity Drive(s)" that covers that.

... and I agree that the manual link should be more prominent.

Where's that at? I'm looking...