-
Posts
396 -
Joined
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Dazog
-
-
4 minutes ago, CHBMB said:
Just uploading v6.8.0rc3
Took a while as any time there is new OOT drivers added I need to work out how to add them.
As always THANK YOU
-
8 hours ago, Squid said:
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-545988
Your rootfs is probably full
7% used on rootfs only.
it jumps to 100% when running the plugin.
-
I got this error trying to run the backup/restore plugin on 6.8 RC1
Oct 16 08:23:13 unRAID root: error: /plugins/ca.backup2/include/backupExec.php: uninitialized csrf_token Oct 16 08:23:13 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:23:13 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:23:13 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:23:13 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:25:50 unRAID nginx: 2019/10/16 08:25:50 [crit] 7268#7268: *499895 pwrite() "/var/lib/nginx/client_body/0000001182" failed (28: No space left on device), client: unix:, server: , request: "POST /pub/disks?buffer_length=2 HTTP/1.1", host: "localhost" Oct 16 08:26:03 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:03 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token Oct 16 08:26:05 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: wrong csrf_token Oct 16 08:26:06 unRAID root: error: /plugins/dynamix.plugin.manager/scripts/PluginAPI.php: wrong csrf_token Oct 16 08:26:06 unRAID root: error: /webGui/include/Notify.php: wrong csrf_token Oct 16 08:26:06 unRAID root: error: /webGui/include/Notify.php: wrong csrf_token Oct 16 08:26:12 unRAID root: error: /plugins/ca.backup2/include/backupExec.php: uninitialized csrf_token Oct 16 08:26:14 unRAID root: error: /plugins/ca.backup2/include/backupExec.php: uninitialized csrf_token Oct 16 08:26:22 unRAID root: error: /plugins/ca.backup2/include/backupExec.php: uninitialized csrf_token Oct 16 08:26:23 unRAID root: error: /plugins/ca.backup2/include/backupExec.php: uninitialized csrf_token Oct 16 08:26:32 unRAID root: error: /plugins/ca.backup2/include/backupExec.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token Oct 16 08:26:33 unRAID root: error: /plugins/ca.backup2/include/backupExec.php: uninitialized csrf_token Oct 16 08:26:34 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:35 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:36 unRAID root: error: /webGui/include/DeviceList.php: wrong csrf_token Oct 16 08:26:36 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:37 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:38 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:39 unRAID root: error: /webGui/include/DeviceList.php: wrong csrf_token Oct 16 08:26:39 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:40 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:42 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:26:42 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /webGui/include/DeviceList.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token Oct 16 08:26:43 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token Oct 16 08:26:44 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: uninitialized csrf_token Oct 16 08:26:44 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:45 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:46 unRAID root: error: /webGui/include/DeviceList.php: wrong csrf_token Oct 16 08:26:46 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:46 unRAID root: error: /webGui/include/DeviceList.php: wrong csrf_token Oct 16 08:26:46 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:47 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:47 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:48 unRAID root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Oct 16 08:26:52 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:52 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:52 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token Oct 16 08:26:53 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:53 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:53 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token Oct 16 08:26:54 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:54 unRAID root: error: /webGui/include/Notify.php: uninitialized csrf_token Oct 16 08:26:54 unRAID root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: uninitialized csrf_token
-
Are other people affected like me due to this bug from Nvidia?
Fixed a regression introduced in the 430.* series of releases that caused a segmentation fault in libnvcuvid.so while using Video Codec SDK APIs on certain graphics boards.
My server locks up after 1-2 days due to this.
Since this is fixed in a beta build, and slackbuilds doesn't build beta builds.
I will hold out hope for end of month new card announcements for new stable.
-
-
Will the Dynamix System Statistics plugin be updated to match Unraid 6.7/6.8 iconography?
-
They already released it.
WOW.
You guys are awesome!
-
-
57 minutes ago, starbetrayer said:
It is just you.
<PLUGIN name="&name;" author="&author;" version="&version;" pluginURL="&pluginURL;" launch="&launch;" support="https://forums.unraid.net" min="6.8.0-rc0w">
6.8.0-rc0w
That's a lot of releases for development.
I am betting that the 6.8.0 is close by now.
They haven't hit the next milestone
6.8.0-rcn0sy
- 1
-
43 minutes ago, limetech said:
Yes, latest 5.2.x.
Not 5.3 :0
Atleast we know now 5.4 in Nov is next LTS
-
47 minutes ago, Pducharme said:
Thanks for Unraid! i gladly paid a Pro licence, and had 3 or 4 of my good friends also do the same i still continue to advertise Unraid as one of the best Home Media Storage system. I think you should have a more "business" version, for company that want to manage VMs and Storage, etc.
Also, please udate the Kernel to 5.2.7 to support newer Ryzen 3000 temp sensors, etc. (
)
6.8 is on the horizon.
Possibly kernel 5.3 since it's due to be stable soon
It could also be the new LTS kernel.
- 1
-
Will we see a 6.7.3 with updated kernel before 6.8 series starts?
Since the 6.7 series will be used by some people for a time after 6.8 releases and while it's being tested.
- 1
-
8 hours ago, mihcox said:
Is there any traction on this, i use my for .ts -> .mp4 x265 transcoding and would love to monitor the progress.
Yes, alot of them got added into latest telegraf build.
-
-
QEMU updates arrive with major point releases.
I assume unraid 6.8 will have QEMU 4.0 or possibly 4.1 since it will be final soon.
-
18 hours ago, pappaq said:
I think you didn't enable the persistance-mode. Do that before testing with: nvidia-smi --persistence-mode=1
sorry, your right.
Once i run the command it works
I just have to set persistence mode on at each boot :0
* i justed tested emby, it latches to p0 for transcodes and goes back to p8 once trasncode stops!*
- 1
-
4 hours ago, Xaero said:
I was under the impression that Emby doesn't have this behavior?
To see if it does, and part of "why" run
watch nvidia-smi
Check the power state is not latched to P0.
Start a stream, verify the power state latches to P0
Stop the stream, verify the process has ended, and that the power state is stuck in P0
Run fuser -v /dev/nvidia*
To see what processes are still using the driver.
Card is always at P0
Stream or no stream.I will wait to see if someone creates a docker or script to fake the desktop to trick nvidia's cards into letting us not having to run P0 24/7
-
On 7/4/2019 at 1:23 PM, Xaero said:
Edit:
This is not a problem with an easy solution at all.
I can monitor the transcode processes and make sure that everything is killed - but the only solution is to kill Plex:
https://forums.plex.tv/t/stuck-in-p-state-p0-after-transcode-finished-on-nvidia/387685/24
I can user fuser -vk /dev/nvidia* and it will immediately switch to a P8 state. The only process using the card when this is run is "Plex Media Server"
It's not hard to write a script that will only do this if:
There are no processes using the card and the card is in a P0 state. I just don't know if there are any undesirable side-effects of doing it this way.
Here is such a script:#!/bin/bash while true; do cur_pstate=$(nvidia-smi --query-gpu=pstate --format=csv,noheader) running_processes=$(ps --no-headers "$(nvidia-smi |tail -n +16 | head -n -1 | sed 's/\s\s*/ /g' | cut -d' ' -f3)" | wc -l) 2>/dev/null if [[ $cur_pstate = "P0" && $running_processes -eq 0 ]]; then # if we got here, the card is only running the Xorg process and is in the P0 state, let's fix that. fuser -kv /dev/nvidia* echo "Reset Power State" fi #sleep so we aren't blocking a thread constantly. sleep 1 done
Starting the X server on Unraid does allow one to open nvidia settings; to do this you can use a script like this to start the X server (note, that since chvt and fgconsole aren't available, you will have to switch back to VT7 by pressing Ctrl+Alt+F7):
#!/bin/bash ##This will only work on single GPU systems: GPUID=$(nvidia-xconfig --query-gpu-info | grep BusID | sed 's/^[^:]*: //') #Now that we know the PCI BusID of the card we can create the X server with a fake display: nvidia-xconfig -s -a --allow-empty-initial-configuration --use-display-device=None --virtual=640x480 --busid "$GPUID" -o /dev/stdout | X :99 -config /dev/stdin&
Once you have that server running, you can return to the default unraid GUI and run:
nvidia-settings -c :99
To open nvidia-settings on the card. You could also store an xorg configuration file and use that for the virtual X display, and to set persistent nvidia settings.The only way I can think of to fix this properly is to figure out why the Plex process is claiming the card and prevent that from happening. I'll look into it some more, but this needs to be fixed properly by Plex/nVidia. The linked thread at the Plex forums has more information.
I may be able to detach the Plex Transcoder process with the wrapper script, making it it's own entity, and then trapping the SIGINT/SIGKILL in the wrapper and using it to kill the transcoder, effectively using the wrapper script to separate the Plex Media Server process from the Plex Transcoder process. It's pretty kludgy, but might work.
Oh Boy:
We're in idle P-State while transcoding territory!
Any idea about us emby users?
-
It's sad that people have now made this awesome hard work become a post worthy of:
https://old.reddit.com/r/ChoosingBeggars/
Please remember before this came out, we had to buy expensive large core processors AND use more power to do what we are doing today.
Thank you again for all your hard work. Without it we are back to what we had before which is nothing.
*I hope your family member is doing well. No amount of software/Computer work is worth not having those memories of said family members.*
- 3
-
Wow AMD DID have a cve that the linux firmware update patched:
https://www.phoronix.com/scan.php?page=news_item&px=AMD-SEV-Vulnerability-Micro-Up
Unraid patched it before CVE became public :0 -
1 minute ago, notphilip said:
Does this update have drivers for 9900k gpu?
Have to wait for 5.x kernel.
Which i ASSUME will be Unraid 6.8 beta series
-
35 minutes ago, limetech said:
Damn, I do follow that repo and also the slackware64-current package list. What happened with this release, was that it was actually built and tested a couple days ago when 4.19.53 was released. Then noticed kernel was up to .55 very quickly and in looking at change log there is a single change (probably related to 'sack panic' changes) - and any time Greg K-H creates another patch release with a single change, it's probably important 😳 So I did a quick kernel update and rebuilt this 6.7.1 release & didn't notice that firmware update from yesterday - yeah this stuff is changing rapidly these days!
How important is the f/w update to you? I can generate a 6.7.2 pretty quickly if so...
Not a CVE. I wouldn't worry.
I assume just this is the last update before AMD drops new firmware for Zen2 and EPYC2.
Be more worried if u did a respin 4 kernel versions will release...
-
Awesome work.
Next Unraid point release can you grab the latest Kernel firmware again to pull in this commit for us AMD users:
Thanks again!
- 1
-
11 minutes ago, limetech said:
Yup.
No one can sleep anymore.
They seem to be releasing kernel builds daily now :O
Time to setup a jarvis to build unraid builds with just the new kernels
- 1
[Plugin] Linuxserver.io - Unraid Nvidia
in Plugin Support
Posted
Has anyone wrote a bash script to enable these commands after array has started?
nvidia-smi --persistence-mode=1
fuser -v /dev/nvidia*
It allows the cards to go into p8 when not in use. (Save power mode)
I ain't very good at bash scripts.