Recent content by NevadaTech

NOT SOLVED - I just don't see a way to change the title back :( Blah. After a few days the CPU/unified memory error has returned. I have not seen the AMD-Vi error return - I'm sticking with the IOMMU set to Enabled (vs Auto) was the fix for that. Current plan is to swap the memory from the...

Yes, I agree completely. The similarity+constant is why I thought the DIMM was bad. In one maintenance window I pulled the RAM and installed it reverse order. I also let the mobo dictate the default memory settings. I sure there are ways to eek out 10% more performance if I tweaked settings but...

About 2 days ago I updated the AMD-microcode waited for a couple hours and no CPU/memory errors showed up on the console, the AMD-Vi wait loop still appeared but it seemed a little less frequent (seemed or reality?) shutdown I then went into the BIOS and set the IOMMU to Enabled instead of...

Here's another cut from today's console messages dumped via dmesg. I'm leaning to the microcode because the error cache level: L3/GEN, tx: GEN, mem-tx: RD seems to reference the L3 cache of the CPU. And the AMD-Vi error is related to IO-MMU. To me, with the other things tested, that leaves...

Hello, I have a server crashing and I'd like some help. Please! Over the last couple weekend I've had a small maintenance window where I could take it offline for a couple hours. This weekend is a longer window so I'd like to get as much testing in as possible. So far I've taken the server...

Oy, bit by this bug also. Extra input... I wasn't sure which disk was my booter, other posts say 'EFI BIOS' partition, I have 'BIOS boot' and 'EFI System' partitions, so which is it? for me it was the EFI System partition my guessing was based on listing devices and I saw /dev/nvme0n1p2 had an...

Necro I know Thanks! A quick fix for me. I did not need to delete the lock-frontend. A Refresh and Upgrade proceeded normally. On PBS 3.2-7

Up vote this! Thanks, worked for me on Proxmox 8.1.10 host with an Ubuntu 22.04 guest. Remember to always install your qemu-guest-agent when you build your guests.

This fixed things. Thanks Lee for pointing me to check for the LVM. For others, if you follow the bytefreaks instructions, they mostly work. After the passwd -S bob; this gets you the (S)tatus of the user's passwordd; then follow that up with a passwd bob; to actually set your password

I believe you are correct about the LVM. Hah! I was searching for a fix and wound up on the same bytefreaks page.

and one with the lsblk /dev/sda

here's a pic of the output

Hello, I have a vm/guest that the password listed does not work. Sigh. This is the guest not the host. The guest is an Ubuntu 22.04 server. Proxmox 8.1.10 The normal process of boot into single user mode then resetting passwd should work, but... the guest boots too fast. I cannot use the Shift...

While poking around last night I noticed this * I still couldn't ping my ISP gateway * when I looked at the streaming firewall logs there was a bunch of traffic hitting the router, the traffic was a mix of private and public IP; that was a big help, it kinda said the basic plan/setup was correct...

So this setting is wrong. Some of the other post/setups that referred to this were router behind router (double NAT) setups. If your WAN DHCP gives you a 192.168.x.x or 172.(16-32?).x.x or 10.x.x.x address then you do need it. Most cases don't.