caballopazo

thank you trurl... let me sit on this for a little bit. will revert back to 6.4 for now, i had backed up my usb flash drive so all is back to how it was prior to this. will take a stab it once my head is clearer... one thing for sure, i tried to installed Fix Common Problems plugin, but cant be found in the applications under 6.4? wanted to start fixing issues before the next run a this.

spoke to soon, still crashing... and i'm not able to see why....

Thank you Frank1940, i ran the Install/Update the Fix Common Problems plugin, then go to Tools -> Update Assistant and click "Run Tests found one plugin backupCA that was no longer compatible with unraid and it suggested to delete it. did a system reboot but prior i stop all auto start on vm's and dockers. i've manually re-started 75% of my dockers and 50% of my VM's. i'm monitoring it before turning them all on... then my last test would be to do a reboot and let it all turn on automatically.

Hi all, i've updated from 6.4 boots perfectly, but after a few minutes after all my dockers have gone up, my system just crashes. can't record any logs as it disappears. is there anything i should had done previously before moving from 6.4 to 6.8?

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!!

hi everyone, i'm running version 2.3.4... i believe it's now catching up to me as every dl i'm trying to do is given me an error since last night. i held back from doing the update as it's not appearing on the docker tab in unraid. how can i update binhex-sabnzbd in unraid 6.4 terminal? thanks

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

hi everyone, just wanted to post an update to this post. the problem is solved now. basically i was following what ASROCK forums were telling me to do by pairing my 2 x 8GB sticks by slot. and they were strongly recommending to pair them by slots of the same color - especially white. i decided after testing both sticks one by one, to pair them one on the white slot and another one on blue slot of the MB. all is back perfect now. thanks everyone for your support on this.

hi delarius. would you advise where i can find that on a montherbaord bios? which setting, i got asrock 970 extreme 4 and cannot find it. thanks for your reply

hi guys, i did a cleaning too, dusted everything out of the nas. and still i'm not able for unraid to allocate what is installed. i tested all the slots one stick at a time and all work well. the only major change i did that i'm wondering if it's causing the issue 1- upgrading unraid to 6.3.5 from 5. and 2- i upgraded my bios MB 970 extreme4 thanks everyone, i'm reading many posts about this issue but no one has find a fix. thx

yes bios recognize it and also i dont have an onboard video, i have 970 extreme 4 mb also i run memcheck no problem both sticks at the same time, they were recognized and did 4 memtest passes all good

hi guys, i've been trying to get this issue fix, and i'm not getting any support. i also posted on the asrock forums and did the testing they required and all slots are working properly. the only thing left to do is perhaps go back to previous bios but i want to check back here first. system boots and recognizes each stick one at a time. stick 8GB no problem. as soon as you add a second stick (same brand, same size, etc) the unraid gui dashboard see's it installed but wont allocated more than 7.881gb. any suggestions??

i did some testing moving my stick around. i had orginally installed 2 x 8GB + 1 x 4GB sticks of ram. i removed the 4GB of ram and just left the 2 x 8GB that are the same brand of memory. they are both in the blue slots as for some reason one of the two white slots isnt reading one of the sticks. i also updated unraid to 6.3.5 to make sure it's at it's latest version. also updated the plugin dynamix webgui to 20170526 version. still having issues, below are my spec and updated screen shots showing my issue, as well as the free and dmidecode -t 17 also i'm attaching the memtest start up so you can see that the motherboard is well recognizing the 2 sticks. note, i dont have any onboard video on my bios either. hope someone can help, i'm going crazy trying to find answers... i see a lot of questions about this, but not a solid answer. is this an issue with unraid?? root@Tower:~# dmidecode -t 17 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0012, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM0 Bank Locator: A1_BANK0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum0 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0014, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: Unknown Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: A1_DIMM1 Bank Locator: A1_BANK1 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: A1_Manufacturer1 Serial Number: A1_SerNum1 Asset Tag: A1_AssetTagNum1 Part Number: Array1_PartNumber1 Rank: Unknown Configured Clock Speed: Unknown Handle 0x0016, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM2 Bank Locator: A1_BANK2 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum2 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0018, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: Unknown Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: A1_DIMM3 Bank Locator: A1_BANK3 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: A1_Manufacturer3 Serial Number: A1_SerNum3 Asset Tag: A1_AssetTagNum3 Part Number: Array1_PartNumber3 Rank: Unknown Configured Clock Speed: Unknown

hi guys, i have the same issue, not sure if the above solved the problem, but here are my specs unraid 6.3.2 free total used free shared buff/cache available Mem: 8071464 5950368 1177376 504988 943720 1111740 Swap: 0 0 0 dmidecode -t 17 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0012, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM0 Bank Locator: A1_BANK0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum0 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0014, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: Unknown Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: A1_DIMM1 Bank Locator: A1_BANK1 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: A1_Manufacturer1 Serial Number: A1_SerNum1 Asset Tag: A1_AssetTagNum1 Part Number: Array1_PartNumber1 Rank: Unknown Configured Clock Speed: Unknown Handle 0x0016, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM2 Bank Locator: A1_BANK2 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum2 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0018, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: A1_DIMM3 Bank Locator: A1_BANK3 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum3 Part Number: F3-14900CL9-4GBXL Rank: 2 Configured Clock Speed: 667 MHz

hi guys, i have the same issue, not sure if the above solved the problem, but here are my specs unraid 6.3.2 free total used free shared buff/cache available Mem: 8071464 5950368 1177376 504988 943720 1111740 Swap: 0 0 0 dmidecode -t 17 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0012, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM0 Bank Locator: A1_BANK0 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum0 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0014, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: Unknown Data Width: 64 bits Size: No Module Installed Form Factor: DIMM Set: None Locator: A1_DIMM1 Bank Locator: A1_BANK1 Type: Unknown Type Detail: Synchronous Speed: Unknown Manufacturer: A1_Manufacturer1 Serial Number: A1_SerNum1 Asset Tag: A1_AssetTagNum1 Part Number: Array1_PartNumber1 Rank: Unknown Configured Clock Speed: Unknown Handle 0x0016, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: None Locator: A1_DIMM2 Bank Locator: A1_BANK2 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum2 Part Number: F3-1866C10-8GSR Rank: 2 Configured Clock Speed: 667 MHz Handle 0x0018, DMI type 17, 34 bytes Memory Device Array Handle: 0x0010 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 4096 MB Form Factor: DIMM Set: None Locator: A1_DIMM3 Bank Locator: A1_BANK3 Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MHz Manufacturer: Undefined Serial Number: 00000000 Asset Tag: A1_AssetTagNum3 Part Number: F3-14900CL9-4GBXL Rank: 2 Configured Clock Speed: 667 MHz

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

thanks for your reply on the other post. one question, is the symlink set up inside the container folder where the media file resides?, do you have an example?

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

Thank you Johnnie Black!!!

hi guys sorry for the confusion, i'm a newbie and just need to follow the right process, and i'm seeing a lot of discussions on how to do the parity swap, and what i'm understanding, you are explaining how to swap a data drive using the current parity drive because the new drive bought is bigger than the current parity. however, i have the actual parity drive reading errors and want to replace it with a new one - note it's the same specs as my current parity drive that's failing. do i still need to follow the "parity swap procedure" even though i'm not planning on keeping the current "defective" parity drive in my array? or is there another process i'm missing to just replace a parity drive for another drive due to failure? thank you for your help.