tkenn1s

As another data point; this does not seem to affect all nvidia GPUs. I'm running the plugin on 6.11.5 w/ a Quadro P2200 and there are no such logs in syslog.

Apologies if this is not the right topic to post; please let me know if there's a better place to do so. I've been unable to change the docker icon from the unraid web UI; see bug: I was able to work around this issue by: modifying the `<Icon>` tag in the original template [eg. within `/boot/config/plugins/dockerMan/templates/`] and not the user template removing images from both `/var/local/emhttp/plugins/dynamix.docker.manager/images/` and `/var/lib/docker/unraid/images/` refreshing the main docker page

Just to clarify ... I wasn't "doing it wrong". I understand that the directories are mapped. That wasn't the issue. What I needed access to were the _tools_ [ie. par2, etc...]. Those aren't natively available on unraid, but are installed within the container.

How are backup notifications sent? And, what format are they in? I'd like to track backup completion using something like Healthchecks. I could write a script to do this, but it'd be better if CA Backup could do it natively.

I'm seeing my card always reporting as power level P0 with 6.9.0-rc2. However, when I was using the nvidia-plugin from LinuxServer.io, it would always go back to P8 when idle. It looks like even trying to force power save mode with `nvidia-smi -pm 1` doesn't switch the card to P8. How do I get my card into P8 mode since it should be spending most of its time idle? # nvidia-smi -pm 1 Enabled persistence mode for GPU 00000000:03:00.0. All done. # nvidia-smi Sat Feb 27 16:31:38 2021 +-----------------------------------------------------------------------------+ | NVIDIA-SMI 455.45.01 Driver Version: 455.45.01 CUDA Version: 11.1 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===============================+======================+======================| | 0 Quadro P2200 On | 00000000:03:00.0 Off | N/A | | 57% 44C P0 20W / 75W | 0MiB / 5058MiB | 0% Default | | | | N/A | +-------------------------------+----------------------+----------------------+ +-----------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=============================================================================| | No running processes found | +-----------------------------------------------------------------------------+

Yeah. Unless the images have been updated recently, stable is on 440 which has busted P-states using Plex.

I believe that's what the question was about.

Apparently this is expected whenever you're running headless. You can force your GPU into P8 by: Enabling a dummy X-server Installing and running Nvidia's persistenced daemon Toggling persistence mode using nvidia-smi from /boot/config/go I opted for #3 since I didn't want to have a bunch of stuff running just to get to a lower power mode. I added the following to the go file and it now boots into power state P8. # enable nvidia persistence mode if [ -x /usr/bin/nvidia-smi ]; then /usr/bin/nvidia-smi -pm 1 fi

I just installed 6.9.0-beta29 [haven't run any encode / decode yet] and it looks like my card is in the P0 state after booting. I've attached a screen shot from the GPU plugin. Sorry, really new to this. Is this expected? UPDATE: Just did a HW transcode w/in Plex. As soon as the transcode stopped, the GPU went to P8. Is there a way I can get the GPU to P8 w/o having to run a transcode?

One more feature request. FR: When I move to the next page, it keeps me at the bottom of the page. It would be nice if it repositions you at the top.

@housewrecker Thank you for GAPS. This is awesome. Do you have an official place where I can make feature requests or report bugs? FR: I would love to be able to mark items as "do not want" [eg. there are lots of sequels that were complete flops and I don't particularly care to waste storage for them] FR: It would be nice to be able to see that a scan is in progress. I started a search for my library and navigated away to another tab. When I went back to 'missing', it just showed me there was nothing available [and did not show a scan was already in progress]. I assumed it was still working in the background and after a few hours I saw recommendations. Bug: I really like the links to tmdb for other movies / what I have. However, they all just point to 'https://www.themoviedb.org/movie/' and not any particular movie. Bug: I'm getting suggestions and the "owned" item is blank [see screenshot attached]. I do have "xXx: Return of Xander Cage", which shows in "Missing", but also doesn't give me a recommendation card for.

Ah ha! Thanks Johnnie. I think that's exactly what happened.

From what I could find about Seagate's SMART reporting, there was this site -- http://sgros.blogspot.com/2013/01/seagate-disk-smart-values.html. The TL;DR is that Seagate encodes the error attributes as a 48-bit value, with the upper 16 bits representing the actual number of errors and the lower 32 bits representing the number of reads/seeks. So, decimal 43047327 for attribute 197 is 0x0000 0290 D99F. Meaning 0 ECC recovered errors in nearly 43 million reads. The drive is new and only ran pre-clear, so, the relatively low number of reads would be about right. But, I would imagine those lower 32 bits will roll over at some point. In any case, I'm not convinced the drive has actually shown any read/seek errors thus far.

Doesn't seem that either of these should apply here, though. First, the drive isn't part of the array; it's not even formatted. So, there shouldn't be any data being written to it. Second, more importantly, at least from my naive reading of the SMART report, there weren't any ECC errors. Attribute 195 [Hardware ECC Recovered] shows that there were zero ECC recovered reads. Additionally, both attribute 1 and 7 also show zero read/seek errors. I guess this was just some anomaly with unraid and is nothing to worry about?