Recent content by CycloneB

No add-on in the browser, but totally possible I tweaked a setting over the years. No tweaks on the new node as that's how it looked from the first login to the web UI.

I am adding a new node to my existing cluster. Two of the older cluster members started at pve6 and the third started right when pve9.0 came out. This new one installed right to pve9.2. I need help with a quality-of-life change that I just cannot seem to figure out. On the existing members from...

I am sad to see this is still a bug in 2026. Maybe someday it will get corrected. Likely would happen upstream, so who knows when.

Anyone experience better results on the newer kernels are we all still pinning to the older ones? With that bug report, I got one request for logs, but then silence since.

I wish I stayed on pve8 longer. After this issue, I pinned to 6.8.12-20-pve from 6.17.13-2-pve and have been stable since. Sadly, the original issue corrupted my zfs pool during a scrub, so I’ve been slowly restoring/rebuilding things from older backups (thank you 3, 2, 1!). I’m hesitant to...

The log entry was so long I had to split it across two posts b/c of the character limits, which goes to show how excessive this seems!

I see this thread from 2021 and didn't want to necro it in case this is a different issue with the same result. In my syslog, I get dozens of these messages at a time. Is this expected? From the prior thread, it sounded like a coder at some point wanted to suppress/remove these, but I don't...

Sounds VERY familiar, especially once the poster mentioned an impacted SATA Controller.

@wuselfaktor , fyi that I submitted https://bugzilla.proxmox.com/show_bug.cgi?id=7505 per a recommendation from @fiona in another thread about a different 6.17 kernel issue. I put a link to this thread in the bug report. Thank you again for your diligent work on this!

Just an FYI that since I uninstalled mdadm, I do not have that alert anymore. I sadly fell into another problem, but I've now gotten stable using steps outlined in that thread. I wouldn't be surprised if that problems was contributing to seeing this, but as @Neobin mentioned, there is no need...

OMG Thank you! I am seeing the same issue and keep suffering zfs pool corruption the last few days. I just pinned back to 6.8.12-20-pve from 6.17.13-2-pve to see if it helps. I have a Raptor Lake (i5-13500) processor. I will try pinning to the version you identified. I see that PCIe Passthrough...

I don't ever recall explicitly installing mdadm (but I could have just forgotten), but no, I've never used a software raid until I defined the zfs inside TrueNAS. When I do an apt remove mdadm, I do see the following list of packages to be uninstalled though: The following packages were...

And the spinners look good too, if I'm reading this right. When I spin up the VM again, I get these messages: Apr 05 18:22:36 <node> kernel: md/raid1:md126: Disk failure on sda1, disabling device.md/raid1:md126: Operation continuing on 2 devices. Apr 05 18:22:36 <node> kernel: sd 0:0:0:0: [sda]...

I removed the startup option on TrueNAS, rebooted the host, and ran smartctl to check for things: nvme0n1 is the boot SSD, so ignoring that drive. So the NVMe look good, right? Spinners in the next post due to character limits.