Search results

If this happens again what specific logs should I be capturing to help with troubleshooting?

Thank you for direction. Is there a way I can get more details as to which specific mountpoint was not available at the time?

I had some pending updates. I rebooted the server and the container started normally. I would still like to learn what happened here if anyone can point me in the right direction. Thank you.

This morning my normal scheduled backup ran however the lxc would not start after the backup completed. Error after trying to start. lxc-start 113 20230704025941.778 INFO lsm - ../src/lxc/lsm/lsm.c:lsm_init_static:38 - Initialized LSM security driver AppArmor lxc-start 113...

I noticed the syslog was filling up with the following message over and over. Can someone help me understand what I am seeing here? Kernel Version Linux 5.15.102-1-pve #1 SMP PVE 5.15.102-1 (2023-03-14T13:48Z) PVE Manager Version pve-manager/7.4-3/9002ab8a Apr 07 23:03:56 pm systemd[1]...

Thank you for this!

So MDev is a part of VT-g which isnt available on 11th gen. Got it. Thats why I wasn't seeing MDev Type options? Looks like the iGPU is being passed successfully to the VM but the VM needs a newer kernel. Sadly I don't think OMV 5 will support anything newer then what it has at the moment. [...

Maybe it is being passed through? On my OMV VM host I see: 06:10.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4c8a] (rev 04) (prog-if 00 [VGA controller]) 06:10.0 VGA compatible controller: Intel Corporation Device 4c8a (rev 04) Subsystem: ASUSTeK Computer Inc. Device...

I replaced my i5-10600K with a i7-11700K (ASUS PRIME Z590-V MB). Booted up and Proxmox detected and identified CPU. Ran updates. Rebooted. Noticed my Open Media Vault VM which I pass through iGPU for plex transcoding is not booting. (*knew I forgot something*) VM still had the PCI passthrough...

Disabling only tso as several others have recommend seemed to do the trick! Thank you! ethtool -K eno1 tso off Added to /etc/network/interfaces as well. Have not tested to see if it survives a reboot yet.

On my American Megatrends BIOS nothing appears to have changed on its own that I am aware of. If there is a specific setting you can suggest I look at.. I gladly will.

Wanted to add: Same for all cpu* /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:intel_pstate analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency...

Testing this now.

Not sure what I did or what changed. Recently I had to reboot for some updates and to upgrade some RAM. I noticed my power consumption was about 20-30w higher than usual and I thought maybe that was because of the ram... then I recalled I dont have a cron setup for my cpu scaling governors...

[ 1979.225665] e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <1c> TDT <be> next_to_use <be> next_to_clean <1b> buffer_info[next_to_clean]...

I recently reinstalled netdata and have been receiving notifications like this: Output of ip -s link show vmbr0 20: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether fc:34:97:a1:31:7d brd ff:ff:ff:ff:ff:ff RX...

Very nice. Thank you for sharing. Installed netdata and it is logging the spikes at 84C. I find it hard to believe the drive is actually hitting that.

What are you using to generate this graph?

I am getting these errors on both of my nvme drives now as well. Just a few moments ago it got the following: This message was generated by the smartd daemon running on: host name: pm DNS domain: xx The following warning/error was logged by the smartd daemon: Device: /dev/nvme0...

Yup. It was fixed: https://git.proxmox.com/?p=proxmox-backup.git;a=commitdiff;h=171a00ca9770c02e569a1cfe6671a092cfa11fa7