Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Off Topic
    4. Proxmox
    5. Brauche Hilfe bei proxmox v6 zu v7

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Brauche Hilfe bei proxmox v6 zu v7

    This topic has been deleted. Only users with topic management privileges can see it.
    • Feuersturm
      Feuersturm @darkiop last edited by

      @darkiop sagte in Brauche Hilfe bei proxmox v6 zu v7:

      @feuersturm Schieb zur Sicherheit nochmal ein

      apt dist-upgrade

      hinterher.

      Mach ich.

      1 Reply Last reply Reply Quote 0
      • S
        saeft_2003 Most Active @Feuersturm last edited by

        @feuersturm sagte in Brauche Hilfe bei proxmox v6 zu v7:

        @saeft_2003 sagte in Brauche Hilfe bei proxmox v6 zu v7:

        @feuersturm

        Hast du einen lxc (vielleicht sogar wireguard) laufen?
        Nein wireguard hab ich nicht im Einsatz

        Und einen anderen lxc oder nur VMs?

        Feuersturm 1 Reply Last reply Reply Quote 0
        • Feuersturm
          Feuersturm @saeft_2003 last edited by Feuersturm

          @saeft_2003 sagte in Brauche Hilfe bei proxmox v6 zu v7:

          Und einen anderen lxc oder nur VMs?

          Container und VMs sind gemischt. Primär sind es LXCs und eine VM, wenn ich mich richtig erinnere.

          Siehst du einen Zusammenhang zu meinem Problem?

          S 1 Reply Last reply Reply Quote 0
          • S
            saeft_2003 Most Active @Feuersturm last edited by

            @feuersturm

            Bei mir wurde auch das eingezeigt und dann nichts mehr…

            
Loading Linux 5.15.83-1-pve ...

            Während dem Update gab es folgenden Fehler, dass ist bei mir der einzigste lxc den ich habe. Kann natürlich auch Zufall sein. Bin echt kein linux profi…

            
usr/sbin/grub-probe: error: disk `lvmid/d6vUe1-VmEL-SEgR-sIoS-IGLg-l441-4JTJ9F/UxkIqX-7fZT-iWgh-YcIu-0Qfh-Rnfd-GXLmxI' not found.
Found Ubuntu 21.04 (21.04) on /dev/mapper/pve-vm--1500--disk--0
Adding boot menu entry for UEFI Firmware Settings ...
done
            Feuersturm 1 Reply Last reply Reply Quote 0
            • Feuersturm
              Feuersturm @saeft_2003 last edited by Feuersturm

              @saeft_2003 ich poste dir später mal ein paar Screenshots, wie ich es bei mir wieder mit dem alten Kernel zum laufen bekomme habe.

              S 1 Reply Last reply Reply Quote 0
              • S
                saeft_2003 Most Active @Feuersturm last edited by

                @feuersturm

                Das wäre echt super. Weil das Problem hatte ich bei meinem Testsystem das habe ich einfach neu aufgesetzt. Bei meinem Produktivsystem steht das Update noch an. Davor hab ich etwas bammel auch wenn ich weiß das ich einfach neu aufsetzten kann…

                crunchip 1 Reply Last reply Reply Quote 0
                • crunchip
                  crunchip Forum Testing Most Active @saeft_2003 last edited by

                  @saeft_2003 sagte in Brauche Hilfe bei proxmox v6 zu v7:

                  das Problem

                  ein Problem, aber nicht das selbe

                  S 2 Replies Last reply Reply Quote 0
                  • S
                    saeft_2003 Most Active @crunchip last edited by

                    @crunchip

                    Ok hatte gedacht das es evtl das gleiche Problem war…

                    1 Reply Last reply Reply Quote 0
                    • S
                      saeft_2003 Most Active @crunchip last edited by saeft_2003

                      @crunchip

                      Vorbereitungen / Voraussetzungen

                      Folgendes sollte vor einem Upgrade sichergestellt und überprüft werden:

                      Achtung: Entfernen Sie unbedingt das Meta-Paket linux-image-amd64 und das entsprechende passende Zusatzpaket wie linux-image-4.19-amd64! Sind diese Pakete installiert, kann es zu massiven Problemen während des Upgrades kommen. Erfahrungen zeigten, dass sogar der vollständige BootLoader entfernt werden könnte!

                      Könnte das etwas mit meinem Problem zu tun haben?

                      Edit: Das steht im offiziellen wiki

                      Upgrade wants to remove package 'proxmox-ve'

                      If you have installed Proxmox VE on top of Debian Buster, you may have installed the package 'linux-image-amd64', which conflicts with current 6.x setups. To solve this, you have to remove this package with

                      apt remove linux-image-amd64

                      before the dist-upgrade.

                      1 Reply Last reply Reply Quote 1
                      • Feuersturm
                        Feuersturm last edited by Feuersturm

                        Ich hab noch einmal in dem Log term.log.1 im Pfad var\log\apt\ nachgesehen und dort steht am Ende auch das, was du @saeft_2003 auch in deinem Log Auszug hattest

                        [...]
stat: cannot statx '/dev/mapper/pve-snap_vm--103--disk--0_Current_20221008': No such file or directory
lsblk: /dev/mapper/pve-snap_vm--103--disk--0_Current_20221008: not a block device
stat: cannot statx '/dev/mapper/pve-snap_vm--103--disk--0_UpdateAuf_Ubuntu20LTS': No such file or directory
lsblk: /dev/mapper/pve-snap_vm--103--disk--0_UpdateAuf_Ubuntu20LTS: not a block device
stat: cannot statx '/dev/mapper/pve-snap_vm--103--disk--0_Update_auf_6d5d54': No such file or directory
lsblk: /dev/mapper/pve-snap_vm--103--disk--0_Update_auf_6d5d54: not a block device
stat: cannot statx '/dev/mapper/pve-snap_vm--103--disk--0_VorUpdate_20210116': No such file or directory
lsblk: /dev/mapper/pve-snap_vm--103--disk--0_VorUpdate_20210116: not a block device
stat: cannot statx '/dev/mapper/pve-snap_vm--103--disk--0_VorUpdate_20211212': No such file or directory
lsblk: /dev/mapper/pve-snap_vm--103--disk--0_VorUpdate_20211212: not a block device
stat: cannot statx '/dev/mapper/pve-snap_vm--105--disk--0_influxdb_ssh': No such file or directory
lsblk: /dev/mapper/pve-snap_vm--105--disk--0_influxdb_ssh: not a block device
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13601: grub-probe
grub-probe: error: disk `lvmid/w8EijX-RSBf-RtMO-H4qI-9Zdl-Xtvj-baV7lV/J8PMJU-J3aX-IDsm-xQ8D-dLqG-54Ds-5EU6bk' not found.
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13699: grub-probe
grub-probe: error: disk `lvmid/w8EijX-RSBf-RtMO-H4qI-9Zdl-Xtvj-baV7lV/MH9xuu-N9sk-trKO-TDFF-KxLC-eAgD-kr06O4' not found.
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13795: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/G7Sabl-ID5k-fdYg-06vc-bh04-AAMt-We1RI5' not found.
Found Ubuntu 18.04.6 LTS (18.04) on /dev/mapper/data2-vm--2010--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13862: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/wHAfZv-fei3-f35o-FnxH-rOlM-6il1-m2bHVZ' not found.
Found Ubuntu 18.04.6 LTS (18.04) on /dev/mapper/data2-vm--2060--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13919: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/g0hjoK-QQ8N-0Jnf-fnm3-HR4E-FxvE-I2kVIG' not found.
Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/data2-vm--3108--disk--1
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 13976: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/OnR9t0-5tlo-h4ir-CTQK-ndou-U1sC-LSk3pG' not found.
Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/data2-vm--3109--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14067: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/4gJg58-GKRC-fC1J-W1Aq-etR1-aLvN-j28iH0' not found.
Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/data2-vm--3201--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14124: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/B8aHNJ-7Qu5-ebzy-239W-vhg4-1q2B-LgA2iJ' not found.
Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/data2-vm--4000--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14181: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/ir2NVA-rf2w-u8tY-cvyC-Ae4G-q6aE-PUq2FV' not found.
Found Ubuntu 20.04.5 LTS (20.04) on /dev/mapper/data2-vm--5000--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14238: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/SCBSz9-xzdE-Uq3D-EIbM-l2AZ-VGkU-Pyre88/tzD2nF-x954-d3Ty-sodg-dEt2-Uwr0-KDJtei' not found.
Found Ubuntu 22.04.1 LTS (22.04) on /dev/mapper/data2-vm--7000--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14295: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/w8EijX-RSBf-RtMO-H4qI-9Zdl-Xtvj-baV7lV/J8PMJU-J3aX-IDsm-xQ8D-dLqG-54Ds-5EU6bk' not found.
Found Ubuntu 20.04.5 LTS (20.04) on /dev/mapper/pve-vm--103--disk--0
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
File descriptor 3 (pipe:[448678]) leaked on vgs invocation. Parent PID 14370: /usr/sbin/grub-probe
/usr/sbin/grub-probe: error: disk `lvmid/w8EijX-RSBf-RtMO-H4qI-9Zdl-Xtvj-baV7lV/MH9xuu-N9sk-trKO-TDFF-KxLC-eAgD-kr06O4' not found.
Found Ubuntu 18.04.4 LTS (18.04) on /dev/mapper/pve-vm--105--disk--0
Adding boot menu entry for UEFI Firmware Settings ...
done

                        Nachdem mein Update ja nicht weiter ging hatte ich Montior und Tastatur angeschlossen und ich sah auf dem Bildschirm nur ein

                        Loading Linux 5.15.83-1-pve ...

                        Über das Bootmenü konnte ich dann über das folgende Menü einen älteren Kernel 5.4.203 wählen und das System ist erstmal wieder gestartet.
                        5b00afc4-f52d-422b-a777-0a10a518da13-grafik.png
                        6bca15d0-8508-4ab9-8601-d7f881541dd6-grafik.png

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          saeft_2003 Most Active @Feuersturm last edited by

                          @feuersturm

                          Danke für deine ausführliche Antwort. Hast du dann den Kernel genommen wo in Klammern recovery mode dahinter steht?

                          Was genau hast du dann gemacht als proxmox wieder lief?

                          Feuersturm 1 Reply Last reply Reply Quote 0
                          • Feuersturm
                            Feuersturm @saeft_2003 last edited by

                            @saeft_2003 sagte in Brauche Hilfe bei proxmox v6 zu v7:

                            @feuersturm

                            Danke für deine ausführliche Antwort. Hast du dann den Kernel genommen wo in Klammern recovery mode dahinter steht?

                            Was genau hast du dann gemacht als proxmox wieder lief?

                            Ich hab den Eintrag ohne den Recovery mode ausgewählt.
                            Als das System dann wieder erreichbar war hab ich diese Schritte ausgeführt: https://forum.iobroker.net/topic/61132/brauche-hilfe-bei-proxmox-v6-zu-v7/63

                            1 Reply Last reply Reply Quote 1
                            • crunchip
                              crunchip Forum Testing Most Active last edited by

                              @saeft_2003 sagte in Brauche Hilfe bei proxmox v6 zu v7:

                              Könnte das etwas mit meinem Problem zu tun haben

                              möglich,
                              ich kann mich aber an mein upgrade nicht mehr erinnern, ich weiß nur das es bei mir ohne jegliche Probleme durch lief

                              1 Reply Last reply Reply Quote 0
                              • S
                                saeft_2003 Most Active last edited by

                                Hab mich heute getraut mein produktivsystem auf V7 anzuheben hat alles geklappt 😊

                                Feuersturm 1 Reply Last reply Reply Quote 1
                                • Feuersturm
                                  Feuersturm @saeft_2003 last edited by

                                  @saeft_2003 hattest du den Befehl
                                  apt remove linux-image-amd64
                                  vorher bei dir noch ausgeführt?

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    saeft_2003 Most Active @Feuersturm last edited by

                                    @feuersturm

                                    ja aber der meinte dass das paket nicht installiert ist.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post

                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate

                                    970
                                    Online

                                    31.9k
                                    Users

                                    80.1k
                                    Topics

                                    1.3m
                                    Posts

                                    5
                                    83
                                    5756
                                    Loading More Posts
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    Community
                                    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                    The ioBroker Community 2014-2023
                                    logo