Maginos

For the issues with Nextcloud and Paperless, this could be the solution indeed. I started the "Docker Safe New Permissions" at around 7:45 a.m. CET and it's still running. Since PID and PUID were already set for both containers, I only added the UMASK to the containers. What I don't understand is, why the permissions of the folder of my dad changes. He said, he edited a file in this folder a few months ago and didn't access it since then. Yesterday the folder had 644 perms and he was not able to access it. But why does that happen?

Hi guys, I have strange permissions issues with my unraid servers and I'm searching for help to fix this permanently. 90% of the time, everything works fine with my SMB shares, but sometimes I can observe the following: When I click on a share on my Win PC, I get an error message that I don't have permission to enter this share. The same can occur not only with shares, but also with folders or files within the share. So the permission error can occur either by clicking on a share, folder or file. I found, that this issue can be resolved by using the "New Permissions" functionality on unraid. But since this is occuring every few weeks and I would like my father to access his files on the server without me resetting the permissions, I would like to solve this permanently. What the "New Permissions" function does, it sets the user/group to nobody/users and the directories to 777, the read/write files to 666 and the read only files to 444. So the troubleshooting could begin with following commands: find /mnt/user/share -type d -not -perm 777 find /mnt/user/share -type f -perm 644 or find /mnt/user/share -type f -not perm 666 -o -type f -not -perm 444 The first commands searches for all directories on the share that don't have 777 permissions, the second one searches for all files with permission 644. As of my understanding, the second number can not be 4 or less, or the smb user has no access to the directory/file. The first command is actually very useful, since there are only a few lines of output. The found folders were created by paperless-ngx: /mnt/user/home_florian/Dokumente/3_Media/documents/originals/Eduard Eberle/2024 /mnt/user/home_florian/Dokumente/3_Media/documents/originals/Sonstiges/2024 /mnt/user/home_florian/Dokumente/3_Media/documents/originals/Agentur für Arbeit/2024 /mnt/user/home_florian/Dokumente/3_Media/documents/archive/Eduard Eberle/2024 /mnt/user/home_florian/Dokumente/3_Media/documents/archive/Sonstiges/2024 /mnt/user/home_florian/Dokumente/3_Media/documents/archive/Agentur für Arbeit/2024 I have no idea what the problem with these folders is. The folders with 2023 at the end have all the correct permissions and all other folders from paperless-ngx too. So why have these folders other permissions than the others? The command find /mnt/user/share -type f -perm 644 is actually much more helpful than find /mnt/user/share -type f -not perm 666 -o -type f -not -perm 444 Here's the reason why: I found out, that I have files with permissions 766 on the server (I don't know why these files have these permissions... All of them were uploaded via SMB and not via my Nextcloud) and these also contribute to the output. When I search specifically for files with 644 permissions, I get files which were upload by the following applications: - Notability (note taking App on my iPad, upload via WebDAV) - Thunderbird (via Nextcloud mail attachment, upload also via WebDAV) - Paperless-ngx again (upload through Paperless-ngx itself, locally) It is worth noting, that NOT ALL FILES which were uploaded from these applications have wrong permissions, only a few. I also have a nextcloud connected, which has access to the same data. I use the linuxserver container and the shares on my unraid server are mounted with -v option in the linuxserver container. The issued that my dad had today was, that he wasn't able to access a folder on his share because of this permission issue. After setting new permissions, everything was fine. He accesses this folder only on this PC via SMB and not on his mobile phone. The last time, he edited a file in this folder was some months ago and this was again via SMB. As you can see, I am able to find what causes the problems for the wrong SMB permissions error, but I don't understand why only a few files and folders are affected and why only they get the wrong permissions. I resetted the permissions with "New permissions" several time, but after some time, they occur again. Can anyone help me with this? Thank you for your help! Maginos

After deactivating Talk in the Mastercontainer, the OOM errors were gone, so this seemed to be the fix.

Some further information concerning the Ubuntu vm: Since yesterday, I had network connectivity errors coming from nowhere. Today I obverved, that the vm doesn't get an IP address from the DHCP server. I was able to resolve this by executing the command "dhclient enp1s0". After that, the vm got a valid IP address from the DHCP server. To make this persistent, I edited the file in the /etc/netplan/ folder and changed "enp11s0" to "enp1s0" (for whatever reason the interface name is wrong...). After a reboot, the vm got its IP from the DHCP. While I was working today on this problem, the unraid host ran into high memory and cpu utilization again (screenshot below). I checked the cpu utilization of the vm again and it was around 50% (4 GB). I shut down the vm and after around 5 minutes, CPU and memory on the unraid host went back to normal. So I think it's very likely, that the OOM error is related with the ubuntu vm.

Hi guys, the Fix Common Problems plugin reported, that I have several Out of memory errors on my server. For resolving this issue I should post my diagnostics here in the forum. I think I might know from where these errors came from, so here some background information: - My server has 32 GB of RAM, around 7 GB are used in idle - Yesterday I created a Ubuntu server vm and assigned first 6 GB to the vm (Initial and Max memory = 6 GB). On this vm I installed Nextcloud All In One with all the available containers. On this vm, I think I ran out of memory, when the NC did some scans (build up the photo library, etc.). - Then I added 2 GB more Ram to the vm, so that it has a total of 8 GB. - Suddenly I noticed, that my unraid server used over 90% of its Ram permanently and the CPU usage went up to around 100%, so I checked the Ram usage of the Ubuntu VM. This was around 5 GB. - Since CPU and memory usage didn't go down, I shut down the Ubuntu server vm and after some minutes, CPU and memory were at a normal level again. I also have a screenshot of the Memory utilization recorded by my Zabbix Server. The time in the graph, where the gap is, I restarted the server and before that, the zabbix agent on the unraid server was not available. I hope, you can help me find out, what process caused this OOM error. Thank you for your help! Maginos tilda-diagnostics-20231229-1031.zip

Nope. It seems so, yes. The pikvm is connected to the HDMI port of the MB and the CLI of unraid is responsive. At the same time, handbrake is starting with passed through /dev/dri device and is converting a mov file to m4v with my custom QSV preset without any issue. So I guess my problem is solved. Thank you ich777 for your fast response and your help!

Hi guys, @TitanTigger and @leutnantlurch, I found a solution to this: ich777 gave me the hint, that a second GPU is not necessary for my setup and that I can use the iGPU for both the console output and for plex/handbrake hardware transcoding.

I tried this. I had connected the pikvm to the GT 710 and changed then the BIOS setting to "PCIE". Then there was no console output after the screen with the blue background and the different boot options for unraid. So I switched back to "Auto". Thank you, I didn't know about that! Again what learnt.

Hi guys, I have a question concerning the GT 710 in my unraid server: How can I tell unraid, that it should use the GT 710 for the output of the console instead of the iGPU from my i5-11400? The background of this is, that I want to use the iGPU for plex or handbrake and the GT 710 for my pikvm. I tried different settings in the BIOS concerning primary display, but everything else except for "Auto" didn't give any output on the corresponding port (available options are "CPU GPU" and "PCIE"). What I can observe is, that when I connect the pikvm to the HDMI port of the GT 710, the console output stops at a certain point in the boot process, while at the HDMI port of the MB, it goes directly to the login shell. This has worked without any issues in the past before, but for a few months, it doesn't work any longer. Here is my syslinux configuration: kernel /bzimage append pcie_acs_override=downstream,multifunction vfio_iommu_type1.allow_unsafe_interrupts=1 initrd=/bzroot Has anyone an idea, what I can do about this? Thank you for your help!

Second news to share: With the BIOS setting "Auto" as primary display, I can get to the login prompt as normal, when I connect the pikvm to the HDMI port of the mainboard. When I select "PCIE" in the BIOS and connect the pikvm to the GT 710, I get to the same point as posted above. So how can I tell unraid, that it should use the GT 710 as primary display?

I have another information to share: When I connect the GT 710 to another display, I get the same output. So the pikvm doesn't seemt to be the problem.

If the resolution of the console is not supported by the pi/pikvm, wouldn't there be no video output at all at the pikvm? Btw, I use a Raspberry Pi 4 for the pikvm, so it should support resolutions up to 4K60p. Or do you think the boot process starts with a resolution the pi/pikvm supports and at a certain point it changes to a resolution, which is not supported by the pi/pikvm? This seems unlikely to me. Concerning your suggestion with "kernal video=", where do I have to put that and is it correct? kernal vs kernel.

Oh man. It should not be necessary to do that. I really like the functionality of pikvm, but that annoys me. Maybe I will search for help on the discord server.

No, I've build the pikvm myself on base of a RPi 4.

Unfortunately not. I will keep you up updated, if I find a solution.

I had the same warning yesterday and got it resolved. On the discord of linuxserver, I got the tip to update three conf files. When you open the logs of your nextcloud docker, do you see a message, where it says, that you use older versions of ssl.conf, nginx.conf and site-confs/default.conf? If yes, you can do the following: 1. cd /mnt/user/appdata/nextcloud 2. mv nginx.conf nginx_backup.conf 3. cp nginx.conf.sample nginx.conf Repeat step 2 and 3 for all three files, then docker stop nextcloud && docker start nextcloud Then check in the nextcloud, if you have any warning and in that case, resolve them. Hope this helps.

Have you set up notifications in unraid? There's one option to recieve email notifications from your server and the results from the clamav scan are included. Or do you want to recieve mail notifications only from your clamav scan and not from everything else?

Yes, you can use the user scripts plugin for that. Just paste your rclone command into a new script, set the suitable cronjob for the execution of the script and your good to go. I highly recommend you to control the result of the rclone job. The second option would be to paste your rclone command in the crontab of the root user of unraid itself. I personally would use rclone only via the cli, since the terminology of rclone is not very complicated. So I personally would not use the rclone-browser.

Hi guys, as the title suggests, I have a question concerning pikvm. The base of my unraid server is a Asus Prime Z590-A motherboard and an Intel i5-11400 with Intel UHD 730. Since I use the iGPU for Plex transcoding or Handbrake, I had to put in a dedicated GPU for pikvm, which is a GT 710. So the pikvm is connected to the GT 710. Unfortunately, the pikvm stops at a certain point in the boot process and doesn't show the console prompt, as you can see in the picture. I bound the VGA controller and the Audio device of the GT 710 to VFIO at boot, but that didn't help. What else can I do to make pikvm show the whole boot process again? Thank you for your help! Maginos

Good to know. Since I had also issues with Brave, I gave Firefox a shot. Unfortunately it seems, that Firefox also has its issues...

Got it. I deleted the /boot/config/super.dat file one more time and rebooted. After assigning all the drives correctly and hitting "Start Array", my Firefox browser showed that he has to send the data once again to show this page. I hit cancel and everything was fine. So the problem was, that I always clicked "Send again" in the Firefox browser.

Hi guys, today I tried to upgrad my cache pool (named nmvecache) from 2x500 GB to 2x2 TB. I went with the guide from the forum here and at the point, where the new SSDs are assigned to the pool, the problems started. After inserting the two new SSDs, I booted up and unraid showed me, that two drives are missing. So I assigned the two new SSDs to the cache pool and started the array. This did not work and I got two "x" before the two drives in the main tab, where normally is a blue or green spot. The array didn't start and I first got the error message in the lower left corner, that the array has a stale configuration. Then I unassigned the two new SSDs from the cache pool, deleted the cache pool and created another cache pool named "nvmecache". I deleted the two SSDs (in the unassigned device area) and added them to the new cache pool and hit "Start Array". But the array didn't start. Then I searched for this "stale configuration" error here in the forum and found, that one person got it solved by deleting the files "super.dat" and "super.old" in the /boot/config folder. That are files, where information about the disks are stored. After deleting the two files I rebooted the server and tried to assign the two new SSDs to the new cache pool nvmecache. But again, the array doesn't start. It shows for 1 second, that it started and then immediately the page reloads and it is shown, that the array didn't start. I add the diagnostics. What can I do to get the new SSDs running? Thank you very much for your help! Maginos tilda-diagnostics-20230705-2153.zip

Yes I know. I thougt, it might be helpful for you. I already posted the output of the log file in this post as txt file.

This is my output from the docker container: docker run -d --name='ClamAV' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tilda" -e HOST_CONTAINERNAME="ClamAV" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='http://its.ucsc.edu/software/images/clam.png' -v '/mnt/user':'/scan':'ro' -v '/mnt/nmvecache/appdata/clamav':'/var/lib/clamav':'rw' 'tquinnelly/clamav-alpine' -i --log=/var/lib/clamav/log.log --max-filesize=4096M --file-list=/scan/file-list.txt 7fd0b66f015ed72c98def70d4a2f24faa1ce017b16c414b772856200a7b8ad02 The command finished successfully!

Nope, I had only the -i option in Post-Arguments. I added the other parameters you suggest and I think on Monday, I will see, if they help. Since the -f option is not listed in the Docker Hub page, can you tell what this parameter does?