Search results

Automatically-scaled graphs are great for specific use-cases, but they can require extra mental processing when doing visual scanning. For example: A VM using 0.2 CPU with regular peaks of 0.3 looks like it's using more CPU than a VM using 0.4 with a single peak of 1.2. Examples: Without...

I have the Samsung 980 NVMe (MZ-V8V500B/AM specifically) And my issue is showing up almost the same: By default, the NVMe SMART sensors are showing either something reasonable (29.85-32.85C (Though always .85)), or a warning temp of 83.85C. There's nothing in between. If I had graphs they...

In my case it is the 980 (MZ-V8V500B/AM specifically). I'll move my questions to that thread.

I have a different but seemingly related issue: By default, the NVMe SMART sensors are showing either something reasonable (29.85-32.85C (Though always .85)), or a warning temp of 83.85C. There's nothing in between. Edit: I've moved the rest of this post to...

Interestingly enough, I just did a fresh install of `7.2-11` last week and I've already gotten email notifications about the NVMe temps. I came to this thread wanting a convenient way to test cooling solutions while watching temps, not realizing that Proxmox's temp handling wasn't available...

There's one big capability that OpenWRT has and pfSense does not: CAKE It's the reason why I'm installing OpenWRT on the new box this week instead of transferring pfSense to it

I had a possibly related issue that I solved and documented here: https://forum.proxmox.com/threads/proxmox-7-docker-stoped-working.101926/post-441959 Short version is that I created a named pipe inside an LXC and that broke docker for all other containers. After I deleted it everything was...

Here's an experience I found so interesting that I registered a forum account to share it: I had the exact same error ("Error starting daemon: error initializing graphdriver: driver not supported"), but it was also preceded by [graphdriver] prior storage driver overlay2 failed: driver not...