Recent content by bigun89

Can we get a status update? Was I right?

100% it's the cable. That's an FS brand and I've always had trouble out of them. Intel has a compatibility chart that lists the DAC's that will work with their cards. I'm sure you can find one that will work outside of the compatibility chart, but it's a crapshoot at best and it may cause you...

The configuration looks fine. My configuration is somewhat similar, except my PBS install is virtual and is accessing a SAN and has a dedicated NIC for it - nothing I can add there. I'm starting to bank on some incompatibility in the hardware - especially since you're using twinax. Look over...

Can I see the /etc/network/interfaces files from both servers? Also, what models are these SFP+ cards? How are they connected? Twinax? Fiber? If fiber, what models are the modules? What kind of fiber is being used? I can see the OS is detecting a link, but in the world of SFP+ I've seen...

Enabled the CONFIG_VIRTIO_CONSOLE option in the kernel and the issue is resolved.

Is it possible to schedule a backup job to run right after another backup job finishes?

The proxmox hypervisor is reporting this upon boot?

I've done passthru with my Nvidia Quadro P900 to my Plex VM using this walkthru: https://youtu.be/-HCzLhnNf-A?t=679 Relevant info starts at about the 11:19 mark. On an initial glance, there's some grub config that has to happen on the proxmox hypervisor, probably more missing. While the end...

If you want a dedicated connection, I'd personally use a network that leaves no room for guesswork. PVE: 128.50.50.1 / 255.255.255.252 PBS: 128.50.50.2 / 255.255.255.252 No gateway necessary.

I'm fairly certain the issue has something to do with the serial device not populating, I think the driver is in place, so I don't know quite what to do at this point. Trying to list the socket: # ls -la /dev/virtio-ports/org.qemu.guest_agent.0 ls: cannot access...

Ok, I think I figured out my own issue, I had to delete the volume group before I could reuse the iSCSI device. Everything seems to be working now.

Ok, I used the old volume group name (SAN_VG), now the storage I had removed previous to the reconfiguration, is now back. With the files I destroyed still listed. Some very weird things are going on.

Odd, I may have found a bug, here's how I produced it. 1 - Configured a LUN with an ID of 0 2 - Setup iSCSI on Proxmox using LUN with the ID of 0 3 - Began use of LUN (put containers or VM's on it - I used it for quite some time) 4 - Setup alternate storage, and moved everything off of iSCSI to...

I have a LUN configured on my SAN, and I can add the iSCSI storage without issue. However when I attempt to configure a LVM volume on said iSCSI storage, the base volume never populates. root@homeproxmox:~# pveversion -v proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve) pve-manager: 7.2-14...

I found out what happened. After an update, my vzdump.conf got overwritten and the dump dir I had specified got removed. One of my own old thread clued me in.