I might type a more clarified response later as I'm kinda mentally drained right now... but somehow against all odds I SUCCESSFULLY RECOVERED MY 9 GUESTS FROM MY OLD SERVER!!!!!! i couldn't / wouldn't give up hope.. i've spent so much time over the last week trying to recover my guests which...
I successfully added all of the suggested kernels in chroot and was able to select them in the proxmox boot menu.. each one kernel panicked at the same spot. i am now going to leave the server running memtest overnight. i have noticed that there are at least 2 newer versions of the motherboard...
Sadly this hardware is extremely old... I was given a 24 thread system from a friend years ago and the system has been running 24/7 for some time. I obviously regret ever typing anything into terminal a few days ago. If I make it out of this I plan to upgrade to more modern hardware and...
I didn't realize the photos were hard to read as I had reduced their filesize to fit as an attachment to this forum. I know that the grub menu shows a pve-kernel of 4.x something (off of memory and I'm not in front of it now) I am happy to copy the output of pveversion -v if you think it would...
thank you for taking the time to reply. i will gladly try a separate drive to ensure it is not a hardware issue. i feel like i'm so close to resolving this and that is is something to do with grub (i could be wrong)
I was looking into...
i decided to keep jabbing at it to make it worse... at least i didn't succeed in making it worse. i went back into the debian live usb and updated from 5 to 6 and then 6 to 7 using chroot.. my pveversion -v at least now shows everything updated and even zfs-utils-linux is installed properly...
i went back into the debian usb live and got a pve version. i assume its not good to be showing a proxmox-ve version of 7.4.1 while the manager is showing 5.4.3 but what do i know. i also see that zfsutils-linux is not correctly installed. i'm gonna wait and see if anyone here has any...
I managed to get something to update while in chroot.. now when i try to boot proxmox it makes it past importing the pool i think.. at least im not getting that error anymore... now its just a kernel panic.
i've made more progress.. i decided to switch to a debian 9 live usb
following the steps listed here https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/Debian%20Stretch%20Root%20on%20ZFS.html#rescuing-using-a-live-cd
# zpool export -a
# zpool import -N -R /mnt rpool
# zpool import...
I made it a bit further... i found this..
mount -o bind /lib /mnt/lib and mount -o bind /lib64 /mnt/lib64
which allowed me to successfully chroot into /mnt
however i am getting error while loading shared libraries libapt-pkg.so.5.0 cannot open shared object file: no such file or directory now...
I rebooted the live usb to try again... i was able to mount the pool pve1 to /mnt but still get stuck at chroot... no matter what i do i keep getting no such file or directory
Hello all, I'm back again because I've managed to brick my promox again. I was attempting to finally update my proxmox 5 setup... didn't realize I was so outdated. I was getting numerous issues resolving the repositories... even just updating the 5 to the latest version before attempting to...