Search results

From this very forum. Credit goes to @gfngfn256. He's a google-fu master. :cool: I always install via shell installer direct from Nvidia. bad idea?

Previous versions of 6.8.12-x-pve series requires this boot option `thunderbolt.host_reset=false` to work (I'm using grub). But that option don't appear to work with 6.8.12-4-pve. Never mind. Reboot the node and it's back online. So the above option still works (Unsure why it didn't work...

Why not try 6.8.12-1? That has an update to fix a null pointer exception (unsure if it's the same bug as yours but can't hurt to try).

It was the latest 6.5 from proxmox. Note what works for my setup may well not work on others, there's really a YMMV on this. There seems to be a lot of unknowns and I honestly cannot find a pattern.. E.g. I know of a cluster setup with 3x Lenovo P3 Ultras (IIRC)... I can't remember if they're...

FWIW I've updated to the latest Intel microcode (i9-13900H) back on 6.8.12-1... Been 7 days without trouble. Don't think this CPU is affected by the high current bug, however it does seem this latest microcode also limit the turbo mode more compared to previous firmwares (really hard to tell so...

Anything you can see in the console? Is it a hard freeze, or is there a kernel stack trace? Try switching back to 6.5 and see how it goes.. If that works for you pin it. FWIW I'm back on 6.8.12-1 after updating to the latest intel microcode. Been stable for around 3 days (but still counting).

Anybody can help identify what's wrong here? I will probably look for a USB serial to better diagnose this. The latest kernel 6.8.12-1 seems to be pretty unstable in my setup. Kernel almost always crashes when that node is doing daily backups. 6.8.x is a hit and miss for me, sometimes it just...

CPU is a i9-13900H, 64 GB of RAM. Ran memtest86+ when I first got this. Prob 6 months old now and never ran mem test again. Will try to find a time to retest. Microcode is on 20240531-1. Will have to setup something to monitor thermals & cooling I guess.. Great tips, thanks. No... 6.5 is...

Wish I'm this lucky.. Just had a hard crash on this problem node with 6.8.8-1 (Was trying to compile an application which is pretty CPU intensive). Nothing on the console, nothing useful in the journal from last boot. Jun 25 09:43:51 pve-3 sshd[530192]: Received disconnect from 172.16.b.c port...

That worked! I'll start testing 6.8.8-1 now and see how it goes. Will report back. Quick update: So far so good.. Did a VM backup, copied a 40 GB file back and forth between the VM and a NFS share... Did see 2x split lock traps but VM didn't freeze. No kernel panics on host. So sustained I/O...

Yup. Dependency confirmed resolved and the stray 6 packages are updated now. Will schedule for a reboot later today and see how it goes. Update: No go with kernel 6.8.8 for me as hitting a driver issue with my QNA-T310G1S dongle. No access to Windows machines with Thunderbolt so I can't even...

Thanks. Going to revert the custom kernel boot params and continue to test. Getting various issues trying to apply updates. First, I get these: W: (pve-apt-hook) !! WARNING !! W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'! W: (pve-apt-hook) W: (pve-apt-hook) If...

Focus is on zero kernel panics so didn't look for any downsides.. No side-effects AFAICT (Other than the split-lock issues that only showed up after I applied your suggest boot config). No apparently slowdown on NVMe throughput (didn't perform any benchmarks though). Time will tell.. Just...

It's been more than 2 weeks since I applied the changes suggested by jsterr. Happy to report the node is stable so far. Going to re-enable VM backups on this node and that will be the ultimate stability test. Fingers crossed.

What do you mean? Don't have to restore from any data? It's pretty easy to use an older kernel. Just download the kernel (if it's not already there, e.g. when upgrading from an older version of Proxmox). and then run something like this: proxmox-boot-tool kernel pin 6.5.13-5-pve To re-use...

Trying this now... Tried so many things: 1. Disable cstates 2. Disable e-cores 3. Pin to older kernel 4. Trying different Intel microcode. (Tried the May release yesterday and kernel panic overnight) But every time the NVMe is hit hard (e.g. doing a backup), the kernel will sometimes crash...

When did you run this trigger? As mentioned previously you can only run this command when the task progress is at about 96-98%.. Any earlier wouldn't work, and any later is too late.

You have to run the udevadm trigger command at the 98%, else it will not work. The problem only happens around that 95% mark. At that point the entire LVM sub-system is not working. Commands like lvdisplay etc will hang. Run udevadm trigger and the LVMs will work again. And when LVM is working...

pve-firewall is a feature/part of Proxmox, so you're not using any additional software.

Here're some tips after I tried restoring my firewall VM (Untangle) onto proxmox. 1. First up, make sure Proxmox firewall (pve-firewall) is not a problem. SSH to your PVE and run "pve-firewall stop" and see if everything works now. If it's still broken, continue to step 2. 2. Are you using...