Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 547

[ensall]

Not sure when the issue actually started happening but I logged in to setup a new test VM and when I went to start it it immediately failed when I had a vNIC setup on it. After removing the vNIC to test further I was then unable to get a console to open up to it. I checked my 2 other running VMs and the console fails to open on them as well. Each error I get always starts with the line I used in the title. All of my currently running systems are fine and accessible at the moment. The only major change was in mid-December I ran the upgrade from 6 to 7 and haven't attempted to create a new VM since then. Any tips on where I should look? I've verified that I can run an apt update and an apt upgrade but it finds nothing at the moment. I haven't tried restarting the system yet which I've found some old references to trying in different forums across the internet.

Error when trying to open a VNC console to a currently running system:
()
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 547: elf_machine_rela_relative: Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed!
TASK ERROR: Failed to run vncproxy.

Error when trying to start the newly created VM with a vNIC:
Inconsistency detected by ld.so: ../sysdeps/x86_64/dl-machine.h: 547: elf_machine_rela_relative: Assertion `ELFW(R_TYPE) (reloc->r_info) == R_X86_64_RELATIVE' failed!
kvm: -netdev type=tap,id=net0,ifname=tap205i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on: network script /var/lib/qemu-server/pve-bridge failed with status 32512
TASK ERROR: start failed: QEMU exited with code 1

 

[ensall]

Apparently I'm also unable to run any of the pvenode commands for this same reason. I'm guessing a reboot may be my best next step potentially.

 

[ensall]

Looks like I'm having some LVM issues with my large data pool that I'm going to have to try and work through to recover from the looks of it. One disk isn't activating properly

 

[ensall]

May possibly be having a drive with some upcoming issues. Manually deactivating the lvm with vgchange <lvm name> -an then vgchange <lvm name> -ay got it back online and the server seems happy again. SMART is showing PASSING on everything but the oldest drive is probably 6 years old now and the newest is maybe 3 with near constant on time and who knows how many reads and writes at this point so it's probably time to check into new storage for it