Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Off Topic
    4. Proxmox
    5. [Gelöst]Backup of VM 210 failed-CT is locked-snapshot-delete

    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

    [Gelöst]Backup of VM 210 failed-CT is locked-snapshot-delete

    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      GOETSCHHOFER last edited by GOETSCHHOFER

      Habe erst jetzt bemerkt, dass seit ca. 2 Wochen das backup in proxmox nicht fehlerfrei durchläuft.

      Bekomme folgende Fehlermeldung:
      CT ist locked ?
      Was bedeutet dies ? Hier sieht man ein Schloss ?
      df0cc256-7f36-4c2c-849d-c18cf6d11049-image.png
      Ich kann hier auch kein händisches backup starten ?

      Habe hier etwas dazu gefunden:
      https://dannyda.com/2020/05/23/how-to-fix-ct-is-locked-rollback-on-proxmox-ve-pve-how-to-unlock-container-ct-on-proxmox-ve/
      9b04c7c6-b1ed-41ee-b56b-5288a7b3c92c-image.png

      Bekomme aber bei Einstieg über die shell und Eingabe pct unlock 200 folgende Fehlermeldung.

      login as: karl
      karl@192.168.1.177's password:
      Linux LXC-INFLUXDB-192 5.4.143-1-pve #1 SMP PVE 5.4.143-1 (Tue, 28 Sep 2021 09:10:37 +0200) x86_64
      
      The programs included with the Debian GNU/Linux system are free software;
      the exact distribution terms for each program are described in the
      individual files in /usr/share/doc/*/copyright.
      
      Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
      permitted by applicable law.
      Last login: Fri May  6 14:40:37 2022 from 192.168.1.3
      karl@LXC-INFLUXDB-192:~$ pct unlock 200
      -bash: pct: command not found
      karl@LXC-INFLUXDB-192:~$
      
      
      

      Vielen Dank für die Hilfe.

      LG

      Karl

      INFO: starting new backup job: vzdump 100 200 210 --mode snapshot --compress zstd --mailnotification always --node NUC --quiet 1 --mailto karl.goetschhofer@gmail.com --storage usb_backup_120GB
      INFO: Starting Backup of VM 100 (qemu)
      INFO: Backup started at 2022-04-29 21:00:02
      INFO: status = running
      INFO: VM Name: VM-IOBROKER-192.168.1.140
      INFO: include disk 'scsi0' 'local-lvm:vm-100-disk-0' 20G
      INFO: backup mode: snapshot
      INFO: ionice priority: 7
      INFO: creating vzdump archive '/media/usb_backup/dump/vzdump-qemu-100-2022_04_29-21_00_02.vma.zst'
      INFO: started backup task '1d748c56-d60c-4e19-a028-7b8aaa6b40a1'
      INFO: resuming VM again
      INFO:   1% (290.0 MiB of 20.0 GiB) in 3s, read: 96.7 MiB/s, write: 44.5 MiB/s
      INFO:   2% (464.0 MiB of 20.0 GiB) in 6s, read: 58.0 MiB/s, write: 45.3 MiB/s
      INFO:   3% (648.9 MiB of 20.0 GiB) in 9s, read: 61.6 MiB/s, write: 39.5 MiB/s
      INFO:   4% (880.9 MiB of 20.0 GiB) in 12s, read: 77.3 MiB/s, write: 22.3 MiB/s
      INFO:   5% (1.0 GiB of 20.0 GiB) in 15s, read: 52.1 MiB/s, write: 38.6 MiB/s
      INFO:   6% (1.2 GiB of 20.0 GiB) in 19s, read: 49.7 MiB/s, write: 26.1 MiB/s
      INFO:   7% (1.4 GiB of 20.0 GiB) in 24s, read: 39.9 MiB/s, write: 33.8 MiB/s
      INFO:   8% (1.6 GiB of 20.0 GiB) in 30s, read: 34.4 MiB/s, write: 25.4 MiB/s
      INFO:   9% (2.0 GiB of 20.0 GiB) in 35s, read: 73.2 MiB/s, write: 31.3 MiB/s
      INFO:  11% (2.3 GiB of 20.0 GiB) in 38s, read: 102.7 MiB/s, write: 52.1 MiB/s
      INFO:  15% (3.0 GiB of 20.0 GiB) in 41s, read: 268.2 MiB/s, write: 32.5 MiB/s
      INFO:  16% (3.2 GiB of 20.0 GiB) in 51s, read: 16.7 MiB/s, write: 15.9 MiB/s
      INFO:  17% (3.4 GiB of 20.0 GiB) in 1m 1s, read: 19.9 MiB/s, write: 17.3 MiB/s
      INFO:  18% (3.6 GiB of 20.0 GiB) in 1m 15s, read: 15.0 MiB/s, write: 15.0 MiB/s
      INFO:  19% (3.8 GiB of 20.0 GiB) in 1m 27s, read: 16.9 MiB/s, write: 15.5 MiB/s
      INFO:  20% (4.0 GiB of 20.0 GiB) in 1m 37s, read: 20.3 MiB/s, write: 15.8 MiB/s
      INFO:  21% (4.3 GiB of 20.0 GiB) in 1m 40s, read: 89.4 MiB/s, write: 52.1 MiB/s
      INFO:  22% (4.4 GiB of 20.0 GiB) in 1m 43s, read: 49.5 MiB/s, write: 40.9 MiB/s
      INFO:  23% (4.6 GiB of 20.0 GiB) in 1m 51s, read: 25.4 MiB/s, write: 24.5 MiB/s
      INFO:  24% (4.8 GiB of 20.0 GiB) in 1m 58s, read: 30.3 MiB/s, write: 18.8 MiB/s
      INFO:  25% (5.0 GiB of 20.0 GiB) in 2m 5s, read: 31.8 MiB/s, write: 26.4 MiB/s
      INFO:  26% (5.2 GiB of 20.0 GiB) in 2m 10s, read: 34.1 MiB/s, write: 29.2 MiB/s
      INFO:  27% (5.4 GiB of 20.0 GiB) in 2m 22s, read: 16.9 MiB/s, write: 16.4 MiB/s
      INFO:  28% (5.7 GiB of 20.0 GiB) in 2m 33s, read: 30.0 MiB/s, write: 16.1 MiB/s
      INFO:  29% (5.8 GiB of 20.0 GiB) in 2m 37s, read: 19.9 MiB/s, write: 16.9 MiB/s
      INFO:  30% (6.0 GiB of 20.0 GiB) in 2m 48s, read: 18.8 MiB/s, write: 16.2 MiB/s
      INFO:  31% (6.2 GiB of 20.0 GiB) in 2m 51s, read: 76.1 MiB/s, write: 37.7 MiB/s
      INFO:  32% (6.4 GiB of 20.0 GiB) in 2m 56s, read: 35.5 MiB/s, write: 28.5 MiB/s
      INFO:  33% (6.6 GiB of 20.0 GiB) in 3m 5s, read: 23.8 MiB/s, write: 19.5 MiB/s
      INFO:  34% (6.8 GiB of 20.0 GiB) in 3m 17s, read: 16.6 MiB/s, write: 16.6 MiB/s
      INFO:  35% (7.0 GiB of 20.0 GiB) in 3m 28s, read: 19.8 MiB/s, write: 16.2 MiB/s
      INFO:  36% (7.2 GiB of 20.0 GiB) in 3m 40s, read: 15.7 MiB/s, write: 15.7 MiB/s
      INFO:  37% (7.4 GiB of 20.0 GiB) in 3m 54s, read: 15.3 MiB/s, write: 15.3 MiB/s
      INFO:  38% (7.6 GiB of 20.0 GiB) in 4m 7s, read: 15.3 MiB/s, write: 15.3 MiB/s
      INFO:  39% (7.9 GiB of 20.0 GiB) in 4m 15s, read: 40.3 MiB/s, write: 16.5 MiB/s
      INFO:  40% (8.0 GiB of 20.0 GiB) in 4m 20s, read: 16.7 MiB/s, write: 16.7 MiB/s
      INFO:  41% (8.3 GiB of 20.0 GiB) in 4m 23s, read: 103.9 MiB/s, write: 67.0 MiB/s
      INFO:  42% (8.4 GiB of 20.0 GiB) in 4m 27s, read: 36.2 MiB/s, write: 30.2 MiB/s
      INFO:  43% (8.6 GiB of 20.0 GiB) in 4m 37s, read: 18.5 MiB/s, write: 18.1 MiB/s
      INFO:  44% (8.8 GiB of 20.0 GiB) in 4m 49s, read: 15.4 MiB/s, write: 15.4 MiB/s
      INFO:  45% (9.0 GiB of 20.0 GiB) in 5m 2s, read: 16.5 MiB/s, write: 16.5 MiB/s
      INFO:  46% (9.2 GiB of 20.0 GiB) in 5m 14s, read: 16.3 MiB/s, write: 15.7 MiB/s
      INFO:  47% (9.4 GiB of 20.0 GiB) in 5m 26s, read: 16.9 MiB/s, write: 16.3 MiB/s
      INFO:  48% (9.6 GiB of 20.0 GiB) in 5m 38s, read: 16.9 MiB/s, write: 16.5 MiB/s
      INFO:  49% (9.8 GiB of 20.0 GiB) in 5m 51s, read: 16.1 MiB/s, write: 16.1 MiB/s
      INFO:  50% (10.1 GiB of 20.0 GiB) in 5m 57s, read: 41.1 MiB/s, write: 15.9 MiB/s
      INFO:  51% (10.3 GiB of 20.0 GiB) in 6m, read: 85.8 MiB/s, write: 46.7 MiB/s
      INFO:  52% (10.5 GiB of 20.0 GiB) in 6m 3s, read: 74.9 MiB/s, write: 42.1 MiB/s
      INFO:  53% (10.6 GiB of 20.0 GiB) in 6m 7s, read: 30.8 MiB/s, write: 18.4 MiB/s
      INFO:  58% (11.8 GiB of 20.0 GiB) in 6m 10s, read: 387.9 MiB/s, write: 24.0 MiB/s
      INFO:  60% (12.1 GiB of 20.0 GiB) in 6m 13s, read: 125.7 MiB/s, write: 46.5 MiB/s
      INFO:  61% (12.3 GiB of 20.0 GiB) in 6m 16s, read: 52.1 MiB/s, write: 41.7 MiB/s
      INFO:  62% (12.5 GiB of 20.0 GiB) in 6m 19s, read: 60.3 MiB/s, write: 44.6 MiB/s
      INFO:  63% (12.6 GiB of 20.0 GiB) in 6m 22s, read: 53.2 MiB/s, write: 44.8 MiB/s
      INFO:  64% (12.8 GiB of 20.0 GiB) in 6m 27s, read: 36.2 MiB/s, write: 28.2 MiB/s
      INFO:  67% (13.4 GiB of 20.0 GiB) in 6m 30s, read: 206.6 MiB/s, write: 14.2 MiB/s
      INFO:  71% (14.2 GiB of 20.0 GiB) in 6m 33s, read: 282.8 MiB/s, write: 46.8 MiB/s
      INFO:  75% (15.1 GiB of 20.0 GiB) in 6m 36s, read: 279.1 MiB/s, write: 32.2 MiB/s
      INFO:  80% (16.2 GiB of 20.0 GiB) in 6m 39s, read: 380.6 MiB/s, write: 36.7 MiB/s
      INFO:  82% (16.4 GiB of 20.0 GiB) in 6m 42s, read: 77.3 MiB/s, write: 49.3 MiB/s
      INFO:  85% (17.0 GiB of 20.0 GiB) in 6m 45s, read: 214.2 MiB/s, write: 48.9 MiB/s
      INFO:  86% (17.3 GiB of 20.0 GiB) in 6m 48s, read: 79.4 MiB/s, write: 31.7 MiB/s
      INFO: 100% (20.0 GiB of 20.0 GiB) in 6m 51s, read: 934.8 MiB/s, write: 22.6 MiB/s
      INFO: backup is sparse: 11.02 GiB (55%) total zero data
      INFO: transferred 20.00 GiB in 411 seconds (49.8 MiB/s)
      INFO: archive file size: 5.98GB
      INFO: removing backup 'usb_backup_120GB:backup/vzdump-qemu-100-2022_04_19-21_00_01.vma.zst'
      INFO: Finished Backup of VM 100 (00:06:52)
      INFO: Backup finished at 2022-04-29 21:06:54
      INFO: Starting Backup of VM 200 (lxc)
      INFO: Backup started at 2022-04-29 21:06:54
      INFO: status = running
      ERROR: Backup of VM 200 failed - CT is locked (snapshot-delete)
      INFO: Failed at 2022-04-29 21:06:54
      INFO: Starting Backup of VM 210 (lxc)
      INFO: Backup started at 2022-04-29 21:06:54
      INFO: status = running
      **ERROR: Backup of VM 210 failed - CT is locked (snapshot-delete)**
      INFO: Failed at 2022-04-29 21:06:54
      INFO: Backup job finished with errors
      
      TASK ERROR: job errors
      
      G Dr. Bakterius 2 Replies Last reply Reply Quote 0
      • G
        GOETSCHHOFER @GOETSCHHOFER last edited by GOETSCHHOFER

        @FredF @guergen

        Ich bekomme bei meinem locked LXC bei Eingabe über die Shell (qm unlock 200 folgende Fehlermeldung:
        Offenbar kennt er den Befehl nicht ?

        Danke für die Hilfe.

        Karl

        LXC-GRAFANA-192 login: karl
        Password: 
        Last login: Fri May  6 14:41:39 CEST 2022 from 192.168.1.3 on pts/2
        Linux LXC-GRAFANA-192 5.4.143-1-pve #1 SMP PVE 5.4.143-1 (Tue, 28 Sep 2021 09:10:37 +0200) x86_64
        
        The programs included with the Debian GNU/Linux system are free software;
        the exact distribution terms for each program are described in the
        individual files in /usr/share/doc/*/copyright.
        
        Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
        permitted by applicable law.
        karl@LXC-GRAFANA-192:~$ pct unlock 210
        -bash: pct: command not found
        karl@LXC-GRAFANA-192:~$ ^C
        karl@LXC-GRAFANA-192:~$ ^C
        

        https://forum.iobroker.net/topic/53757/gelöst-bitte-hilfe-proxmox-iob-ct-is-locked?_=1651842147431

        qm ... ist für VM's
        pct ... ist für LXc's

        1 Reply Last reply Reply Quote 0
        • Dr. Bakterius
          Dr. Bakterius Most Active @GOETSCHHOFER last edited by

          @goetschhofer sagte in Backup of VM 210 failed - CT is locked (snapshot-delete):

          Bekomme aber bei Einstieg über die shell und Eingabe pct unlock 200 folgende Fehlermeldung.

          Den Befehl musst du unter Proxmox und nicht im LXC absetzen.

          G 1 Reply Last reply Reply Quote 1
          • G
            GOETSCHHOFER @Dr. Bakterius last edited by

            @dr-bakterius

            Vielen, vielen Dank. Da bin ich jetzt aber ordentlich auf dem Schlauch gestanden.

            Funktioniert. 👍

            Danke

            Karl

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

            Support us

            ioBroker
            Community Adapters
            Donate

            582
            Online

            31.7k
            Users

            79.8k
            Topics

            1.3m
            Posts

            2
            4
            3386
            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