brettm357

replaced links with exact same links now works - strange

Updated to 5.9.4 see notes As of release branch 5.7.x we've made some important changes to the Wireless Uplink feature (feature details HERE). We removed the "Enable automatic uplink failover" from wireless uplinks as it is no longer needed. We added the ability to opt an AP in or out of wireless uplinking to another AP. This is done by checking the "Allow meshing to another access point" option found under device properties>Config>Wireless Uplink. This option should be disabled on wired APs, but is required to be enabled on wireless APs. If you disable this option on a downlink/wireless AP, then your AP will be disconnected from the network and require further action (including physical access). If upgrading from 5.6>5.7 then this already be disabled on wired APs, but if upgrading from an earlier 5.7. release then this may be enabled on wired APs. Again, this option should be enabled on downlink/wireless UAPs only. It should not be enabled on wired UAPs. We added the ability to set uplink priorties. This allows you to define the preferred uplinks for a downlink/wireless AP. When using IPS signature suppression, make sure to click Apply Changes after you've completed your customizations. If you had installed a custom SSL certificate you may need to re-add the cert. Please note that the name and alias should be `unifi` not`ubnt`. Known Issues: Some statistics on the dashboard are still under development. Please share any and all feedback!

Will update tonight

Will update today

Updated to 5.8.8 see note: *****SPECIAL UPDATE NOTE***** Upgrading from 5.8.6 to 5.8.8 is blocked due to the database ending up in a partially "broken" state post upgrade to 5.8.6. Therefore you can only purge your current lab install, install 5.8.3, restore a backup (from 5.8.3), then upgrade to 5.8.8.

Was unable to get Disc 6 back online so i replaced it Still getting read errors on Parity 2 Diagnostics attached main-nas-diagnostics-20180320-1116.zip

Help Please - This is driving me crazy Have read and reread the posts I have a IBM M1015 card with sas9220 chipset I am getting the "PAL" error trying to flash to it mode Have created the usb boot with rufus using fat32 as freedos - system card is plugged into is a 32bit windows 10

Both drives are plugged into motherboard but i am running a Supermicro SASLP-MV8 card for my remaining drives is it possible that can cause this

Update - Disc 6 had a Red Cross. Restarted Unraid now disc 6 is listed as not installed - Parity 2 read errors reset back to zero

Help please, Have just completed a parity check and now have read errors on Parity 2 and Disc 6. Diagnostic Attached main-nas-diagnostics-20180315-0300.zip

Ok - yes just using onboard graphics Didnt seem to have this error on an Ubuntu VM ??

Have this error everytime my Linux Mint VM starts - Only happens on Mint

Back down to 5.7.18 then upgrade to latest - System seems to break when upgrading from 5.7.19 Will do a fresh install on my system to check latest version

Update complete for 5.8.3

Have installed an Ubuntu VM and setup a VPN as per Gridrunner's video - Everything connects and works except when i run a DNS leak test DNS servers from my VPN show up and also Openvpn servers If my tunnel is up shouldnt only DNS servers from my VPN provider only show in the test ??