mgworek

my error above might have something to do with php? https://github.com/phanan/koel/issues/289

I got further with the manual sync but dies at 3% with "[symfony\Component\Debug\Exception\FatalThrowableError] Fatal error: Call to undefined function App\Models\exif_imagetype() " Well check my logs to see what is going on, likes like maybe a problem with artwork or something.

That worked. Thanks!

Any idea how to manually run the scan from the cli with your docker? Before when I build my test docker I was able to run this to manually scan. php artisan koel:sync now it says "Could not open input file: Artisan" i found that command on the keel Wiki Thanks

You can manually download older firmware, probably would want 4.15 and install it. Thats if youre talking about the gateway. You can do the same for the AP's but don't know the right version number

Thanks for updating it to the latest version!

Version UniFi 5.2.7 is officially out.

Thanks and sorry for not know that already. I just trying every search combo i could think of that never came up. but now if i do sas spin down it comes up. i must have been searching for everything but the obvious. Walking away with head down....

i am now getting this in logs non stop Sep 14 14:53:39 Tower kernel: mdcmd (65903): spindown 7 Sep 14 14:53:39 Tower kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5 Sep 14 14:53:39 Tower emhttp: err: mdcmd: write: Input/output error I disabled spin down on the drive for now. if its supposed to be spun up those errors don't come up but if its set to spin down, they keep coming up multiple times per second

good point. I totally forgot that it was a SAS disk. I haven't used one before in my system.

I thought the pre clears were good but I've noticed that the drive won't spin down. I tried to run a short test but it failed right away. Running 6.2.0-rc5 tower-smart-20160914-1410.zip tower-diagnostics-20160914-1417.zip

haven't had to preclear a drive in ages. It said it passed but got this. ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdk # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [14:58:14 @ 74 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [7:19:05 @ 151 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCES/usr/local/emhttp/plug ins/preclear.disk/script/preclear_disk.sh: line 782: echo: write error: No space left on device # /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 807: echo: write error: No space left on device # cat: write error: No space left on device # /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1357: echo: write error: No space left on device # /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1358: echo: write error: No space left on device # /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1367: /boot/preclear_reports/preclear_report_5000c500742a477b_2016.09. 10-22:33:12.txt: Invalid argument # /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1383: /tmp/.preclear/sdk/smart_out: No such file or directory ############################################################################################################################ Warning: file_put_contents(): Only 0 of 545 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/noti fy on line 191############################################################################################################## Warning: file_put_contents(): Only 0 of 187 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/noti fy on line 192 root@Tower:/usr/local/emhttp

once the current unraid rc is released, you won't have the updating problem but you could also put this in your go file. "echo "0 2 * * * docker exec Emby-Server update" | sudo tee -a /var/spool/cron/crontabs/root". Change the times to whatever you want but that updated the docker every night for me when I was running the Emby betas. Or you can just run 'docker exec Emby-Server update" from the cli and it will update it.

? I am on the latest public release 3.0.6070. It takes a couple of hours to get the docker to get updated but its up to date. If you are not on the latest beta/rc of unraid, manually run an update on the docker or delete it and reinstall it. It will keep your settings and will download the latest version.

Anyone know how to downgrade mono in the docker? I see I have 4.4.1 and now having issues playing videos. I know there have been reported problems with Emby and 4.4.1. I can connect to the docker and see my version but no idea how to downgrade. Thanks

So they are.... I know that ls.io is reorganizing their repositories right now, and I'm sure the apps will be back available shortly. Thanks for the info. I took the other unifi docker and put the ls.io info in and it worked. Thanks for the update!

All of the linuxserver.io dockers are gone for the community apps? Did I Miss something?

Settings -> Maintenance-> Backup-> Backup Data Retention Is this what you were looking for? That controls how much data is in the manual backup you create. This is a little different. Say your system is running nicely. Ubiquiti makes an update you didn't notice or didn't know about. You restart your unRaid box, and when it comes online the newest Unifi version is installed automatically, but that update breaks your setup or erases your settings (which has happened with at least one recent firmware release). That's not so easy to recover from, because you needed to backup before you even knew there was an update that was going to be installed. I'll just manually backup frequently, but it is a bit concerning. the new Beta 5.1.0 has auto backup so it won't be long.

I just finally got it to work myself. I had to blow away my docker image, cleaned out all unused and unifi templates. Created a new docker image, installed the unifi docker and worked on first try.

I never got 5.0.6 to work. I tried your instructions but didn't help me. My gateway from them came in and my 4.x install wouldn't see it so I had to install the server on my Mac in order to use it. I will keep trying this docker and the other unifi docker and hopefully one of them will work for me and the others who can't get this one to work.

Thanks!

Asking again if you could update the the latest official reason 5.0.6 when can please. It is no longer in beta. The other docker has already been updated but there are a bunch of us that are unable to run it. we get stuck at an error message. Someone people have found a work around but doesn't work with everyone. Hopefully when you update your docker it solves the problem. Thanks!

Having the same issue with the timezone issue with my emby server.

any chance you can explain how you deleted the file? Thanks

Getting the same error, but Unifi is working fine for me (after a restart). Restart didn't help me. Still have same error. I ordered their Gateway last week so I will be good once it gets here. I was just trying to to be up to date with my current setup before I export my config.