dl09r

All I did was go to my docker, toggled the Advanced View, and added to the Repository "pducharme/unifi-video-controller:testing". Saved it and it pulled the update, installed it, and rebooted the docker.

Perfect! Just updated and things are running smoothly. Man, seriously, I appreciate you doing this.

Interesting as I don't have those options enabled.

Okay, no worries then. This upcoming weekend, I'm going to play around and see if it's a php thing or something else.

Here's a question for you folks. So, I've got my unraid server access through NPM and it works great for remote access. One of the things I notice is when I "apply an update" or anything that requires a pop-up windows to be created, no text is shown... just a blank window with the window title header. For an example, using my internal network IP address to access my unraid server, I can to to the system log icon and click it and see line items in the log entry. If I was to do that using my external access (https://unraid.abcdefg.com), I get nothing but a blank window. Here's my config: # ------------------------------------------------------------ # unraid.abcdefg.com # ------------------------------------------------------------ server { set $forward_scheme http; set $server "10.10.10.200"; set $port 80; listen 8080; listen 4443 ssl http2; server_name unraid.abcdefg.com; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-3/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-3/privkey.pem; access_log /data/logs/proxy_host-2.log proxy; location / { # Force SSL include conf.d/include/force-ssl.conf; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } Any thoughts?

Yeah, sorry about that. My comment was in reference to beta releases for Unifi Video. Latest beta I'm tracking is this one: https://community.ui.com/releases/UniFi-Video-3-10-11-beta-4/45423f88-6a3f-40d8-925e-40b5b9b59446

Good day. Any possibility of trying the Beta Releases?

# ------------------------------------------------------------ # uvc.?????.com # ------------------------------------------------------------ server { set $forward_scheme https; set $server "?????"; set $port 7443; listen 8080; listen 4443 ssl http2; server_name uvc.?????.com; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-7/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-7/privkey.pem; access_log /data/logs/proxy_host-6.log proxy; location / { # Force SSL include conf.d/include/force-ssl.conf; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; } Here is my config file. - Scheme = https - Forward Hostname / IP = 192.168.160.200 - Forward Port = 7443 - Websockets Support = enabled - SSL Certificate = yes, LE certs - HTTP/2 Support = enabled With the information from my last post (above), I think this should hopefully paint the picture. Like I said before, I'm able to get to the site, login in, see all my cameras, but once you go to live view, I get the message, "Unable to load (camera name) live stream. Thanks in advance for your time and assistance. Let me know if you need more information.

Good evening Dev and All - I've been able to get NPM up and running with little to knowledge of nginx or reverse proxy. I do have one question wrt (with reference to) Unifi Video docker. I spent the last day and a half trying to figure out (reading and experimenting) the missing magical setting to make this work. And what I mean by working is, getting Live Stream to work. I've been able to get the main page working, to include LE ssl certificates. Slightly shocked how easy that was, but when you go to watch a video feed, the Live Stream doesn't work. Here are the settings that have either been populated or enabled. Nothing else has been selected or enabled. - Scheme = http - Forward Hostname / IP = 192.168.160.200 - Forward Port = 7080 - Websockets Support = enabled - SSL Certificate = yes, LE certs - HTTP/2 Support = enabled I've seen many nginx configs that say they work, but not familiar enough to adopt or adapt the settings into NPM. Would anyone happen to have any insight into how to get the Live Stream to work? Thanks in advance. Dev - Thank you for designing something for the somewhat inexperienced user(s).

Exactly! The story of my past four months. Further complicated by a lack of understanding as to why you would use this card to do what you want to do with it. Compounded by, "wait, what! You want to hook SSD drives to it as well, and it support and perform TRIM?" The IRC chat forums can be helpful, but in this case they were more amused by the situation I was presenting. Most concluded with, "there is no problem, just connect your SSDs to your motherboard SATA ports and all will be well." Hadn't thought about reformatting to ext4 for most of my SSDs. But for my cache (BTRFS) I don't think I will be so lucky. On a happier note, I was able to find genuine LSI 9300-8i (used) on eBay for $130. Unfortunately I'm still filling out my Urgent Operational Needs Statement to convey the urgency of this purchase to the home sergeant major.

Simply out of curiosity, I had concluded with the same end result late yesterday afternoon. As my setup was a undesirable hardware approach to verify/validate, I appreciate your similar results.

@johnnie.black I did submit a somewhat lengthy email to the SCSI team with reference to the situation. I'm not sure as to the official means of approach with them, but I hope to gain some insight from there perspective. On one hand, looking/comparing the MPT2SAS/MPT3SAS merge from the beginning, up to the point of kernel 4.20 release, it looks like several corrections have been made. Again, I'm no expert and haven't slept at a Holiday Inn for quite some time. Nevertheless, I look forward to any response I receive from that team. Your options aren't unreasonable by any means. SAS3 controllers are slowly coming down in price. If I was thinking about future capabilities and functions of unraid, an SSD only array would require a SAS3 controller, ensuring the necessary house cleaning actions could function appropriately. In my situation, I'm comfortable with waiting to see what 6.7 addresses WRT this TRIM situation. If it doesn't address or resolve the situaiton, I may progress to the SAS3 series controller. I don't like jumping to conclusions (can be costly), so I'll turn my patience dial up a few more ticks and wait and see...

Sir, greatly appreciate the update. I would suspect you are testing the non-released beta version? Would you be able to confirm what version/increment of kernel you are now on? Again @johnnie.black, thank you very much for the update.

The last time I checked, most of the SCSI changes were implemented in 4.19. I haven't done a full 4.19 vs 4.20 breakdown in the SCSI and FS areas/modules to see what additional changes were implemented. If 6.7 drops with 4.19, we "should" be good. If 6.7 comes with a Slackware re-baseline, even better, as there are several updated packages that would compliment the improvements. The other aspect I have been becoming familiar with is UNMAP. Similar to FSTRIM, it provides instructions to the PCI bus to perform certain actions. Again, learning as time permits. Nevertheless, it seems the SCSI community acknowledged the collapse of several modules and programming language/library optimization has effected several functionalities in the HBA world. I'm really hoping it all comes to bed at 4.19 or 4.20. Again, fingers crossed.

@slimshizn I've been patiently trying not to post anything ETA-like verbiage on here. But I'm pretty sure a good Unraid system re-baseline, with the newly released 4.20 linux kernel, should provide the improvements/fixes we'd expect (fingers crossed).

There seems to be a lot of SCSI changes in 4.19. Based on looking at the latest discussion in the Linux SCSI development, I believe there are several significant mpt3sas changes made: mpt3sas: Added new #define variable IOC_OPERATIONAL_WAIT_COUNT mpt3sas: Separate out mpt3sas_wait_for_ioc mpt3sas: Refactor mpt3sas_wait_for_ioc function mpt3sas: Call sas_remove_host before removing the target devices mpt3sas: Fix Sync cache command failure during driver unload mpt3sas: Don't modify EEDPTagMode field setting on SAS3.5 HBA devices mpt3sas: Fix driver modifying persistent data in Manufacturing page11 mpt3sas: Bump driver version to 27.100.00.00. > - Fix removed q->mq_ops non-NULL check in wbt_enable_default() > - Remove spurious return in ide-io.c:ide_timer_expiry() > - Dropped DM legacy path removal patch, now in mainline > - Dropped ib_srp patch, now in mainline > - Fixed a missing port unlock in IDE > - Add SCSI ufs to the BSG conversions > - Add patch to remove bsg-lib queue hook dependencies > - Fixed missing clear of IO contexts > - Added blk-mq backend for blk_lld_busy() PLUS, it sounds like there are some signification performance improvements (https://www.spinics.net/lists/linux-scsi/msg125041.html) in 4.19 that trigger some happy dancing... Concluding, I guess the last point that one could make is there are several utilities updated in the "rolling release" world that make be applicable to assisting in resolving the HBA situation. I wait in great anticipation for Unraid 6.7. It may be the "Honey Hole" (love me some of my hometown heroes, American Pickers) of an update that we all are looking for. Thank you @limetech for your insight and update.

Not to go overboard on exploring this situation, I'm working to gather all the same pieces in my current setup, with the exception of all the array drives, and just a few SSDs. Can't afford to screw up my main system. Furthermore, there seems to be several different things going on. One being, the migration of mpt2sas and mpt3sas. With those two converged, on the surface, nothing should have changed. One thing I came across was a linux tool called sg_unmap. It communicates vis SCSI rather ATA. I want to see if the issue is communication commands, but i'm unsure how to sideload packages on unraid. Lastly, the package in which the command/program fstrim resides, there is an update to that package 2.32 > 2.33 that mentions a few things about FITRIM ioctl failed. Does anyone know how to update this package (util-linux)? Package was released on the 19th of October (https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/) The journey continues...

Thanks for confirming that. I've spent the past 30 minutes or so digging through the mpt3sas kernel module code, comparing it to previous versions. Unfortunately I'm down a monitor due to my little sitting with me, watching Peppa Pig... oh the sacrifices...

I'm in the same boat. I've been playing with the idea of upgrading my HBA to a 9300-8i, but I'm not entirely sure it will resolve the trim issue. And before it is recommended again, I know that I can connect my SSDs to the motherboard to regain the trim capability, but with having my hard drives located in another chassis, I'd rather not. I haven't had a lot of time to dissect the drivers in this latest update, but I know one thing... Unraid is Linux.... and I know Linux.... (just had a weird flash back)

I've been looking and can't find anything specific. I know there is probably a "manual way" to do it, but not sure what that process looks like. For the masses... I can confirm that the "develop branch" has a fix (what ever the fix actually is) that makes my setup work without getting stuck at UNPACKING. Mileage may vary.

Sent you a message.

Was coming here to see if anyone else noticed that too. Did a lot of searching and it looks like there is a fix in the develop branch.