Ghostie

So as an update a rebuild succeeded after a reseat so no idea what was causing it hopefully it stays stable

Currently using an LSI 9207-8i flashed in IT mode purchased from a reputable seller on ebay, unfortunately dont have any alternative LSI cards just a SATA expander board which is less optimal from my research. Do you know if there are specific models of issue from LSI that dont work well with high capacity Seagate drives? Currently attempting another rebuild on the diasabled drive (disk 7), do you know if the prior rebuild couldve failed due to the read errors spanning multiple drives (inclusive of parity)? Additionally, any guidance for troubleshooting potential power/cabling issues? Drives are currently split across 2 6 pin ports on the PSU which is a 750w EVGA gold, no GPU in host main power consumption is from CPU which is i9-10900 and drives that are 8 HDDs, 4 sata SSDs and 2x m.2 nvmes

For additional details, this has occurred one time prior and I reseat all the cables to see if the issue persisted. After doing so I was able to rebuild the disabled disk, but the issue has re-presented itself after I attempted to move ~5TB from cache to array via mover. I'm trying to isolate what component is failed and am utterly confused between a failed drive, the LSI card, or the SAS cables. I've done another reseat and am attempting another rebuild (prior rebuild on disk 7 failed towards almost the very end with approx 1 TB left and started generating read errors again). I've also swapped the SAS cables on the LSI card's ports to see if they perhaps start occurring elsewhere. The disabled disk only has power on hours of 2739 (3m 22d)

Hey folks, I have read errors on multiple drives occurring on my host, there has been no recent power failure or anything that could trigger multiple drive failures and most of my drives are relatively new. I'm trying to pinpoint if there is an actual drive failure or if there could be an issue with cabling or my LSI. Unfortunately, I'm not very good at reading SMART data. Short self-tests past without issue, extended self-tests pass for 2/3 of the drives with the 3rd one aborting with the reason being "aborted by host." Was wondering if someone could help me review my diagnostics to see where the issue lies. Thre read errors were showing on sdg (parity), sdh, and sdf

+1

Any idea how I can resolve the above mentioned bug? <edit> all is fine in the world after a system reboot

I did a docker prune and that only reaped a stopped container (not one of the ones from the issue described) and an unused network. I don't see any of the problem dockers in the GUI so I don't quite follow how it obtains the list of containers from the GUI?

The listed containers that show up in the plugin are not visible in the gui nor in `docker ps` / `docker images`. Can you specify where the plugin is looking so I can clean up the files there? I've taken a look in the USB files under /boot/config/../dockerMan/templates* and I could not find where the plugin is sourcing the stale plugins from, its not really an issue but I would prefer to clean it up

Hey guys had a quick question, I see some stale docker containers in the update portion of the plugin (these were not installed via the CA apps pre-generated template but custom generated), how do I clean up the old container files so they don't show up for selecting to update in the plugin?

Worked like a charm - thanks!

Ah my bad, should've read more. Were you able to find a solution? <edit> I think I got it to work by editing /speedtest-tracker/nginx/site-confs/default to whatever ports I want e.g. 4568 for "listen 4568 ssl" and then adding a port forward variable in the template to forward 4568 to 4568 and then doing the same normal process for the vpn container of allow-listing those ports. WebUI up and running now.

I can't seem to get to the webUI when specifying a network as "none" and specifying a specific container network as the network in extra parameters e.g. -net=container:myvpn_container Normally, for my other containers, I'll add the port to an allowlist for the webui and did the same for this. However when specifying a WebUI port such as 4856 or what have you the port mappings still show as 443->443 and 80->80. Any idea what I could be doing wrong here? Use-case is I want to test my speed for my VPN connection

I'm trying to have speedtest cli on their by default which requires curling a script first and then installing via apt as well as installing dnsutils for nslookup/dig So how do I go about doing this on unraid? Can you explain how to adjust the Docker template to the path in the Unraid UI? Do I go to "add path" -> tried doing that but I can't specify a file only a directory I don't really follow the part about "mount it" or "then in the Docker template to the path" - can you explain it to me like I'm 5 y/o lol

For the debian-bullseye container I was wondering if you could elaborate on establishing persistence for tool downloads. In the container documentation it states "If you want to install some other application you can do that by creating a user.sh and mounting it to the container to /opt/scripts/user.sh (a standard bash script should do the trick)." I've created a user.sh script, but I don't know what you mean by "mounting it to the container to /opt/scripts/user.sh" - could you explain what you mean and how to do it?