the1poet

Hey, I've been experiencing the same issues since upgrading my primary server to 6.12.x. Didn't before the update. Might have to role back as well 2nd time this week. Deleted my docker image and restored data, but not going to bother if it seems there's bugs with this release.

I am using this: https://firewalla.com/products/firewalla-gold

Since upgrading one of my servers to 6.10 rc3, my firewall has been reporting suspicious traffic to an IP address 52.40.54.163 in America, originating from my unraid server. Is this an IP address of a server managed by unraid? If so, why after this update is this traffic connecting to an IP address and not to a FQDN?

@trurl I've changed over to ipvlan. will monitor and see how it goes. thanks for the help.

Attached complete syslog syslog-192.168.1.12.log.zip

hi @trurl, i just grabbed from the top of where it started showing that error, down. Did you want before that? The "Starting diagnostics collection..." didn't complete so I had to force power down, then ran diagnostics after it powered back on. homenas-diagnostics-20211113-1254.zip

I've pressed the power button which has gone back to the terminal and it's currently at: Starting diagnostics collection... How long does this usually take?

I noticed a while back that my server would sometimes stop responding. This prompted me to dump my syslog's to another server so I could access them the next time it happened. Can anyone explain what this log means and why the server has stopped responding? Currently running 6.10.0-rc2 Thanks syslog.txt

Hi Devar, apologies for not replying for so long. Life in general has been very busy. I was sick the day I did it and in a bit of a fever state so my memory of the day is a bit foggy... which is the why I didn't get around to updating the day after. As it's been quite some time, I'm not sure I could write accurate instructions on how I did it. From memory, the link I provided wasn't far off what I did, it was just getting the USB stick to boot into UEFI mode was the issue. I had to find a 32bit version of UEFI as the the program that patched the firmware was 32bit. I hope that's of some use?

I ended up biting the bullet and flashin in IT mode. Will do a write up of the process on the weekend when I've got time. It was quite painful, so hopefully the lesson I learned will help someone else in the process.

Hi all, I recently decided to move from my onboard sata to a raid card and purchased a Silverstone ECS04. I read on a reddit post someone saying it shouldn't need IT mode, but I don't want to waste countless hours testing to find I need IT mode. Here's the device: https://www.silverstonetek.com/product.php?pid=706&area=en If it does require IT mode, can someone point me in the direction of what's required to flash? I can see various posts around on how to do it, but the Silverstone page doesn't appear to have firmware or instructions on how to flash the firmware. The device uses the LSI SAS2308 chipset. Can I just get firmware from the chipset website? Any help would be greatly appreciated. Thanks edit: On the LSI website (which redirects to broadcom.com) I found the chipset here: https://www.broadcom.com/products/storage/sas-sata-controllers/sas-2308 ^ this does not have any drivers, but if I go to related devices, https://www.broadcom.com/products/storage/host-bus-adapters/sas-9207-8i ^ I find a LSI device which has all the drivers, etc If I follow the instructions here: https://www.bussink.ch/?tag=sas2flash Will this work for my device?

Hi aptalca. Appreciate the work the team does. I've filled out the contact form on the unraid website and expressed my interest for you guys to get the assistance you need to fix the issue. Hopefully others do as well.

Did some testing, now I've scanned my library after health checks and left it running over night. So far, so good. Thank you for the speedy response. Are there any plans to simplify the GUI for creating plugins? Perhaps having tick boxes for common settings or fields with descriptions and parse those as variables to the script? Just thinking of you and not getting bugged by end users as much if the process was simpler? Don't get me wrong, I appreciate your hard work... just a suggestion to potentially improve things. Thanks again!

Sorry for not clarifying... 5.1 audio.

Can anyone offer advice on creating plugins? What I want to create seems simple enough. I want to convert any video file that has surround sound that isn't ac3, aac, or mp3, and transcode to ac3, and copy the rest (video, subtitles, etc). It's late here and I'll have another crack at it on the weekend, just thought if someone could steer me in the right direction. tl;dr, I have 10 year old surround sound that doesn't support DD+, DTS-HD, and most other modern surround sound files. As a result, I want to convert my videos with surround sound audio to something that will play on my speakers. Thanks

I've posted a bug report on the GitHub page for this project, but I'm linking it here to see if other unraid users can reproduce it. https://github.com/Josh5/unmanic/issues/90 Can others take a look and confirm if they have the same problem? Basically having issue not converting a file if the container is the same, copy the video stream, and convert the audio stream. The worker will ignore the file.

Solved Issue was with a docker and a memory leak.

Oh wow, I thought I was going mad when my unraid server constantly stopped responding since the weekend. I was wracking my brains, as one of my kids turned off my UPS which coincided at the same time the docker for Unifi Video updates that people are talking about in this thread. I also recently installed a new graphics card and set up emby/plex dockers to use it for transcoding (so I wasn't sure if something I did there caused it as well.) I was getting the "unable to fork" messages constantly. I posted in general support, didn't get a reply, then started trying different troubleshooting steps, etc. I finally had time today to properly troubleshoot and found the thread in top for this docker was hammering my RAM. Couldn't agree more about your statement about linux memory management. Couldn't understand why unraid was saying I had x memory, but I kept getting errors hinting at something was hogging all the RAM. Anyway, I can be at ease now I know the cause... I was about to give up.

Another error: php-fpm[2010]: [ERROR] fork() failed: Resource temporarily unavailable (11)

So I've reverted back to the non Nvidia linux server build, running v6.6.6 in safe mode, and still getting errors. For example: crond[1780]: unable to fork (user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null)

Hi, There's a number of changes I recently made to my server, and an unexpected power off that could be the cause of the issues I'm having. Currently my server is slow and I get errors when access the web GUI. For example, I just tried the docker tab and got this: Warning: exec(): Unable to fork [pgrep 'dockerd'] in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 190 I'm also getting lots of email notifications with the following: cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null /bin/sh: fork: retry: Resource temporarily unavailable The dashboard is also not loading all information correctly, showing errors such where the memory utilisation is: <br /> <b>Warning</b>: exec(): Unable to fork [grep -Po '^Mem(Total|Available):\s+\K\d+' /proc/meminfo] in <b>/usr/local/emhttp/plugins/dynamix/include/DashUpdate.php</b> on line <b>279</b><br /> <br /> <b>Warning</b>: exec(): Unable to fork [df /boot /var/log /var/lib/docker|grep -Po '\d+%'] in <b>/usr/local/emhttp/plugins/dynamix/include/DashUpdate.php</b> on line <b>280</b><br /> <br /> <b>Warning</b>: Division by zero in <b>/usr/local/emhttp/plugins/dynamix/include/DashUpdate.php</b> on line <b>281</b><br /> 0% Backstory (things I've changed or happened recently): I installed a GTX 1050 and installed the linuxserver plugin that installs the Nvidia drivers I've subsequently set up emby to access the GPU and confirmed it's working correctly I deleteed my docker.img (troubleshooting this problem) as some dockers after a while were stopping and then not responding. My kids pulled the power on the server, so it had a hard power off. Is anyone able to shed some light on what's going and could be the root cause? Any help would be much appreciated. Attached is my diagnostics..

After some googling, I found the solution here: https://caddy.community/t/solved-reverse-proxy-is-redirecting-to-local-ip-in-remote-browser/1985/5 Basically, I needed to add "insecure_skip_verify" to the block in caddy. It now works fine.

Thanks. I added the domain to the config file, but I'm still getting the same error message. This is what my config.php file has now: array ( 0 => '192.168.1.x', 1 => 'nextcloud.mydomain.com', ),

I'm not sure what you mean. Where would I look for this setting?

Is anyone able to provide some advice on how to get this to work behind Caddy? I followed these instructions here: https://techcoreduo.com/2018/04/28/how-to-install-nextcloud-on-unraid/#comments They advise to use LetsEncrypt, but I am already using a Caddy docker to reverse proxy to my other web based services. I've got this in my caddy config file for the server: nextcloud.mydoman.com { gzip proxy / 192.168.1.9:443 { transparent } } Whenever I try to access the server via the URL, I get the following error from the Nginx built into the NextCloud docker: Any idea what I'm doing wrong? I can access NextCloud internally without any issue. It's just the caddy redirect breaks something when forwarding to the server.