NAS-Man

When GPU Statistics plugin is installed log constantly fills with this: Mar 9 01:51:02 MediaNAS kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Mar 9 01:51:03 MediaNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 9 01:51:03 MediaNAS kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Mar 9 01:51:04 MediaNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 9 01:51:04 MediaNAS kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Mar 9 01:51:05 MediaNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 9 01:51:05 MediaNAS kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Mar 9 01:51:06 MediaNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 9 01:51:06 MediaNAS kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Mar 9 01:51:07 MediaNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 9 01:51:07 MediaNAS kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Mar 9 01:51:08 MediaNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] Mar 9 01:51:08 MediaNAS kernel: caller _nv000708rm+0x1af/0x200 [nvidia] mapping multiple BARs Mar 9 01:51:09 MediaNAS kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window] When I remove GPU Statistics Plugin it stops.

Yes

Upgraded from 6.8.3 to 6.9.0 stable CPU Temp reporting much higher then it actually is, do you account for the 20 degree Celsius offset AMD has in place?

Upgraded from 6.8.3 to 6.9 stable and I also have this problem of Temp reporting higher than it is.

I have the same constant log entries, don't want to mute the warnings even though they are harmless other than spamming the log. I uninstalled plugin for now will try again after new Unraid update which hopefully will be out soon with newer kernel. Hopefully a new Nvidia driver update as well will fix this issue. Appreciate your work & time @b3rs3rk, it's a great plugin and like you said it's most likely not something you did or can fix.

Can you make a Miscreated game server docker?

I believe he is referring to this Linux ark server manager. FezVrasta's ark server tools. https://github.com/FezVrasta/ark-server-tools

If you don't have a path for transcode under edit of jellyfin docker then just add one named Transcode, container path: /transcode, host path: /tmp /transcode for path in jellyfin transcoding settings path

Install GPU Statistics Plugin from Community Apps & it will show info on dashboard tab. Set transcoding location in docker to /tmp which is memory in Unraid.

When one gets released, add a +1 for me. Thanks

Directly Accessing and adding a SSL cert to Plex on Unraid. https://www.target-bravo.com/blog/2018/7/10/blog-headline-1-6y3tj-49m5s-7tbal-gc7z3

Just found out MacOS High Sierra does not support Nvidia RTX cards, with Apple and Nvidia in some kind of conflict dispute none of the updates to MacOS since High Sierra support any Nvidia Cards.

Installed HighSiera by following your video which works fine until I make any change via the vm template (yes I edited the xml afterwords and added the xml at the bottom from line 136 on. Also added the icon location back correct in xml. Then on reboot it just goes to clover install again, not boot the installed HighSiera. So I added back the correct loader & nvram info in xml which fixes the boot issue. But at this point any changes in vm template breaks the vm even after adding the custom lines from 136 on back in xml. So I added everything in template I want including Nvidia RTX 2060 gpu passthrough and compare the new created xml with the previuous working xml. I then replace in the new created xml from the vm template lines 136 and so on back to the bottom, the icon location, the correct type of nic, the correct loader info, the correct nvram info and it boots all the way up but with 4 little screens side by side at top of the screen. Any idea what is causing this or what I may be doing wrong? Unraid Nvidia 6.8.2 Is support from @SpaceInvaderOne gone for macinabox? I see no replies for this docker from him since December 19, 2019 last year.

https://selfhostedhome.com/self-host-password-management-bitwarden/

Can't you just do the backup without using snapshot feature? I could but would rather not take down my outside network with pfsense vm going down during backup.

I changed the backup location in vm backup settings to /mnt/cache/ by accident I was up long time tired made mistake of not changing in vm instead. pfsense does not natively support qemu-guest-agent at the moment, will snapshots still work ok?

I had snapshots enabled and it broke my pfsense vm and had to manually restore. Going to disable vm backup plugin for now and wait for you to work out the bugs. Thanks @JTok

2020-01-05 07:00 information: Windows 10 can be found on the system. attempting backup. 2020-01-05 07:00 information: creating local Windows 10.xml to work with during backup. 2020-01-05 07:00 information: /mnt/cache/backup/Windows 10 exists. continuing. 2020-01-05 07:00 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. Windows 10 is running. can_backup_vm set to y. 2020-01-05 07:00 information: actually_copy_files is 1. 2020-01-05 07:00 information: can_backup_vm flag is y. starting backup of Windows 10 configuration, nvram, and vdisk(s). sending incremental file list Windows 10.xml sent 7,392 bytes received 35 bytes 14,854.00 bytes/sec total size is 7,292 speedup is 0.98 2020-01-05 07:00 information: copy of Windows 10.xml to /mnt/cache/backup/Windows 10/20200105_0700_Windows 10.xml complete. sending incremental file list 6d8d5b31-ae31-9fdc-f498-fa9c73b2221a_VARS-pure-efi.fd sent 131,241 bytes received 35 bytes 262,552.00 bytes/sec total size is 131,072 speedup is 1.00 2020-01-05 07:00 information: copy of /etc/libvirt/qemu/nvram/6d8d5b31-ae31-9fdc-f498-fa9c73b2221a_VARS-pure-efi.fd to /mnt/cache/backup/Windows 10/20200105_0700_6d8d5b31-ae31-9fdc-f498-fa9c73b2221a_VARS-pure-efi.fd complete. 2020-01-05 07:00 information: extension for /mnt/user/isos/Win10_1903_V1_English_x64.iso on Windows 10 was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 information: extension for /mnt/user/isos/virtio-win-0.1.160-1.iso on Windows 10 was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 information: the extensions of the vdisks that were backed up are . 2020-01-05 07:00 information: vm_state is running. vm_original_state is running. not starting Windows 10. 2020-01-05 07:00 information: backup of Windows 10 to /mnt/cache/backup/Windows 10 completed. 2020-01-05 07:00 information: number of days to keep backups set to indefinitely. 2020-01-05 07:00 information: cleaning out backups over 3 in location /mnt/cache/backup/Windows 10/ 2020-01-05 07:00 information: did not find any config files to remove. 2020-01-05 07:00 information: did not find any nvram files to remove. /tmp/vmbackup/scripts/user-script.sh: line 2809: 😞 command not found 2020-01-05 07:00 information: did not find any image files to remove. 2020-01-05 07:00 information: removing local Windows 10.xml. removed 'Windows 10.xml' 2020-01-05 07:00 information: pfsense can be found on the system. attempting backup. 2020-01-05 07:00 information: creating local pfsense.xml to work with during backup. 2020-01-05 07:00 information: /mnt/cache/backup/pfsense exists. continuing. 2020-01-05 07:00 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. pfsense is running. can_backup_vm set to y. 2020-01-05 07:00 information: actually_copy_files is 1. 2020-01-05 07:00 information: can_backup_vm flag is y. starting backup of pfsense configuration, nvram, and vdisk(s). sending incremental file list pfsense.xml sent 7,574 bytes received 35 bytes 15,218.00 bytes/sec total size is 7,477 speedup is 0.98 2020-01-05 07:00 information: copy of pfsense.xml to /mnt/cache/backup/pfsense/20200105_0700_pfsense.xml complete. sending incremental file list 7ee726f1-17c6-3496-d3a2-cb1916f748eb_VARS-pure-efi.fd sent 131,240 bytes received 35 bytes 262,550.00 bytes/sec total size is 131,072 speedup is 1.00 2020-01-05 07:00 information: copy of /etc/libvirt/qemu/nvram/7ee726f1-17c6-3496-d3a2-cb1916f748eb_VARS-pure-efi.fd to /mnt/cache/backup/pfsense/20200105_0700_7ee726f1-17c6-3496-d3a2-cb1916f748eb_VARS-pure-efi.fd complete. 2020-01-05 07:00 information: extension for /mnt/user/isos/pfSense-CE-2.4.4-RELEASE-p3-amd64.iso on pfsense was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 failure: extension for /mnt/user/domains/pfsense/vdisk1.snap on pfsense is the same as the snapshot extension snap. disk will always be skipped. this usually means that the disk path in the config was not changed from /mnt/user. if disk path is correct, then try changing snapshot_extension or vdisk extension. 2020-01-05 07:00 information: extension for /mnt/user/domains/pfsense/vdisk1.snap on pfsense was found in vdisks_extensions_to_skip. skipping disk. 2020-01-05 07:00 information: the extensions of the vdisks that were backed up are . 2020-01-05 07:00 information: vm_state is running. vm_original_state is running. not starting pfsense. 2020-01-05 07:00 information: backup of pfsense to /mnt/cache/backup/pfsense completed. 2020-01-05 07:00 information: number of days to keep backups set to indefinitely. 2020-01-05 07:00 information: cleaning out backups over 3 in location /mnt/cache/backup/pfsense/ 2020-01-05 07:00 information: did not find any config files to remove. 2020-01-05 07:00 information: did not find any nvram files to remove. /tmp/vmbackup/scripts/user-script.sh: line 2809: 😞 command not found 2020-01-05 07:00 information: did not find any image files to remove. 2020-01-05 07:00 information: removing local pfsense.xml. removed 'pfsense.xml' 2020-01-05 07:00 information: finished attempt to backup Windows 10, pfsense to /mnt/cache/backup. 2020-01-05 07:00 information: cleaning out logs over 1. 2020-01-05 07:00 information: removed '/mnt/cache/backup/logs/20200103_0819_unraid-vmbackup.log'. 2020-01-05 07:00 information: cleaning out error logs over 10. find: '/mnt/cache/backup/logs/*unraid-vmbackup_error.log': No such file or directory 2020-01-05 07:00 information: did not find any error log files to remove. 2020-01-05 07:00 warning: errors found. creating error log file. sending incremental file list 20200105_0700_unraid-vmbackup.log sent 8,049 bytes received 35 bytes 5,389.33 bytes/sec total size is 7,930 speedup is 0.98 2020-01-05 07:00 Stop logging to log file. 2020-01-05 07:00 Stop logging to error log file. 2020-01-05 07:00:02 Removed: /tmp/vmbackup/scripts/user-script.sh 2020-01-05 07:00:02 Removed: /tmp/vmbackup/scripts/user-script.pid

I got a notification of a failed error from vm backup when it tried to do a backup from a set schedule. When going to vm backup in settings this error is shown at the top of vm backup settings tab right above basic settings.

Warning: parse_ini_file(/boot/config/plugins/vmbackup/vdisk-list.txt): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(501) : eval()'d code on line 55

Upgraded from 6.7.2 to 6.8 with only one problem, the pfsense vm hang issue described here: I was able to fix with @bastl workaround. Thanks

I also had this problem when upgrading to 6.8 and used your emulate a Intel Skylake CPU on my Threadripper as a workaround for now until this issue gets resolved. Thank You

You meant 6.9 instead of 5.9