caballopazo

has anyone confirm this is good?

i found the issue, for those of you with foscam, new firmware 11.37.2.65, you need to add user, password on the path line. user:password@IPaddress all works well.

good day everyone. i would need your help on an issue that occurred after i upgraded my asus router firmware and zoneminder docker. i had an issue with my ip's that i taught was related to the firmware on my router, but afterwards i notice it was tplink powerline adapter that made my network go down. after realizing the issue, i disconnected the tplink and all went back to normal for the exeption of zoneminder, i was getting unable to connect error. i did check update in unraid and there was a new docker update which brought me from 1.30.4 to 1.32.3... here's the issue: - i have two cameras running, but only 1 connects - i'm able to access both cameras throught their own gui ip address - at first not knowing the issue, i deleted the camera that was not connecting and it's database (captures) from the previous version, thinking a fresh re-install will get that camera connected back, no luck here's the log from zoneminder docker gui: 2019-07-27 07:40:14zmc_m36906ERRUnable to get response, disconnectingzm_remote_camera_http.cpp1096 2019-07-27 07:40:14zmc_m36906ERRUnable to read headerzm_remote_camera_http.cpp670 here's the log from unraid docker zoneminder : Jul 27 07:40:13 0dfec7332ad9 zmc_m3[6906]: ERR [zmc_m3] [Unable to read header] Jul 27 07:40:13 0dfec7332ad9 zmc_m3[6906]: ERR [zmc_m3] [Unable to get response, disconnecting] Jul 27 07:40:13 0dfec7332ad9 zmc_m3[6906]: INF [zmc_m3] [Return from Capture (-1), signal loss] Jul 27 07:40:13 0dfec7332ad9 zmc_m3[6906]: INF [zmc_m3] [Failed to capture image from monitor 3 outside front (1/1)] my set ups are exactly the same as my other camera, i even tried changing the IP address of the previous camera to a new one, in case zoneminder docker still keeps that ip address in its previous set ups.

hi everyone. i'm currently on version 6.4 running a couple VM's ...that i cannot go without using. i'm hearing that new unraid version needs to make sure MB bios is up to date or some VM's may not work. i'm running an ASRock - 970 Extreme4 which i dont believe the manufacturer still updates... Said that, is there anyone that has this motherboard bios version 2.80 that has done the update without any issues to their vm's and dockers? thanks everyone in advance!!

agreed .. will need to think to update!!! have a great weekend and thanks for your help!

hi everyone i followed these steps thank you all for the support. i will check back once the parity finishes rebuilding.

thank you Squid. i was able to check all the wires, and harness to power supply was off. all came back ok, however, i now have a brand new disk i install two weeks ago showing me a red x. smart test is showing in good shape. i'm not sure why is not given me a green light. here's the log and diagnostics, and also a screen shot of the system log tower-diagnostics-20180824-1934.zip

having the same problem now. i got home and my shares are no longer showing on unraid. my dockers and VM have disappear, if i try to reboot or power down, it doesnt work, i have to hard reboot. below is my diagnostics, also a screen shot of the log error i'm getting tower-diagnostics-20180824-0730.zip

is this going to always increase the VM size by 5GB every time it reaches a threshold space warning?

hi everyone, i would like to set up plex server to be give access to my ios and android devices in my network (plexpass)... however, more important i wouldn't want to start buying extra SSD's to save the metadata. i would like all heavy metadata files to either be saved in my array (shares) or can i configure the docker (unraid app), to be set up so it could use the existing metadata currently saved. obviously, the docker will still run from my cache ssd. is there someone that can suggest how to configure this, or if it can't be done? using unraid 6.3.2 thanks everyone