BRiT

Maybe your Content View behavior got reset? I use my own feed to filter out forums I don't care for. When I click on the longer title of the thread it seems to still take me to the first unread comment. This is from Account, Account Settings, Content View Behavior, Take me to comments I haven't read.

I ran it native. But I've upgraded systems since I posted that message over a DECADE ago.

I didn't mark it as a solution. I don’t see how it takes away flexibility of movement. You have your server in a spot, that doesn't change at all. You merely have a tiny little Access Point on top of it. Are you saying you were going to use a laptop as an unraid server? How were you going to add any storage to it? Adding any amount of external storage to a laptop is as restrictive as you claim to want to avoid. Maybe rethink your plan before throwing shade at those give creative ideas.

Use the Hack-Around mentioned earlier. Connect you unraid server via wire to a wireless Access Point that then connects to your WiFi above the drivers seat.

@jonp @limetech can you provide insight into what's happening?

I use putty to connect via SSH to the server and it never times out. It only disconnects upon shutdowns.

Also, quick Google that IP says it's part of PIA VPN. So using PIA VPN causes that to happen. https://spur.us/context/138.199.30.2

What do you have installed? It is likely a torrent program you opted to install and configure and run. It then picked this random high numbered port to use for callbacks.

Try what Squid suggested earlier.

Ask in the ZFS plugin support thread.

Doesn't happen for me at all.

The preclear Docker container works well. I used it to test and validate a new drive the other month before I had to replace a failed data drive.

Correct. User 0 does NOT include cache.

At what point does the error occur, when you go to post the topic or during the setup of it? It looks like I'm able to create a poll, but I have not attempted to go beyond this basic step.

When my docker(s) update they do not impact the other dockers.

They suggested you use Multiple Cache Pools, not Data Pools. So essentially every chia drive is its own cache pool.

Try posting in any official support threads.

Have you tried turning it off and on again?

Would you kindly submit a feature request detailing what additional information should be anonymized. That way the developers have a better idea of what's needs to be improved. Guiding developers would be beneficial to everyone.

You don't seem to be eager to help yourself. If you were, by merely reading 7 posts before your question you would see all that you need is posted by trurl. I'll try to link to it, but mobile doesn't do to well with linking, so if it doesn't go to exact post, you'll have to do the work yourself...

I run monthly parity checks. I don't understand how anyone could be comfortable with only running 2 full parity checks over an entire year. At the least, I would pick a schedule that allows a full parity check to complete within the month.

Not at all.

It would be for more than just the UI.

@xrqp did you order from "Seagate Store" which now shows as HyperHawk storefront on Amazon? I've been going through the Q&A on the X18s and X16s trying to figure out which resellers are with full 5 years and which are OEM meaning no direct coverage from Seagate. It's a bit of a hassle, but its a savings of $75 for 1 drive or $225 for 3, which I'm looking to pickup. I'll definitely need to setup Parity Tuner if I expand to 16TB or 18TB drives. I had a power outage last week Thursday that killed an 8TB drive completely, despite being on UPS. It won't power up even in other systems or enclosures. The other 3 drives are fine. I ordered an 8TB drive that could be delivered Friday. The preclear took 33-35 hours for 1 Pass to ensure the drive was suitable. I started the data rebuild this morning. Should be finished in another 6-8 hours. It will be nice to be back on a protected array.

I see some slightly older model Seagate Exos X16 16TB drives around $325 or around $20.32 TB. I see some saying the warranty starts from date of manufacturing and not date of sales. It all depends if you get an OEM or Retail unit. That seems rather difficult to find out on some of the Amazon listings. I also see statements where "The limited warranty extends only to the OEM and may not be assigned or transferred without Seagate’s consent."