thegizzard

Hey guys for some reason zmninja isnt working properly after the update. It logs in but montage images are empty and the events do not play. I updated the ffmpeg option and turned off cambozola. Did I miss anything else?

Does anyone have problems with MODECT recording a few seconds of gray screen instead of actual motion? It looks almost like signal loss but happens very frequently. I am getting a lot of junk on my disk. I've searched the zone minder docs and forums and can't find a reference to this. I am using amcrest cams. Sent from my SM-N950U using Tapatalk

BOOM. That was it. Below is now the output from the terminal. root@GrimLock:~# docker exec -it Zoneminder bash root@8a037a6782e7:/# crontab -l # Daytime camera operation 0 8 * * * /usr/bin/zmpkg.pl Daytime # Nighttime camera operation 0 20 * * * /usr/bin/zmpkg.pl Nighttime root@8a037a6782e7:/# Awesome as always dlandon

Both commands work manually from the terminal. Below is from the log Aug 5 07:32:08 8a037a6782e7 zmpkg[3118]: INF [Command: Nightime] Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Command: Nighttime] Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Sanity checking States table...] Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Command: state] Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Updating DB: Nighttime] Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Marking Nighttime as Enabled] Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Command: Daytime] Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Sanity checking States table...] Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Command: state] Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Updating DB: Daytime] Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Marking Daytime as Enabled] But when I check for cron I get this result root@8a037a6782e7:/# crontab -l no crontab for root This is the contents of my 'cron' file in appdata/Zoneminnder/ # Daytime camera operation 0 8 * * * /usr/bin/zmpkg.pl Daytime # Nightime camera operation 0 20 * * * /usr/bin/zmpkg.pl Nighttime Could the problem be that I created that file with notepad on windows? just a guess.

Understood. I have 2 camera states. One used for Daytime and one for Nighttime. They are called Daytime and Nightime. I can change these manually in Zoneminder or zmNinja. What I cannot do is automate the changing of these states. The first post shows how to do it using the commands i quoted above, but it does not seem to work for me. Any suggestions? Sent from my SM-N950U using Tapatalk

It looks like I do have cron, but no luck scheduling state changes from Daytime to Nighttime. Has anyone else gotten this to work with this docker? Sent from my SM-N950U using Tapatalk

Does this work? I have a single file called cron It contains: # Daytime camera operation 0 8 * * * /usr/bin/zmpkg.pl Daytime # Nightime camera operation 0 20 * * * /usr/bin/zmpkg.pl Nighttime I restarted the zoneminder docker When i run the commands ... docker exec -it Zoneminder bash crontab -l It returns no crontab for root i dont think these commands were added to crontab and zoneminder has not switched modes. Any recommendations? I am not even sure I have cron on my system. I have never used it for anything else.

Thanks dlandon. Your efforts are much appreciated. Donation Sent!

I also want to echo thanks for your work on this container. I am quite happy with my camera setup right now. Sent from my SM-N950U using Tapatalk

Thanks. I'm chasing it there too. It works up to 3072*2044 without error. Sent from my SM-N950U using Tapatalk

4K doesnt work. Everything works fine until I set my new 4K camera (monitor 7) to 4K (3840x2160). It works fine at 2560x1440, but when I set it to 4K, errors start flying. See attached log. Any ideas on why? zm-log.html

Are there any good replacements for Crashplan?

Yep. Some files have that. Not ur fault. Sent from my SM-N920V using Tapatalk

Wow. Wow I used Nzbget from around 2008-2013 But this was before I used unraid. It worked just fine. When I moved onto unraid I pretty much automatically started using SABNZBD. It was much glossier. It worked well and no complaints. Now I have a huge library and sabnzbd is not so great. Lots of repair fails and repairs are slow as molasses. Enter CHBMBs suggestion to try NZBGET. Not as glossy as SABNZBD. But wow! It's fast! It repairs! It repairs fast!! I recognizes duplicates! This is exactly what I needed. Thanks guys. Donation on the way. Sent from my SM-N920V using Tapatalk

Bump.. looking for the same.

Is anyone aware of an unraid docker that supports multicore par2? I assume others need this too.

Good to know. Seems like a lot of discussion on this point and no conclusions. Is there a SABNZBD docker that supports multiform par2? Sent from my SM-N920V using Tapatalk

Multicore PAR2? Sorry folks I see this is being discussed by I am not catching the solution. I started clean and I had a checked by greyed out enable multicore par2 box. I tried it that way but only saw one par2 job with TOP. So I added Extra PAR2 Parameters = -t+ this did not work at all. verify jobs just bailed. I tried to remove the parameters and the multicore par2 check is gone. Does anyone know how to make this work?

Correct, you nailed it all. I've been using this flash drive for a while, but I have just refreshed the entire system, so I will probably replace the flash drive now soon. It's had a few fs errors over the years. I am at peace with where I am now. I did exactly what you said with the very last drive. I let unraid format the array without adding parity. All is well. If I didn't have Crashplan, I would literally be crying. Fortunately, I have it and I am not worried about the files I can easily replace that were not on Crashplan. Most importantly, I dont want anyone else to lose data this way. I really love UNRAID. And I am looking forward to a better and faster system then I ever had before.

FWIW, I think I know what happened. Because my most critical data is saved on CrashPlan, I decided to just start over. All went well until I tried to add one more drive to the array. This was an RFS drive that I copied over to Disk 1 and then formatted to XFS using UNASSIGNED DEVICES. Unraid DID NOT accept this XFS drive, and said it needed to be reformatted. This is exactly how I lost 28TB of DATA. I used UNASSIGNED DEVICES to format XFS, then I copied data to these drives. UNRAID did not recognize their XFS, and required a FORMAT. I tried overnight to recover XFS before I quit and started over. I am now out of drives, but I am sure this situation is repeatable. 1. Format a drive XFS with UNASSIGNED DEVICES 2. Try to add it to a new array configuration You will not be able to do so without reformatting the drive in the array. Which is totally fine, unless you added data to the drive before trying to add it to the array like I did. I hope this helps someone avoid the loss of data that I just experienced. Attached diagnostics. grimlock-diagnostics-20160918-1519.zip

adding diagnostics. megatron-diagnostics-20160917-1433.zip

I just tried it and I got the same result. I set each to XFS and I checked each one. See attached.

Apologies if this is a double post, but I lost two drives without parity and decided to rebuild with XFS. When I had all my data on XFS drives I tried to start the array and it asked me to reformat my XFS drives (and lose their data)... I said NO, but now each of my drives is unmountable with no XFS or any FS. Is there a way for me to restore XFS and more importantly all of my data? See attached. All of the blank FS disks are XFS disks filled with data.

I copy files daily to UNRAID using SyncBackFree... Crashplan backs up files from UNRAID.

Thanks. Updated to v3.6.4. No probs.