Search results

I do not have multi-path. The only connection to the SAN portal IP as defined in the iSCSI dialog is via a Layer2 VLAN. To that end, I do see two connections on the SAN for each node, which would seem to imply multi-path. But based upon the network design, the unexpected connection is from...

Posting from both nodes as there are differences. root@proxmox-1:~# pvs WARNING: Not using device /dev/sde for PV l12ZPk-uvn7-5B0E-4eIh-XdGA-IPe2-eGsGs8. WARNING: PV l12ZPk-uvn7-5B0E-4eIh-XdGA-IPe2-eGsGs8 prefers device /dev/sdd because device was seen first. PV VG Fmt Attr...

Yes, I am using ext4. Mainly because I couldn't create an LVM using the iSCSI LUN. I created a new iSCSI instance on the EMC and have been messing with it. I have it in storage, but cannot create an LVM. When I try, I get: create storage failed: device...

What I have: 2 x HP DL380 G7's 1 x EMC SAN presenting 4.7TB via iSCSI Cisco-based network Each server has four NICs connected as such: enp3s0f0/vmbr0 - Managment enp3s0f1/vmbr1 - 802.1q Trunk for VM connectivity enp4s0f0/vmbr2 - iSCSI (this is a L2 VLAN, no routing in or out) enp4s0f1/vmbr3 -...

Welcome. I always try to do that. If I had trouble, perhaps someone else is or will experience the same thing. I haven't opened a new thread yet, but likely will as i'm beating my head against the wall.

Resolved. Tracked down to a VLAN/port mix up between storage and migration networks. I tracked it down by pinging each node's iSCSI IP from each node and then trying to ping the SAN. On my new node, I could not ping the SAN, so I followed that rabbit. Migration is still not working as...

Following instructions found here: https://pve.proxmox.com/wiki/Cluster_Manager Did a fresh install and after creating the cluster on an existing node, I went thought the join process via the web GUI. After completing it, I appear to have a cluster. So I decided to play with a machine...

Correct, In the case of the above screen shots, there was no local storage beyond a DVDR and the USB drive. I will run that command with the USB drive in and report back.

HP DL380 G7 96GB of RAM Diskless, booting from USB and using iSCSI. This is my second proxmox server, the first one is identical HW with a little less RAM, but it does use local storage. It also boots from USB. I do not recall having these issues before. What's funny is the installer reports...

I have no access to the managment interface, vmbr0, or it's associated physical interface. Vmbr1 is up (trunked) and VM's are running. If i need to do something with the VM's I either have to go to the console or ilo to the console and run qm from the shell. Again, no hardware has changed...

vmbr0 is toast. So no management via web, ssh, etc. Nothing I do seems to bring it back. vmbr1 is up, so those VM's that 's either started from the physical console or via ilo are running normally. But I have no easy way to admin the box. I don't sit in front of the console and have a...

Ok, I can grep it out and take a pic of the interface, but it is there. And f1 is vmbr1, which is feeding the VM's, f0 is vmbr0 which is the management interface. And no changes were made. I merely ran updates, which appeared to hang in the web interface. I came back everal hours later. So...

With no management interface, I'm stuck with taking pictures of the monitor either live or in ilo. Attached is the /etc/network/interfaces The output of ip a is ~136 entries, so not sure how to capture that in its entirety.

I've been running proxmox on a DL380G7 for a couple of years. I've slowly been migrating machines from an old ESXI server. Yesterday, while troubleshooting an unrelated network issue, I noticed that I was significantly behind on updates so I upgraded using the option in the web gui. Upon a...