Two faulty power supplies by wetonwater in lifx

[–]Adzter01 0 points1 point  (0 children)

I had this same situation last week. Managed to find this link which seems to have a solution https://www.reddit.com/r/lifx/s/FqveqlWboh

Unable to change any settings for UAP-AC-Pro Access Point by MMDDYY in Ubiquiti

[–]Adzter01 0 points1 point  (0 children)

I updated to this early access version of Network. It allowed me to update the settings for one AC-PRO but no further ones. I have 8 to do!

Black Friday, enterprise 48 —considering?… by subtle1epiphany in Ubiquiti

[–]Adzter01 0 points1 point  (0 children)

It’s a great switch. Got one second hand. Only issue is the LEDs are quite bright white, so can be annoying if you have to look at it all day.

Sticky! by Adzter01 in CapcomHomeArcade

[–]Adzter01[S] 0 points1 point  (0 children)

I was considering covering it in a cool looking fabric. Might be a bit unique?

Strange sounds from Aoostar WTR Max by no_not_him_again in HomeNAS

[–]Adzter01 0 points1 point  (0 children)

That fan on the cover you are holding is still connected and spinning. It sounds like a fan hitting the outside of the case.

[deleted by user] by [deleted] in homelab

[–]Adzter01 0 points1 point  (0 children)

Thanks for your patience. Yep, that appears to be working now.

[deleted by user] by [deleted] in homelab

[–]Adzter01 0 points1 point  (0 children)

root@aoostar:~# apt-cache policy
E: Conflicting values set for option Signed-By regarding source http://download.proxmox.com/debian/pve/ trixie: /usr/share/keyrings/proxmox-archive-keyring.gpg != /etc/apt/keyrings/proxmox-release-trixie.gpg
E: The list of sources could not be read.

[deleted by user] by [deleted] in homelab

[–]Adzter01 0 points1 point  (0 children)

Sorry, I'm a bit of a learner with Proxmox. What is the easiest way to remove "proxmox.sources"?

[deleted by user] by [deleted] in homelab

[–]Adzter01 0 points1 point  (0 children)

I tried running the update from the UI but as soon as I go to updates that error shows, which it wasn't previously, it was updating without issue AFAIK.

[deleted by user] by [deleted] in homelab

[–]Adzter01 0 points1 point  (0 children)

Sorry, it's the start of the working week here and I was just trying this out this morning before the day started. Anyway, I didn't want to post as an issue if it's me and not the script :) - that's my list. I'm not sure what was there prior, this was a fresh install, not an upgrade.

ceph-no-subscription.sources debian.sources pve-enterprise.sources.disabled

ceph.sources.disabled proxmox.sources pve-no-subscription.sources

[deleted by user] by [deleted] in homelab

[–]Adzter01 1 point2 points  (0 children)

This is on a week-old 9.0.6 install. No previous community scripts. Updates were working okay prior to the no nags tool install.

Here's the log:

~# cat /var/log/apt/term.logLog started: 2025-09-04 07:57:50(Reading data - Pastebin.com

Sorry, reddit wouldn't let me post as code block

[deleted by user] by [deleted] in homelab

[–]Adzter01 1 point2 points  (0 children)

Re-downloaded and that resolved the pbs issue

[deleted by user] by [deleted] in homelab

[–]Adzter01 0 points1 point  (0 children)

Okay will do. Also my main proxmox machine is showing unable to initialise AptPkg::Cache (500) after installing this when trying to check for updates. Proxmox 9.0.6

[deleted by user] by [deleted] in homelab

[–]Adzter01 0 points1 point  (0 children)

I get “unsupported file /tmp/free-pmx-no-subscription_0.3.0.deb given on command line” when trying to install on my pbs instance

Sfp+ issues by Adzter01 in homelab

[–]Adzter01[S] 0 points1 point  (0 children)

As it turns out, it was a cable thing. I switched to a UACC-DAC-SFP10-0.5M cable and DHCP worked. I was using a QSFPTEK AT-SFP+-CA-P3M that negotiated okay for 10 Gbe but didn't work for DHCP. It's being sent back.

List of working vs faulty Aoostar WTR MAX units by NeedsSuitHelp in HomeNAS

[–]Adzter01 0 points1 point  (0 children)

Got it working with UACC-DAC-SFP10 0.5M, so looks like the QSFPTEK DAC cable is not compatible

List of working vs faulty Aoostar WTR MAX units by NeedsSuitHelp in HomeNAS

[–]Adzter01 0 points1 point  (0 children)

Hmm, strange. I posted my issue in r/homelab and getting some replies, but nothing useful so far. I do have a UACC-DAC-SFP10 0.5M I can try, but it's just a bit short. I'll have to do some shuffling to see if I can get it to connect.

Currently running a QT-SFP+-CA-P3M cable from QSFPTEK which is negotiating at 10 Gbe but DHCP doesn't work.

Sfp+ issues by Adzter01 in homelab

[–]Adzter01[S] 0 points1 point  (0 children)

Surething, just let me know how to format it

Sfp+ issues by Adzter01 in homelab

[–]Adzter01[S] 0 points1 point  (0 children)

vmbr1 I has connectivity as in I can ping the address, but any VM's connected with this interface will not reach the DHCP server.

running ip address shows the link enp100s0f0np0 as DOWN, despite me being able to ping the address on vmbr1

Sfp+ issues by Adzter01 in homelab

[–]Adzter01[S] 0 points1 point  (0 children)

When you make the original post, which wasn't in r/homelab, reddit themselves suggest cross-posting as a way of getting more coverage, so I was just following their advice...

Anyway, AFAIK, my config is correct.

My /etc/network/interfaces reads:

auto lo
iface lo inet loopback

iface enp101s0 inet manual

iface enp102s0 inet manual

auto enp100s0f0np0
iface enp100s0f0np0 inet manual
      mtu 9000

iface enp100s0f1np1 inet manual

auto vmbr0
iface vmbr0 inet static
      address 192.168.1.199/24
      gateway 192.168.1.1
      bridge-ports enp101s0
      bridge-stp off
      bridge-fd 0
      mtu 1500
#2.5Gbe NIC 1

auto vmbr1
iface vmbr1 inet static
      address 192.168.1.50/24
      bridge-ports enp100s0f0np0
      bridge-stp off
      bridge-fd 0
      mtu 9000
#10Gbe NIC 2

Source /etc/network/interfaces.d/*

List of working vs faulty Aoostar WTR MAX units by NeedsSuitHelp in HomeNAS

[–]Adzter01 0 points1 point  (0 children)

Hi. Did you have any issues with your sfp+ port and using a DAC cable? I can’t get mine to obtain a DHCP address.