Recent content by epicurean

  1. E

    Warning: UPDATING these packages broke my pci passthrough.

    Is there any new fix or update to this error? I am getting the same type of error with USB 3.0 PCIE controllers in 2 Windows 10 VMs, and the USB ports will be unresponsive. A Proxmox server restart will enable the USB ports again but the same error shows up error writing "1" to...
  2. E

    network link goes down when moving sfp+ cable from one switch to another (identical settings)

    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
  3. E

    network link goes down when moving sfp+ cable from one switch to another (identical settings)

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

    network link goes down when moving sfp+ cable from one switch to another (identical settings)

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

    network link goes down when moving sfp+ cable from one switch to another (identical settings)

    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...
  6. E

    Proxmox node crashes with write-error on swap drive

    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
  7. E

    Proxmox node crashes with write-error on swap drive

    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?
  8. E

    Proxmox node crashes with write-error on swap drive

    Any help /direction greatly appreciated!
  9. E

    Proxmox node crashes with write-error on swap drive

    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!
  10. E

    [SOLVED] Node not in cluster after reboot.

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

    [SOLVED] Node not in cluster after reboot.

    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...
  12. E

    Cluster broke down; no longer can access GUI

    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...
  13. E

    proxmox 8.0 server loses connection after a few hours

    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
  14. E

    proxmox 8.0 server loses connection after a few hours

    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...
  15. E

    Unable to start ubuntu VM trying to passthrough a google coral TPU

    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