apandey

Is your usb boot drive OK? Perhaps post diagnostics

Is the other end same on the PC, same port on patch panel / router? Maybe try another port direct to router to see if thag changes anything

What is on the other side of the cable? NIC is identified as 2.5gbps, but negotiated at 100mbps

The attached zip file has a single disk SMART output, not diagnostics

What exactly is the question?

Probably no one has contributed a docker template for it yet

For current version of unraid, the manual is the right way to go https://wiki.unraid.net/Manual/Storage_Management#Removing_data_disk.28s.29 You will need to rewrite parity either way, so that will take whatever time it takes

Yes, for anything not having an obvious other place, start here. If it's misplaced, a mod can always move it to another subforum

Anything in /boot/config/go will get executed at startup

Is this on a Mac? I see this occasionally and it's something to do with dns handling. A good way to verify is by going to chrome settings and toggle private dns on then off. Then it starts resolving again. I've reproduced it many times but not figured out why

@MAM59, you have me worried now. I have a mellanox connect-x 3 card which has the same from ethtool. It's connected via a DAC cable to a PC and I seem to get full 10gbps when there are no other bottlenecks on that connection ~# ethtool eth2 Settings for eth2: Supported ports: [ FIBRE ] Supported link modes: 1000baseX/Full 10000baseCR/Full 10000baseSR/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: No Supported FEC modes: Not reported Advertised link modes: 1000baseX/Full 10000baseCR/Full 10000baseSR/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: No Advertised FEC modes: Not reported Speed: 10000Mb/s Duplex: Full Auto-negotiation: off Port: Direct Attach Copper PHYAD: 0 Transceiver: internal Supports Wake-on: d Wake-on: d Should I be concerned?

There is clearly something wrong with your volume mount. Can you share a screenshot of your docker config for shinobi. The video data directory in my case is /home/Shinobi/videos inside the container, so I don't know why you are using /dev/shm, which is a device path. I am using shinobicctv/shinobi container template

The confusion has been summed up in the last few posts, now all that remains is for someone to unpin the thread so it's not prominently visible to add to the confusion. It will get a proper solution at some point I hope

Those instructions should work

Is knownIPAddress accessible over http instead of https? Is xxxxxxx.unraid.net resolved if you use a public dns server like https://www.nslookup.io/domains/xxxxxxx.unraid.net/dns-records/

It would be nice if unraid has an option to log the actual cause of drive spin up. I am assuming there is an explicit decision to spin up the drive at some point due to some requested IO, and given how frequently this question comes up, it would be good if there is some in-built way to troubleshoot this rather than indirect means. I am not sure what is feasible, but a better tool will probably be immensely useful Right now, no indirect measurement is sufficient by itself to pin down the cause. It can be an already open file, or access to a not-open file, or directory listing, or some filesystem operation etc. And we need separate tools to observe each of these in isolation

That is what I have, pfSense with VPN server. All network security happens here and availability is not a concern due to focused application. Unraid is then just another appliance on the inside then

I don't know of a guide, I had prior experience with haproxy and looked up whatever I needed help for to set it up. Broadly, I think it means: 1. Change pfsense web UI port, so that 80/443 are freed up for haproxy 2. Install haproxy addon in pfsense. Create a frontend to listen at 80 or 443 on a pfsense IP (let's assume pfsense IP) . Create a backend this frontend routes to. I would start with http to begin with until you understand how it works 3. Have your local domain resolve to haproxy frontend IP (let's assume my.home resolves to pfsense IP) 4. On the haproxy backend, create ACLs to map each app-name.my.home sub domain to it's respective ip and port wherever that app is running (the Docker ip and port in unraid) That should resolve app-name.my.home if your clients use pfsense dns In my case, I have a more evolved setup: - I have a public domain x.com - I have mapped home.x.com to haproxy frontend IP - I have acme plugin in pfsense to issue a wildcard certificate for *.home.x.com from letsencrypt. This allows me to setup a proper https frontend for haproxy, and this is also why I use a public domain name - I have a https frontend running at port 443 using the wildcard certificate. This is how I access my backend apps. All my backend apps are http, so ssl terminates at haproxy - I also have a http frontend running at port 80 which simply redirects to https. Please note my whole setup is intranet only. None of this is exposed to the internet. I use a VPN into my network if I need to access these remotely

The little > icon on top right of web UI will open a terminal for you. If you have ssh enabled, you can also directly connect from another ssh client. If you want something running non interactively, look at user scripts plugin

Intel site has comprehensive listing of specs, even for very old EOL products https://www.intel.com/content/www/us/en/products/sku/52214/intel-core-i72600k-processor-8m-cache-up-to-3-80-ghz/specifications.html

Settings tab -> Docker, scroll down to docker volume info. I should have been more specific, it's this volume I asked to scrub. But @JorgeB has good point on checking size first If docker volume is filling up, it usually means some container is writing data into it, rather than to an external volume mounted to the container. If volume is getting full, try using container size calculator on docker tab to see where the issue is. A much more accurate picture can also be obtained using these scripts: https://github.com/SpaceinvaderOne/Unraid_check_docker_script

From your diagnostics, I can see it listed in lspci output. I can also see it being initialized in syslog When you go to Tools tab, system devices, does it show up under PCI device listing. How are you trying to give it to the VM?

What i saw was not diagnostics. It just had your wireguard config in a zip. Diagnostics will never put that stuff there and all the stuff that is supposed to be in diagnostics zip wasn't there at all. Also the file wasn't named correctly to be a diagnostics file. How did you generate it?

Seems you have shared your wireguard details, which exposes your server to external attacks. So as a first step, you should rotate your keys so that no one is able to access your server from outside If you need help, you should share diagnostics which is a safe way to share details on your server setup

You are getting write errors from btrfs. Run a scrub to see if you have any filesystem corruption. Run memtest86 to rule out any bad RAM issues