PTRFRLL

Deleted and rebooted, still same issue. Looks like part of the problem is eth0/eth1 are assigned to the Ethernet ports on my motherboard, which are not connected. Is there a way to disable those and only use PCIe card?

Strange thing is, they both show as Up and that they are a member of the bond, here's eth1 for example

Understood but the links don't even show as connected whereas the 2nd, backup NIC does. Same as in mode 4, only 2 of the 4 NICs showed connected.

I believe I've done that:

I have an Intel Pro/1000 Quad Port PCI adapter in my server. All 4 ports are connected to my managed switch via Ethernet. unRAID does not seem to be utilizing all 4 ports, just two. When the server boots I see link activity on all 4, so I believe the switch, cabling and adapter are all working just fine. unRAID recognizes all 4 ports but states that 2 of the 4 are down and never uses them. Currently my network bonding is in mode 1 (active/backup) but even if I switch to link aggregation (mode 4) it still only uses 2 links. Attached is my syslog. Any ideas? syslog.txt

Pulseway is a great tool that allows you to remotely monitor servers from iOS, Android, and the web. I mainly use it on iOS for the notifications about loss of network, high CPU usage or my server being shutdown. It was one of the few things I missed when I switched my server to unRAID. Luckily, I figured out how to get it installed and working. Here's the steps I took: 1. Download the Pulseway Agent for Slackware from Pulseway's website 2. Copy the pulseway_x64.txz to /boot/extra (this is also the flash smb share so flash/extra) 3. Create a new folder,pulseway, in the /boot directory 4. Reboot unRAID 5. SSH into server and copy config.xml.sample to config.xml: cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml 6. Edit the config.xml file you just copied, you'll need to add your Pulseway username/password and setup any notifications you want to receive (change the Enabled flag from False to True). I enabled Network interface monitoring (change interface name to br0) as well as WhenOffline, HighCpuUsage and MemoryLow notifications. 7. Start Pulseway service: /etc/rc.d/rc.pulseway start 8. Copy the id file generated by Pulseway to the /boot/pulseway directory (if you don't do this, the server will show up as a new machine in Pulseway every time unRAID boots): cp /var/pulseway/pulseway.id /boot/pulseway/pulseway.id 9. Copy your config file to /boot/pulseway cp /etc/pulseway/config.xml /boot/pulseway/config.xml 10. Add the following lines to /boot/config/go cp /boot/pulseway/config.xml /etc/pulseway/config.xml cp /boot/pulseway/pulseway.id /var/pulseway/pulseway.id /etc/rc.d/rc.pulseway start 11. Reboot unRAID and make sure everything works! Explanation: unRAID's OS is stored in RAM so any changes you make do not persist after a reboot/shutdown. That's why we need to move everything to the /boot drive (the flash drive unRAID boots from). On startup, we're installing Pulseway, copying the config and id files to their respective locations and then starting the service. Troubleshooting: If the Pulseway service fails to start, you can look in the syslog for clues as to why: cat /var/log/syslog | grep pulseway Typically, the problem is a misconfigured config.xml file Changelog 1/19/2021: Removed unneeded symlink commands