veeco

Upgraded from 9.2-unraid tag to 9.3-unraid no issues so far, all UniFi devices connected. The updated Client Devices page is nice.

I figured it out, TLDR: reset BIOS settings if boot is hanging I saved my old settings to a User Profile and created a new profile with default settings. Boot to 7.1.0 worked. I went through and enabled every setting I changed, and boot still worked. Loading the old profile breaks boot. When I switch profiles, the "save changes" diff shows no settings actually changing. It doesn't make much sense but maybe there is some hidden or corrupt setting.

It hangs, no command prompt, just this (see image)

Upgraded 7.0.1 -> 7.1.0 and I could not boot. I tried all boot options and moving the USB to different ports. I grabbed a different USB flash drive, installed a fresh copy of 7.1.0. Same thing, would not boot. I installed 7.0.1 on that same new USB and it booted just fine. I then followed these instructions to downgrade my main install to 7.0.1 and everything booted up fine. So at least on my hardware, 7.1.0 breaks boot. I can provide diagnostics if requested. Hardware: ASUSTeK COMPUTER INC. ROG STRIX B560-I GAMING WIFI , Version Rev 1.xx American Megatrends Inc., Version 2302 BIOS dated: Wed 13 Nov 2024 12:00 AM 11th Gen Intel® Core™ i5-11500 @ 2.70GHz

Upgraded with no issues. All hardware adopted automatically (Switch US-24, Switch USW-Lite-8-PoE, U6-Lite, U6-LR).

EDIT: I'll follow up on UI forums, looks like someone else spotted it as well: https://community.ui.com/releases/UniFi-Network-Application-8-0-24/43b24781-aea8-48dc-85b2-3fca42f758c9#comment/87c8b4cc-3b0e-4927-a271-fc61aedaff24 Looking in the container, I found the files at: `/usr/lib/unifi/webapps/ROOT/app-unifi/react/fonts/` I see that js i properly loading, for example: `https://192.168.3.152:8443/manage/react/js/5869.2f02b1d33b809f53b77e.js` But the path to the fonts is missing the `manage/react` prefix: `https://192.168.3.152:8443/fonts/UI_Sans_v8_Regular.eb36d6ff9c768a1639ca397b4dd84137.woff2` It looks like a Unifi problem with the wrong paths, unless there is some configuration option. You can see the inline style loading the wrong path:

Thanks for creating this image. I ported over with no problems. One thing I noticed in the browser console is that font files are failing to load. I'm not sure if this expected:

I'm also experiencing slow SMB browsing, mainly in Kodi when doing a library scan for updates. I noticed this after switching off SMBv1 and using SMBv3. I did a test and enabled an identical NFS share and the media scanning was drastically faster, maybe 20 seconds vs ~1-2 minutes. However I experienced weird audio popping issues on the NFS share and switched back to SMB. Going back to SMBv1 isn't an option since it's a dated and insecure protocol. I am able to watch movies, so transfer speed doesn't seem to be an issue. Some more info: There are 127 movies in individual folders, 18 tv shows in individual folders, so not a ton. Why is SMB so slow when NFS browsing / listing is near instant?