ken-ji

Odd. Can you post a screenshot (or text copy) of what you are seeing now? particularly running root@MediaStore:~# ls -al /root/.ssh /boot/config/ssh /boot/config/ssh/root lrwxrwxrwx 1 root root 21 Apr 8 02:48 /root/.ssh -> /boot/config/ssh/root/ /boot/config/ssh: total 120 drwx------ 3 root root 8192 Mar 22 18:44 ./ drwx------ 11 root root 8192 Apr 27 21:07 ../ drwx------ 2 root root 8192 Apr 19 22:47 root/ -rw------- 1 root root 668 May 3 2019 ssh_host_dsa_key -rw------- 1 root root 605 May 3 2019 ssh_host_dsa_key.pub -rw------- 1 root root 227 May 3 2019 ssh_host_ecdsa_key -rw------- 1 root root 177 May 3 2019 ssh_host_ecdsa_key.pub -rw------- 1 root root 411 May 3 2019 ssh_host_ed25519_key -rw------- 1 root root 97 May 3 2019 ssh_host_ed25519_key.pub -rw------- 1 root root 980 May 3 2019 ssh_host_key -rw------- 1 root root 645 May 3 2019 ssh_host_key.pub -rw------- 1 root root 1679 May 3 2019 ssh_host_rsa_key -rw------- 1 root root 397 May 3 2019 ssh_host_rsa_key.pub -rw------- 1 root root 1773 Aug 12 2020 ssh_known_hosts -rw------- 1 root root 3312 Mar 22 18:47 sshd_config /boot/config/ssh/root: total 48 drwx------ 2 root root 8192 Apr 19 22:47 ./ drwx------ 3 root root 8192 Mar 22 18:44 ../ -rw------- 1 root root 418 Mar 9 08:19 authorized_keys -rw------- 1 root root 883 Mar 9 08:19 id_rsa -rw------- 1 root root 209 Apr 19 22:47 id_rsa.pub -rw------- 1 root root 3473 Apr 19 22:45 known_hosts

Because of a weird speed issue where I now need to spin up my array before running parity checks etc. and my personal opinions about php, I had to take up the bash challenge (this might even be sh compatible) Only did the spin them all up one though. #!/bin/bash . /usr/local/emhttp/state/var.ini curl --unix-socket /var/run/emhttpd.socket \ --data-urlencode cmdSpinupAll=apply \ --data-urlencode startState=$mdState \ --data-urlencode csrf_token=$csrf_token \ http://127.0.0.1/update

Holy --- ! You're correct about the spin up thing.... hmm I think I'll look into this angle... and probably create a cron script to wake up the drives prior to major activities

Are you absolutely sure you do not have anything in your system? user scripts plugin? cron jobs? and if you delete/rename /boot/config/ssh/root folder and reboot? does it come back?

It might be, but I've only heard from @Zonediver so have no other points of reference and am not having luck seeing anything like this in the wild (or my ability to google has failed me) In any case I'll try some hardware tweaks when I am able and report back.

So there really is something wrong with 6.9.2 and some LSI controllers I had a parity check run start and was wondering why it said it was running at 90MB/s at the start. So I stopped it and ran some benchmarks and saw this: Disk 4 actually read 60MB/s at one point but restarting the benchmark painted the usual 244MB/s value I don't see any other issues in my logs. I'm currently allowing a parity check to complete before I try anything else. I'll probably try things like switching ports on the controller or switching controllers to an LSI 9200-8e (I think) when I get back home to my server mediastore-diagnostics-20210424-1011.zip

Ok. now that I have time to try upgrading again. I did and the problem has gone away. The one thing I did though beforehand was to finally flash my controller to P40 so maybe that was it.

Well I had a parity check run then and the speeds got capped to the slow 60MBs so its not the DiskSpeed-Docker's fault I think.

I'm wondering if anybody with an LSI card using the mpt3sas driver has noticed any speed issues? I'm using a LSI SAS9206-16E HBA and its dual linked to an expander / enclosure - ARC-4036 I've had this setup for a long while now and I've always gotten the maximum speed out of all my HDDs from it. But when I upgraded to 6.9.2 this weekend, half of my drives on the HBA started running at 60MBs only compared to the usual ~200MBs When I reverted back to 6.9.1 the drives all ran at their max speed When I have time, I'll try to upgrade again and see if the problem occurs again I don't have the all drives benchmark in 6.9.2 which gives really weird results. ^ This is Disk 5 (black is 6.9.2)

You can try making a request to Limetech, but you'll need to know what you need exactly (I'm not sure either)

I think most users here limit VMs and dockers at the router level, which would have better control of the network than Unraid itself. I could do that with my Mikrotik router, but I never needed to.

The error: "Specified qdisc not found" indicates that the qdisc modules are not installed/available. So this would probably be unsupported unless the modules are compiled and loaded in (either by Limtech or some plugin)

The first time docker engine starts up (or you've blown away the local-kv.db file) it picks a /16 network for the default docker0 network it starts from 172.17.0.0/16 and keeps going to 172.18.0.0/16 until it gives up The criteria for picking is the subnet is not used by the local machine, which is odd - so probably your USB ethernet adapter dropped off or wasn't connected when the docker engine last started up You're screen shots indicate the a bad config: * br2 is 172.17.0.0/24 (which is a subset of 172.17.0.0/16 * you have 3 default gateways (which will invariably confuse the OS as to which interface to use to talk to the world) I suggest you try renumbering br2 to some other sensible IP range 172.20.0.0/24 or the 192.168.x.0/24 if its a possibility and make sure the default routes are really what you want (most of the time it isn't), and it can be resolved by either specifying no gateway on the other interfaces. Also, as a possible security measure, it is not necessary to have an IP on the other interfaces (save for eth0/br0). Docker can still function as in my setup Unraid is only accessible via br0, but I can run docker containers and VMs on all my subnets (VLANs)

It'll be gone upon reboot it has no imapct whatsoever as far as I can tell. and if you want to remove it the correct command would be rmdir /usr/local/emhttp/-

@dlandon Minor quibble: You have this line in the plg file mkdir - /tmp/&name;/scripts it creating a '-' directory in /usr/local/emhttp

I recommend sticking all your containers that are grouped together in their own VLAN, and have your router restrict access to the VLAN This is probably the easiest way to achieve what you want since macvlan networking is like running a virtual switch on the br0.10 interface so everybody on VLAN10 would be able to see the traffic

It is... this is a snippet of my nginx reverse proxy running on VLAN3 with its own IP. Unraid cannot be accessed from VLAN3, only nginx and any related containers on that same interface. It's up to my router to restrict access to/from other VLANs

Hmm... containers in bridge networks are by default accessible by all the assigned IP of all the interfaces of the host. This is the default docker behavior and Unraid did not support the advanced mode here. However, think about it a bit. If you assign an ip on VLAN10 to Unraid, the containers can now be accessed on this IP in VLAN 10, but Unraid services become accessible as well. If there is no IP as you have it now, all containers on bridge networks, will only be accessible via the VLAN1 ip address So the best answer for a container to be accessible only from VLAN10, you would need to do custom docker networks and assign the desired IP (or dynamically via Docker) to the container. I think you already have this setup. Is there any reason you must run with a bridge network rather than a macvlan?

Odd. so if you do not have an IP address assigned to eth0.10, Unraid can still be reached via that VLAN? How exactly? are you just not confusing accessing it over your router? client (VLAN 10) -> router (VLAN 10) -> router (VLAN1) -> unraid(VLAN1/br0)

Hmmm. you'll need to validate that the LSI card you have is actually working as you just acquired it to replace the Highpoint 2722.Maybe test the LSI on another machine if you have any with the shelf connected.

During boot up, the LSI should be prompting to press Ctrl-A to enter the card setup utility, does this not work on your QNAP?

You're using the 8e (external), How is it connected to your HDDs? Are you using an Shelf/JBOD enclosure? SFF-8088->SFF-8088 is the usual here or are you feeding the cables back in SFF-8088->SATA? make sure you are using forward breakout cables as these are one directional and you can't use the other one (backward breakout) which is meant for controller/Motherboard SATA -> SAS enclosure (SFF-8088)

You can check if the LSI card does see HDD during POST by accessing the card's utility (Ctrl-A during bootup) Sometimes the settings on the card might have some of the ports disabled

I am not sure about writes, but while it is not connected, it will definitely be writing out the connect to an account message to the docker log for the container.

This is just sample code, but it can go into your script at line 2 (first possible code line) what the 1st line does is check if there exists a file /var/lock/script.lock (note the typo) and if it does, it prints "Still running" for the user reference and exits the script (lines 2 and 3) If the script still keeps running beyond the check (ie the file doesn't exist) it will then create the file and the script can do whatever you want. Then at the end of the script, the command I showed will forcibly delete any existing /var/lock/script.lock. All in all this means that when the script starts up, it checks if the lock file exists and will abort if it exists. this means a previously running script is still running (or crashed/aborted) and the script will no longer run until the lock file has been deleted. When the script does run, the last thing it will do is delete the lock file, thus allowing the script to run again.