pederm

There seems to be different home directories depending on whether a script is invoked in the background or not. I have created a simple script with this contents: #!/bin/bash ls ~ -al When running in foreground, it lists the /root directory: drwx--x--- 7 root root 300 Jul 17 17:31 . drwxr-xr-x 20 root root 440 Jul 17 17:24 .. -rw------- 1 root root 16 Jul 17 17:31 .bash_history -rw-r--r-- 1 root root 316 Jul 15 04:27 .bash_profile -rwxr-xr-x 1 root root 60 Jul 15 04:27 .bashrc drwx------ 3 root root 60 Jul 17 17:20 .cache drwxr-xr-x 4 root root 80 Jul 17 17:20 .config lrwxrwxrwx 1 root root 30 Jul 15 04:27 .docker -> /boot/config/plugins/dockerMan drwx------ 3 root root 60 Jul 17 17:20 .local drwx------ 2 root root 60 Jul 17 17:22 .screen lrwxrwxrwx 1 root root 21 Jul 15 04:27 .ssh -> /boot/config/ssh/root -rw-r--r-- 1 root root 180 Jul 17 17:23 .wget-hsts -rw------- 1 root root 7606 Jul 17 17:20 keyfile -rw-rw-rw- 1 root root 28512 Jul 17 17:21 patch.sh When running in background, it lists the / directory: drwxr-xr-x 20 root root 440 Jul 17 17:24 . drwxr-xr-x 20 root root 440 Jul 17 17:24 .. -rw-r--r-- 1 root root 228 Jul 17 17:20 .wget-hsts drwxr-xr-x 2 root root 3820 Jul 17 17:20 bin drwx------ 10 root root 4096 Jan 1 1970 boot drwxr-xr-x 18 root root 3840 Jul 17 17:24 dev drwxr-xr-x 63 root root 3340 Jul 17 17:24 etc drwxr-xr-x 2 root root 40 Jul 15 04:27 home drwxr-xr-x 2 root root 0 Jul 17 17:20 hugetlbfs lrwxrwxrwx 1 root root 10 Jul 15 04:27 init -> /sbin/init drwxr-xr-x 1 root root 100 Jun 9 21:34 lib drwxr-xr-x 7 root root 4440 Jul 17 17:20 lib64 drwxr-xr-x 13 root root 260 Jul 17 17:24 mnt drwxrwxrwx 4 root root 80 Jul 17 17:24 opt dr-xr-xr-x 632 root root 0 Jul 17 17:19 proc drwx--x--- 7 root root 300 Jul 17 17:31 root drwxr-xr-x 19 root root 1180 Jul 17 17:24 run drwxr-xr-x 2 root root 5400 Jul 17 17:20 sbin dr-xr-xr-x 13 root root 0 Jul 17 17:19 sys drwxrwxrwt 16 root root 440 Jul 17 17:34 tmp drwxr-xr-x 1 root root 240 Jul 16 12:08 usr drwxr-xr-x 15 root root 360 Jul 17 17:20 var Would it be possible to use the /root directory when running in background also?

To avoid getting trouble with htop and similar, I had to replace vt102 with xterm-256color

A new version of the docker is now available, which seems to fix the problem

When searching for Jitsi in the apps tab, there seems to be docker images available since April 8th

According to sources, a 5406 beta bios exist for Asus x370 boards, which seems to play nice with both Ryzen 3rd gen and virtualization (AGESA 1.0.0.4B). Probably the one that @cjbconnor refers to? I have downloaded it for my x370 Prime, but have not flashed it. Other manufacturers seems to have released this some time ago for their x370 based boards, just not Asus. In case anybody has tried this on an Asus x370 based board, please report results.

Unraid allows me to get the most out of the available hardware, which includes providing contents for my family through Plex.

I have put this into the go file: /usr/local/sbin/zenstates --c6-disable The same setup has been running for a long time without exhibiting these crashes.

The last couple of months, my server has been suffering of annoying halts with no apparent pattern. Attached is a photo of the last moments of todays crash. Any hints are welcome. asus-diagnostics-20190728-1928.zip

I faced a similar problem on my Asus x370 board after a BIOS update. According to Spaceinvader Ones excellent video, please ensure that the IOMMU setting in BIOS is changed from Automatic to Enabled. After that when setting pcie_acs_override, the hardware passed through as before.

Installed 6.5.3-rc1 on my Ryzen system, apparently no change to boot-time of my Ubuntu Bionic VM with GTX1050-passthrough.

@AhmedI changed the ip-address to the host-name in the remote line of the ovpn-file and it started working.

Running Ryzen, I at some point got the impression, that turning off address space layout randomization (ASLR) would provide a more stable environment. I have therefore added this to the go script: echo 0 | tee /proc/sys/kernel/randomize_va_space I actually dont know whether this (still) is a good idea. Also it seems to provide a more stable Ryzen system when adding the rcu-nocbs option (substitute the number of cores minus one for 11): label unRAID OS kernel /bzimage append rcu_nocbs=0-11 initrd=/bzroot

I PCIEX16_1 is an old AMD Redwood graphics card, which is exclusively used by Unraid. In the PCIEX_2 slot is the Nvidia 1050Ti located. A dedicated mouse and keyboard is also used exclusively by Unraid.

On my Asus Prime x370 Pro, I have updated BIOS to the latest 3203, and in this BIOS I enable SVM in order to allow Virtual Machines to run. In the Unraid syslinux.cfg I specify two options for my Ryzen 1600x: rcu_nocbs=0-11 processor.max_cstate=1. With the latest beta of Unraid 6.4, it runs with my Nvidia 1050Ti as passthrough for any OS. For Windows 10, I use OVMF and No to Hyper-V.