Recent content by zenny

I had the same issue. The SSD gets detected with other OS except Proxmox9. It was detected by Proxmox7 earlier. Even `lsblk` did not detect the SSD!

I did check with other computers and switches and still the issue persists. Seems like there must be something wrong with either with the connectors or the cable itself. Anyway thanks for your attention and suggestion. Cheers,

I have switched to the Cat5.E patch cable and the Gigabits started working. # ethtool enp2s0f0 Settings for enp2s0f0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full...

Hi, I installed PM9 using the default installer. I have 2 Gigabit NICs built-in in Supremicro H8DGU mobo as of below and I am connected only to a single port: # lspci | grep -i Ethernet 02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) 02:00.1 Ethernet...

I have posted the solution in https://forum.proxmox.com/threads/good-signatrue-yet-shows-up-gpg-error-no_pubkey-dd4ba3917e23bf59-on-apt-update.156721/post-716694 if you are interested. Indeed, it was a bumpy ride. Thanks.

Thanks @fabian and @sterzy for your inputs. However, after going through several issues similar to mine, I went through two interesting posts viz. https://www.linuxuprising.com/2021/01/apt-key-is-deprecated-how-to-add.html and...

To be honest, it has been working with 751. I shall try with 755 and get back to you (update didn't work with `drwxr-xr-x 2 root root 4.0K Oct 31 10:04 trusted.gpg.d/` either! Fyi, I have the following file system status: # stat /etc/apt/trusted.gpg.d File: /etc/apt/trusted.gpg.d Size...

Nope, it was by default 644 as other keys as evident from below: # ls -lah /etc/apt/trusted.gpg.d/ total 92K drwxr-xr-x 2 root root 4.0K Oct 31 10:04 ./ drwxr-xr-x 8 root root 4.0K Sep 24 2021 ../ -rw-r--r-- 1 root root 8.5K Mar 18 2023 debian-archive-bookworm-automatic.gpg -rw-r--r-- 1 root...

There is nothing else other than what was minimally required to run proxmox7 is installed as evident from the `apt policy` output. Nothing other than debian11 bullseye repos are activated. # apt policy Package files: 100 /var/lib/dpkg/status release a=now 500...

Thanks for your reply. The location of the gpg key and file permissions looks alright as follows: # ls -lah /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg -rw-r--r-- 1 root root 1.2K Dec 14 2020 /etc/apt/trusted.gpg.d/proxmox-release-bullseye.gpg `apt-key list` reports valid unexpired...

Hi, I am on debian 11 bullseye (this was upgraded from buster and was working). I am still on PVEv7, fyi. But when I tried to update, I encountered: # apt update Get:1 http://download.proxmox.com/debian/pve bullseye InRelease [2,768 B] Hit:2 https://deb.debian.org/debian-security...

Bump!

Thanks for a warning. Please find below the output you asked for. # curl --silent --user-agent 'Debian APT-HTTP/1.3 (2.2.4)' http://download.proxmox.com/debian/dists/bullseye/InRelease -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Architectures: amd64 Codename: bullseye Components...

There is nothing wrong because I have no control over the GPG keys. Nevertheless, this got solved by appending '[trusted=true]' to the '/etc/apt/sources.list.d/pve-install-repo.list' to look like: deb [arch=amd64 trusted=true] http://download.proxmox.com/debian/pve bullseye pve-no-subscription...

That is exactly what I did in the OT above for debian 11 bullseye, but no go. And I do not see any reason to download the v6 key in bullseye as in the example. ;-)