ZipsServer

A new diag is attached. A preclear using the Unassigned Devices plugin just failed for some reason. mastertower-diagnostics-20200726-1307.zip

Could it possibly be a disk problem? I have three external hard drives running in a btrfs pool through Unassigned Devices. My system just froze again and I was unable to run diagnostics. I also noticed that my dockers using the Unassigned Devices btrfs pool were not working properly and the Unassigned Devices plugin UI was not displaying any info. I hard disconnected the external hard drives and everything returned to normal. Unsure if this was the cause of previous problems. Attached is the diags i just ran. mastertower-diagnostics-20200719-1509.zip EDIT: I want to clarify that I have run these external disks through a preclear without any errors and SMART seemed to be ok. This leads me to believe there may be a problem with using a manually created btrfs pool (no raid) with external disks. Any thoughts here?

This problem has happened 5+ times now. Every time I am unable to get diagnostics. I am able to get the syslog, but it really only shows rcpbind messages from my NFS shares.

I ran a MEMTEST for 18 hours with no errors. Still unsure what is causing these issues.

Hiya, Unfortunately I have had some reoccurring "out of memory" problems with my server over the past few weeks. This time I was actually able to get some diagnostics output which I have attached. I had to run `diagnostics` from the command line which also gave errors. Starting diagnostics collection... Warning: file_put_contents(): Only 0 of 5 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 80 Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 12 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 665 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 13 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 599 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 1034 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 15 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 14 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 11 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 85 Warning: file_put_contents(): Only 0 of 82 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 101 Warning: file_put_contents(): Only 0 of 2 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 120 Warning: file_put_contents(): Only 0 of 34 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 122 echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device echo: write error: No space left on device Warning: file_put_contents(): Only 0 of 29 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 Warning: file_put_contents(): Only 0 of 25 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 160 EDIT: Currently running a MEMTEST. First pass completed without an error. tower-diagnostics-20200710-1912.zip

I am having the same problem with PIA. None of the endpoints are working for me. Had to set STRICT_PORT_FORWARD='no' to get PIA to work.

Is there any reason Lidarr might be gobbling up memory and causing my server to freeze up? Twice now Lidarr has been associated with a process called `mono` using 3+GB (>30%) of MEM. Both times this caused my server to come to a standstill.

Same exact problem here after updating a few minutes ago. - 30.06.19: - Add geoip2 module.

Thanks for the reply. Yes I read the main README, but it do not seem to specify how to use a DNS provider other than the ones listed. It seems that I am missing something obvious or that it is not possible.

My reverse proxies just stopped working and it appears that LetsEncrpyt container is to blame. No errors were logged, but I assume it has something to do with the tls-sni validation change. I set up a new container and it was not able to create the cert using http (port 80 is blocked by ISP). I set up this docker long ago before the auth/validation changes and it appears that I will have to use the DNS validation option. I currently host domains with Google domains and Namecheap. I would rather not switch for simplicity and because I use their email forwarding services (and do not want any email interruptions). Is there anyway to setup validation with Google Domains or Namecheap? I couldn't find a README

Hello! I have a few questions about the username/password combo and encryption for MQTT. I have already setup my username and password for the MQTT server. I have also seen that the passwords on the server side are encrypted once added. However, as I understand it, the MQTT clients will still send the username/password as unencrypted plain text to the server if SSL/TLS are not used. Is my understanding correct here? The docker description states that it supports certificates. How do I setup SSL/TLS for the MQTT broker? Is there another way to secure the MQTT clients from packet sniffing? Thanks!

I had the same problem with a custom VPN. You need to populate the VPN_Remote field in the Docker settings with the gateway address, even though it is set to custom (You didn't need to do that before)... I just stopped and started DelugeVPN and I am having the same issue. I am using PIA and I am not sure what VPN_REMOTE value I need to use... Sorry for the noob question.

Can anyone provide guidance on how to configure this docker to use VyprVPN? https://support.goldenfrog.com/hc/en-us I believe that I am not configuring the .opvn file correctly. Many thanks!

Hi all, I am having a GUI issue with S3 Sleep. I am running UNRAID 6.1.7 and S3 Sleep 2015.12.14. The unconditional sleep button that is usually on the "Main" tab of the GUI does not seem to exist. The Sleep Setting are on the "Settings" tab, but there is no unconditional sleep button on the "Main" tab. Anyone else having this issue? My guess is that there is some conflict with the 6.1.7 update?

Hi there again, I am having some trouble flashing my M1015 that just arrived today. I already have the file for flashing the card on my unRaid machine. I put them on a flash drive and mounted it on my unRaid machine using SNAP. I them tried to run the first .sh and it gave me this root@Harvard:/mnt/disk/usbcruzer/LSISAS2008ControllersP11Linux/Flash/LSI# ls 1_ListAllAdaptors.sh* 2118ir.bin* 2118it.bin* 2_Backup_Current_Firmware_Bios.sh* 3_Flash_to_IR_mode.sh* 3_Flash_to_IT_mode.sh* 4_ListAllAdaptorsAfterFlash.sh* LSI\ 6Gbs\ Serial\ Attached\ SCSI\ (SAS)\ Integrated\ RAID.pdf* LSI_SAS_2008_Product_Brief.pdf* Original_Readme_Files/ __ReadMeFirst.txt* mptsas2.rom* sas2flash* sas2flash10* sas2flash5* sas2flash8* sas2flash9* <ruzer/LSISAS2008ControllersP11Linux/Flash/LSI# 1_ListAllAdaptors.sh List information about all adapters found Press Enter key to start, or CTRL-C to quit. Proceeding to find LSI Controllers Log will be AdaptersCurrentFW-Bios.txt in the current directory LSI Corporation SAS2 Flash Utility Version 11.00.00.00 (2011.08.22) Copyright (c) 2008-2011 LSI Corporation. All rights reserved No LSI SAS adapters found! Limited Command Set Available! ERROR: Command Not allowed without an adapter! ERROR: Couldn't Create Command -l Exiting Program. I looked afterward and there was no AdaptersCurrentFW-Bios.txt to be found. I also tried using the -o option but it gave the same output. <ControllersP11Linux/Flash/LSI# 1_ListAllAdaptors.sh -o List information about all adapters found Press Enter key to start, or CTRL-C to quit. Proceeding to find LSI Controllers Log will be AdaptersCurrentFW-Bios.txt in the current directory LSI Corporation SAS2 Flash Utility Version 11.00.00.00 (2011.08.22) Copyright (c) 2008-2011 LSI Corporation. All rights reserved No LSI SAS adapters found! Limited Command Set Available! ERROR: Command Not allowed without an adapter! ERROR: Couldn't Create Command -l Exiting Program. Am I running the .sh wrong? Or should I not mount the usb drive using SNAP? Does it need to be run under the /boot directory? I currently have my array stopped and I have the card plugged into the PCIe 2.0 x16_2 slot (black, at x 4 link) with no SAS cable attached as seen below. I also tried plugging it into the PCIe 2.0 x16_1 slot (blue) Any Ideas? I hope its not something stupid.

@Ford Prefect, That makes sense. I honestly cant describe how grateful I am. Thank you!

Hi guys, I dont know much at all about these SAS cards and I am having trouble figuring out how to flash mine. I guess I just need a big picture overview of what to do. I am planning on buying the M1015 and flashing it to the SAS2008. I have read the first 10 pages of this thread and I have downloaded the files from Madburg's OP, but I still cant wrap my head around everything. I know it is laid out pretty clearly, but there are a few missing links that I cant fill in because im a noob. I am hoping to flash this card on my unRAID box so I downloaded LSI SAS2008 Controllers(P11)Linux.rar - 3.16 MB http://www.mediafire.com/?doepi97zo4ao4c7 and I downloaded LSI MegaRAID to SAS2008(P11).zip - 5.87 MB http://www.mediafire.com/?98j2l2314l6g77w 1.) So do I run "LSI MegaRAID to SAS2008(P11)" first and then "LSI SAS2008 Controllers(P11)Linux.rar"? And are there any other files I need? 2.) I cant tell whether I can run LSI MegaRAID to SAS2008(P11)" on my unRAID machine or not because I am not sure what DOS runs under. (yes i am that uneducated) This zip file provided detailed instructions on what to do so I think I can follow those if i do run it on my unRAID. 3.) Then for "LSI SAS2008 Controllers(P11)Linux.rar", im guessing i run the 1,2,3,4 files in order, but then what is the "2118it.bin" file for? 4.) Also, it says to "First step is to copy the sas2flash(5/8/9/10/11) you will be using to just plain sas2flash." Where am I copying it to and how do I run it? and when I copy it I am supposed to rename the file to just sas2flash? (just clarification) 5.) Also, i have read posts saying that there is a new P14? Which files do i replace in the original set? And where can I get the new files because they are not posted in the OP? With that, hopefully I can figure out the rest. I appreciate everyone's hard work in getting these files together and I appreciate your response in advance.