apologies, i should've mentioned i'm not entirely too familar with CLI -- the googling I did led me to believe it was something in /etc/network/interfaces that i needed to edit, but i'm not sure how i find/discover the details of the spare NIC i put in, in order to address it to switch it
So my network interface died. Kaput. I plugged in a spare one I had floating around but I've never messed with network devices in CLI before. Is there a way I can edit /etc/network/interfaces to tell Proxmox to ignore the dead NIC and listen to the new one I plugged in? Or is there another way...
Just an update: I tried absolutely everything I could think of. As a last resort, I decided to run a system diagnostic. Turns out one single 16GB RAM had decided to give up the ghost, it was throwing over 7 million errors. I wouldn't have believed it if I hadn't seen it for myself. Brand new...
Assuming it's corrupt as you say since I was unable to boot into rescue shell. Is there a way to reinstall Proxmox without losing all VM and LXC data on the disk?
Boot hangs at "loading initial ramdisk" ... I'm not a debian expert but I left Proxmox on default when installing so I think that would be ext4. Nope, no BIOS update or anything different. I just simply ran the latest update through the Proxmox GUI and then after a reboot it wouldn't start.. I...
I've been running Proxmox for the last few months without issue. I applied the latest update last night and now Proxmox refuses to boot any futher than "Loading initial ramdisk"
Naturally I googled what that means and it seems a few people have been stuck at this point before, yet not of the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.