dnoyeb

Just wanted to check in and see if there were plans to update the unifi wifi and unifi video dockers to the latest versions?

i tried and tried to get it working without swapping virtio to sata and e1000 while using the 7 beta, no dice. So I simply did it the way he shows it in his post instead; worked like a champ and no audio dropouts... I can finally stop using my stand alone Openelec box; happy dance.

johnodon, thanks for the updated instructions (yea it's been a few months since i checked in)... i used these to install the openelec 7 latest beta and I didn't have a single issue while playing back full dts-hd audio... unreal... finally get to use my unraid box to it's fullest. Thanks!

i'm not sure this is still working... I swear it was working fine back on 6.1.1 but on 6.1.4 and now 6.1.6, on an app like Sabnzbd which I have limited to "--cpuset-cpus=0,1" I'll see it spiking all 4 cores on my i7 (as well as the hyperthreaded cores) and I'll even have issues where in sab it'll show loads upwards of 20 and it'll impact another docker that is assigned 2-5 to the point the other docker loses connections with the cameras (camera server) Is there some better way to tell if it really is still working like it should?

i wonder if going this route vs the openelec route could fix my issue with sound stuttering every once and a while on DTS MA / TrueHD feeds... know what i'm testing this weekend.

sadly I don't think this made it in the 6.1.4 release looks like i'll be building from scratch again I guess.

I have this same issue. Only happening on TrueHD and DTS-HD. Would love this fixed. Well at least i'm not alone! whew! makes me feel better... Maybe the 6.0 release has some new drivers or something in it, cannot wait to try it out. Probably wait for the unraid official instead of installing it from scratch this time around though

Just curious, to any of you guys running nvidia hardware I have a question. Have you tried watching any TrueHD or DTS HD Master audio 7.1 movies? I find that after I put in the "options snd-hda-intel enable_msi=1" in the config file; I can watch all my movies flawlessly that are just normal old DTS or DD 5.1... However anytime I watch a FULL movie in either TrueHD or DTS HD Master audio that about every 15-20 minutes the audio will cut out for about 1-2 seconds then come right back. Anyways, it only happens on that specific setup... anyone else have any experience with it? I've gone as far as building a custom openelec vm and it has the same issue; so not just the one that is built into unRaids... I do have my Vid card in a slower PCIex lane as I only had one 16x lane, but before I go building an all new unraid box; I figured i'd see if that'll be worth it... Not CPU related, cpu is sitting on its rear...

so, just got done watching a full movie on the vm... 3 or 4 times throughout the movie the audio would go completely out while the video kept going; then it would all sync up and keep going. this is after adding the mentioned setting to the config file... any other ideas?

gotcha... Total side note... In your guide you have /ext setup to hit a drive you have mounted via unassigned devices... I am trying to do the same thing but it's not showing up (I just reinstalled both dockers so it's back down on 4.3 for now) Does the external drive need to be formatted anything in particular? I think mine is NTFS from windows usage...

That’s because the CrashPlan Docker has auto updated itself to 4.4.1 and the CrashPlan Docker Desktop doesn’t. ok... so.... is there a fix?

I just wish I knew why the docker desktop won't work anymore... just sits at "upgrading..." and shows version 4.3.0. I had this working fine until a recent reboot... Thu Oct 1 14:49:16 CDT 2015 : Restarting CrashPlan Backup Engine Thu Oct 1 14:49:16 CDT 2015 : Starting using /etc/init.d/crashplan... upgrade.sh: line 30: /etc/init.d/crashplan: No such file or directory Thu Oct 1 14:49:16 CDT 2015 : New CrashPlan Backup Engine: root 45 43 36 14:49 ? 00:00:05 /usr/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx1024m -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false -classpath /usr/local/crashplan/lib/com.backup42.desktop.jar:/usr/local/crashplan/lang com.backup42.service.CPService Thu Oct 1 14:49:16 CDT 2015 : Exiting upgrade script That's what shows up in the log folder in the config folder.... looks like it's trying to upgrade and cannot...

any headway on getting this working again? Had it working fine until I rebooted my docker today and then the desktop part sat at "upgrading" forever... the screen went away and now when I try to launch it says it cannot connect to the engine (same stuff discussed on the previous two pages).

watched my first movie just now... had a good bit of jitter from time to time, would happen about every 20 minutes or so. Video playback was fine but audio would freak out. Hopefully it's a setting I can change in the config files somewhere... Update: Added options snd-hda-intel enable_msi=1 to my sound.conf file in the config folder of the VM I built and it seems to have fixed the jitters on trueHD so i'm hopeful it fixed the random issues mentioned in the paragraph above... will need to watch a movie tomorrow to confirm.

So I found some example xml's from johnodon in his PXE boot thread and managed to get Openelec beta 5 installed through the Ubuntu live boot cd mode... Strangely enough, passthrough audio is working fine for me with the full install vs using the beta 3 from Limetech where it would not work and menu sounds caused clicking noises galore (yes I tried the fixes mentioned in this thread, no help). Not sure if there is just some stuff in the full version that's not in the forked version. Anyways, i'm going to watch some stuff and see how it works out... If anyone else out there is having issues, I recommend checking out johnodon's pxe thread and look at his xml... I found that every time i edited the VM in the webgui I would have to re-edit the xml and change out ALL the lines of code for the disk controller (from <disk> to </disk> and change the nic from the virtio to e1000.

That was it, I was putting it on the repository field as it shows on the first post... guess the location changed at some point where it needed to be. Moved it to extra parameters and the webgui is back, thanks!

http://[iP]:[PORT:8080]/ .. tried it on the Sabnzb, plex, unifi-video ones... all of them do the same thing. Side note, soon as I remove the cpu flag, it comes right back... so weird I went ahead and put something besides the default in there and still don't see an option for webui.. https://192.168.2.51:9080 is what I put in for Sab ..

Using 6.1.2, applying --cpuset-cpus=4,5 to one of my dockers and while it looks like yes, it is working... There is a side effect. I cannot hit the view webgui anymore from the docker page. That option is simply gone now... Can anyone confirm this / know what it is doing? Here's an example: --cpuset-cpus=4,5 pducharme/unifi-video-controller however it happens on any container I put a --cpuset-cpus= on.

Right on... I just see something where people can get a little more granular being extremely helpful in forcing a balancing job on the drives when adding new ones... for example, select a sub folder then display all the folders with the ability to checkbox them or something... That way one could select a 60 movies of 120 and move them to a new drive and balance stuff out... anyways, just an idea, love the app and using it right now to level stuff out best I can

one thing that would be really slick if it could do: work with wildcards... For example, pull all files from /Movies/T* so it would grab all folders that began with T... Just trying to level out my drives a little and find that the Movies folder has 2tb of files in it, don't really want to move all of them off; just want to move like 1tb of them.

Ok, so I stopped all the dockers and then restarted the docker service /etc/rc.d/rc.docker restart and now the sizes are showing up correctly. So at least I didn't have to restart the whole server / array etc.. thanks for your help.

Heh, so guess it was case sensitive, had to capitalize the BALANCE part of the word and it worked. root@unRAID:/# docker exec -it unBALANCE bash root@7329b09743c1:/# df --block-size=1 /mnt/disk* Filesystem 1B-blocks Used Available Use% Mounted on /dev/md1 2500419588096 2425063636992 75355951104 97% /mnt/disk1 /dev/md2 2000337846272 1874974928896 125362917376 94% /mnt/disk2 /dev/md3 2000337846272 1687861276672 312476569600 85% /mnt/disk3 /dev/md4 2500419588096 2031731822592 468687765504 82% /mnt/disk4 rootfs 16776654848 370003968 16406650880 3% /mnt rootfs 16776654848 370003968 16406650880 3% /mnt rootfs 16776654848 370003968 16406650880 3% /mnt root@7329b09743c1:/#

Am I doing something wrong here? root@unRAID:/# docker exec -it unbalance bash Error response from daemon: no such id: unbalance

Sure thing, here ya go: (thanks in advance) root@unRAID:/mnt/cache/appdata/unbalance# df --block-size=1 /mnt/disk* Filesystem 1B-blocks Used Available Use% Mounted on /dev/md1 2500419588096 2425063636992 75355951104 97% /mnt/disk1 /dev/md2 2000337846272 1874974928896 125362917376 94% /mnt/disk2 /dev/md3 2000337846272 1687861276672 312476569600 85% /mnt/disk3 /dev/md4 2500419588096 2031731822592 468687765504 82% /mnt/disk4 /dev/md5 2999127797760 18181910528 2980945887232 1% /mnt/disk5 /dev/md6 2999127797760 33751040 2999094046720 1% /mnt/disk6 - 16776654848 369299456 16407355392 3% / root@unRAID:/mnt/cache/appdata/unbalance#

I've restarted the container and even completely removed it. Latest version of unbalance and version 6.1.2 of unraid. This shows up in the log: I: 2015/09/18 10:33:07 unraid.go:224: Unraid Box Condition: &{NumDisks:7 NumProtected:7 Synced:2015-09-13 11:46:18 -0500 CDT SyncErrs:0 Resync:0 ResyncPrcnt:0 ResyncPos:0 State:STARTED Size:9001514868736 Free:981883203584 NewFree:981883203584} I: 2015/09/18 10:33:07 unraid.go:225: Unraid Box SourceDiskName: I: 2015/09/18 10:33:07 unraid.go:226: Unraid Box BytesToMove: 0 I: 2015/09/18 10:33:07 unraid.go:237: Id(1); Name(md1); Path(/mnt/disk1); Device(sde), Free(70.2G); NewFree(70.2G); Size(2.3T); Serial(WDC_WD25EZRX-00AZ6B0_WD-WCC070048629); Status(DISK_OK); Bin(<nil>) I: 2015/09/18 10:33:07 unraid.go:237: Id(2); Name(md2); Path(/mnt/disk2); Device(sdd), Free(116.8G); NewFree(116.8G); Size(1.8T); Serial(WDC_WD20EARS-00MVWB0_WD-WMAZA0897315); Status(DISK_OK); Bin(<nil>) I: 2015/09/18 10:33:07 unraid.go:237: Id(3); Name(md3); Path(/mnt/disk3); Device(sdc), Free(291G); NewFree(291G); Size(1.8T); Serial(WDC_WD20EARX-00PASB0_WD-WMAZA5099252); Status(DISK_OK); Bin(<nil>) I: 2015/09/18 10:33:07 unraid.go:237: Id(4); Name(md4); Path(/mnt/disk4); Device(sdb), Free(436.5G); NewFree(436.5G); Size(2.3T); Serial(WDC_WD25EZRX-00AZ6B0_WD-WCC070063815); Status(DISK_OK); Bin(<nil>) I: 2015/09/18 10:33:07 unraid.go:237: Id(5); Name(md5); Path(/mnt/disk5); Device(sdf), Free(0); NewFree(0); Size(0); Serial(WDC_WD30EFRX-68AX9N0_WD-WCC1T0371541); Status(DISK_OK); Bin(<nil>) I: 2015/09/18 10:33:07 unraid.go:237: Id(6); Name(md6); Path(/mnt/disk6); Device(sdh), Free(0); NewFree(0); Size(0); Serial(WDC_WD30EFRX-68AX9N0_WD-WCC1T0376504); Status(DISK_OK); Bin(<nil>)