aptalca

Hi guys, I've been using the beta version of this plug-in for the last couple of weeks on beta 21 and noticed some issues. 1) A few of my drives had smart disabled (not sure why, I also posted this in the unraid beta thread) After manually turning smart on everything worked well. I think it would be great if this plug-in could check whether smart is disabled and enable it as necessary. 2. Preclear reports are not tagged with the date in the filename so the reports for the same drives get overwritten with multiple preclears. It would be nice to be able to see the preclear history on the drives. 3. This new (used) drive I added had smart turned on, all attributes and capabilities can be viewed in unraid, but when I run the preclear the script does not get or show any smart data. Is there any log I can provide? Here's the preclear log: http://pastebin.com/VEBg2mnV Thanks

If you mean kde themes, it *may* be possible but mostly very complicated and not worth it. If you try to emulate this guide: http://www.omgubuntu.co.uk/2013/02/ubuntu-ambiance-plasma-theme-kde you would need to exec in and either try and do everything from command line or modify the /startapp.sh to start other gui elements (like the settings window) on container start so you can change them

Make sure you read the instructions listed here: https://hub.docker.com/r/aptalca/zoneminder-1.29/ The webgui address is http://serverip:port/zm

As far as i can see from the links you have, it is always about SAS2008 cards! The problem is that Fujitsu is not LSI. Although the card may be "just rebranded", probably there are checks in place to prevent crossflashing with LSI or other firmware. For example, when talking about SAS2008 cards there is a key firmware (P07) that will allow you to override the "Vendor mismatch". The newer versions will not offer this opportunity and instead just quit with an error! Do you have an original Fujitsu Firmware that you can flash? Is there an HBA firmware from Fujitsu? And be careful to pick the right one! I used a tool from Fujitsu in a similar situation on a D2607 and successfully bricked the card. The computer won't post any more with the card plugged. Edit: The spec sheet for D2616 says SAS2108. Edit2: The equivalent 6 GB/s HBA from LSI/Avago is named SAS2308 and the card itself is called SAS-9217-8i http://www.avagotech.com/products/server-storage/host-bus-adapters/sas-9217-8i#specifications Sorry, wrong link. All the 2108 FW cause the signature error Still have the original files, hopefully can just flash that back. Fuji doesnt provide any files or bios's for the card that i can find. They also do not support IT mode or pass trough, only solution is to make every drive a RAID0, but then you cannot add more drives without destroying the entire config. Making it useless for unRAID in my case. Thanks for all your help so far, i was hoping this would be a quick flash but its turned into a multi day nightmare haha I'm totally confused about the 2008/2108 issue, but if it is recognized as a 2008 rev 04 by megaraid, you can try the latest firmware found here: http://www.avagotech.com/products/server-storage/host-bus-adapters/tab/tab4#tab-current-drivers4-abc Look for the one listed under 9211-8i_Package_P20_IR_IT_Firmware_BIOS_for_MSDOS_Windows That one is P20 and was released very recently (03/2016). It might support rev 04 if it truly is an SAS2008

The screenshot you posted shows the card being recognized as SAS2008 but your post on the other thread says SAS2108 Which one is your card? You might be trying the wrong firmware

Try this thread if you haven't already. They have newer versions of the firmware: http://forums.laptopvideo2go.com/topic/29059-sas2008-lsi92409211-firmware-files

github page says to put the script in /usr/bin and modify a couple of scripts in there. That location is within the container. You can get into the container by typing the following in unraid terminal: docker exec -it Zoneminder-1_29 bash (I'm assuming you are using the 1.29 version) You can retrieve the script from github using wget and copy into /usr/bin You can edit the other scripts with nano (just install nano with apt-get install and then do "export TERM=xterm") Keep in mind thatif you edit or reinstall the container, those changes you made will be lost Good luck Do you think it would be wiser to run zoneminder in a VM since I want to mess around with it so much? I just got my VT-x working on my p8z77-v LK... updating the BIOS fixed the bug where it wasn't working. If you're gonna mess with something too much, it's always better to custom install yourself from scratch. If you just want a working version of zoneminder that is super easy to install, then this is the container for you [emoji6]

I'll look into it It seems there is already a container for this in CA. It is by Bjonness

I'll look into it

github page says to put the script in /usr/bin and modify a couple of scripts in there. That location is within the container. You can get into the container by typing the following in unraid terminal: docker exec -it Zoneminder-1_29 bash (I'm assuming you are using the 1.29 version) You can retrieve the script from github using wget and copy into /usr/bin You can edit the other scripts with nano (just install nano with apt-get install and then do "export TERM=xterm") Keep in mind thatif you edit or reinstall the container, those changes you made will be lost Good luck

Scheduled backups? What kind of sorcery is this? [emoji14] I can't wait to try it

Yep, it does

It should shut down the UPS completely. The way it is supposed to work is that before UNRAID shuts down, the APCUPSD software issues a kill-power command to the UPS which also has a time setting (maybe 60 seconds). This allows for UNRAID to complete its shutdown before power is removed completely by the UPS shutting down to prevent excessive discharge of its batteries. The other thing for anyone to remember is to adjust the APCUPSD setting so that the shutdown process begins with enough battery power left for it to run to completion. It's also normal to set the PC's BIOS to allow an automatic start up when mains power is restored. I don't think the ups shutdown works on the cyber power ones. It certainly doesn't work on mine and others reported the same. All other features work, though.

Isn't that Windows only?

By default, it runs as user nobody and group users, which should have write access to your user shares in unraid. Some config folders of certain docker containers may not provide write access for the user nobody or the group users. If that's the issue, you can set the environment variables USER_ID and GROUP_ID to 0 when you install/edit the container in unraid gui so it will run as root. It's explained in the container description

Yeah the echo ended up becoming one of my best purchases. I integrated that thing with my lights, media center and everything. My friend's kids especially love chatting with Alexa lol

That forum post refers to the older version. I probably should update it to reflect that. The correct directions for ver 1.29 are on the docker hub page as well as the github page

If I change my Dockers to use /mnt/cache/ how do back them up? I've got my Dockers running from /mnt/user/AppData so that everything is protected in the Array. It's one of the questions I've had about Dockers and unRAID, but I haven't been able to find a definitive answer. Look into cache pooling. That way you can have multiple disks as part of a single cache share and every piece of data exists on two separate disks (more of a mirroring approach rather than a parity protected system, but unlike traditional raid mirroring, this system uses bttrfs's builtin feature and it is very flexible in terms of showing disks of different sizes) Or you can periodically back up the cache drive contents on a user share via a simple copy operation or rsync. The reasons most people use cache shares for dockers are: 1. There is a bug that affects some containers and breaks them when they are on a user share (may be related to use of symlinks) 2. Writes to the protected array are much slower due to the parity calculation. Whereas if you use an ssd as a cache drive it can be much much faster so you get better performance in most dockers 3. Having the containers on a user share may put too much stress on the parity drive in the long run

Here's the Unraid logs from restarting it. How do you check if the docker image is full? I highly doubt it is, since it's 10GB and I saw this same issue when it was the only docker app installed, but I can check. Apr 12 08:52:44 Media php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'restart' 'PlexRequests' Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: veth27e6fc1: renamed from eth0 Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth27e6fc1. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for vethca05738. Apr 12 08:52:44 Media kernel: device vethca05738 left promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethca05738) entered disabled state Apr 12 08:52:44 Media kernel: device vethfcc4630 entered promiscuous mode Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: nf_conntrack: falling back to vmalloc. Apr 12 08:52:44 Media avahi-daemon[2629]: Withdrawing workstation service for veth04d6a32. Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered disabled state Apr 12 08:52:44 Media kernel: eth0: renamed from veth04d6a32 Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:44 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state Apr 12 08:52:58 Media emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f PlexRequests Apr 12 08:52:59 Media kernel: docker0: port 3(vethfcc4630) entered forwarding state I actually needed the logs for the container (by typing the command I posted in terminal), but. . . those messages in the unraid log don't seem right. Perhaps jonp or limetech can elaborate as there may be an issue with your network settings

Click on advanced view

Could your docker image file be full by any chance? Also try the following in unraid terminal docker logs PlexRequests That might show more info on any potential errors

Can you post a screenshot of your container settings? The issue is not obvious to me. Is this a new install? I would recommend deleting the local folder and reinstalling it from scratch.

Can you post a screenshot of your container settings?

You probably used a/mnt/user location for the config folder. Change it to /mnt/cache or /mnt/disk and it should work

Great to hear is working. Let me know if you find any other bugs It seems it was premature (they accidentally changed the version number in their github). It has now been reverted. No version 1.29.1 yet :-) I believe the internal updater should update in the case of incremental updates (versions 1.29.X) but honestly, ever since I created the first zoneminder container, I don't think there has been any incremental updates, so that has not been tested. Worst case, I'll push an update to the container.