So, I just realized that all my LXC do not have networking. Can someone point me in the right direction? I just upgraded proxmox hoping that would solve it but the issue remains
Just like the title says. I tried using the console to reboot manually, still no network. This is a plain vanilla install of ubuntu, unprivileged. I would not expect such an issue.
I didn't replace it, and I've already disabled and uninstalled UFW. Same issue.
[53629.876044] i40e 0000:b5:00.2 eno7: NIC Link is Down
[53629.889244] vmbr0: port 1(eno7) entered disabled state
[53641.563446] i40e 0000:b5:00.2 eno7: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: None...
I see a lot of these in dmesg
I did disable the pve firewall and then installed UFW. Perhaps I botched it?
I also see a ton of these on boot:
[ 54.788646] i40e 0000:b5:00.2: Error I40E_AQ_RC_ENOSPC, forcing overflow promiscuous on PF
[ 54.788752] i40e 0000:b5:00.2: Error...
I believe what happened, was when I was creating the LVs manually, the old proxmox 4 debian install is still showing up first in search results. So I ended up with a weird configuration. Based on this post, disabling the mounting of the data lvm-thin is the proper solution...
And even more than help, I'm looking for the fundamentals of how this Data LV is supposed to work with proxmox.
Is it just an LV?
Do you create a file system on it?
Are we supposed to mount /dev/pve/data at /var/lib/vz?
If I don't mount it, how is it showing as fine in proxmox and I can...
So, I believe I have a fundamental mistake in my setup, and I'm really hoping someone can help me resolve it because I'm definitely new, and having a rough time figuring out the "proper" way to store data in proxmox.
I initially set up this host with a manual install of proxmox on debian...
I was able to solve this by comparing my storage.cfg to the default and removing a line. I think you’re right I did have to recreate the lm without a file system but now I can’t remember. Thanks for the help.
I got that exact switch 3 weeks ago and I hate it. I wish I wouldn't have updated to the newest firmware, it's worse now than before. Have to unplug the power on the switch in order to get it to activate a new sfp+ plugged in. Unacceptable
I had to expand my root LV, so I deleted my LV data, and then expanded root, that went fine. This was the process:
sudo rm -rf /var/lib/vz
sudo lvremove /dev/pve/data -y
sudo lvcreate -y --zero n -l 100%FREE -T -c 256K -n data pve
sudo mkfs.ext4 /dev/pve/data
But now when I try to restore...
I actually solved this by running fsck on the nvme after returning it to the previous port. I had a pcie riser cable laying around so I’m just gonna call this solved for now. Happy to hear the right way to do it though.
So, I’m new to lvms and lvs and vgs and so on. I worked my way through a Debian buster install and then proxmox on top of it because my zfs had a feature that required it vs normal install.
But I believe I was able to replicate the normal disk setup. i have two partitions on my nvme, boot and...
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.