ken-ji

Please note that there is distinction between a direct write to array disks vs cache disks. When a write to array disk occurs, Unraid needs to read the parity disk + target array disk, then using that compute the new parity value, and then write to the target array disk and the parity disk. If you try to read from any drive during this time, you'll have disk I/O contention at a 4:1 ratio. It won't be a problem just yet, but you will encounter stuttering and pauses which depends on your hardware and the speed the download is ocurring. As for the CPU, your i3 is more than enough to do the parity computation. I only use a Pentium G4620. Upgrading CPU won't make a difference. You didn't provide your complete specs or the diagnostics file, so you'll only get general tips If you have a spare HDD (or SSD which is even better), you can add it and assign it as a cache drive. This speeds up your download as it will only need to write to cache drive like in any normal system. But files on the cache will only get moved to array on a schedule You also didn't consider the state of your network, is Unraid connected via gigabit?

I think all of the user replaceable APC UPS have a software interface where you update the battery install date. I never had one plugged into a windows machine, so I'm not sure about that, but I was able to update one of mine before using the apctest (?) command which is part of apcupsd software package. Higher end ones, just require you to telnet into the management IP and a menu is there for resetting the date.

Hmm... Preclear is just the really cautious making sure the drives are not part of the infant mortality batch. Have you ever replaced a disk in a raid 5 array and watch the rebuild scream with errors as the destination disk fails almost immediately? Not a pretty sight, specially when the stakeholders bearing down over your shoulder. Even our vendor decided to give our expensive fc raid 5 array multiple complete write overwrite shakedowns over a week before they declared it ready for usage. Unraid is an excellent balance between price and function versus ZFS which is also excellent, but it's better for people with a lot more money. Imagine that I can't add a single disk to my ZFS pool to resize it... Most raid 5 will let you and so will unraid.

Are you downloading to the cache drive or the array drive? Because downloading to the array can result in I/O starvation - parity is being read and written to, array disk is being written to, (maybe a different) array disk being read from (movie stream) - and if happens, this can cause your disk access to be very slow and make CPU usage look a lot higher - the dashboard silently includes I/O wait time as CPU usage. Some users, like me, download to a cache drive so unRAID will handle disk I/O better.

Hmm... 2GB of RAM... do you manually update versions? the Update OS command fails on my brothers machine also with 2GB RAM as there is not enough /tmp space to hold both the downloaded zip file and the unpacked files.

That's mighty weird... but I've only used the RouterOS devices so far (and 3 models of them) with great success... Just to be clear, your PC/laptop is on the same subnet as the switch? ie IP 192.168.88.x/24? Other than this, I have no idea what's wrong and unfortunately connecting to the serial console might require tapping the pins or having a SOL config available - if a rollover cable is not enough...

Try unplugging all the cables except your PC/Laptop. Restart the switch. You should be able to access the switch then on the default IP. If not, try restarting the switch while initially holding the reset button/pin down for a few seconds...

This is what I do.

Quick disclaimer - not running as a VM Its 100% same for baremetal installs, if the USB fails, you create a new USB, apply the backup zip file (or however you backup the USB config) and boot. Apply for registration maigration to the new USB and you're done. So other than fun things to watch out for, like plop suddenly failing to boot the USB; or incompatibilities with the kernel and virtualization (which should not happen, but hey its software); or automated upgrading not working right. Also, unless you are on the pro license, the DVD will count against the total number of attached storage drives you have when the array starts up.

Its quite possible - buit you have to understand what the limitations are depending on what your network has or supports. If you do not have VLANs (or a second physical LAN), you will end up with a mix of containers on eth0/br0 running in bridge or host mode, which means they share unRAID IP; and another group of containers on eth1/br1 running is custom network, which means they have their own IP, and can talk to unRAID (If unRAID does not have an 2nd IP assigned to this NIC) Since you mentioned having 2 NIC and 2 IPs... but did not elaborate, I also did not elaborate too much on the possible config, and assumed you did not have VLAN/2nd LAN support.

Hmm... the separation you seem to want might require VLAN / or 2nd physical LAN support on your network. Think of it this way. Docker supports any combination of the following: one host network - container network is the host itself a bridged network - an internal bridge is made which NATs the outgoing connections and does port forwardings on the host ports to the container ports a macvlan network - an internal bridge is made, which is a subinterface. This allows packets to go in and out of the parent NIC so the containers seem like they are members of the NIC network and have their own IP apart from the host, but a built-in security feature prevents packets from the containers to loopback to the parent NIC Docker networks cannot have the same subnet defined so if your two NICs are on the same LAN (even with different IPs) containers on the macvlan network can only be bound to one NIC (usually the 2nd). The other containers will need to be running in bridged (or host) mode - which make them available on the other NIC (the primary)

did you run the gateway container with the privileged option? and check your gateway on the client containers... are they pointing to .2 vs .1?

Its a convention I think. bond0 must contain eth0 So if you want to exclude eth0. Turn off bonding for eth0 "Enable bonding: No". then enable bonding for any other interface - which will create bondX - X being the lowest number member of the bond You probably need to be ready to boot unRAID in local GUI mode, so you can easily mess with the network interfaces. If you can't, you can power down. and modify the config/network-rules.cfg file manually to force unraid which NIC is eth0 and so on.

Yes. /mnt/user is a special mount with very weak permissions by default... I wonder if the security here can be tightened up ... but then only plugins would have access at this level typically... root@MediaStore:~# ls -ald /mnt/user drwxrwxrwx 1 nobody users 168 Dec 14 21:28 /mnt/user/

Hmm. you'll need to setup like this (Mine is like this): * br0 (eth0) - unRAID (VLAN 1) - one and only VM on this port as well. * br1 (eth1) - Dockers (VLAN 1 - custom network) + (br1.3) Dockers (VLAN 2) The only real benefit you'll get be adding the 4port NIC is to be able to serve a lot of clients better as LACP only improves bandwidth when talking to a lot of clients, and does not allow a single client to go faster than a single cable (1Gbps), so if you many plex clients and your server can handle all the streams easily, you can add the 4 port and make a LACP bridge out of that and migrate the docker network to it. This means you'll be using plex with its own IP on the custom network (br0) and is known to generate call traces for no reason - depending on the hardware.