Recent content by CCWTech

Yes, I finished the upgrade, just asking if there is anything to prevent it.

Maybe I will run a reboot command with a 30 minute timer on the ones w/o OOB. Then if it doesn't stay online during the upgrade at least I will have a way to get back in assuming the reboot works fine! :)

I was able to get in and finish the upgrade. My main reason for posting is to see if there is anything I can do to prevent lockups on future upgrades where OOB isn't an option.

root@tch-phy:/etc/network# dmesg | grep eth [ 1.279165] tg3 0000:13:00.0 eth0: Tigon3 [partno(N/A) rev 5720000] (PCI Express) MAC address 94:40:c9:13:aa:1c [ 1.279169] tg3 0000:13:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [ 1.279171] tg3...

root@tch-phy:/etc/network# cat interfaces # network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory'...

root@tch-phy:~# ifreload -a -d debug: args = Namespace(all=True, currentlyup=False, CLASS=None, iflist=[], noact=False, verbose=False, debug=True, withdepends=False, perfmode=False, nocache=False, excludepats=None, usecurrentconfig=False, syslog=False, systemd=False, force=False...

Just did another one that got stuck here: Warning communications lost with UPS 98% Progress. This one I can still SSH into so not a huge deal (and I do have OOB on this server as well), but not sure why I am running into stuck updates...

I have been doing a number of 6 to 7, and 7 to 8 upgrades without many problems. However today, I encountered an upgrade that got stuck on "Reloading network config on first install" Progress 96%. Luckily, this server (which is remote to me) has out of band (OOB / HPE ILO) and I am not stuck...

Still crashes with 6.5 Kernel. Any other ideas?

Still having instability. Trying 6.5 Kernel.

This is my CPU: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 48 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Vendor ID: AuthenticAMD BIOS Vendor...

Added amd64-microcode Changed CPU type to host Testing now...

Virtio-Win-0.1.240 I'll monitor logs and post here if something remarkable shows up. It will reboot okay after installation, but after that it becomes really unstable.

proxmox-ve: 8.0.2 (running kernel: 6.2.16-19-pve) pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390) proxmox-kernel-helper: 8.0.3 pve-kernel-5.15: 7.4-6 pve-kernel-5.11: 7.0-10 proxmox-kernel-6.2.16-19-pve: 6.2.16-19 proxmox-kernel-6.2: 6.2.16-19 proxmox-kernel-6.2.16-15-pve: 6.2.16-15...

bios: ovmf boot: order=virtio0;net0 cores: 6 cpu: x86-64-v2-AES efidisk0: local-lvm:vm-102-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M machine: pc-q35-8.0 memory: 8192 meta: creation-qemu=8.0.2,ctime=1699376846 name: Windows11 net0: virtio=3A:0B:D2:AC:4E:1F,bridge=vmbr0,firewall=1 numa: 0...