Hey all,
Pretty new to Proxmox and all, and recently I got my setup for my home network and everything up and running. What came next was getting Proxmox up and running on my Dell R710 and we'd be all set. Getting it installed had its own quirks (as enterprise hardware does) but it was running smooth.
After getting a test enviornment set up on something on a more readily accessible VLAN I got the system switched over to the proper subnet and VLAN A-OK and rebooted it. I noticed that it of course didnt crop up when it rebooted. Checked the console and it was fine, but I remembered for quick and dirty troubleshooting it was in a port on the wrong VLAN (in this case VLAN 50 instead of 40). So I redid the cables to make them a bit neater as a whole and got it plugged into the right ports for the proper VLAN Access.
It still didnt make the web interface come up so I rebooted the system again, as it seems it needs that for networking changes, annnnnnd now the entire thing is kaput.
Attached is the image of the output I get on boot.
The only other things that occured before this was me setting up Bridges for the 8 Ethernet ports i have on the system, assigning them IPs, and getting everything under the same VLAN. I had a total of 8 Linux Bridges for each port, with VMBR0 - VMBR7.
My intention was simply to assign a bridge per VM, as some of these will serve as game servers, while others as little enviornments for me to mess around with in my homelab as little virtual computers on their own ports.
The sytem has one VM thats setup, listed with a VMID of 400, 12GB of RAM, and a 64GB disk.
I do have a RAID Controller, a PERC H700 I believe, with two 500GB disks each in their own single Raid 0 as to act as a passthrough (one of which has the PROXMOX install on it) and a RAID 5 containing a bunch of little 250GB drives to make a >1TB pool that I had hoped to use for handing out to VMs.
Theres nothing critical on this setup, if I have to send it to Valhalla and reinstall thats fine. I just want to know why this happened and how do I prevent it from happening again. As I fully assume this is either Enterprise hardware being quirky, or I scuffed something up when messing with those interfaces.
The current BIOS is 6.2.3, however, I plan on updating this to the latest version both for troubleshooting, but also it sounds like having the latest version helps smooth out some quirks with any OS you run on it, but also allows for faster ram configurations and can help reduce general issues with RAM.
Any help or input would be appreicated. Cheers
Update: Pushing the BIOS to 6.6.0 (latest version) did not fix the issue
Pretty new to Proxmox and all, and recently I got my setup for my home network and everything up and running. What came next was getting Proxmox up and running on my Dell R710 and we'd be all set. Getting it installed had its own quirks (as enterprise hardware does) but it was running smooth.
After getting a test enviornment set up on something on a more readily accessible VLAN I got the system switched over to the proper subnet and VLAN A-OK and rebooted it. I noticed that it of course didnt crop up when it rebooted. Checked the console and it was fine, but I remembered for quick and dirty troubleshooting it was in a port on the wrong VLAN (in this case VLAN 50 instead of 40). So I redid the cables to make them a bit neater as a whole and got it plugged into the right ports for the proper VLAN Access.
It still didnt make the web interface come up so I rebooted the system again, as it seems it needs that for networking changes, annnnnnd now the entire thing is kaput.
Attached is the image of the output I get on boot.
The only other things that occured before this was me setting up Bridges for the 8 Ethernet ports i have on the system, assigning them IPs, and getting everything under the same VLAN. I had a total of 8 Linux Bridges for each port, with VMBR0 - VMBR7.
My intention was simply to assign a bridge per VM, as some of these will serve as game servers, while others as little enviornments for me to mess around with in my homelab as little virtual computers on their own ports.
The sytem has one VM thats setup, listed with a VMID of 400, 12GB of RAM, and a 64GB disk.
I do have a RAID Controller, a PERC H700 I believe, with two 500GB disks each in their own single Raid 0 as to act as a passthrough (one of which has the PROXMOX install on it) and a RAID 5 containing a bunch of little 250GB drives to make a >1TB pool that I had hoped to use for handing out to VMs.
Theres nothing critical on this setup, if I have to send it to Valhalla and reinstall thats fine. I just want to know why this happened and how do I prevent it from happening again. As I fully assume this is either Enterprise hardware being quirky, or I scuffed something up when messing with those interfaces.
The current BIOS is 6.2.3, however, I plan on updating this to the latest version both for troubleshooting, but also it sounds like having the latest version helps smooth out some quirks with any OS you run on it, but also allows for faster ram configurations and can help reduce general issues with RAM.
Any help or input would be appreicated. Cheers
Update: Pushing the BIOS to 6.6.0 (latest version) did not fix the issue
Attachments
Last edited: