Re: [PVE-User] (no subject)

Re: [PVE-User] (no subject)

[Aaron Lauterer]

Are those OSDs bluestore ones or still old file-store ones?

Have you tried running `ceph-volume lvm activate --all`?

It should search for bluestore OSDs and activate them. Activating means, 
mounting the tmpfs into the /var/lib/ceph/osd/ceph-{id} and starting the systemd 
units.

On 7/21/23 21:56, Humberto Jose de Sousa wrote:
> Hi folks,
> 
> I upgraded my ceph cluster from Octopus to Pacific and Pacific to Quincy,
> no problems here.
> 
> So I upgraded pve 7 to 8. After reboot the OSDs don't up. There is no
> directory /etc/ceph/osd/ and json files. The directory
> /var/lib/ceph/osd/ceph-<id>/ is empty.
> 
> How can I recreate the lost files?

Re: [PVE-User] SPAM: Re:

[Aaron Lauterer]

On 7/24/23 19:17, Humberto Jose de Sousa wrote:
> Hi Aaron,
> 
> It was OSDs Bluestore.
> I tried only `ceph-volume simple scan /dev/sdx` and it didn't work.

"simple" is for legacy file store OSDs :)

> In the end I decided to destroy and recreate.
> 
> This problem only occurred with one of the five updates. I didn't
> understand ...
> 
> Thanks!
> Em seg., 24 de jul. de 2023 às 05:58, Aaron Lauterer <a.lauterer@proxmox.com>
> escreveu:
> 
>> Are those OSDs bluestore ones or still old file-store ones?
>>
>> Have you tried running `ceph-volume lvm activate --all`?
>>
>> It should search for bluestore OSDs and activate them. Activating means,
>> mounting the tmpfs into the /var/lib/ceph/osd/ceph-{id} and starting the
>> systemd
>> units.
>>
>> On 7/21/23 21:56, Humberto Jose de Sousa wrote:
>>> Hi folks,
>>>
>>> I upgraded my ceph cluster from Octopus to Pacific and Pacific to Quincy,
>>> no problems here.
>>>
>>> So I upgraded pve 7 to 8. After reboot the OSDs don't up. There is no
>>> directory /etc/ceph/osd/ and json files. The directory
>>> /var/lib/ceph/osd/ceph-<id>/ is empty.
>>>
>>> How can I recreate the lost files?
>>
>>
> 

[PVE-User] (no subject)

[Christian Karg]

Please kill the mailadress service@rundit.de mailto:service@rundit.de from newsletter list
 
 
Ich, Christian Karg verbleibe mit freundlichen Grüßen. Sie können mich gerne persönlich unter meinem Mobiltelefon anrufen:
0179 75 12 77 2 (national Deutschland)
00491797512772 (international weltweit)
service@rundit.de mailto:service@rundit.de (persönliche Mailadresse)
 
Meine Aufgabenbereiche und Fachkompetenzen in der RunDIT: 
- ERP Software odoo.
- Speichersystem Synology und andere Hersteller (OMV).
- IT-Service für mittelständische Firmen.
- Webseiten konfigurieren und Designen.
 
Weitere IT Services des kompletten Portfolios der Firma RunDIT, die ich gerne in einem persönlichen Gespräch Ihnen näher erläutere. Das komplette Portfolio erfahren Sie auf den Webseiten https://rundit.de , https://kargchristian.me und https://myodoo.services

RunDIT – Michael Ruhl
Bayernstr. 7
96272 Hochstadt am Main (Deutschland)
ruhl@rundit.de mailto:service@rundit.de
service@rundit.de mailto:service@rundit.de
https://rundit.de https://www.rundit.de/

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
 
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
 
---------------- bisheriger bzw. früherer Mailinhalt ----------------------------------------
From lindsay.mathieson@gmail.com  Thu Aug 31 02:10:56 2023
Return-Path: <lindsay.mathieson@gmail.com>
X-Original-To: pve-user@lists.proxmox.com
Delivered-To: pve-user@lists.proxmox.com
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by lists.proxmox.com (Postfix) with ESMTPS id 1CB5E85BD
 for <pve-user@lists.proxmox.com>; Thu, 31 Aug 2023 02:10:56 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id EEBE12A8D
 for <pve-user@lists.proxmox.com>; Thu, 31 Aug 2023 02:10:25 +0200 (CEST)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com
 [IPv6:2607:f8b0:4864:20::62c])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by firstgate.proxmox.com (Proxmox) with ESMTPS
 for <pve-user@lists.proxmox.com>; Thu, 31 Aug 2023 02:10:24 +0200 (CEST)
Received: by mail-pl1-x62c.google.com with SMTP id
 d9443c01a7336-1c1e780aa95so1481495ad.3
 for <pve-user@lists.proxmox.com>; Wed, 30 Aug 2023 17:10:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s 221208; t\x1693440616; x\x1694045416; darn=lists.proxmox.com;
 h=content-transfer-encoding:subject:from:content-language:to
 :user-agent:mime-version:date:message-id:from:to:cc:subject:date
 :message-id:reply-to;
 bh=JOWBtYOxxAIUmBKjc0DMB4dEWmDSdqBVrLHgqJFwov0=;
 b=g/QWB++bfmPAc1WX2K2g8Lhk9geLBcXH4gXjIPAQP64rcq8HjLFxgpWlA6wtPDAG0w
 HWDVL+h614tNruoFElClV3c+ani4alBX2Q3xsk3D4HyHruTNivJGGMcObQstquFkoX1s
 MEq7/zPzGhSiohJRh/mk8ppXSA9F6r3DtyqOp/mHqWMONwkaFGku3L9FQtpztZs3i1j9
 SsjT1mOQjlfrM01cL3yoL4IsUrBOyWvYJ9B9r5DLWGH1J9ekYeGJNbxKtl7f19m8no80
 NKWRZ2SfOAMRhBy122K6qCJDWdlidb7WDlXY2tOg3Y35mok9MlKwPIFCgHaCTyhSxrxs
 94vg=X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d\x1e100.net; s 221208; t\x1693440616; x\x1694045416;
 h=content-transfer-encoding:subject:from:content-language:to
 :user-agent:mime-version:date:message-id:x-gm-message-state:from:to
 :cc:subject:date:message-id:reply-to;
 bh=JOWBtYOxxAIUmBKjc0DMB4dEWmDSdqBVrLHgqJFwov0=;
 b=GfluJhqCajM0jZTTZvrEeVqbF+uHzlosDUMJaxJ+Y6L+z5aYFXpv6x40MpBT3BZIel
 mKnhgprLULe84lP4cvr4UX8Q8ag00JM+rPgndg45fMWL4TgtG9INIl236aRh9phj2SJr
 Vhr7ArKEWst4u0C562qYiMnR3ToVpmKap1nT8Cjf5Nq7iHC1yE4UGWO9OZe6t/A2p5Xy
 pRSTtCh6KRKelyrn+9stUF0fP+u8E639q2wRfmAyERduecfsdr0ER3ZpKa6EITakUhv3
 Q1mXInosgkCOAgVBQ6i9tqGQTnt2B6TLd6+zQvIz0nclAicZQXzj6kCPxGy9K/30cjYS
 WnIA=X-Gm-Message-State: AOJu0Yxd6SI3ldm6FH2JvHOsp4Ja3cW88vGAY5fpZYscYmKOV8q49z7T
 mvP9bwRgCSKR2rWlsPxejPgR9cCt2TYX-Google-Smtp-Source: AGHT+IFldOedHPeTF9bVFSkl9h9wDUmIkh1YlNCGqhwB6FLTvEnttu2mobHMhZxIzNasisp23nUHsw=X-Received: by 2002:a17:902:b407:b0:1bd:f1ae:309d with SMTP id
 x7-20020a170902b40700b001bdf1ae309dmr3477871plr.9.1693440615739;
 Wed, 30 Aug 2023 17:10:15 -0700 (PDT)
Received: from [192.168.1.160] (167-179-176-9.a7b3b0.bne.nbn.aussiebb.net.
 [167.179.176.9]) by smtp.gmail.com with ESMTPSA id
 e2-20020a170902b78200b001aaf2e8b1eesm69464pls.248.2023.08.30.17.10.13
 for <pve-user@lists.proxmox.com>
 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits\x128/128);
 Wed, 30 Aug 2023 17:10:15 -0700 (PDT)
Message-ID: <db01d069-1c6c-8294-1f62-f0756305a310@gmail.com>
Date: Thu, 31 Aug 2023 10:10:11 +1000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.14.0
To: "pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Content-Language: en-US
From: Lindsay Mathieson <lindsay.mathieson@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.732 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DKIM_SIGNED               0.1 Message has a DKIM or DK signature,
 not necessarily valid
 DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature
 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's
 domain
 DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from
 domain DMARC_PASS               -0.1 DMARC pass policy
 FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider
 RCVD_IN_DNSWL_NONE     -0.0001 Sender listed at https://www.dnswl.org/,
 no trust
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: [PVE-User] USB Expansion Card for PCIE Hub passthrough?
X-BeenThere: pve-user@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE user list <pve-user.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>,
 <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-user/>
List-Post: <mailto:pve-user@lists.proxmox.com>
List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>,
 <mailto:pve-user-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2023 00:10:56 -0000

Looking to purchase a USB expansion card to passthrough entire to my
Windows 11 VM, hoping it will help with USB audio issues and improve
occasional mouse/keyboard weirdness. Already have an NVidia Card
passthrough working fine.


Will any generic USB Card do or should I be looking for particular
brands/chipsets?

Currently looking at a Orico 7 Port USB 3.0 PCIe Dual Chip Card.


Thanks.

--
Lindsay Mathieson

[PVE-User] (no subject)

[Leandro Roggerone]

root@pve:~# apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]
Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists... Done


E: Repository 'http://security.debian.org buster/updates InRelease' changed
its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can
be applied. See apt-secure(8) manpage for details.
E: Repository 'http://ftp.debian.org/debian buster InRelease' changed its
'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can
be applied. See apt-secure(8) manpage for details.
E: Repository 'http://ftp.debian.org/debian buster-updates InRelease'
changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: This must be accepted explicitly before updates for this repository can
be applied. See apt-secure(8) manpage for details.

This is my source.list
root@pve:~# cat /etc/apt/sources.list
deb http://ftp.debian.org/debian buster main contrib

deb http://ftp.debian.org/debian buster-updates main contrib

# security updates
deb http://security.debian.org buster/updates main contrib

This was working ok until sat 14.
Any idea ?
Thanks!

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: [PVE-User] (no subject)

[Leandro Roggerone]

thanks Martin.
According to documentation , for a non subscription environment ,this is
how it should looks like:

root@pve:/etc/apt# cat /etc/apt/sources.list
deb http://ftp.debian.org/debian bullseye main contrib

deb http://ftp.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org/debian-security bullseye-security main
contrib

After running apt-get update from cli , it did not return any error.
seems to be working ok now.
Thanks again.
Leandro.

El mar, 17 ago 2021 a las 11:44, Martin Holub via pve-user (<
pve-user@lists.proxmox.com>) escribió:

>
>
>
> ---------- Forwarded message ----------
> From: Martin Holub <martin@holub.co.at>
> To: pve-user@lists.proxmox.com
> Cc:
> Bcc:
> Date: Tue, 17 Aug 2021 16:43:30 +0200
> Subject: Re: [PVE-User] (no subject)
> Hi,
>
> On Aug 14th "Bullseye" was released, therefore Buster moved from
> "stable" to "oldstable" and Bullseye became the new "stable" Version of
> Debian.
>
> Cheers.
> Martin
>
> Am 17.08.21 um 16:37 schrieb Leandro Roggerone:
> > root@pve:~# apt-get update
> > Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
> > Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]
> > Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
> > Reading package lists... Done
> >
> >
> > E: Repository 'http://security.debian.org buster/updates InRelease'
> changed
> > its 'Suite' value from 'stable' to 'oldstable'
> > N: This must be accepted explicitly before updates for this repository
> can
> > be applied. See apt-secure(8) manpage for details.
> > E: Repository 'http://ftp.debian.org/debian buster InRelease' changed
> its
> > 'Suite' value from 'stable' to 'oldstable'
> > N: This must be accepted explicitly before updates for this repository
> can
> > be applied. See apt-secure(8) manpage for details.
> > E: Repository 'http://ftp.debian.org/debian buster-updates InRelease'
> > changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
> > N: This must be accepted explicitly before updates for this repository
> can
> > be applied. See apt-secure(8) manpage for details.
> >
> > This is my source.list
> > root@pve:~# cat /etc/apt/sources.list
> > deb http://ftp.debian.org/debian buster main contrib
> >
> > deb http://ftp.debian.org/debian buster-updates main contrib
> >
> > # security updates
> > deb http://security.debian.org buster/updates main contrib
> >
> > This was working ok until sat 14.
> > Any idea ?
> > Thanks!
> >
> > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> > Libre
> > de virus. www.avast.com
> > <
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
> >
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
>
>
>
>
> ---------- Forwarded message ----------
> From: Martin Holub via pve-user <pve-user@lists.proxmox.com>
> To: pve-user@lists.proxmox.com
> Cc: Martin Holub <martin@holub.co.at>
> Bcc:
> Date: Tue, 17 Aug 2021 16:43:30 +0200
> Subject: Re: [PVE-User] (no subject)
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Re: [PVE-User] (no subject)

[Leandro Roggerone]

Hello , Martin.
Im still in pve 6.04.
I was looking at the document you pointed out (Upgrade from 6.x to 7.0)
It is frustrating to see that upgrading  is a very difficult process.
My cluster contains 2 servers.
Both are in production , at 50 - 60 % storage and memory capacity so it is
not easy for me to create backups and move VMs.

I will study how to proceed with this update from pve 6  to 7.
Perhaps:
Adding a third new box already running version 7.
Adding a networking storage ? need to check out wich one.

Meanwhile , until I can go to pve 7 , I think I should upgrate to latest
pve 6 and disable automatic upgrades ...
Do you think it is ok ?

Thanks for your words!!
Leandro.


El mié, 18 ago 2021 a las 14:58, Martin Holub (<martin@holub.co.at>)
escribió:

> Hi Leandro,
>
> Are you already on PVE7? Otherwise, just changing the Sources to Bullseye,
> i'm pretty shure that this will break things, or at least produce unwanted
> results. If you want to upgrade to Debian Bullseye better check
> https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
>
> Best regards
> Martin
> Am 18.08.21 um 15:19 schrieb Leandro Roggerone:
>
> thanks Martin.
> According to documentation , for a non subscription environment ,this is
> how it should looks like:
>
> root@pve:/etc/apt# cat /etc/apt/sources.list
> deb http://ftp.debian.org/debian bullseye main contrib
>
> deb http://ftp.debian.org/debian bullseye-updates main contrib
>
> # security updates
> deb http://security.debian.org/debian-security bullseye-security main
> contrib
>
> After running apt-get update from cli , it did not return any error.
> seems to be working ok now.
> Thanks again.
> Leandro.
>
> El mar, 17 ago 2021 a las 11:44, Martin Holub via pve-user (<
> pve-user@lists.proxmox.com>) escribió:
>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Martin Holub <martin@holub.co.at>
>> To: pve-user@lists.proxmox.com
>> Cc:
>> Bcc:
>> Date: Tue, 17 Aug 2021 16:43:30 +0200
>> Subject: Re: [PVE-User] (no subject)
>> Hi,
>>
>> On Aug 14th "Bullseye" was released, therefore Buster moved from
>> "stable" to "oldstable" and Bullseye became the new "stable" Version of
>> Debian.
>>
>> Cheers.
>> Martin
>>
>> Am 17.08.21 um 16:37 schrieb Leandro Roggerone:
>> > root@pve:~# apt-get update
>> > Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
>> > Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]
>> > Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
>> > Reading package lists... Done
>> >
>> >
>> > E: Repository 'http://security.debian.org buster/updates InRelease'
>> changed
>> > its 'Suite' value from 'stable' to 'oldstable'
>> > N: This must be accepted explicitly before updates for this repository
>> can
>> > be applied. See apt-secure(8) manpage for details.
>> > E: Repository 'http://ftp.debian.org/debian buster InRelease' changed
>> its
>> > 'Suite' value from 'stable' to 'oldstable'
>> > N: This must be accepted explicitly before updates for this repository
>> can
>> > be applied. See apt-secure(8) manpage for details.
>> > E: Repository 'http://ftp.debian.org/debian buster-updates InRelease'
>> > changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
>> > N: This must be accepted explicitly before updates for this repository
>> can
>> > be applied. See apt-secure(8) manpage for details.
>> >
>> > This is my source.list
>> > root@pve:~# cat /etc/apt/sources.list
>> > deb http://ftp.debian.org/debian buster main contrib
>> >
>> > deb http://ftp.debian.org/debian buster-updates main contrib
>> >
>> > # security updates
>> > deb http://security.debian.org buster/updates main contrib
>> >
>> > This was working ok until sat 14.
>> > Any idea ?
>> > Thanks!
>> >
>> > <
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>> >
>> > Libre
>> > de virus. www.avast.com
>> > <
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>> >
>> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> > _______________________________________________
>> > pve-user mailing list
>> > pve-user@lists.proxmox.com
>> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>> >
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Martin Holub via pve-user <pve-user@lists.proxmox.com>
>> To: pve-user@lists.proxmox.com
>> Cc: Martin Holub <martin@holub.co.at>
>> Bcc:
>> Date: Tue, 17 Aug 2021 16:43:30 +0200
>> Subject: Re: [PVE-User] (no subject)
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Libre
> de virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>
>

Re: [PVE-User] (no subject)

[Alain Péan]

Le 24/08/2021 à 17:13, Leandro Roggerone a écrit :
> Hello , Martin.
> Im still in pve 6.04.
> I was looking at the document you pointed out (Upgrade from 6.x to 7.0)
> It is frustrating to see that upgrading  is a very difficult process.
> My cluster contains 2 servers.
> Both are in production , at 50 - 60 % storage and memory capacity so it is
> not easy for me to create backups and move VMs.
>
> I will study how to proceed with this update from pve 6  to 7.
> Perhaps:
> Adding a third new box already running version 7.
> Adding a networking storage ? need to check out wich one.
>
> Meanwhile , until I can go to pve 7 , I think I should upgrate to latest
> pve 6 and disable automatic upgrades ...
> Do you think it is ok ?

Hello Leandro,

If you are under Proxmox 6.4, you cannot move "accidentaly", by software 
upgrades, to 7.0. Because 6.x is based on Debian 10, and 7.x on Debian 
11, so you have to change the repository to point to the newer release.

What I do personnaly is to test the upgrade on a test cluster, to see 
how it works. I have an old server on which I setup a nested proxmox ve 
cluster with three small VMs. I test the upgrade process on this nested 
cluster, before applying it to production cluster.

For your produxtion cluster, you should have backups of your VMs (for 
example on an NFS storage). It would be indeed a good thing to have à 
third host to have a minimum cluster with quorum.

Good luck !

Alain

-- 
Administrateur Système/Réseau
C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
Boulevard Thomas Gobert (ex Avenue de La Vauve), 91120 Palaiseau
Tel : 01-70-27-06-88 Bureau A255

Re: [PVE-User] (no subject)

[Leandro Roggerone]

ok , guys  ... I think I will add a third box but it will take some time.
Meanwhile:
Currently i'm using following repo:

deb http://ftp.debian.org/debian bullseye main contrib
deb http://ftp.debian.org/debian bullseye-updates main contrib
# security updates
deb http://security.debian.org/debian-security bullseye-security main
contrib

I have never run any manual upgrade however the system is running the
apt-get update command once a day.
a) Does It means I should not try to go back to the buster repo ?


b)Since Im still running pve 6 , if It is possible to fix my repolist ,
wich should I use ?
Before I got the update alert I was using this:

deb http://ftp.debian.org/debian buster main contrib
deb http://ftp.debian.org/debian buster-updates main contrib
# security updates
deb http://security.debian.org buster/updates main contrib

c) Is it possible to confirm if some packages have been upgraded ?
So I can decide to whether to go back to buster , keep using bullseye.
d) If there is no chance to change the repolist to the proper one , should
I disable automatic updates to avoid the system crashes ?

Thanks guys.
Leandro.




<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

El mar, 24 ago 2021 a las 14:21, Martin Holub (<martin@holub.co.at>)
escribió:

> Hi Leandro,
>
> So if you can't schedule a downtime for, at least, some VMs i would add a
> 3rd Box. Also in terms of having a valid Quorum a 3rd Box would be a good
> thing.
>
> About the Upgrade, as Alain pointed out, there is no way to accidentially
> upgrade, at least if you don't put "bullseye" in the sources.list manually
> (like you did, that's why i asked about the Upgrade). So just make shure
> you explicitly use "buster", not "stable" or "bullseye" in the Debian repo.
> If apt still complains about the release change just run an update using
> "apt-get update --allow-releaseinfo-change", this should fix things you. If
> you already upgraded some packages from the bullseye repo i would keep
> things running as they are for now (obviously nothing broke by now, so
> don't touch it...) and start planning the Upgrade to 7.0. The Upgrade to
> 7.0 was hassle free for the Clusters i ran it by now. Also telling from
> Forum and Mailing Lists, i wouldn't expect any issues as long as you don't
> have any special setups with PCI passthrough Devices or something like
> that.
>
> Best
> Martin
> Am 24.08.21 um 17:13 schrieb Leandro Roggerone:
>
> Hello , Martin.
> Im still in pve 6.04.
> I was looking at the document you pointed out (Upgrade from 6.x to 7.0)
> It is frustrating to see that upgrading  is a very difficult process.
> My cluster contains 2 servers.
> Both are in production , at 50 - 60 % storage and memory capacity so it is
> not easy for me to create backups and move VMs.
>
> I will study how to proceed with this update from pve 6  to 7.
> Perhaps:
> Adding a third new box already running version 7.
> Adding a networking storage ? need to check out wich one.
>
> Meanwhile , until I can go to pve 7 , I think I should upgrate to latest
> pve 6 and disable automatic upgrades ...
> Do you think it is ok ?
>
> Thanks for your words!!
> Leandro.
>
>
> El mié, 18 ago 2021 a las 14:58, Martin Holub (<martin@holub.co.at>)
> escribió:
>
>> Hi Leandro,
>>
>> Are you already on PVE7? Otherwise, just changing the Sources to
>> Bullseye, i'm pretty shure that this will break things, or at least produce
>> unwanted results. If you want to upgrade to Debian Bullseye better check
>> https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
>>
>> Best regards
>> Martin
>> Am 18.08.21 um 15:19 schrieb Leandro Roggerone:
>>
>> thanks Martin.
>> According to documentation , for a non subscription environment ,this is
>> how it should looks like:
>>
>> root@pve:/etc/apt# cat /etc/apt/sources.list
>> deb http://ftp.debian.org/debian bullseye main contrib
>>
>> deb http://ftp.debian.org/debian bullseye-updates main contrib
>>
>> # security updates
>> deb http://security.debian.org/debian-security bullseye-security main
>> contrib
>>
>> After running apt-get update from cli , it did not return any error.
>> seems to be working ok now.
>> Thanks again.
>> Leandro.
>>
>> El mar, 17 ago 2021 a las 11:44, Martin Holub via pve-user (<
>> pve-user@lists.proxmox.com>) escribió:
>>
>>>
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Martin Holub <martin@holub.co.at>
>>> To: pve-user@lists.proxmox.com
>>> Cc:
>>> Bcc:
>>> Date: Tue, 17 Aug 2021 16:43:30 +0200
>>> Subject: Re: [PVE-User] (no subject)
>>> Hi,
>>>
>>> On Aug 14th "Bullseye" was released, therefore Buster moved from
>>> "stable" to "oldstable" and Bullseye became the new "stable" Version of
>>> Debian.
>>>
>>> Cheers.
>>> Martin
>>>
>>> Am 17.08.21 um 16:37 schrieb Leandro Roggerone:
>>> > root@pve:~# apt-get update
>>> > Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
>>> > Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]
>>> > Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
>>> > Reading package lists... Done
>>> >
>>> >
>>> > E: Repository 'http://security.debian.org buster/updates InRelease'
>>> changed
>>> > its 'Suite' value from 'stable' to 'oldstable'
>>> > N: This must be accepted explicitly before updates for this repository
>>> can
>>> > be applied. See apt-secure(8) manpage for details.
>>> > E: Repository 'http://ftp.debian.org/debian buster InRelease' changed
>>> its
>>> > 'Suite' value from 'stable' to 'oldstable'
>>> > N: This must be accepted explicitly before updates for this repository
>>> can
>>> > be applied. See apt-secure(8) manpage for details.
>>> > E: Repository 'http://ftp.debian.org/debian buster-updates InRelease'
>>> > changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
>>> > N: This must be accepted explicitly before updates for this repository
>>> can
>>> > be applied. See apt-secure(8) manpage for details.
>>> >
>>> > This is my source.list
>>> > root@pve:~# cat /etc/apt/sources.list
>>> > deb http://ftp.debian.org/debian buster main contrib
>>> >
>>> > deb http://ftp.debian.org/debian buster-updates main contrib
>>> >
>>> > # security updates
>>> > deb http://security.debian.org buster/updates main contrib
>>> >
>>> > This was working ok until sat 14.
>>> > Any idea ?
>>> > Thanks!
>>> >
>>> > <
>>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>>> >
>>> > Libre
>>> > de virus. www.avast.com
>>> > <
>>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
>>> >
>>> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>> > _______________________________________________
>>> > pve-user mailing list
>>> > pve-user@lists.proxmox.com
>>> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>> >
>>>
>>>
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Martin Holub via pve-user <pve-user@lists.proxmox.com>
>>> To: pve-user@lists.proxmox.com
>>> Cc: Martin Holub <martin@holub.co.at>
>>> Bcc:
>>> Date: Tue, 17 Aug 2021 16:43:30 +0200
>>> Subject: Re: [PVE-User] (no subject)
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user@lists.proxmox.com
>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>>
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Libre
>> de virus. www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>
>>

[PVE-User] (no subject)

[Aaron Wood]

Hi all,

I just edited a few posts I made last night (
https://forum.proxmox.com/threads/latest-proxmox-update-causes-windows-10-guest-to-bsod-loop-with-kernel-security-check-failure.84867/)
and now I see "You have been banned for the following reason: Spam. Please
contact the administrator if this was done in error.."

Does anyone know how I can contact an admin? Are there any admins watching
this list? I was trying to reply to my post with some info for Stefan only
to see that the system banned me...

Thanks,
Aaron

Re: [PVE-User] (no subject)

[Thomas Lamprecht]

Hi!

On 25.02.21 21:18, Aaron Wood wrote:
> I just edited a few posts I made last night (
> https://forum.proxmox.com/threads/latest-proxmox-update-causes-windows-10-guest-to-bsod-loop-with-kernel-security-check-failure.84867/)
> and now I see "You have been banned for the following reason: Spam. Please
> contact the administrator if this was done in error.."
> 
> Does anyone know how I can contact an admin? Are there any admins watching
> this list? I was trying to reply to my post with some info for Stefan only
> to see that the system banned me...

Sorry about that ban, it seems the forums ban software got triggered by your
post and was mistakenly confirmed as such in the moderation queue, sorry
about that inconvenience!

Your account should be restored again.

In general, if there's any issue with such things you can write directly to
office@proxmox.com

Best regards,
Thomas