Search results

I changed the connectors ( another pair of brocade ), same OM3 cable, and link is back up. SO either 1 or both of the previous connectors is the culprit

I didnt know an OM3 cable can be so sensitive. I will try the suggestions and revert with my results Thank you

Actually, I am using the same OM3 cable + brocade sfp+ connectors. Yes, the same cable works fine with other devices for both switches

I migrated all my network connections from a brocade icx7250 to another identical one with exactly the same vlan settings. When I move the sfp+ cable from one of my nodes to the new switch, the network line goes down. I put the sfp+ cable back to the old switch and the link came back on. Both...

it is a xfs boot disk. no zfs unfortunately. it was a single intel S3500 480gb I am able to boot the node again, but it will predictably go into the same error and go down when I tried to backup any of the vms

Is it the proxmox boot disk? If I do a brand new proxmox install , would that still keep all my data already in the VMs?

Any help /direction greatly appreciated!

One of my proxmox node sudden has log i/o error -5 File system shut down due to log error multiple "write-error on swap-device " errors. I cant do anything with it. Please help salvage my node, or do I need a new proxmox boot disk? Much thanks!

I got desperate . So I took remove the node from the cluster and joined it back again

One node in my cluster of 5 no longer is seen by the other nodes. This was after a power outage, and whilst I can restart the other nodes with no issues, this one cannot start its VMs because it has no quorom. It can ping to all the nodes but it cannot see the other nodes. pvecm status shows...

I have a similar problem where I no longer can see or access the other nodes in my cluster via the GUI. cat /etc/pve/corosync.conf root@b360m:~# cat /etc/pve/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: 800G1 nodeid: 1 quorum_votes: 1...

Thanks! This is the exact step by step way to resolve the r8169 driver issue: https://medium.com/@pattapongj/how-to-fix-network-issues-after-upgrading-proxmox-from-7-to-8-and-encountering-the-r8169-error-d2e322cc26ed

This is a Dell wyse 5070 with just 1 ubuntu VM. It loses LAN connection and will not reconnect until I shutdown and start up again This is the console output: r8169 0000:01:00.0 enp1s0: rtl_ephyar_cond == 1 (loop: 100, delay:10) r8169 0000:01:00.0 enp1s0: rtleriar_cond == 1 (loop:100...

Just wanna update that I can at least get the ubuntu VM to boot by by adding host kernel boot argument pcie_port_pm=off to /etc/default/grub

is this related to google coral TPU being a A+E M.2 or mini pcie format?

I have a google coral tpu in wyse 5070 (CPU J4125) that I am trying to passthrough to ubuntu VM. The VM cannot start if I add the coral TPU. The wyse is running proxmox 8.02 This is the error message vfio-pci 0000:02:00.0: unable to change power state from D3cold to D0, device inaccessible Any...

I have PBS installed as a container in a proxmox 7 host, with CIFS share from a truenas server as its storage. It was working fine until a reboot (after recent proxmox updates) and now it has no network connection. The other VMs on the same host are fine. "hostname 'PBS' does not resolves to...

This is the error msg again when i try to start nut-snmp root@X10SLM:~# systemctl status nut-server.service ● nut-server.service - Network UPS Tools - power devices information server Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor pr> Active: failed (Result...

actually thats exactly how I did it in the link you posted What I cannot figure out is the error messages that came with a new proxmox install. it was fine with the previous proxmox install (also 7.0)

the APC SUA1000 that I am using manual suggest that if I use the AP9617 network card(which I do for the snmp), then i should NOT connect up via USB