Bonjour,
Depuis ce matin, mon home assistant ne fonctionne plus . Il tournait depuis 6 mois sans problème et là depuis ce matin la panne.
Il fonctionne sur promox et j’ai un petit drapeau jaune sur la VM
Tu as quoi dans les log de la vm et de proxmox ?
Statut : running (IO ERROR)
Merci de votre aide.
J’ai vu le message.
Mais je n’ai aucune idée de ce qu’il faut faire.
Boboss
N’ayant jamais rencontré ce problème, je ne peux répondre « par expérience », mais une simple recherche « proxmox running(io-error) » renvoie sur le forum Proxmox.
Tubas disqu en train de mourir
J’espère que tu as un backup externalisé ?
Ah la fin du DD.
C’est vrai que lui n’est plus très jeune.
J’ai une sauvegarde externalisée.
cela sent le changement du SSD !
CE qui est bizarre, j’ai un jeedom et un serveur mqtt qui tourne avec ?
Merci de ton expertise. @ddfdom
Boboss
Et tu as quoi dans les logs proxmox ?
En tout cas le disque plein c’est pas ce qui est indiqué. Mais comme on a que des morceau d’écran on peut pas trop voir a quoi ça correspond.
Parmi les causes évoquées sur le forum Proxmox : saturation (non pas du disque mais dépassement d’un quota).
Autres causes : problème réseau pour un stockage réseau (NFS).
Pour avoir une certitude s’il s’agit d’un problème matériel sur un disque local, le mieux est de regarder le résultat de la commande dmesg et, si besoin, de faire une analyse SMART.
A faire depuis le node Proxmox et pas sur la VM.
Je les trouve où les log ?
Petite recherche et hop :
Citation
Mar 04 19:22:10 pve1 kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability LTR DPC]
Mar 04 19:22:10 pve1 kernel: acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
Mar 04 19:22:10 pve1 kernel: PCI host bridge to bus 0000:00
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: root bus resource [mem 0xdf200000-0xfeafffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:00.0: [8086:0a04] type 00 class 0x060000 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: [8086:0a16] type 00 class 0x030000 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: BAR 0 [mem 0xf7800000-0xf7bfffff 64bit]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: BAR 2 [mem 0xe0000000-0xefffffff 64bit pref]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: BAR 4 [io 0xf000-0xf03f]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:03.0: [8086:0a0c] type 00 class 0x040300 PCIe Root Complex Integrated Endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:03.0: BAR 0 [mem 0xf7d34000-0xf7d37fff 64bit]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:14.0: [8086:9c31] type 00 class 0x0c0330 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:14.0: BAR 0 [mem 0xf7d20000-0xf7d2ffff 64bit]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:16.0: [8086:9c3a] type 00 class 0x078000 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:16.0: BAR 0 [mem 0xf7d3e000-0xf7d3e01f 64bit]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:19.0: [8086:1559] type 00 class 0x020000 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:19.0: BAR 0 [mem 0xf7d00000-0xf7d1ffff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:19.0: BAR 1 [mem 0xf7d3c000-0xf7d3cfff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:19.0: BAR 2 [io 0xf080-0xf09f]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1b.0: [8086:9c20] type 00 class 0x040300 PCIe Root Complex Integrated Endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1b.0: BAR 0 [mem 0xf7d30000-0xf7d33fff 64bit]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: [8086:9c10] type 01 class 0x060400 PCIe Root Port
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: Enabling MPC IRBNCE
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: Intel PCH root port ACS workaround enabled
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: [8086:9c16] type 01 class 0x060400 PCIe Root Port
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: PCI bridge to [bus 02]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: bridge window [mem 0xf7c00000-0xf7cfffff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: Enabling MPC IRBNCE
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: Intel PCH root port ACS workaround enabled
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1d.0: [8086:9c26] type 00 class 0x0c0320 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1d.0: BAR 0 [mem 0xf7d3b000-0xf7d3b3ff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.0: [8086:9c43] type 00 class 0x060100 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: [8086:9c03] type 00 class 0x010601 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: BAR 0 [io 0xf0d0-0xf0d7]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: BAR 1 [io 0xf0c0-0xf0c3]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: BAR 2 [io 0xf0b0-0xf0b7]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: BAR 3 [io 0xf0a0-0xf0a3]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: BAR 4 [io 0xf060-0xf07f]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: BAR 5 [mem 0xf7d3a000-0xf7d3a7ff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: PME# supported from D3hot
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.3: [8086:9c22] type 00 class 0x0c0500 conventional PCI endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.3: BAR 0 [mem 0xf7d39000-0xf7d390ff 64bit]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.3: BAR 4 [io 0xf040-0xf05f]
Mar 04 19:22:10 pve1 kernel: acpiphp: Slot [1] registered
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
Mar 04 19:22:10 pve1 kernel: pci 0000:02:00.0: [8086:08b1] type 00 class 0x028000 PCIe Endpoint
Mar 04 19:22:10 pve1 kernel: pci 0000:02:00.0: BAR 0 [mem 0xf7c00000-0xf7c01fff 64bit]
Mar 04 19:22:10 pve1 kernel: pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: PCI bridge to [bus 02]
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 11
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKB disabled
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 5
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 10
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 5
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKF disabled
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 11
Mar 04 19:22:10 pve1 kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 10
Mar 04 19:22:10 pve1 kernel: iommu: Default domain type: Translated
Mar 04 19:22:10 pve1 kernel: iommu: DMA domain TLB invalidation policy: lazy mode
Mar 04 19:22:10 pve1 kernel: SCSI subsystem initialized
Mar 04 19:22:10 pve1 kernel: libata version 3.00 loaded.
Mar 04 19:22:10 pve1 kernel: ACPI: bus type USB registered
Mar 04 19:22:10 pve1 kernel: usbcore: registered new interface driver usbfs
Mar 04 19:22:10 pve1 kernel: usbcore: registered new interface driver hub
Mar 04 19:22:10 pve1 kernel: usbcore: registered new device driver usb
Mar 04 19:22:10 pve1 kernel: pps_core: LinuxPPS API ver. 1 registered
Mar 04 19:22:10 pve1 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it
Mar 04 19:22:10 pve1 kernel: PTP clock support registered
Mar 04 19:22:10 pve1 kernel: EDAC MC: Ver: 3.0.0
Mar 04 19:22:10 pve1 kernel: efivars: Registered efivars operations
Mar 04 19:22:10 pve1 kernel: NetLabel: Initializing
Mar 04 19:22:10 pve1 kernel: NetLabel: domain hash size = 128
Mar 04 19:22:10 pve1 kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
Mar 04 19:22:10 pve1 kernel: NetLabel: unlabeled traffic allowed by default
Mar 04 19:22:10 pve1 kernel: mctp: management component transport protocol core
Mar 04 19:22:10 pve1 kernel: NET: Registered PF_MCTP protocol family
Mar 04 19:22:10 pve1 kernel: PCI: Using ACPI for IRQ routing
Mar 04 19:22:10 pve1 kernel: PCI: pci_cache_line_size set to 64 bytes
Mar 04 19:22:10 pve1 kernel: e820: reserve RAM buffer [mem 0x00058000-0x0005ffff]
Mar 04 19:22:10 pve1 kernel: e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
Mar 04 19:22:10 pve1 kernel: e820: reserve RAM buffer [mem 0xc5a31000-0xc7ffffff]
Mar 04 19:22:10 pve1 kernel: e820: reserve RAM buffer [mem 0xcb954000-0xcbffffff]
Mar 04 19:22:10 pve1 kernel: e820: reserve RAM buffer [mem 0xd9909000-0xdbffffff]
Mar 04 19:22:10 pve1 kernel: e820: reserve RAM buffer [mem 0xda000000-0xdbffffff]
Mar 04 19:22:10 pve1 kernel: e820: reserve RAM buffer [mem 0x21fe00000-0x21fffffff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: vgaarb: bridge control possible
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Mar 04 19:22:10 pve1 kernel: vgaarb: loaded
Mar 04 19:22:10 pve1 kernel: clocksource: Switched to clocksource tsc-early
Mar 04 19:22:10 pve1 kernel: VFS: Disk quotas dquot_6.6.0
Mar 04 19:22:10 pve1 kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Mar 04 19:22:10 pve1 kernel: AppArmor: AppArmor Filesystem Enabled
Mar 04 19:22:10 pve1 kernel: pnp: PnP ACPI init
Mar 04 19:22:10 pve1 kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0x0680-0x069f] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0xffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0xffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0xffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0x1c00-0x1cfe] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0x1d00-0x1dfe] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0x1e00-0x1efe] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0x1f00-0x1ffe] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0x1800-0x18fe] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:01: [io 0x164e-0x164f] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:03: [io 0x1854-0x1857] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:04: [io 0x0a00-0x0a1f] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:04: [io 0x0a00-0x0a0f] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe102000-0xfe102fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe104000-0xfe104fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe106000-0xfe106fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe108000-0xfe108fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe10a000-0xfe10afff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe10c000-0xfe10cfff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe10e000-0xfe10efff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe112000-0xfe112fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe111000-0xfe111007] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:07: [mem 0xfe111014-0xfe111fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfed1c000-0xfed1ffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfed10000-0xfed17fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xf8000000-0xfbffffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfed20000-0xfed3ffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfed90000-0xfed93fff] could not be reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfed45000-0xfed8ffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xff000000-0xffffffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xfee00000-0xfeefffff] could not be reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xf7fdf000-0xf7fdffff] has been reserved
Mar 04 19:22:10 pve1 kernel: system 00:08: [mem 0xf7fe0000-0xf7feffff] has been reserved
Mar 04 19:22:10 pve1 kernel: pnp: PnP ACPI: found 9 devices
Mar 04 19:22:10 pve1 kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Mar 04 19:22:10 pve1 kernel: NET: Registered PF_INET protocol family
Mar 04 19:22:10 pve1 kernel: IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear)
Mar 04 19:22:10 pve1 kernel: tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear)
Mar 04 19:22:10 pve1 kernel: Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
Mar 04 19:22:10 pve1 kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear)
Mar 04 19:22:10 pve1 kernel: TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)
Mar 04 19:22:10 pve1 kernel: TCP: Hash tables configured (established 65536 bind 65536)
Mar 04 19:22:10 pve1 kernel: MPTCP token hash table entries: 8192 (order: 5, 196608 bytes, linear)
Mar 04 19:22:10 pve1 kernel: UDP hash table entries: 4096 (order: 5, 131072 bytes, linear)
Mar 04 19:22:10 pve1 kernel: UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear)
Mar 04 19:22:10 pve1 kernel: NET: Registered PF_UNIX/PF_LOCAL protocol family
Mar 04 19:22:10 pve1 kernel: NET: Registered PF_XDP protocol family
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: PCI bridge to [bus 02]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: bridge window [mem 0xf7c00000-0xf7cfffff]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:00: resource 8 [mem 0xdf200000-0xfeafffff window]
Mar 04 19:22:10 pve1 kernel: pci_bus 0000:02: resource 1 [mem 0xf7c00000-0xf7cfffff]
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x780 took 16835 usecs
Mar 04 19:22:10 pve1 kernel: PCI: CLS 64 bytes, default 64
Mar 04 19:22:10 pve1 kernel: DMAR: ACPI device « INT33C2:00 » under DMAR at fed91000 as 00:15.1
Mar 04 19:22:10 pve1 kernel: DMAR: ACPI device « INT33C3:00 » under DMAR at fed91000 as 00:15.2
Mar 04 19:22:10 pve1 kernel: DMAR: ACPI device « INT33C0:00 » under DMAR at fed91000 as 00:15.3
Mar 04 19:22:10 pve1 kernel: DMAR: ACPI device « INT33C1:00 » under DMAR at fed91000 as 00:15.4
Mar 04 19:22:10 pve1 kernel: DMAR: ACPI device « INT33C4:00 » under DMAR at fed91000 as 00:15.5
Mar 04 19:22:10 pve1 kernel: DMAR: ACPI device « INT33C5:00 » under DMAR at fed91000 as 00:15.6
Mar 04 19:22:10 pve1 kernel: DMAR: ACPI device « INT33C6:00 » under DMAR at fed91000 as 00:17.0
Mar 04 19:22:10 pve1 kernel: DMAR: No ATSR found
Mar 04 19:22:10 pve1 kernel: DMAR: No SATC found
Mar 04 19:22:10 pve1 kernel: DMAR: IOMMU feature pgsel_inv inconsistent
Mar 04 19:22:10 pve1 kernel: DMAR: IOMMU feature sc_support inconsistent
Mar 04 19:22:10 pve1 kernel: DMAR: IOMMU feature pass_through inconsistent
Mar 04 19:22:10 pve1 kernel: DMAR: dmar0: Using Queued invalidation
Mar 04 19:22:10 pve1 kernel: DMAR: dmar1: Using Queued invalidation
Mar 04 19:22:10 pve1 kernel: Trying to unpack rootfs image as initramfs…
Mar 04 19:22:10 pve1 kernel: pci 0000:00:02.0: Adding to iommu group 0
Mar 04 19:22:10 pve1 kernel: pci 0000:00:00.0: Adding to iommu group 1
Mar 04 19:22:10 pve1 kernel: pci 0000:00:03.0: Adding to iommu group 2
Mar 04 19:22:10 pve1 kernel: pci 0000:00:14.0: Adding to iommu group 3
Mar 04 19:22:10 pve1 kernel: pci 0000:00:16.0: Adding to iommu group 4
Mar 04 19:22:10 pve1 kernel: pci 0000:00:19.0: Adding to iommu group 5
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1b.0: Adding to iommu group 6
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.0: Adding to iommu group 7
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1c.3: Adding to iommu group 8
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1d.0: Adding to iommu group 9
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.0: Adding to iommu group 10
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.2: Adding to iommu group 10
Mar 04 19:22:10 pve1 kernel: pci 0000:00:1f.3: Adding to iommu group 10
Mar 04 19:22:10 pve1 kernel: pci 0000:02:00.0: Adding to iommu group 11
Mar 04 19:22:10 pve1 kernel: DMAR: Intel(R) Virtualization Technology for Directed I/O
Mar 04 19:22:10 pve1 kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Mar 04 19:22:10 pve1 kernel: software IO TLB: mapped [mem 0x00000000c715b000-0x00000000cb15b000] (64MB)
Mar 04 19:22:10 pve1 kernel: Initialise system trusted keyrings
Mar 04 19:22:10 pve1 kernel: Key type blacklist registered
Mar 04 19:22:10 pve1 kernel: workingset: timestamp_bits=36 max_order=21 bucket_order=0
Mar 04 19:22:10 pve1 kernel: zbud: loaded
Mar 04 19:22:10 pve1 kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Mar 04 19:22:10 pve1 kernel: fuse: init (API version 7.39)
Mar 04 19:22:10 pve1 kernel: integrity: Platform Keyring initialized
Mar 04 19:22:10 pve1 kernel: integrity: Machine keyring initialized
Mar 04 19:22:10 pve1 kernel: Key type asymmetric registered
Mar 04 19:22:10 pve1 kernel: Asymmetric key parser ‹ x509 › registered
Mar 04 19:22:10 pve1 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
Mar 04 19:22:10 pve1 kernel: io scheduler mq-deadline registered
Mar 04 19:22:10 pve1 kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Mar 04 19:22:10 pve1 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
Mar 04 19:22:10 pve1 kernel: ACPI: button: Power Button [PWRB]
Mar 04 19:22:10 pve1 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Mar 04 19:22:10 pve1 kernel: ACPI: button: Power Button [PWRF]
Mar 04 19:22:10 pve1 kernel: thermal LNXTHERM:00: registered as thermal_zone0
Mar 04 19:22:10 pve1 kernel: ACPI: thermal: Thermal Zone [TZ00] (28 C)
Mar 04 19:22:10 pve1 kernel: thermal LNXTHERM:01: registered as thermal_zone1
Mar 04 19:22:10 pve1 kernel: ACPI: thermal: Thermal Zone [TZ01] (30 C)
Mar 04 19:22:10 pve1 kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Mar 04 19:22:10 pve1 kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Mar 04 19:22:10 pve1 kernel: hpet_acpi_add: no address or irqs in _CRS
Mar 04 19:22:10 pve1 kernel: Linux agpgart interface v0.103
Mar 04 19:22:10 pve1 kernel: loop: module loaded
Mar 04 19:22:10 pve1 kernel: ACPI: bus type drm_connector registered
Mar 04 19:22:10 pve1 kernel: tun: Universal TUN/TAP device driver, 1.6
Mar 04 19:22:10 pve1 kernel: PPP generic driver version 2.4.2
Mar 04 19:22:10 pve1 kernel: i8042: PNP: No PS/2 controller found.
Mar 04 19:22:10 pve1 kernel: mousedev: PS/2 mouse device common for all mice
Mar 04 19:22:10 pve1 kernel: rtc_cmos 00:02: RTC can wake from S4
Mar 04 19:22:10 pve1 kernel: rtc_cmos 00:02: registered as rtc0
Mar 04 19:22:10 pve1 kernel: rtc_cmos 00:02: setting system clock to 2025-03-04T18:22:06 UTC (1741112526)
Mar 04 19:22:10 pve1 kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram
Mar 04 19:22:10 pve1 kernel: i2c_dev: i2c /dev entries driver
Mar 04 19:22:10 pve1 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Mar 04 19:22:10 pve1 kernel: device-mapper: uevent: version 1.0.3
Mar 04 19:22:10 pve1 kernel: device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Probing EISA bus 0
Mar 04 19:22:10 pve1 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Mar 04 19:22:10 pve1 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Mar 04 19:22:10 pve1 kernel: platform eisa.0: EISA: Detected 0 cards
Mar 04 19:22:10 pve1 kernel: intel_pstate: Intel P-state driver initializing
Mar 04 19:22:10 pve1 kernel: ledtrig-cpu: registered to indicate activity on CPUs
Mar 04 19:22:10 pve1 kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
Mar 04 19:22:10 pve1 kernel: fbcon: Deferring console take-over
Mar 04 19:22:10 pve1 kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Mar 04 19:22:10 pve1 kernel: drop_monitor: Initializing network drop monitor service
Mar 04 19:22:10 pve1 kernel: NET: Registered PF_INET6 protocol family
Mar 04 19:22:10 pve1 kernel: Freeing initrd memory: 59840K
Mar 04 19:22:10 pve1 kernel: Segment Routing with IPv6
Mar 04 19:22:10 pve1 kernel: In-situ OAM (IOAM) with IPv6
Mar 04 19:22:10 pve1 kernel: NET: Registered PF_PACKET protocol family
Mar 04 19:22:10 pve1 kernel: Bridge firewalling registered
Mar 04 19:22:10 pve1 kernel: Key type dns_resolver registered
Mar 04 19:22:10 pve1 kernel: ENERGY_PERF_BIAS: Set to ‹ normal ›, was ‹ performance ›
Mar 04 19:22:10 pve1 kernel: microcode: Current revision: 0x0000001c
Mar 04 19:22:10 pve1 kernel: IPI shorthand broadcast: enabled
Mar 04 19:22:10 pve1 kernel: sched_clock: Marking stable (1167002839, -653166)->(1168522129, -2172456)
Mar 04 19:22:10 pve1 kernel: registered taskstats version 1
Mar 04 19:22:10 pve1 kernel: Loading compiled-in X.509 certificates
Mar 04 19:22:10 pve1 kernel: Loaded X.509 cert ‹ Build time autogenerated kernel key: 6d309e8f3156a5eb84afb20d509197bd84628d5b ›
Mar 04 19:22:10 pve1 kernel: Key type .fscrypt registered
Mar 04 19:22:10 pve1 kernel: Key type fscrypt-provisioning registered
Mar 04 19:22:10 pve1 kernel: Key type encrypted registered
Mar 04 19:22:10 pve1 kernel: AppArmor: AppArmor sha256 policy hashing enabled
Mar 04 19:22:10 pve1 kernel: integrity: Loading X.509 certificate: UEFI:db
Mar 04 19:22:10 pve1 kernel: integrity: Loaded X.509 cert ‹ Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53 ›
Mar 04 19:22:10 pve1 kernel: integrity: Loading X.509 certificate: UEFI:db
Mar 04 19:22:10 pve1 kernel: integrity: Loaded X.509 cert ‹ Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4 ›
Mar 04 19:22:10 pve1 kernel: ima: No TPM chip found, activating TPM-bypass!
Mar 04 19:22:10 pve1 kernel: Loading compiled-in module X.509 certificates
Mar 04 19:22:10 pve1 kernel: Loaded X.509 cert ‹ Build time autogenerated kernel key: 6d309e8f3156a5eb84afb20d509197bd84628d5b ›
Mar 04 19:22:10 pve1 kernel: ima: Allocated hash algorithm: sha256
Mar 04 19:22:10 pve1 kernel: ima: No architecture policies found
Mar 04 19:22:10 pve1 kernel: evm: Initialising EVM extended attributes:
Mar 04 19:22:10 pve1 kernel: evm: security.selinux
Mar 04 19:22:10 pve1 kernel: evm: security.SMACK64
Mar 04 19:22:10 pve1 kernel: evm: security.SMACK64EXEC
Mar 04 19:22:10 pve1 kernel: evm: security.SMACK64TRANSMUTE
Mar 04 19:22:10 pve1 kernel: evm: security.SMACK64MMAP
Mar 04 19:22:10 pve1 kernel: evm: security.apparmor
Mar 04 19:22:10 pve1 kernel: evm: security.ima
Mar 04 19:22:10 pve1 kernel: evm: security.capability
Mar 04 19:22:10 pve1 kernel: evm: HMAC attrs: 0x1
Mar 04 19:22:10 pve1 kernel: PM: Magic number: 1:15:392
Mar 04 19:22:10 pve1 kernel: thermal cooling_device7: hash matches
Mar 04 19:22:10 pve1 kernel: acpi PNP0C0D:00: hash matches
Mar 04 19:22:10 pve1 kernel: RAS: Correctable Errors collector initialized.
Mar 04 19:22:10 pve1 kernel: clk: Disabling unused clocks
Mar 04 19:22:10 pve1 kernel: Freeing unused decrypted memory: 2028K
Mar 04 19:22:10 pve1 kernel: Freeing unused kernel image (initmem) memory: 4804K
Mar 04 19:22:10 pve1 kernel: Write protecting the kernel read-only data: 34816k
Mar 04 19:22:10 pve1 kernel: Freeing unused kernel image (rodata/data gap) memory: 904K
Mar 04 19:22:10 pve1 kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Mar 04 19:22:10 pve1 kernel: x86/mm: Checking user space page tables
Mar 04 19:22:10 pve1 kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Mar 04 19:22:10 pve1 kernel: Run /init as init process
Mar 04 19:22:10 pve1 kernel: with arguments:
Mar 04 19:22:10 pve1 kernel: /init
Mar 04 19:22:10 pve1 kernel: with environment:
Mar 04 19:22:10 pve1 kernel: HOME=/
Mar 04 19:22:10 pve1 kernel: TERM=linux
Mar 04 19:22:10 pve1 kernel: BOOT_IMAGE=/boot/vmlinuz-6.8.12-2-pve
Mar 04 19:22:10 pve1 kernel: tsc: Refined TSC clocksource calibration: 1696.074 MHz
Mar 04 19:22:10 pve1 kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1872aa7eed8, max_idle_ns: 440795242723 ns
Mar 04 19:22:10 pve1 kernel: clocksource: Switched to clocksource tsc
Mar 04 19:22:10 pve1 kernel: e1000e: Intel(R) PRO/1000 Network Driver
Mar 04 19:22:10 pve1 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
Mar 04 19:22:10 pve1 kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
Mar 04 19:22:10 pve1 kernel: i801_smbus 0000:00:1f.3: SPD Write Disable is set
Mar 04 19:22:10 pve1 kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
Mar 04 19:22:10 pve1 kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Mar 04 19:22:10 pve1 kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 1
Mar 04 19:22:10 pve1 kernel: ehci-pci 0000:00:1d.0: debug port 2
Mar 04 19:22:10 pve1 kernel: i2c i2c-0: 1/2 memory slots populated (from DMI)
Mar 04 19:22:10 pve1 kernel: i2c i2c-0: Successfully instantiated SPD at 0x50
Mar 04 19:22:10 pve1 kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7d3b000
Mar 04 19:22:10 pve1 kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Mar 04 19:22:10 pve1 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
Mar 04 19:22:10 pve1 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar 04 19:22:10 pve1 kernel: usb usb1: Product: EHCI Host Controller
Mar 04 19:22:10 pve1 kernel: usb usb1: Manufacturer: Linux 6.8.12-2-pve ehci_hcd
Mar 04 19:22:10 pve1 kernel: usb usb1: SerialNumber: 0000:00:1d.0
Mar 04 19:22:10 pve1 kernel: hub 1-0:1.0: USB hub found
Mar 04 19:22:10 pve1 kernel: hub 1-0:1.0: 2 ports detected
Mar 04 19:22:10 pve1 kernel: ahci 0000:00:1f.2: version 3.0
Mar 04 19:22:10 pve1 kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar 04 19:22:10 pve1 kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Mar 04 19:22:10 pve1 kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x000000000004b810
Mar 04 19:22:10 pve1 kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar 04 19:22:10 pve1 kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
Mar 04 19:22:10 pve1 kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
Mar 04 19:22:10 pve1 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
Mar 04 19:22:10 pve1 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar 04 19:22:10 pve1 kernel: usb usb2: Product: xHCI Host Controller
Mar 04 19:22:10 pve1 kernel: usb usb2: Manufacturer: Linux 6.8.12-2-pve xhci-hcd
Mar 04 19:22:10 pve1 kernel: usb usb2: SerialNumber: 0000:00:14.0
Mar 04 19:22:10 pve1 kernel: hub 2-0:1.0: USB hub found
Mar 04 19:22:10 pve1 kernel: hub 2-0:1.0: 9 ports detected
Mar 04 19:22:10 pve1 kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
Mar 04 19:22:10 pve1 kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar 04 19:22:10 pve1 kernel: usb usb3: Product: xHCI Host Controller
Mar 04 19:22:10 pve1 kernel: usb usb3: Manufacturer: Linux 6.8.12-2-pve xhci-hcd
Mar 04 19:22:10 pve1 kernel: usb usb3: SerialNumber: 0000:00:14.0
Mar 04 19:22:10 pve1 kernel: hub 3-0:1.0: USB hub found
Mar 04 19:22:10 pve1 kernel: hub 3-0:1.0: 4 ports detected
Mar 04 19:22:10 pve1 kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x8 impl SATA mode
Mar 04 19:22:10 pve1 kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst
Mar 04 19:22:10 pve1 kernel: scsi host0: ahci
Mar 04 19:22:10 pve1 kernel: scsi host1: ahci
Mar 04 19:22:10 pve1 kernel: scsi host2: ahci
Mar 04 19:22:10 pve1 kernel: scsi host3: ahci
Mar 04 19:22:10 pve1 kernel: ata1: DUMMY
Mar 04 19:22:10 pve1 kernel: ata2: DUMMY
Mar 04 19:22:10 pve1 kernel: ata3: DUMMY
Mar 04 19:22:10 pve1 kernel: ata4: SATA max UDMA/133 abar m2048@0xf7d3a000 port 0xf7d3a280 irq 45 lpm-pol 3
Mar 04 19:22:10 pve1 kernel: e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
Mar 04 19:22:10 pve1 kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Mar 04 19:22:10 pve1 kernel: usb 2-1: new full-speed USB device number 2 using xhci_hcd
Mar 04 19:22:10 pve1 kernel: e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) ec:a8:6b:fd:05:69
Mar 04 19:22:10 pve1 kernel: e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
Mar 04 19:22:10 pve1 kernel: e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
Mar 04 19:22:10 pve1 kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 04 19:22:10 pve1 kernel: ata4.00: supports DRM functions and may not be fully accessible
Mar 04 19:22:10 pve1 kernel: ata4.00: ATA-9: Crucial_CT120M500SSD3, MU05, max UDMA/133
Mar 04 19:22:10 pve1 kernel: ata4.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 32), AA
Mar 04 19:22:10 pve1 kernel: ata4.00: Features: Trust Dev-Sleep NCQ-sndrcv NCQ-prio
Mar 04 19:22:10 pve1 kernel: ata4.00: supports DRM functions and may not be fully accessible
Mar 04 19:22:10 pve1 kernel: usb 1-1: New USB device found, idVendor=8087, idProduct=8000, bcdDevice= 0.04
Mar 04 19:22:10 pve1 kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 04 19:22:10 pve1 kernel: hub 1-1:1.0: USB hub found
Mar 04 19:22:10 pve1 kernel: hub 1-1:1.0: 8 ports detected
Mar 04 19:22:10 pve1 kernel: usb 2-1: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Mar 04 19:22:10 pve1 kernel: usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 04 19:22:10 pve1 kernel: ata4.00: configured for UDMA/133
Mar 04 19:22:10 pve1 kernel: ahci 0000:00:1f.2: port does not support device sleep
Mar 04 19:22:10 pve1 kernel: scsi 3:0:0:0: Direct-Access ATA Crucial_CT120M50 MU05 PQ: 0 ANSI: 5
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: Attached scsi generic sg0 type 0
Mar 04 19:22:10 pve1 kernel: ata4.00: Enabling discard_zeroes_data
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] 4096-byte physical blocks
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] Write Protect is off
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Mar 04 19:22:10 pve1 kernel: ata4.00: Enabling discard_zeroes_data
Mar 04 19:22:10 pve1 kernel: sda: sda1 sda2 sda3
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] supports TCG Opal
Mar 04 19:22:10 pve1 kernel: sd 3:0:0:0: [sda] Attached SCSI disk
Mar 04 19:22:10 pve1 kernel: e1000e 0000:00:19.0 eno1: renamed from eth0
Mar 04 19:22:10 pve1 kernel: usb 2-4: new high-speed USB device number 3 using xhci_hcd
Mar 04 19:22:10 pve1 kernel: usb 2-4: New USB device found, idVendor=1a40, idProduct=0201, bcdDevice= 1.00
Mar 04 19:22:10 pve1 kernel: usb 2-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Mar 04 19:22:10 pve1 kernel: usb 2-4: Product: USB 2.0 Hub [MTT]
Mar 04 19:22:10 pve1 kernel: hub 2-4:1.0: USB hub found
Mar 04 19:22:10 pve1 kernel: hub 2-4:1.0: 7 ports detected
Mar 04 19:22:10 pve1 kernel: usb 2-7: new full-speed USB device number 4 using xhci_hcd
Mar 04 19:22:10 pve1 kernel: usb 2-7: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
Mar 04 19:22:10 pve1 kernel: usb 2-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 04 19:22:10 pve1 kernel: usb 2-4.3: new full-speed USB device number 5 using xhci_hcd
Mar 04 19:22:10 pve1 kernel: usb 2-4.3: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Mar 04 19:22:10 pve1 kernel: usb 2-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 04 19:22:10 pve1 kernel: usb 2-4.3: Product: RFPLAYER
Mar 04 19:22:10 pve1 kernel: usb 2-4.3: Manufacturer: Ziblue
Mar 04 19:22:10 pve1 kernel: usb 2-4.3: SerialNumber: A133VCO1
Mar 04 19:22:10 pve1 kernel: usb 2-4.4: new full-speed USB device number 6 using xhci_hcd
Mar 04 19:22:10 pve1 kernel: usb 2-4.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Mar 04 19:22:10 pve1 kernel: usb 2-4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 04 19:22:10 pve1 kernel: usb 2-4.4: Product: RFXtrx433
Mar 04 19:22:10 pve1 kernel: usb 2-4.4: Manufacturer: RFXCOM
Mar 04 19:22:10 pve1 kernel: usb 2-4.4: SerialNumber: A1Z68ZBX
Mar 04 19:22:10 pve1 kernel: fbcon: Taking over console
Mar 04 19:22:10 pve1 kernel: Console: switching to colour frame buffer device 128x48
Mar 04 19:22:10 pve1 kernel: usb 2-4.5: new full-speed USB device number 7 using xhci_hcd
Mar 04 19:22:10 pve1 kernel: raid6: avx2x4 gen() 16416 MB/s
Mar 04 19:22:10 pve1 kernel: raid6: avx2x2 gen() 16357 MB/s
Mar 04 19:22:10 pve1 kernel: usb 2-4.5: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Mar 04 19:22:10 pve1 kernel: usb 2-4.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 04 19:22:10 pve1 kernel: usb 2-4.5: Product: Sonoff Zigbee 3.0 USB Dongle Plus
Mar 04 19:22:10 pve1 kernel: usb 2-4.5: Manufacturer: ITead
Mar 04 19:22:10 pve1 kernel: usb 2-4.5: SerialNumber: a0ab5647675aee118c1381dc8ffcc75d
Mar 04 19:22:10 pve1 kernel: raid6: avx2x1 gen() 14740 MB/s
Mar 04 19:22:10 pve1 kernel: raid6: using algorithm avx2x4 gen() 16416 MB/s
Mar 04 19:22:10 pve1 kernel: raid6: … xor() 8188 MB/s, rmw enabled
Mar 04 19:22:10 pve1 kernel: raid6: using avx2x2 recovery algorithm
Mar 04 19:22:10 pve1 kernel: xor: automatically using best checksumming function avx
Mar 04 19:22:10 pve1 kernel: Btrfs loaded, zoned=yes, fsverity=yes
Mar 04 19:22:10 pve1 kernel: EXT4-fs (dm-1): mounted filesystem ac6a393a-81a8-4961-b074-b04569e662aa ro with ordered data mode. Quota mode: none.
Mar 04 19:22:10 pve1 systemd: Inserted module ‹ autofs4 ›
Mar 04 19:22:10 pve1 systemd: systemd 252.30-1~deb12u2 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
Mar 04 19:22:10 pve1 systemd: Detected architecture x86-64.
Mar 04 19:22:10 pve1 systemd: Hostname set to .
Mar 04 19:22:10 pve1 systemd: Queued start job for default target graphical.target.
Mar 04 19:22:10 pve1 systemd: Created slice system-getty.slice - Slice /system/getty.
Mar 04 19:22:10 pve1 systemd: Created slice system-modprobe.slice - Slice /system/modprobe.
Mar 04 19:22:10 pve1 systemd: Created slice system-postfix.slice - Slice /system/postfix.
Mar 04 19:22:10 pve1 systemd: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
Mar 04 19:22:10 pve1 systemd: Created slice user.slice - User and Session Slice.
Mar 04 19:22:10 pve1 systemd: Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch.
Mar 04 19:22:10 pve1 systemd: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
Mar 04 19:22:10 pve1 systemd: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
Mar 04 19:22:10 pve1 systemd: Expecting device dev-disk-by\x2duuid-CE94\x2d0C9D.device - /dev/disk/by-uuid/CE94-0C9D…
Mar 04 19:22:10 pve1 systemd: Expecting device dev-pve-swap.device - /dev/pve/swap…
Mar 04 19:22:10 pve1 systemd: Reached target ceph-fuse.target - ceph target allowing to start/stop all ceph-fuse@.service instances at once.
Mar 04 19:22:10 pve1 systemd: Reached target ceph.target - ceph target allowing to start/stop all ceph*@.service instances at once.
Mar 04 19:22:10 pve1 systemd: Reached target cryptsetup.target - Local Encrypted Volumes.
Mar 04 19:22:10 pve1 systemd: Reached target integritysetup.target - Local Integrity Protected Volumes.
Mar 04 19:22:10 pve1 systemd: Reached target paths.target - Path Units.
Mar 04 19:22:10 pve1 systemd: Reached target slices.target - Slice Units.
Mar 04 19:22:10 pve1 systemd: Reached target time-set.target - System Time Set.
Mar 04 19:22:10 pve1 systemd: Reached target veritysetup.target - Local Verity Protected Volumes.
Mar 04 19:22:10 pve1 systemd: Listening on dm-event.socket - Device-mapper event daemon FIFOs.
Mar 04 19:22:10 pve1 systemd: Listening on lvm2-lvmpolld.socket - LVM2 poll daemon socket.
Mar 04 19:22:10 pve1 systemd: Listening on rpcbind.socket - RPCbind Server Activation Socket.
Mar 04 19:22:10 pve1 systemd: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket.
Mar 04 19:22:10 pve1 systemd: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
Mar 04 19:22:10 pve1 systemd: Listening on systemd-journald-audit.socket - Journal Audit Socket.
Mar 04 19:22:10 pve1 systemd: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
Mar 04 19:22:10 pve1 systemd: Listening on systemd-journald.socket - Journal Socket.
Mar 04 19:22:10 pve1 systemd: Listening on systemd-udevd-control.socket - udev Control Socket.
Mar 04 19:22:10 pve1 systemd: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
Mar 04 19:22:10 pve1 systemd: Mounting dev-hugepages.mount - Huge Pages File System…
Mar 04 19:22:10 pve1 systemd: Mounting dev-mqueue.mount - POSIX Message Queue File System…
Mar 04 19:22:10 pve1 systemd: Mounting sys-kernel-debug.mount - Kernel Debug File System…
Mar 04 19:22:10 pve1 systemd: Mounting sys-kernel-tracing.mount - Kernel Trace File System…
Mar 04 19:22:10 pve1 systemd: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).
Mar 04 19:22:10 pve1 systemd: Starting keyboard-setup.service - Set the console keyboard layout…
Mar 04 19:22:10 pve1 systemd: Starting kmod-static-nodes.service - Create List of Static Device Nodes…
Mar 04 19:22:10 pve1 systemd: Starting lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling…
Mar 04 19:22:10 pve1 systemd: Starting modprobe@configfs.service - Load Kernel Module configfs…
Mar 04 19:22:10 pve1 systemd: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod…
Mar 04 19:22:10 pve1 systemd: Starting modprobe@drm.service - Load Kernel Module drm…
Mar 04 19:22:10 pve1 systemd: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore…
Mar 04 19:22:10 pve1 systemd: Starting modprobe@fuse.service - Load Kernel Module fuse…
Mar 04 19:22:10 pve1 systemd: Starting modprobe@loop.service - Load Kernel Module loop…
Mar 04 19:22:10 pve1 systemd: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root).
Mar 04 19:22:10 pve1 systemd: Starting systemd-journald.service - Journal Service…
Mar 04 19:22:10 pve1 kernel: pstore: Using crash dump compression: deflate
Mar 04 19:22:10 pve1 systemd: Starting systemd-modules-load.service - Load Kernel Modules…
Mar 04 19:22:10 pve1 systemd: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems…
Mar 04 19:22:10 pve1 kernel: pstore: Registered efi_pstore as persistent store backend
Mar 04 19:22:10 pve1 systemd: Starting systemd-udev-trigger.service - Coldplug All udev Devices…
Mar 04 19:22:10 pve1 systemd: Mounted dev-hugepages.mount - Huge Pages File System.
Mar 04 19:22:10 pve1 systemd: Mounted dev-mqueue.mount - POSIX Message Queue File System.
Mar 04 19:22:10 pve1 systemd: Mounted sys-kernel-debug.mount - Kernel Debug File System.
Mar 04 19:22:10 pve1 systemd: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
Mar 04 19:22:10 pve1 systemd: Finished keyboard-setup.service - Set the console keyboard layout.
Mar 04 19:22:10 pve1 systemd: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
Mar 04 19:22:10 pve1 systemd: modprobe@configfs.service: Deactivated successfully.
Mar 04 19:22:10 pve1 systemd: Finished modprobe@configfs.service - Load Kernel Module configfs.
Mar 04 19:22:10 pve1 systemd: modprobe@dm_mod.service: Deactivated successfully.
Mar 04 19:22:10 pve1 systemd: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
Mar 04 19:22:10 pve1 systemd: modprobe@drm.service: Deactivated successfully.
Mar 04 19:22:10 pve1 systemd: Finished modprobe@drm.service - Load Kernel Module drm.
Mar 04 19:22:10 pve1 systemd: modprobe@efi_pstore.service: Deactivated successfully.
Mar 04 19:22:10 pve1 systemd: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
Mar 04 19:22:10 pve1 systemd: modprobe@fuse.service: Deactivated successfully.
Mar 04 19:22:10 pve1 systemd: Finished modprobe@fuse.service - Load Kernel Module fuse.
Mar 04 19:22:10 pve1 systemd: modprobe@loop.service: Deactivated successfully.
Mar 04 19:22:10 pve1 systemd: Finished modprobe@loop.service - Load Kernel Module loop.
Mar 04 19:22:10 pve1 systemd: Mounting sys-fs-fuse-connections.mount - FUSE Control File System…
Mar 04 19:22:10 pve1 systemd: Mounting sys-kernel-config.mount - Kernel Configuration File System…
Mar 04 19:22:10 pve1 systemd: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
Mar 04 19:22:10 pve1 systemd: Mounted sys-fs-fuse-connections.mount - FUSE Control File System.
Mar 04 19:22:10 pve1 systemd: Mounted sys-kernel-config.mount - Kernel Configuration File System.
Mar 04 19:22:10 pve1 kernel: EXT4-fs (dm-1): re-mounted ac6a393a-81a8-4961-b074-b04569e662aa r/w. Quota mode: none.
Mar 04 19:22:10 pve1 systemd: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
Mar 04 19:22:10 pve1 systemd: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Mar 04 19:22:10 pve1 systemd: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
Mar 04 19:22:10 pve1 systemd: Starting systemd-random-seed.service - Load/Save Random Seed…
Mar 04 19:22:10 pve1 systemd: Starting systemd-sysusers.service - Create System Users…
Mar 04 19:22:10 pve1 systemd: Started dm-event.service - Device-mapper event daemon.
Mar 04 19:22:10 pve1 kernel: spl: loading out-of-tree module taints kernel.
Mar 04 19:22:10 pve1 systemd-journald[342]: Journal started
Mar 04 19:22:10 pve1 systemd-journald[342]: Runtime Journal (/run/log/journal/1a8bd17911384726877a44050114b839) is 8.0M, max 78.3M, 70.3M free.
Mar 04 19:22:10 pve1 systemd-modules-load[343]: Inserted module ‹ vhost_net ›
Mar 04 19:22:10 pve1 systemd: Started systemd-journald.service - Journal Service.
Mar 04 19:22:10 pve1 dmeventd[355]: dmeventd ready for processing.
Mar 04 19:22:10 pve1 kernel: zfs: module license ‹ CDDL › taints kernel.
Mar 04 19:22:10 pve1 kernel: Disabling lock debugging due to kernel taint
Mar 04 19:22:10 pve1 kernel: zfs: module license taints kernel.
Mar 04 19:22:10 pve1 systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage…
Mar 04 19:22:10 pve1 systemd[1]: Finished systemd-random-seed.service - Load/Save Random Seed.
Mar 04 19:22:10 pve1 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes).
Mar 04 19:22:10 pve1 systemd[1]: Finished systemd-sysusers.service - Create System Users.
Mar 04 19:22:10 pve1 systemd-journald[342]: Time spent on flushing to /var/log/journal/1a8bd17911384726877a44050114b839 is 11.306ms for 859 entries.
Mar 04 19:22:10 pve1 systemd-journald[342]: System Journal (/var/log/journal/1a8bd17911384726877a44050114b839) is 1.9G, max 1.9G, 36.0M free.
Mar 04 19:22:10 pve1 systemd-journald[342]: Received client request to flush runtime journal.
Mar 04 19:22:10 pve1 systemd-journald[342]: File /var/log/journal/1a8bd17911384726877a44050114b839/system.journal corrupted or uncleanly shut down, renaming and replacing.
Mar 04 19:22:10 pve1 dmeventd[355]: Monitoring thin pool pve-data-tpool.
Mar 04 19:22:10 pve1 lvm[335]: 11 logical volume(s) in volume group « pve » monitored
Mar 04 19:22:11 pve1 systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev…
Mar 04 19:22:11 pve1 systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices.
Mar 04 19:22:11 pve1 systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage.
Mar 04 19:22:11 pve1 systemd[1]: Starting ifupdown2-pre.service - Helper to synchronize boot up for ifupdown…
Mar 04 19:22:11 pve1 systemd[1]: Starting systemd-udev-settle.service - Wait for udev To Complete Device Initialization…
Mar 04 19:22:11 pve1 udevadm[370]: systemd-udev-settle.service is deprecated. Please fix zfs-import-scan.service, zfs-import-cache.service not to pull it in.
Mar 04 19:22:11 pve1 systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
Mar 04 19:22:11 pve1 systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files…
Mar 04 19:22:11 pve1 systemd[1]: Finished lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 04 19:22:11 pve1 systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems.
Mar 04 19:22:11 pve1 systemd-udevd[371]: Using default interface naming scheme ‹ v252 ›.
Mar 04 19:22:11 pve1 systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files.
Mar 04 19:22:11 pve1 systemd[1]: Found device dev-pve-swap.device - /dev/pve/swap.
Mar 04 19:22:11 pve1 kernel: nuvoton-cir 00:05: [io 0x0240-0x024f]
Mar 04 19:22:13 pve1 kernel: nuvoton-cir 00:05: [io 0x0250-0x025f]
Mar 04 19:22:13 pve1 kernel: nuvoton-cir 00:05: activated
Mar 04 19:22:13 pve1 kernel: nuvoton-cir 00:05: found NCT6776F or compatible: chip id: 0xc3 0x33
Mar 04 19:22:13 pve1 kernel: at24 0-0050: supply vcc not found, using dummy regulator
Mar 04 19:22:13 pve1 kernel: at24 0-0050: 256 byte spd EEPROM, read-only
Mar 04 19:22:13 pve1 kernel: input: PC Speaker as /devices/platform/pcspkr/input/input3
Mar 04 19:22:13 pve1 kernel: spi-nor: probe of spi0.0 failed with error -22
Mar 04 19:22:13 pve1 kernel: usbcore: registered new interface driver usbserial_generic
Mar 04 19:22:13 pve1 kernel: usbserial: USB Serial support registered for generic
Mar 04 19:22:13 pve1 kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Mar 04 19:22:13 pve1 kernel: usbcore: registered new interface driver cp210x
Mar 04 19:22:13 pve1 kernel: usbserial: USB Serial support registered for cp210x
Mar 04 19:22:13 pve1 kernel: cp210x 2-4.5:1.0: cp210x converter detected
Mar 04 19:22:13 pve1 kernel: cdc_acm 2-1:1.0: ttyACM0: USB ACM device
Mar 04 19:22:13 pve1 kernel: usbcore: registered new interface driver cdc_acm
Mar 04 19:22:13 pve1 kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Mar 04 19:22:13 pve1 kernel: usbcore: registered new interface driver ftdi_sio
Mar 04 19:22:13 pve1 kernel: usbserial: USB Serial support registered for FTDI USB Serial Device
Mar 04 19:22:13 pve1 kernel: ftdi_sio 2-4.3:1.0: FTDI USB Serial Device converter detected
Mar 04 19:22:13 pve1 kernel: usb 2-4.3: Detected FT232R
Mar 04 19:22:13 pve1 kernel: usb 2-4.5: cp210x converter now attached to ttyUSB1
Mar 04 19:22:13 pve1 kernel: Loaded X.509 cert ‹ benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf ›
Mar 04 19:22:13 pve1 kernel: Loaded X.509 cert ‹ romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328 ›
Mar 04 19:22:13 pve1 kernel: Loaded X.509 cert ‹ sforshee: 00b28ddf47aef9cea7 ›
Mar 04 19:22:13 pve1 kernel: Loaded X.509 cert ‹ wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600 ›
Mar 04 19:22:13 pve1 kernel: usb 2-4.3: FTDI USB Serial Device converter now attached to ttyUSB0
Mar 04 19:22:13 pve1 kernel: ftdi_sio 2-4.4:1.0: FTDI USB Serial Device converter detected
Mar 04 19:22:13 pve1 kernel: usb 2-4.4: Detected FT232R
Mar 04 19:22:13 pve1 kernel: usb 2-4.4: FTDI USB Serial Device converter now attached to ttyUSB2
Mar 04 19:22:13 pve1 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Mar 04 19:22:13 pve1 kernel: cfg80211: failed to load regulatory.db
Mar 04 19:22:13 pve1 kernel: Bluetooth: Core ver 2.22
Mar 04 19:22:13 pve1 kernel: NET: Registered PF_BLUETOOTH protocol family
Mar 04 19:22:13 pve1 kernel: Bluetooth: HCI device and connection manager initialized
Mar 04 19:22:13 pve1 kernel: Bluetooth: HCI socket layer initialized
Mar 04 19:22:13 pve1 kernel: Bluetooth: L2CAP socket layer initialized
Mar 04 19:22:13 pve1 kernel: Bluetooth: SCO socket layer initialized
Mar 04 19:22:13 pve1 kernel: Intel(R) Wireless WiFi driver for Linux
Mar 04 19:22:13 pve1 kernel: iwlwifi 0000:02:00.0: enabling device (0000 → 0002)
Mar 04 19:22:13 pve1 kernel: iwlwifi 0000:02:00.0: Detected crf-id 0x0, cnv-id 0x0 wfpm id 0x0
Mar 04 19:22:13 pve1 kernel: iwlwifi 0000:02:00.0: PCI dev 08b1/4062, rev=0x144, rfid=0xd55555d5
Mar 04 19:22:13 pve1 kernel: snd_hda_intel 0000:00:03.0: enabling device (0000 → 0002)
Mar 04 19:22:13 pve1 kernel: snd_hda_intel 0000:00:1b.0: enabling device (0000 → 0002)
Mar 04 19:22:13 pve1 kernel: iwlwifi 0000:02:00.0: loaded firmware version 17.3216344376.0 7260-17.ucode op_mode iwlmvm
Mar 04 19:22:13 pve1 kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC283: line_outs=1 (0x21/0x0/0x0/0x0/0x0) type:hp
Mar 04 19:22:13 pve1 kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Mar 04 19:22:13 pve1 kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
Mar 04 19:22:13 pve1 kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
Mar 04 19:22:13 pve1 kernel: snd_hda_codec_realtek hdaudioC0D0: inputs:
Mar 04 19:22:13 pve1 kernel: snd_hda_codec_realtek hdaudioC0D0: Mic=0x19
Mar 04 19:22:13 pve1 kernel: usbcore: registered new interface driver btusb
Mar 04 19:22:13 pve1 kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
Mar 04 19:22:13 pve1 kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
Mar 04 19:22:13 pve1 kernel: Adding 8011772k swap on /dev/mapper/pve-swap. Priority:-2 extents:1 across:8011772k SS
Mar 04 19:22:13 pve1 kernel: Registered IR keymap rc-rc6-mce
Mar 04 19:22:13 pve1 kernel: IR RC6 protocol handler initialized
Mar 04 19:22:13 pve1 kernel: rc rc0: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:05/rc/rc0
Mar 04 19:22:13 pve1 kernel: rc rc0: lirc_dev: driver nuvoton-cir registered at minor = 0, raw IR receiver, no transmitter
Mar 04 19:22:13 pve1 kernel: input: Nuvoton w836x7hg Infrared Remote Transceiver as /devices/pnp0/00:05/rc/rc0/input2
Mar 04 19:22:13 pve1 kernel: nuvoton-cir 00:05: driver has been successfully loaded
Mar 04 19:22:13 pve1 lvm[478]: PV /dev/sda3 online, VG pve is complete.
Mar 04 19:22:13 pve1 lvm[478]: VG pve finished
Mar 04 19:22:13 pve1 systemd[1]: Activating swap dev-pve-swap.swap - /dev/pve/swap…
Mar 04 19:22:13 pve1 systemd-fsck[513]: fsck.fat 4.2 (2021-01-31)
Mar 04 19:22:13 pve1 systemd-fsck[513]: There are differences between boot sector and its backup.
Mar 04 19:22:13 pve1 systemd-fsck[513]: This is mostly harmless. Differences: (offset:original/backup)
Mar 04 19:22:13 pve1 systemd-fsck[513]: 65:01/00
Mar 04 19:22:13 pve1 systemd-fsck[513]: Not automatically fixing this.
Mar 04 19:22:13 pve1 systemd-fsck[513]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Mar 04 19:22:13 pve1 systemd-fsck[513]: Automatically removing dirty bit.
Mar 04 19:22:13 pve1 systemd-fsck[513]: *** Filesystem was changed ***
Mar 04 19:22:13 pve1 systemd-fsck[513]: Writing changes.
Mar 04 19:22:13 pve1 systemd-fsck[513]: /dev/sda2: 13 files, 2981/261627 clusters
Mar 04 19:22:13 pve1 systemd[1]: Found device dev-disk-by\x2duuid-CE94\x2d0C9D.device - Crucial_CT120M500SSD3 2.
Mar 04 19:22:13 pve1 systemd[1]: Starting systemd-fsck@dev-disk-by\x2duuid-CE94\x2d0C9D.service - File System Check on /dev/disk/by-uuid/CE94-0C9D…
Mar 04 19:22:13 pve1 systemd[1]: Activated swap dev-pve-swap.swap - /dev/pve/swap.
Mar 04 19:22:13 pve1 systemd[1]: Reached target swap.target - Swaps.
Mar 04 19:22:13 pve1 systemd[1]: Started systemd-fsckd.service - File System Check Daemon to report status.
Mar 04 19:22:13 pve1 systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch.
Mar 04 19:22:13 pve1 systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status…
Mar 04 19:22:13 pve1 systemd[1]: Finished systemd-fsck@dev-disk-by\x2duuid-CE94\x2d0C9D.service - File System Check on /dev/disk/by-uuid/CE94-0C9D.
Mar 04 19:22:13 pve1 systemd[1]: Mounting boot-efi.mount - /boot/efi…
Mar 04 19:22:13 pve1 systemd[1]: Mounted boot-efi.mount - /boot/efi.
Mar 04 19:22:13 pve1 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 04 19:22:13 pve1 systemd[1]: Reached target sound.target - Sound Card.
Mar 04 19:22:13 pve1 systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Mar 04 19:22:13 pve1 kernel: iwlwifi 0000:02:00.0: Detected Intel(R) Wireless N 7260, REV=0x144
Mar 04 19:22:13 pve1 kernel: iwlwifi 0000:02:00.0: base HW address: 0c:8b:fd:ee:72:58, OTP minor version: 0x0
Mar 04 19:22:13 pve1 kernel: RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
Mar 04 19:22:13 pve1 kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Mar 04 19:22:13 pve1 kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Mar 04 19:22:13 pve1 kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Mar 04 19:22:13 pve1 kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
Mar 04 19:22:13 pve1 kernel: Console: switching to colour dummy device 80x25
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: [drm] DMAR active, disabling use of stolen memory
Mar 04 19:22:13 pve1 kernel: ieee80211 phy0: Selected rate control algorithm ‹ iwl-mvm-rs ›
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Mar 04 19:22:13 pve1 kernel: [drm] Initialized i915 1.6.0 20230929 for 0000:00:02.0 on minor 1
Mar 04 19:22:13 pve1 kernel: cryptd: max_cpu_qlen set to 1000
Mar 04 19:22:13 pve1 kernel: iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
Mar 04 19:22:13 pve1 kernel: ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no)
Mar 04 19:22:13 pve1 kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
Mar 04 19:22:13 pve1 kernel: i915 display info: display version: 7
Mar 04 19:22:13 pve1 kernel: i915 display info: cursor_needs_physical: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_cdclk_crawl: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_cdclk_squash: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_ddi: yes
Mar 04 19:22:13 pve1 kernel: i915 display info: has_dp_mst: yes
Mar 04 19:22:13 pve1 kernel: i915 display info: has_dsb: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_fpga_dbg: yes
Mar 04 19:22:13 pve1 kernel: i915 display info: has_gmch: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_hotplug: yes
Mar 04 19:22:13 pve1 kernel: i915 display info: has_hti: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_ipc: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_overlay: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_psr: yes
Mar 04 19:22:13 pve1 kernel: i915 display info: has_psr_hw_tracking: yes
Mar 04 19:22:13 pve1 kernel: i915 display info: overlay_needs_physical: no
Mar 04 19:22:13 pve1 kernel: i915 display info: supports_tv: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_hdcp: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_dmc: no
Mar 04 19:22:13 pve1 kernel: i915 display info: has_dsc: no
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mar 04 19:22:13 pve1 kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Mar 04 19:22:13 pve1 kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mar 04 19:22:13 pve1 kernel: input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card1/input7
Mar 04 19:22:13 pve1 kernel: input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card1/input8
Mar 04 19:22:13 pve1 kernel: input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card1/input9
Mar 04 19:22:13 pve1 kernel: AVX2 version of gcm_enc/dec engaged.
Mar 04 19:22:13 pve1 kernel: AES CTR mode by8 optimization enabled
Mar 04 19:22:13 pve1 kernel: intel_rapl_common: Found RAPL domain package
Mar 04 19:22:13 pve1 kernel: intel_rapl_common: Found RAPL domain core
Mar 04 19:22:13 pve1 kernel: intel_rapl_common: Found RAPL domain uncore
Mar 04 19:22:13 pve1 kernel: intel_rapl_common: Found RAPL domain dram
Mar 04 19:22:13 pve1 systemd[1]: Finished ifupdown2-pre.service - Helper to synchronize boot up for ifupdown.
Mar 04 19:22:13 pve1 systemd[1]: Finished systemd-udev-settle.service - Wait for udev To Complete Device Initialization.
Mar 04 19:22:13 pve1 systemd[1]: zfs-import-cache.service - Import ZFS pools by cache file was skipped because of an unmet condition check (ConditionFileNotEmpty=/etc/zfs/zpool.cache).
Mar 04 19:22:14 pve1 kernel: ZFS: Loaded module v2.2.6-pve1, ZFS pool version 5000, ZFS filesystem version 5
Mar 04 19:22:14 pve1 systemd-modules-load[343]: Inserted module ‹ zfs ›
Mar 04 19:22:14 pve1 systemd[1]: Starting zfs-import-scan.service - Import ZFS pools by device scanning…
Mar 04 19:22:14 pve1 systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.
Mar 04 19:22:14 pve1 systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables…
Mar 04 19:22:14 pve1 systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables.
Mar 04 19:22:14 pve1 zpool[546]: no pools available to import
Mar 04 19:22:14 pve1 systemd[1]: Finished zfs-import-scan.service - Import ZFS pools by device scanning.
Mar 04 19:22:14 pve1 systemd[1]: Reached target zfs-import.target - ZFS pool import target.
Mar 04 19:22:14 pve1 systemd[1]: Starting zfs-mount.service - Mount ZFS filesystems…
Mar 04 19:22:14 pve1 systemd[1]: Starting zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev…
Mar 04 19:22:14 pve1 systemd[1]: Finished zfs-mount.service - Mount ZFS filesystems.
Mar 04 19:22:14 pve1 systemd[1]: Reached target local-fs.target - Local File Systems.
Mar 04 19:22:14 pve1 zvol_wait[567]: No zvols found, nothing to do.
Mar 04 19:22:14 pve1 systemd[1]: Starting apparmor.service - Load AppArmor profiles…
Mar 04 19:22:14 pve1 systemd[1]: Starting console-setup.service - Set console font and keymap…
Mar 04 19:22:14 pve1 systemd[1]: Starting networking.service - Network initialization…
Mar 04 19:22:14 pve1 systemd[1]: Starting pvebanner.service - Proxmox VE Login Banner…
Mar 04 19:22:14 pve1 systemd[1]: Starting pvefw-logger.service - Proxmox VE firewall logger…
Mar 04 19:22:14 pve1 systemd[1]: Starting pvenetcommit.service - Commit Proxmox VE network changes…
Mar 04 19:22:14 pve1 apparmor.systemd[571]: Restarting AppArmor
Mar 04 19:22:14 pve1 apparmor.systemd[571]: Reloading AppArmor profiles
Mar 04 19:22:14 pve1 systemd[1]: Starting systemd-binfmt.service - Set Up Additional Binary Formats…
Mar 04 19:22:14 pve1 systemd[1]: systemd-boot-system-token.service - Store a System Token in an EFI Variable was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/LoaderFeatures-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Mar 04 19:22:14 pve1 systemd[1]: systemd-machine-id-commit.service - Commit a transient machine-id on disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id).
Mar 04 19:22:14 pve1 systemd[1]: Starting systemd-tmpfiles-setup.service - Create System Files and Directories…
Mar 04 19:22:14 pve1 systemd[1]: Finished zfs-volume-wait.service - Wait for ZFS Volume (zvol) links in /dev.
Mar 04 19:22:14 pve1 systemd[1]: Finished console-setup.service - Set console font and keymap.
Mar 04 19:22:14 pve1 systemd[1]: Reached target zfs-volumes.target - ZFS volumes are ready.
Mar 04 19:22:14 pve1 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 583 (systemd-binfmt)
Mar 04 19:22:14 pve1 systemd[1]: Finished pvenetcommit.service - Commit Proxmox VE network changes.
Mar 04 19:22:14 pve1 networking[575]: networking: Configuring network interfaces
Mar 04 19:22:14 pve1 systemd[1]: Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System…
Mar 04 19:22:14 pve1 systemd[1]: Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System.
Mar 04 19:22:14 pve1 systemd[1]: Finished systemd-binfmt.service - Set Up Additional Binary Formats.
Mar 04 19:22:14 pve1 pvefw-logger[603]: starting pvefw logger
Mar 04 19:22:14 pve1 systemd[1]: Started pvefw-logger.service - Proxmox VE firewall logger.
Mar 04 19:22:14 pve1 audit[601]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« pve-container-mounthotplug » pid=601 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.141:2): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« pve-container-mounthotplug » pid=601 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[598]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lsb_release » pid=598 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.145:3): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lsb_release » pid=598 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[600]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe » pid=600 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[600]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe//kmod » pid=600 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.146:4): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe » pid=600 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.146:5): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe//kmod » pid=600 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.149:6): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/lxc-copy » pid=606 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.151:7): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/lxc-start » pid=607 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[606]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/lxc-copy » pid=606 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[607]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/lxc-start » pid=607 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[599]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[599]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-cgns » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[599]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-with-mounting » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[599]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-with-nesting » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.154:8): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.155:9): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-cgns » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.155:10): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-with-mounting » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 kernel: audit: type=1400 audit(1741112534.155:11): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-with-nesting » pid=599 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 systemd[1]: Finished systemd-tmpfiles-setup.service - Create System Files and Directories.
Mar 04 19:22:14 pve1 audit[608]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/man » pid=608 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[608]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« man_filter » pid=608 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[608]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« man_groff » pid=608 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[609]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« swtpm » pid=609 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[605]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/lib/NetworkManager/nm-dhcp-client.action » pid=605 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[605]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/lib/NetworkManager/nm-dhcp-helper » pid=605 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[605]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/lib/connman/scripts/dhclient-script » pid=605 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[605]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /{,usr/}sbin/dhclient » pid=605 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 audit[612]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/sbin/chronyd » pid=612 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 systemd[1]: Mounting run-rpc_pipefs.mount - RPC Pipe File System…
Mar 04 19:22:14 pve1 audit[610]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« tcpdump » pid=610 comm=« apparmor_parser »
Mar 04 19:22:14 pve1 systemd[1]: Starting rpcbind.service - RPC bind portmap service…
Mar 04 19:22:14 pve1 systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP…
Mar 04 19:22:14 pve1 systemd[1]: Finished apparmor.service - Load AppArmor profiles.
Mar 04 19:22:14 pve1 systemd[1]: Started rpcbind.service - RPC bind portmap service.
Mar 04 19:22:14 pve1 systemd[1]: Reached target rpcbind.target - RPC Port Mapper.
Mar 04 19:22:14 pve1 systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
Mar 04 19:22:14 pve1 systemd[1]: Reached target sysinit.target - System Initialization.
Mar 04 19:22:14 pve1 systemd[1]: Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
Mar 04 19:22:14 pve1 systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket.
Mar 04 19:22:14 pve1 systemd[1]: Listening on iscsid.socket - Open-iSCSI iscsid Socket.
Mar 04 19:22:14 pve1 systemd[1]: Reached target sockets.target - Socket Units.
Mar 04 19:22:14 pve1 systemd[1]: systemd-pcrphase-sysinit.service - TPM2 PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Mar 04 19:22:14 pve1 systemd[1]: Reached target basic.target - Basic System.
Mar 04 19:22:14 pve1 systemd[1]: Starting dbus.service - D-Bus System Message Bus…
Mar 04 19:22:14 pve1 systemd[1]: Starting e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots…
Mar 04 19:22:14 pve1 systemd[1]: getty-static.service - getty on tty2-tty6 if dbus and logind are not available was skipped because of an unmet condition check (ConditionPathExists=!/usr/bin/dbus-daemon).
Mar 04 19:22:14 pve1 systemd[1]: Starting ksmtuned.service - Kernel Samepage Merging (KSM) Tuning Daemon…
Mar 04 19:22:14 pve1 systemd[1]: Starting lxcfs.service - FUSE filesystem for LXC…
Mar 04 19:22:14 pve1 systemd[1]: proxmox-boot-cleanup.service - Clean up bootloader next-boot setting was skipped because of an unmet condition check (ConditionPathExists=/etc/kernel/next-boot-pin).
Mar 04 19:22:14 pve1 systemd[1]: Starting pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon…
Mar 04 19:22:14 pve1 systemd[1]: Starting qmeventd.service - PVE Qemu Event Daemon…
Mar 04 19:22:14 pve1 systemd[1]: Starting smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon…
Mar 04 19:22:14 pve1 dbus-daemon[616]: [system] AppArmor D-Bus mediation is enabled
Mar 04 19:22:14 pve1 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Mar 04 19:22:14 pve1 kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Mar 04 19:22:14 pve1 systemd[1]: Starting systemd-logind.service - User Login Management…
Mar 04 19:22:14 pve1 systemd[1]: Started watchdog-mux.service - Proxmox VE watchdog multiplexer.
Mar 04 19:22:14 pve1 systemd[1]: Starting zfs-share.service - ZFS file system shares…
Mar 04 19:22:14 pve1 kernel: RPC: Registered named UNIX socket transport module.
Mar 04 19:22:14 pve1 kernel: RPC: Registered udp transport module.
Mar 04 19:22:14 pve1 kernel: RPC: Registered tcp transport module.
Mar 04 19:22:14 pve1 kernel: RPC: Registered tcp-with-tls transport module.
Mar 04 19:22:14 pve1 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Mar 04 19:22:14 pve1 systemd[1]: Started zfs-zed.service - ZFS Event Daemon (zed).
Mar 04 19:22:14 pve1 systemd[1]: Started dbus.service - D-Bus System Message Bus.
Mar 04 19:22:14 pve1 systemd[1]: Started pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon.
Mar 04 19:22:14 pve1 systemd[1]: Started ksmtuned.service - Kernel Samepage Merging (KSM) Tuning Daemon.
Mar 04 19:22:14 pve1 systemd[1]: Started lxcfs.service - FUSE filesystem for LXC.
Mar 04 19:22:14 pve1 systemd[1]: Mounted run-rpc_pipefs.mount - RPC Pipe File System.
Mar 04 19:22:14 pve1 systemd[1]: Started qmeventd.service - PVE Qemu Event Daemon.
Mar 04 19:22:14 pve1 systemd[1]: Reached target rpc_pipefs.target.
Mar 04 19:22:14 pve1 systemd[1]: rpc-gssd.service - RPC security service for NFS client and server was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).
Mar 04 19:22:14 pve1 systemd[1]: Reached target nfs-client.target - NFS client services.
Mar 04 19:22:14 pve1 lxcfs[639]: Starting LXCFS at /usr/bin/lxcfs
Mar 04 19:22:14 pve1 smartd[623]: smartd 7.3 2022-02-28 r5338 [x86_64-linux-6.8.12-2-pve] (local build)
Mar 04 19:22:14 pve1 smartd[623]: Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
Mar 04 19:22:14 pve1 smartd[623]: Opened configuration file /etc/smartd.conf
Mar 04 19:22:14 pve1 smartd[623]: Drive: DEVICESCAN, implied ‹ -a › Directive on line 21 of file /etc/smartd.conf
Mar 04 19:22:14 pve1 smartd[623]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda, type changed from ‹ scsi › to ‹ sat ›
Mar 04 19:22:14 pve1 lxcfs[639]: Running constructor lxcfs_init to reload liblxcfs
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], opened
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], Crucial_CT120M500SSD3, S/N:14320CE40A87, WWN:5-00a075-10ce40a87, FW:MU05, 120 GB
Mar 04 19:22:14 pve1 systemd[1]: Finished zfs-share.service - ZFS file system shares.
Mar 04 19:22:14 pve1 zed[636]: ZFS Event Daemon 2.2.6-pve1 (PID 636)
Mar 04 19:22:14 pve1 systemd[1]: Reached target zfs.target - ZFS startup target.
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], found in smartd database 7.3/5319: Crucial/Micron Client SSDs
Mar 04 19:22:14 pve1 lxcfs[639]: mount namespace: 5
Mar 04 19:22:14 pve1 lxcfs[639]: hierarchies:
Mar 04 19:22:14 pve1 lxcfs[639]: 0: fd: 6: cpuset,cpu,io,memory,hugetlb,pids,rdma,misc
Mar 04 19:22:14 pve1 lxcfs[639]: Kernel supports pidfds
Mar 04 19:22:14 pve1 lxcfs[639]: Kernel supports swap accounting
Mar 04 19:22:14 pve1 lxcfs[639]: api_extensions:
Mar 04 19:22:14 pve1 lxcfs[639]: - cgroups
Mar 04 19:22:14 pve1 lxcfs[639]: - sys_cpu_online
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_cpuinfo
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_diskstats
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_loadavg
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_meminfo
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_stat
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_swaps
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_uptime
Mar 04 19:22:14 pve1 lxcfs[639]: - proc_slabinfo
Mar 04 19:22:14 pve1 lxcfs[639]: - shared_pidns
Mar 04 19:22:14 pve1 lxcfs[639]: - cpuview_daemon
Mar 04 19:22:14 pve1 lxcfs[639]: - loadavg_daemon
Mar 04 19:22:14 pve1 lxcfs[639]: - pidfds
Mar 04 19:22:14 pve1 zed[636]: Processing events since eid=0
Mar 04 19:22:14 pve1 lxcfs[639]: Ignoring invalid max threads value 4294967295 > max (100000).
Mar 04 19:22:14 pve1 kernel: softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
Mar 04 19:22:14 pve1 kernel: softdog: soft_reboot_cmd= soft_active_on_boot=0
Mar 04 19:22:14 pve1 watchdog-mux[633]: Watchdog driver ‹ Software Watchdog ›, version 0
Mar 04 19:22:14 pve1 systemd[1]: e2scrub_reap.service: Deactivated successfully.
Mar 04 19:22:14 pve1 systemd[1]: Finished e2scrub_reap.service - Remove Stale Online ext4 Metadata Check Snapshots.
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], is SMART capable. Adding to « monitor » list.
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.Crucial_CT120M500SSD3-14320CE40A87.ata.state
Mar 04 19:22:14 pve1 smartd[623]: Monitoring 1 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 1 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 5 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 9 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 12 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 171 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 172 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 173 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 174 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 180 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 183 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 184 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 187 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 194 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 196 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 197 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 198 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 199 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 202 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 206 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 210 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 246 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 247 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], same Attribute has different ID numbers: 248 = 0
Mar 04 19:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Crucial_CT120M500SSD3-14320CE40A87.ata.state
Mar 04 19:22:14 pve1 systemd[1]: Started smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon.
Mar 04 19:22:14 pve1 systemd-logind[632]: New seat seat0.
Mar 04 19:22:14 pve1 systemd-logind[632]: Watching system buttons on /dev/input/event1 (Power Button)
Mar 04 19:22:14 pve1 systemd-logind[632]: Watching system buttons on /dev/input/event0 (Power Button)
Mar 04 19:22:14 pve1 systemd-logind[632]: Watching system buttons on /dev/input/event5 (Nuvoton w836x7hg Infrared Remote Transceiver)
Mar 04 19:22:14 pve1 systemd[1]: Started systemd-logind.service - User Login Management.
Mar 04 19:22:14 pve1 systemd[1]: Finished pvebanner.service - Proxmox VE Login Banner.
Mar 04 19:22:15 pve1 kernel: vmbr0: port 1(eno1) entered blocking state
Mar 04 19:22:15 pve1 kernel: vmbr0: port 1(eno1) entered disabled state
Mar 04 19:22:15 pve1 kernel: e1000e 0000:00:19.0 eno1: entered allmulticast mode
Mar 04 19:22:15 pve1 kernel: e1000e 0000:00:19.0 eno1: entered promiscuous mode
Mar 04 19:22:16 pve1 systemd[1]: Finished networking.service - Network initialization.
Mar 04 19:22:16 pve1 systemd[1]: Reached target network.target - Network.
Mar 04 19:22:16 pve1 systemd[1]: Reached target network-online.target - Network is Online.
Mar 04 19:22:16 pve1 systemd[1]: Starting chrony.service - chrony, an NTP client/server…
Mar 04 19:22:16 pve1 systemd[1]: Started lxc-monitord.service - LXC Container Monitoring Daemon.
Mar 04 19:22:16 pve1 systemd[1]: Starting lxc-net.service - LXC network bridge setup…
Mar 04 19:22:16 pve1 systemd[1]: open-iscsi.service - Login to default iSCSI targets was skipped because no trigger condition checks were met.
Mar 04 19:22:16 pve1 systemd[1]: Reached target remote-fs-pre.target - Preparation for Remote File Systems.
Mar 04 19:22:16 pve1 systemd[1]: Reached target remote-fs.target - Remote File Systems.
Mar 04 19:22:16 pve1 systemd[1]: Reached target pve-storage.target - PVE Storage Target.
Mar 04 19:22:16 pve1 systemd[1]: Starting postfix@-.service - Postfix Mail Transport Agent (instance -)…
Mar 04 19:22:16 pve1 systemd[1]: Starting rbdmap.service - Map RBD devices…
Mar 04 19:22:16 pve1 systemd[1]: Starting rpc-statd-notify.service - Notify NFS peers of a restart…
Mar 04 19:22:16 pve1 systemd[1]: Starting ssh.service - OpenBSD Secure Shell server…
Mar 04 19:22:16 pve1 systemd[1]: systemd-pcrphase.service - TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Mar 04 19:22:16 pve1 sm-notify[738]: Version 2.6.2 starting
Mar 04 19:22:16 pve1 systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions…
Mar 04 19:22:16 pve1 systemd[1]: Finished rbdmap.service - Map RBD devices.
Mar 04 19:22:16 pve1 systemd[1]: Started rpc-statd-notify.service - Notify NFS peers of a restart.
Mar 04 19:22:16 pve1 systemd[1]: Finished blk-availability.service - Availability of block devices.
Mar 04 19:22:16 pve1 systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions.
Mar 04 19:22:16 pve1 systemd[1]: Started getty@tty1.service - Getty on tty1.
Mar 04 19:22:16 pve1 systemd[1]: Reached target getty.target - Login Prompts.
Mar 04 19:22:16 pve1 systemd[1]: Finished lxc-net.service - LXC network bridge setup.
Mar 04 19:22:16 pve1 systemd[1]: Starting lxc.service - LXC Container Initialization and Autoboot Code…
Mar 04 19:22:16 pve1 audit[757]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« /usr/bin/lxc-copy » pid=757 comm=« apparmor_parser »
Mar 04 19:22:16 pve1 sshd[751]: Server listening on 0.0.0.0 port 22.
Mar 04 19:22:16 pve1 sshd[751]: Server listening on :: port 22.
Mar 04 19:22:16 pve1 systemd[1]: Started ssh.service - OpenBSD Secure Shell server.
Mar 04 19:22:16 pve1 audit[762]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« /usr/bin/lxc-start » pid=762 comm=« apparmor_parser »
Mar 04 19:22:16 pve1 chronyd[767]: chronyd version 4.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Mar 04 19:22:16 pve1 chronyd[767]: Frequency 9.668 +/- 0.010 ppm read from /var/lib/chrony/chrony.drift
Mar 04 19:22:16 pve1 chronyd[767]: Using right/UTC timezone to obtain leap second data
Mar 04 19:22:16 pve1 chronyd[767]: Loaded seccomp filter (level 1)
Mar 04 19:22:16 pve1 systemd[1]: Started chrony.service - chrony, an NTP client/server.
Mar 04 19:22:16 pve1 systemd[1]: Reached target time-sync.target - System Time Synchronized.
Mar 04 19:22:16 pve1 systemd[1]: Started apt-daily.timer - Daily apt download activities.
Mar 04 19:22:16 pve1 systemd[1]: Started apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
Mar 04 19:22:16 pve1 systemd[1]: Started dpkg-db-backup.timer - Daily dpkg database backup timer.
Mar 04 19:22:16 pve1 systemd[1]: Started e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
Mar 04 19:22:16 pve1 systemd[1]: Started fstrim.timer - Discard unused blocks once a week.
Mar 04 19:22:16 pve1 systemd[1]: Started logrotate.timer - Daily rotation of log files.
Mar 04 19:22:16 pve1 systemd[1]: Started man-db.timer - Daily man-db regeneration.
Mar 04 19:22:16 pve1 systemd[1]: Started pve-daily-update.timer - Daily PVE download activities.
Mar 04 19:22:16 pve1 systemd[1]: Reached target timers.target - Timer Units.
Mar 04 19:22:16 pve1 audit[769]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default » pid=769 comm=« apparmor_parser »
Mar 04 19:22:16 pve1 audit[769]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default-cgns » pid=769 comm=« apparmor_parser »
Mar 04 19:22:16 pve1 audit[769]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default-with-mounting » pid=769 comm=« apparmor_parser »
Mar 04 19:22:16 pve1 audit[769]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default-with-nesting » pid=769 comm=« apparmor_parser »
Mar 04 19:22:16 pve1 systemd[1]: Starting rrdcached.service - LSB: start or stop rrdcached…
Mar 04 19:22:16 pve1 systemd[1]: Finished lxc.service - LXC Container Initialization and Autoboot Code.
Mar 04 19:22:16 pve1 rrdcached[773]: rrdcached started.
Mar 04 19:22:16 pve1 systemd[1]: Started rrdcached.service - LSB: start or stop rrdcached.
Mar 04 19:22:16 pve1 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem…
Mar 04 19:22:16 pve1 postfix[828]: Postfix is using backwards-compatible default settings
Mar 04 19:22:16 pve1 postfix[828]: See Postfix Backwards-Compatibility Safety Net for details
Mar 04 19:22:16 pve1 postfix[828]: To disable backwards compatibility use « postconf compatibility_level=3.6 » and « postfix reload »
Mar 04 19:22:16 pve1 pmxcfs[821]: [main] notice: resolved node name ‹ pve1 › to ‹ 192.168.1.21 › for default node IP address
Mar 04 19:22:16 pve1 pmxcfs[821]: [main] notice: resolved node name ‹ pve1 › to ‹ 192.168.1.21 › for default node IP address
Mar 04 19:22:17 pve1 postfix/postfix-script[924]: starting the Postfix mail system
Mar 04 19:22:17 pve1 postfix/master[926]: daemon started – version 3.7.11, configuration /etc/postfix
Mar 04 19:22:17 pve1 systemd[1]: Started postfix@-.service - Postfix Mail Transport Agent (instance -).
Mar 04 19:22:17 pve1 systemd[1]: Starting postfix.service - Postfix Mail Transport Agent…
Mar 04 19:22:17 pve1 systemd[1]: Finished postfix.service - Postfix Mail Transport Agent.
Mar 04 19:22:17 pve1 systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
Mar 04 19:22:17 pve1 systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosync/corosync.conf).
Mar 04 19:22:17 pve1 systemd[1]: Started cron.service - Regular background program processing daemon.
Mar 04 19:22:17 pve1 systemd[1]: Started proxmox-firewall.service - Proxmox nftables firewall.
Mar 04 19:22:17 pve1 cron[933]: (CRON) INFO (pidfile fd = 3)
Mar 04 19:22:17 pve1 systemd[1]: Starting pve-firewall.service - Proxmox VE firewall…
Mar 04 19:22:17 pve1 cron[933]: (CRON) INFO (Running @reboot jobs)
Mar 04 19:22:17 pve1 systemd[1]: Starting pvedaemon.service - PVE API Daemon…
Mar 04 19:22:17 pve1 systemd[1]: Starting pvestatd.service - PVE Status Daemon…
Mar 04 19:22:18 pve1 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Mar 04 19:22:19 pve1 kernel: e1000e 0000:00:19.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 04 19:22:19 pve1 kernel: vmbr0: port 1(eno1) entered blocking state
Mar 04 19:22:19 pve1 kernel: vmbr0: port 1(eno1) entered forwarding state
Mar 04 19:22:19 pve1 pvestatd[945]: starting server
Mar 04 19:22:19 pve1 systemd[1]: Started pvestatd.service - PVE Status Daemon.
Mar 04 19:22:19 pve1 pve-firewall[946]: starting server
Mar 04 19:22:19 pve1 systemd[1]: Started pve-firewall.service - Proxmox VE firewall.
Mar 04 19:22:19 pve1 pvedaemon[960]: starting server
Mar 04 19:22:19 pve1 pvedaemon[960]: starting 3 worker(s)
Mar 04 19:22:19 pve1 pvedaemon[960]: worker 962 started
Mar 04 19:22:19 pve1 pvedaemon[960]: worker 963 started
Mar 04 19:22:19 pve1 pvedaemon[960]: worker 965 started
Mar 04 19:22:19 pve1 systemd[1]: Started pvedaemon.service - PVE API Daemon.
Mar 04 19:22:19 pve1 systemd[1]: Starting pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon…
Mar 04 19:22:19 pve1 systemd[1]: Starting pveproxy.service - PVE API Proxy Server…
Mar 04 19:22:20 pve1 dmeventd[355]: WARNING: Thin pool pve-data-tpool data is now 100.00% full.
Mar 04 19:22:21 pve1 pve-ha-crm[980]: starting server
Mar 04 19:22:21 pve1 pve-ha-crm[980]: status change startup => wait_for_quorum
Mar 04 19:22:21 pve1 systemd[1]: Started pve-ha-crm.service - PVE Cluster HA Resource Manager Daemon.
Mar 04 19:22:22 pve1 pveproxy[982]: starting server
Mar 04 19:22:22 pve1 pveproxy[982]: starting 3 worker(s)
Mar 04 19:22:22 pve1 pveproxy[982]: worker 983 started
Mar 04 19:22:22 pve1 pveproxy[982]: worker 984 started
Mar 04 19:22:22 pve1 pveproxy[982]: worker 985 started
Mar 04 19:22:22 pve1 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Mar 04 19:22:22 pve1 systemd[1]: Starting pve-ha-lrm.service - PVE Local HA Resource Manager Daemon…
Mar 04 19:22:22 pve1 systemd[1]: Starting spiceproxy.service - PVE SPICE Proxy Server…
Mar 04 19:22:23 pve1 spiceproxy[990]: starting server
Mar 04 19:22:23 pve1 spiceproxy[990]: starting 1 worker(s)
Mar 04 19:22:23 pve1 spiceproxy[990]: worker 991 started
Mar 04 19:22:23 pve1 systemd[1]: Started spiceproxy.service - PVE SPICE Proxy Server.
Mar 04 19:22:23 pve1 pve-ha-lrm[992]: starting server
Mar 04 19:22:23 pve1 pve-ha-lrm[992]: status change startup => wait_for_agent_lock
Mar 04 19:22:23 pve1 systemd[1]: Started pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.
Mar 04 19:22:23 pve1 systemd[1]: Starting pve-guests.service - PVE guests…
Mar 04 19:22:24 pve1 chronyd[767]: Selected source 31.170.8.123 (2.debian.pool.ntp.org)
Mar 04 19:22:24 pve1 chronyd[767]: System clock TAI offset set to 37 seconds
Mar 04 19:22:25 pve1 IPCC.xs[962]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:192.168.1.125 user=root
Mar 04 19:22:25 pve1 pve-guests[994]: root@pam starting task UPID:pve1:000003E4:000007CF:67C744E1:startall::root@pam:
Mar 04 19:22:25 pve1 pvesh[994]: Starting VM 100
Mar 04 19:22:25 pve1 pve-guests[996]: root@pam starting task UPID:pve1:000003E5:000007D2:67C744E1:qmstart:100:root@pam:
Mar 04 19:22:25 pve1 pve-guests[997]: start VM 100: UPID:pve1:000003E5:000007D2:67C744E1:qmstart:100:root@pam:
Mar 04 19:22:26 pve1 systemd[1]: Created slice qemu.slice - Slice /qemu.
Mar 04 19:22:26 pve1 systemd[1]: Started 100.scope.
Mar 04 19:22:26 pve1 kernel: kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and L1TF - L1 Terminal Fault — The Linux Kernel documentation for details.
Mar 04 19:22:27 pve1 pvedaemon[962]: authentication failure; rhost=::ffff:192.168.1.125 user=root@pam msg=Authentication failure
Mar 04 19:22:27 pve1 kernel: tap100i0: entered promiscuous mode
Mar 04 19:22:27 pve1 kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Mar 04 19:22:27 pve1 kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Mar 04 19:22:27 pve1 kernel: fwpr100p0: entered allmulticast mode
Mar 04 19:22:27 pve1 kernel: fwpr100p0: entered promiscuous mode
Mar 04 19:22:27 pve1 kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Mar 04 19:22:27 pve1 kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Mar 04 19:22:27 pve1 kernel: fwln100i0: entered allmulticast mode
Mar 04 19:22:27 pve1 kernel: fwln100i0: entered promiscuous mode
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Mar 04 19:22:27 pve1 kernel: tap100i0: entered allmulticast mode
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Mar 04 19:22:27 pve1 kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Mar 04 19:22:28 pve1 kernel: ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
Mar 04 19:22:28 pve1 kernel: ftdi_sio 2-4.4:1.0: device disconnected
Mar 04 19:22:28 pve1 kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Mar 04 19:22:28 pve1 kernel: ftdi_sio 2-4.3:1.0: device disconnected
Mar 04 19:22:28 pve1 systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status…
Mar 04 19:22:28 pve1 systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Mar 04 19:22:28 pve1 systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Mar 04 19:22:31 pve1 pvesh[994]: Starting VM 101
Mar 04 19:22:31 pve1 pve-guests[996]: root@pam starting task UPID:pve1:00000456:00000A2B:67C744E7:qmstart:101:root@pam:
Mar 04 19:22:31 pve1 pve-guests[1110]: start VM 101: UPID:pve1:00000456:00000A2B:67C744E7:qmstart:101:root@pam:
Mar 04 19:22:32 pve1 systemd[1]: Started 101.scope.
Mar 04 19:22:33 pve1 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Mar 04 19:22:33 pve1 kernel: tap101i0: entered promiscuous mode
Mar 04 19:22:33 pve1 kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Mar 04 19:22:33 pve1 kernel: vmbr0: port 3(fwpr101p0) entered disabled state
Mar 04 19:22:33 pve1 kernel: fwpr101p0: entered allmulticast mode
Mar 04 19:22:33 pve1 kernel: fwpr101p0: entered promiscuous mode
Mar 04 19:22:33 pve1 kernel: vmbr0: port 3(fwpr101p0) entered blocking state
Mar 04 19:22:33 pve1 kernel: vmbr0: port 3(fwpr101p0) entered forwarding state
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 1(fwln101i0) entered disabled state
Mar 04 19:22:33 pve1 kernel: fwln101i0: entered allmulticast mode
Mar 04 19:22:33 pve1 kernel: fwln101i0: entered promiscuous mode
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 1(fwln101i0) entered blocking state
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 1(fwln101i0) entered forwarding state
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 2(tap101i0) entered blocking state
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 2(tap101i0) entered disabled state
Mar 04 19:22:33 pve1 kernel: tap101i0: entered allmulticast mode
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 2(tap101i0) entered blocking state
Mar 04 19:22:33 pve1 kernel: fwbr101i0: port 2(tap101i0) entered forwarding state
Mar 04 19:22:36 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 19:22:36 pve1 pvesh[994]: Starting CT 103
Mar 04 19:22:37 pve1 pve-guests[996]: root@pam starting task UPID:pve1:00000499:00000C22:67C744EC:vzstart:103:root@pam:
Mar 04 19:22:37 pve1 pve-guests[1177]: starting CT 103: UPID:pve1:00000499:00000C22:67C744EC:vzstart:103:root@pam:
Mar 04 19:22:37 pve1 systemd[1]: Created slice system-pve\x2dcontainer.slice - PVE LXC Container Slice.
Mar 04 19:22:37 pve1 systemd[1]: Started pve-container@103.service - PVE LXC Container: 103.
Mar 04 19:22:39 pve1 kernel: EXT4-fs warning (device dm-11): ext4_multi_mount_protect:328: MMP interval 42 higher than expected, please wait.
Mar 04 19:22:42 pve1 systemd[1]: systemd-fsckd.service: Deactivated successfully.
Mar 04 19:22:42 pve1 kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Mar 04 19:22:43 pve1 kernel: usb 2-4.4: reset full-speed USB device number 6 using xhci_hcd
Mar 04 19:22:43 pve1 kernel: usb 2-4.3: reset full-speed USB device number 5 using xhci_hcd
Mar 04 19:22:49 pve1 kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Mar 04 19:22:51 pve1 kernel: Bluetooth: hci0: urb 0000000052020ee1 failed to resubmit (2)
Mar 04 19:22:51 pve1 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Mar 04 19:22:51 pve1 kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Mar 04 19:22:51 pve1 kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Mar 04 19:22:53 pve1 kernel: Bluetooth: hci0: urb 00000000c93245ce failed to resubmit (2)
Mar 04 19:22:53 pve1 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Mar 04 19:22:53 pve1 kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Mar 04 19:22:53 pve1 systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status…
Mar 04 19:22:53 pve1 QEMU[1009]: kvm: libusb_release_interface: -99 [OTHER]
Mar 04 19:22:53 pve1 QEMU[1009]: kvm: libusb_release_interface: -99 [OTHER]
Mar 04 19:22:53 pve1 systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Mar 04 19:22:53 pve1 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 04 19:22:53 pve1 systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Mar 04 19:22:53 pve1 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 04 19:22:53 pve1 systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Mar 04 19:22:53 pve1 kernel: usb 2-1: reset full-speed USB device number 2 using xhci_hcd
Mar 04 19:22:54 pve1 kernel: usb 2-4.3: reset full-speed USB device number 5 using xhci_hcd
Mar 04 19:22:54 pve1 kernel: ftdi_sio 2-4.3:1.0: FTDI USB Serial Device converter detected
Mar 04 19:22:54 pve1 kernel: usb 2-4.3: Detected FT232R
Mar 04 19:22:54 pve1 kernel: usb 2-4.3: FTDI USB Serial Device converter now attached to ttyUSB0
Mar 04 19:22:54 pve1 kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Mar 04 19:22:54 pve1 kernel: ftdi_sio 2-4.3:1.0: device disconnected
Mar 04 19:22:56 pve1 kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Mar 04 19:23:01 pve1 kernel: Bluetooth: hci0: urb 000000002c88c308 failed to resubmit (2)
Mar 04 19:23:01 pve1 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Mar 04 19:23:01 pve1 kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Mar 04 19:23:01 pve1 kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Mar 04 19:23:01 pve1 kernel: Bluetooth: hci0: urb 000000006390d739 failed to resubmit (2)
Mar 04 19:23:01 pve1 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Mar 04 19:23:01 pve1 kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Mar 04 19:23:01 pve1 QEMU[1122]: kvm: libusb_release_interface: -99 [OTHER]
Mar 04 19:23:01 pve1 QEMU[1122]: kvm: libusb_release_interface: -99 [OTHER]
Mar 04 19:23:01 pve1 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 04 19:23:01 pve1 systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Mar 04 19:23:01 pve1 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 04 19:23:01 pve1 systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Mar 04 19:23:02 pve1 pvedaemon[1284]: shutdown VM 100: UPID:pve1:00000504:00001630:67C74506:qmshutdown:100:root@pam:
Mar 04 19:23:02 pve1 pvedaemon[962]: root@pam starting task UPID:pve1:00000504:00001630:67C74506:qmshutdown:100:root@pam:
Mar 04 19:23:05 pve1 kernel: tap100i0: left allmulticast mode
Mar 04 19:23:05 pve1 kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Mar 04 19:23:05 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Mar 04 19:23:05 pve1 kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Mar 04 19:23:05 pve1 kernel: fwln100i0 (unregistering): left allmulticast mode
Mar 04 19:23:05 pve1 kernel: fwln100i0 (unregistering): left promiscuous mode
Mar 04 19:23:05 pve1 kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Mar 04 19:23:05 pve1 kernel: fwpr100p0 (unregistering): left allmulticast mode
Mar 04 19:23:05 pve1 kernel: fwpr100p0 (unregistering): left promiscuous mode
Mar 04 19:23:05 pve1 kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Mar 04 19:23:05 pve1 qmeventd[631]: read: Connection reset by peer
Mar 04 19:23:05 pve1 QEMU[1009]: kvm: libusb_release_interface: -99 [OTHER]
Mar 04 19:23:05 pve1 kernel: usb 2-4.3: reset full-speed USB device number 5 using xhci_hcd
Mar 04 19:23:05 pve1 kernel: ftdi_sio 2-4.3:1.0: FTDI USB Serial Device converter detected
Mar 04 19:23:05 pve1 kernel: usb 2-4.3: Detected FT232R
Mar 04 19:23:05 pve1 kernel: usb 2-4.3: FTDI USB Serial Device converter now attached to ttyUSB0
Mar 04 19:23:05 pve1 kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Mar 04 19:23:05 pve1 kernel: ftdi_sio 2-4.3:1.0: device disconnected
Mar 04 19:23:05 pve1 kernel: usb 2-4.4: reset full-speed USB device number 6 using xhci_hcd
Mar 04 19:23:05 pve1 kernel: ftdi_sio 2-4.4:1.0: FTDI USB Serial Device converter detected
Mar 04 19:23:05 pve1 kernel: usb 2-4.4: Detected FT232R
Mar 04 19:23:05 pve1 kernel: usb 2-4.4: FTDI USB Serial Device converter now attached to ttyUSB0
Mar 04 19:23:05 pve1 kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Mar 04 19:23:06 pve1 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 04 19:23:06 pve1 systemd[1]: 100.scope: Deactivated successfully.
Mar 04 19:23:06 pve1 systemd[1]: 100.scope: Consumed 35.034s CPU time.
Mar 04 19:23:06 pve1 kernel: Bluetooth: hci0: urb 00000000c5084b28 failed to resubmit (2)
Mar 04 19:23:06 pve1 pvedaemon[962]: root@pam end task UPID:pve1:00000504:00001630:67C74506:qmshutdown:100:root@pam: OK
Mar 04 19:23:07 pve1 qmeventd[1308]: Starting cleanup for 100
Mar 04 19:23:07 pve1 qmeventd[1308]: Finished cleanup for 100
Mar 04 19:23:08 pve1 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Mar 04 19:23:08 pve1 kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Mar 04 19:23:08 pve1 systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Mar 04 19:23:08 pve1 kernel: usb 2-7: reset full-speed USB device number 4 using xhci_hcd
Mar 04 19:23:08 pve1 systemd[1]: Reached target bluetooth.target - Bluetooth Support.
Mar 04 19:23:10 pve1 kernel: Bluetooth: hci0: command 0x0c03 tx timeout
Mar 04 19:23:10 pve1 kernel: Bluetooth: hci0: sending initial HCI reset failed (-110)
Mar 04 19:23:10 pve1 systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
Mar 04 19:23:15 pve1 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Mar 04 19:23:21 pve1 kernel: EXT4-fs (dm-11): recovery complete
Mar 04 19:23:21 pve1 kernel: EXT4-fs (dm-11): mounted filesystem 1a29a553-0920-4d32-a267-4da50b7a773b r/w with ordered data mode. Quota mode: none.
Mar 04 19:23:22 pve1 audit[1368]: AVC apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-103_</var/lib/lxc> » pid=1368 comm=« apparmor_parser »
Mar 04 19:23:22 pve1 kernel: kauditd_printk_skb: 16 callbacks suppressed
Mar 04 19:23:22 pve1 kernel: audit: type=1400 audit(1741112602.040:28): apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-103_</var/lib/lxc> » pid=1368 comm=« apparmor_parser »
Mar 04 19:23:23 pve1 kernel: vmbr0: port 2(veth103i0) entered blocking state
Mar 04 19:23:23 pve1 kernel: vmbr0: port 2(veth103i0) entered disabled state
Mar 04 19:23:23 pve1 kernel: veth103i0: entered allmulticast mode
Mar 04 19:23:23 pve1 kernel: veth103i0: entered promiscuous mode
Mar 04 19:23:23 pve1 kernel: eth0: renamed from vethDTIUvq
Mar 04 19:23:23 pve1 pvestatd[945]: modified cpu set for lxc/103: 0
Mar 04 19:23:23 pve1 pvestatd[945]: status update time (44.686 seconds)
Mar 04 19:23:24 pve1 pmxcfs[830]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve1/local: -1
Mar 04 19:23:24 pve1 pmxcfs[830]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve1/local-lvm: -1
Mar 04 19:23:24 pve1 pve-guests[994]: root@pam end task UPID:pve1:000003E4:000007CF:67C744E1:startall::root@pam: OK
Mar 04 19:23:24 pve1 systemd[1]: Finished pve-guests.service - PVE guests.
Mar 04 19:23:24 pve1 systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler…
Mar 04 19:23:24 pve1 kernel: device-mapper: thin: 252:4: reached low water mark for data device: sending event.
Mar 04 19:23:24 pve1 kernel: device-mapper: thin: 252:4: switching pool to out-of-data-space (queue IO) mode
Mar 04 19:23:24 pve1 kernel: vmbr0: port 2(veth103i0) entered blocking state
Mar 04 19:23:24 pve1 kernel: vmbr0: port 2(veth103i0) entered forwarding state
Mar 04 19:23:25 pve1 pvescheduler[1551]: starting server
Mar 04 19:23:25 pve1 systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
Mar 04 19:23:25 pve1 systemd[1]: Reached target multi-user.target - Multi-User System.
Mar 04 19:23:25 pve1 systemd[1]: Reached target graphical.target - Graphical Interface.
Mar 04 19:23:25 pve1 systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP…
Mar 04 19:23:25 pve1 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully.
Mar 04 19:23:25 pve1 systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.
Mar 04 19:23:25 pve1 systemd[1]: Startup finished in 8.534s (firmware) + 7.006s (loader) + 3.846s (kernel) + 1min 15.896s (userspace) = 1min 35.283s.
Mar 04 19:23:32 pve1 pvedaemon[963]: root@pam starting task UPID:pve1:00000633:000021DC:67C74524:qmstart:102:root@pam:
Mar 04 19:23:32 pve1 pvedaemon[1587]: start VM 102: UPID:pve1:00000633:000021DC:67C74524:qmstart:102:root@pam:
Mar 04 19:23:32 pve1 systemd[1]: Started 102.scope.
Mar 04 19:23:34 pve1 kernel: tap102i0: entered promiscuous mode
Mar 04 19:23:34 pve1 kernel: vmbr0: port 4(fwpr102p0) entered blocking state
Mar 04 19:23:34 pve1 kernel: vmbr0: port 4(fwpr102p0) entered disabled state
Mar 04 19:23:34 pve1 kernel: fwpr102p0: entered allmulticast mode
Mar 04 19:23:34 pve1 kernel: fwpr102p0: entered promiscuous mode
Mar 04 19:23:34 pve1 kernel: vmbr0: port 4(fwpr102p0) entered blocking state
Mar 04 19:23:34 pve1 kernel: vmbr0: port 4(fwpr102p0) entered forwarding state
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 1(fwln102i0) entered disabled state
Mar 04 19:23:34 pve1 kernel: fwln102i0: entered allmulticast mode
Mar 04 19:23:34 pve1 kernel: fwln102i0: entered promiscuous mode
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 1(fwln102i0) entered blocking state
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 1(fwln102i0) entered forwarding state
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 2(tap102i0) entered disabled state
Mar 04 19:23:34 pve1 kernel: tap102i0: entered allmulticast mode
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 2(tap102i0) entered blocking state
Mar 04 19:23:34 pve1 kernel: fwbr102i0: port 2(tap102i0) entered forwarding state
Mar 04 19:23:34 pve1 kernel: cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
Mar 04 19:23:34 pve1 kernel: cp210x 2-4.5:1.0: device disconnected
Mar 04 19:23:34 pve1 kernel: ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Mar 04 19:23:34 pve1 kernel: ftdi_sio 2-4.4:1.0: device disconnected
Mar 04 19:23:34 pve1 pvedaemon[963]: root@pam end task UPID:pve1:00000633:000021DC:67C74524:qmstart:102:root@pam: OK
Mar 04 19:23:37 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:23:43 pve1 kernel: usb 2-4.4: reset full-speed USB device number 6 using xhci_hcd
Mar 04 19:23:44 pve1 kernel: usb 2-1: reset full-speed USB device number 2 using xhci_hcd
Mar 04 19:23:44 pve1 kernel: cdc_acm 2-1:1.0: ttyACM0: USB ACM device
Mar 04 19:23:44 pve1 kernel: usb 2-4.5: reset full-speed USB device number 7 using xhci_hcd
Mar 04 19:24:26 pve1 kernel: device-mapper: thin: 252:4: switching pool to out-of-data-space (error IO) mode
Mar 04 19:24:26 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299712)
Mar 04 19:24:26 pve1 kernel: Buffer I/O error on device dm-11, logical block 299711
Mar 04 19:24:26 pve1 kernel: Buffer I/O error on device dm-11, logical block 299712
Mar 04 19:24:26 pve1 kernel: Buffer I/O error on device dm-11, logical block 299713
Mar 04 19:24:30 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299728)
Mar 04 19:24:30 pve1 kernel: Buffer I/O error on device dm-11, logical block 299726
Mar 04 19:24:30 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299744)
Mar 04 19:24:30 pve1 kernel: Buffer I/O error on device dm-11, logical block 299727
Mar 04 19:24:30 pve1 kernel: Buffer I/O error on device dm-11, logical block 299728
Mar 04 19:24:30 pve1 kernel: Buffer I/O error on device dm-11, logical block 299729
Mar 04 19:24:30 pve1 kernel: Buffer I/O error on device dm-11, logical block 299730
Mar 04 19:24:30 pve1 kernel: Buffer I/O error on device dm-11, logical block 299731
Mar 04 19:24:30 pve1 kernel: Buffer I/O error on device dm-11, logical block 299732
Mar 04 19:24:30 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299712)
Mar 04 19:24:36 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:24:59 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:25:22 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:25:43 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:26:02 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:26:21 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:26:27 pve1 pvedaemon[2373]: starting vnc proxy UPID:pve1:00000945:0000660F:67C745D3:vncproxy:102:root@pam:
Mar 04 19:26:27 pve1 pvedaemon[965]: root@pam starting task UPID:pve1:00000945:0000660F:67C745D3:vncproxy:102:root@pam:
Mar 04 19:27:07 pve1 pvedaemon[2499]: start VM 102: UPID:pve1:000009C3:000075D6:67C745FB:qmstart:102:root@pam:
Mar 04 19:27:07 pve1 pvedaemon[962]: root@pam starting task UPID:pve1:000009C3:000075D6:67C745FB:qmstart:102:root@pam:
Mar 04 19:27:07 pve1 pvedaemon[2499]: VM 102 already running
Mar 04 19:27:07 pve1 pvedaemon[962]: root@pam end task UPID:pve1:000009C3:000075D6:67C745FB:qmstart:102:root@pam: VM 102 already running
Mar 04 19:29:23 pve1 pvedaemon[965]: root@pam end task UPID:pve1:00000945:0000660F:67C745D3:vncproxy:102:root@pam: OK
Mar 04 19:29:31 pve1 pvedaemon[2950]: starting vnc proxy UPID:pve1:00000B86:0000ADF1:67C7468B:vncproxy:102:root@pam:
Mar 04 19:29:31 pve1 pvedaemon[962]: root@pam starting task UPID:pve1:00000B86:0000ADF1:67C7468B:vncproxy:102:root@pam:
Mar 04 19:29:33 pve1 pvedaemon[962]: root@pam end task UPID:pve1:00000B86:0000ADF1:67C7468B:vncproxy:102:root@pam: OK
Mar 04 19:30:45 pve1 pvedaemon[963]: root@pam starting task UPID:pve1:00000C69:0000CB04:67C746D5:vncproxy:102:root@pam:
Mar 04 19:30:45 pve1 pvedaemon[3177]: starting vnc proxy UPID:pve1:00000C69:0000CB04:67C746D5:vncproxy:102:root@pam:
Mar 04 19:31:00 pve1 pvedaemon[963]: root@pam end task UPID:pve1:00000C69:0000CB04:67C746D5:vncproxy:102:root@pam: OK
Mar 04 19:33:53 pve1 pvedaemon[962]: root@pam starting task UPID:pve1:00000EA6:00011438:67C74791:qmstart:102:root@pam:
Mar 04 19:33:53 pve1 pvedaemon[3750]: start VM 102: UPID:pve1:00000EA6:00011438:67C74791:qmstart:102:root@pam:
Mar 04 19:33:53 pve1 pvedaemon[3750]: VM 102 already running
Mar 04 19:33:53 pve1 pvedaemon[962]: root@pam end task UPID:pve1:00000EA6:00011438:67C74791:qmstart:102:root@pam: VM 102 already running
Mar 04 19:37:24 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 19:37:24 pve1 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories…
Mar 04 19:37:24 pve1 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Mar 04 19:37:24 pve1 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Mar 04 19:37:24 pve1 systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Mar 04 19:38:33 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299718)
Mar 04 19:38:33 pve1 kernel: buffer_io_error: 26 callbacks suppressed
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299718
Mar 04 19:38:33 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299724)
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299724
Mar 04 19:38:33 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299728)
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299727
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299728
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299729
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299730
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299731
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299732
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299733
Mar 04 19:38:33 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299735)
Mar 04 19:38:33 pve1 kernel: Buffer I/O error on device dm-11, logical block 299735
Mar 04 19:38:33 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299744)
Mar 04 19:43:25 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:43:44 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:44:03 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:44:23 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:44:28 pve1 pvedaemon[962]: root@pam starting task UPID:pve1:00001650:00020C71:67C74A0C:vncproxy:102:root@pam:
Mar 04 19:44:28 pve1 pvedaemon[5712]: starting vnc proxy UPID:pve1:00001650:00020C71:67C74A0C:vncproxy:102:root@pam:
Mar 04 19:48:25 pve1 pvedaemon[962]: root@pam end task UPID:pve1:00001650:00020C71:67C74A0C:vncproxy:102:root@pam: OK
Mar 04 19:48:29 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:48:48 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:49:07 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:49:26 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:49:47 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:50:09 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:50:32 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:50:54 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:51:17 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:51:39 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:52:02 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:52:14 pve1 smartd[623]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 54 to 55
Mar 04 19:52:25 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:52:25 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 19:52:47 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:53:10 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:53:32 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:53:55 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:54:16 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:54:27 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22223 starting block 490448)
Mar 04 19:54:27 pve1 kernel: buffer_io_error: 2 callbacks suppressed
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490368
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490369
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490370
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490371
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490372
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490373
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490374
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490375
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490376
Mar 04 19:54:27 pve1 kernel: Buffer I/O error on device dm-11, logical block 490377
Mar 04 19:54:55 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:55:19 pve1 pvedaemon[7725]: start VM 102: UPID:pve1:00001E2D:00030AAD:67C74C97:qmstart:102:root@pam:
Mar 04 19:55:19 pve1 pvedaemon[962]: root@pam starting task UPID:pve1:00001E2D:00030AAD:67C74C97:qmstart:102:root@pam:
Mar 04 19:55:19 pve1 pvedaemon[7725]: VM 102 already running
Mar 04 19:55:19 pve1 pvedaemon[962]: root@pam end task UPID:pve1:00001E2D:00030AAD:67C74C97:qmstart:102:root@pam: VM 102 already running
Mar 04 19:55:20 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:55:39 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:56:00 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:56:22 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:56:45 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:57:07 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:57:30 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:57:53 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:58:14 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:58:22 pve1 pveproxy[982]: worker 985 finished
Mar 04 19:58:22 pve1 pveproxy[982]: starting 1 worker(s)
Mar 04 19:58:22 pve1 pveproxy[982]: worker 8277 started
Mar 04 19:58:24 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:58:24 pve1 pveproxy[8276]: worker exit
Mar 04 19:58:45 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:59:07 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:59:30 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 19:59:52 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:00:15 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:00:38 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:01:00 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:01:23 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:01:45 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:02:08 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:02:31 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:02:53 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:03:16 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:03:38 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:04:05 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:04:28 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:04:50 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299724)
Mar 04 20:05:06 pve1 kernel: buffer_io_error: 80 callbacks suppressed
Mar 04 20:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299724
Mar 04 20:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299734)
Mar 04 20:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299734
Mar 04 20:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299735
Mar 04 20:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299744)
Mar 04 20:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299743
Mar 04 20:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299744
Mar 04 20:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299745)
Mar 04 20:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299745
Mar 04 20:05:13 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:05:35 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:05:58 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:06:21 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:06:44 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:07:06 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:07:25 pve1 pvedaemon[965]: root@pam successful auth for user ‹ root@pam ›
Mar 04 20:07:29 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:07:51 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:08:14 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:08:36 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:08:59 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:09:21 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:09:44 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:10:07 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:10:29 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:10:52 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:11:14 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:11:37 pve1 pvedaemon[965]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:12:00 pve1 pvedaemon[963]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:12:22 pve1 pvedaemon[962]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-ping › failed - got timeout
Mar 04 20:14:50 pve1 pveproxy[983]: worker exit
Mar 04 20:14:50 pve1 pveproxy[982]: worker 983 finished
Mar 04 20:14:50 pve1 pveproxy[982]: starting 1 worker(s)
Mar 04 20:14:50 pve1 pveproxy[982]: worker 11308 started
Mar 04 20:17:01 pve1 CRON[11713]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 04 20:17:01 pve1 CRON[11714]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 04 20:17:01 pve1 CRON[11713]: pam_unix(cron:session): session closed for user root
Mar 04 20:22:26 pve1 pvedaemon[965]: root@pam successful auth for user ‹ root@pam ›
Mar 04 20:37:27 pve1 pvedaemon[965]: root@pam successful auth for user ‹ root@pam ›
Mar 04 20:38:18 pve1 kernel: perf: interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
Mar 04 20:43:51 pve1 pveproxy[984]: worker exit
Mar 04 20:43:51 pve1 pveproxy[982]: worker 984 finished
Mar 04 20:43:51 pve1 pveproxy[982]: starting 1 worker(s)
Mar 04 20:43:51 pve1 pveproxy[982]: worker 16644 started
Mar 04 20:52:27 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 21:01:11 pve1 pvedaemon[19829]: starting termproxy UPID:pve1:00004D75:0009126C:67C75C07:vncshell::root@pam:
Mar 04 21:01:11 pve1 pvedaemon[963]: root@pam starting task UPID:pve1:00004D75:0009126C:67C75C07:vncshell::root@pam:
Mar 04 21:01:11 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 21:01:11 pve1 login[19833]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Mar 04 21:01:11 pve1 systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Mar 04 21:01:11 pve1 systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0…
Mar 04 21:01:11 pve1 systemd-logind[632]: New session 4 of user root.
Mar 04 21:01:11 pve1 systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Mar 04 21:01:11 pve1 systemd[1]: Starting user@0.service - User Manager for UID 0…
Mar 04 21:01:11 pve1 (systemd)[19839]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Mar 04 21:01:11 pve1 systemd[19839]: Queued start job for default target default.target.
Mar 04 21:01:11 pve1 systemd[19839]: Created slice app.slice - User Application Slice.
Mar 04 21:01:11 pve1 systemd[19839]: Reached target paths.target - Paths.
Mar 04 21:01:11 pve1 systemd[19839]: Reached target timers.target - Timers.
Mar 04 21:01:11 pve1 systemd[19839]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Mar 04 21:01:11 pve1 systemd[19839]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 04 21:01:11 pve1 systemd[19839]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Mar 04 21:01:11 pve1 systemd[19839]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Mar 04 21:01:11 pve1 systemd[19839]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Mar 04 21:01:11 pve1 systemd[19839]: Reached target sockets.target - Sockets.
Mar 04 21:01:11 pve1 systemd[19839]: Reached target basic.target - Basic System.
Mar 04 21:01:11 pve1 systemd[19839]: Reached target default.target - Main User Target.
Mar 04 21:01:11 pve1 systemd[19839]: Startup finished in 197ms.
Mar 04 21:01:11 pve1 systemd[1]: Started user@0.service - User Manager for UID 0.
Mar 04 21:01:11 pve1 systemd[1]: Started session-4.scope - Session 4 of User root.
Mar 04 21:01:11 pve1 login[19856]: ROOT LOGIN on ‹ /dev/pts/0 ›
Mar 04 21:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299724)
Mar 04 21:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299724
Mar 04 21:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299734)
Mar 04 21:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299734
Mar 04 21:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299735
Mar 04 21:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299745)
Mar 04 21:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299745
Mar 04 21:05:06 pve1 kernel: EXT4-fs warning (device dm-11): ext4_end_bio:343: I/O error 3 writing to inode 22227 starting block 299743)
Mar 04 21:05:06 pve1 kernel: Buffer I/O error on device dm-11, logical block 299743
Mar 04 21:07:28 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 21:09:57 pve1 systemd-logind[632]: Session 4 logged out. Waiting for processes to exit.
Mar 04 21:09:57 pve1 systemd[1]: session-4.scope: Deactivated successfully.
Mar 04 21:09:57 pve1 systemd-logind[632]: Removed session 4.
Mar 04 21:09:57 pve1 pvedaemon[963]: root@pam end task UPID:pve1:00004D75:0009126C:67C75C07:vncshell::root@pam: OK
Mar 04 21:10:07 pve1 systemd[1]: Stopping user@0.service - User Manager for UID 0…
Mar 04 21:10:07 pve1 systemd[19839]: Activating special unit exit.target…
Mar 04 21:10:07 pve1 systemd[19839]: Stopped target default.target - Main User Target.
Mar 04 21:10:07 pve1 systemd[19839]: Stopped target basic.target - Basic System.
Mar 04 21:10:07 pve1 systemd[19839]: Stopped target paths.target - Paths.
Mar 04 21:10:07 pve1 systemd[19839]: Stopped target sockets.target - Sockets.
Mar 04 21:10:07 pve1 systemd[19839]: Stopped target timers.target - Timers.
Mar 04 21:10:07 pve1 systemd[19839]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Mar 04 21:10:07 pve1 systemd[19839]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 04 21:10:07 pve1 systemd[19839]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Mar 04 21:10:07 pve1 systemd[19839]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Mar 04 21:10:07 pve1 systemd[19839]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Mar 04 21:10:07 pve1 systemd[19839]: Removed slice app.slice - User Application Slice.
Mar 04 21:10:07 pve1 systemd[19839]: Reached target shutdown.target - Shutdown.
Mar 04 21:10:07 pve1 systemd[19839]: Finished systemd-exit.service - Exit the Session.
Mar 04 21:10:07 pve1 systemd[19839]: Reached target exit.target - Exit the Session.
Mar 04 21:10:07 pve1 (sd-pam)[19842]: pam_unix(systemd-user:session): session closed for user root
Mar 04 21:10:07 pve1 systemd[1]: user@0.service: Deactivated successfully.
Mar 04 21:10:07 pve1 systemd[1]: Stopped user@0.service - User Manager for UID 0.
Mar 04 21:10:07 pve1 systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0…
Mar 04 21:10:07 pve1 systemd[1]: run-user-0.mount: Deactivated successfully.
Mar 04 21:10:07 pve1 systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Mar 04 21:10:07 pve1 systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Mar 04 21:10:07 pve1 systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Mar 04 21:10:37 pve1 pvedaemon[21588]: start VM 102: UPID:pve1:00005454:0009EF99:67C75E3D:qmstart:102:root@pam:
Mar 04 21:10:37 pve1 pvedaemon[963]: root@pam starting task UPID:pve1:00005454:0009EF99:67C75E3D:qmstart:102:root@pam:
Mar 04 21:10:37 pve1 pvedaemon[21588]: VM 102 already running
Mar 04 21:10:37 pve1 pvedaemon[963]: root@pam end task UPID:pve1:00005454:0009EF99:67C75E3D:qmstart:102:root@pam: VM 102 already running
Mar 04 21:10:50 pve1 pvedaemon[962]: root@pam starting task UPID:pve1:00005475:0009F489:67C75E4A:qmshutdown:102:root@pam:
Mar 04 21:10:50 pve1 pvedaemon[21621]: shutdown VM 102: UPID:pve1:00005475:0009F489:67C75E4A:qmshutdown:102:root@pam:
Mar 04 21:14:14 pve1 pveproxy[8277]: worker exit
Mar 04 21:14:14 pve1 pveproxy[982]: worker 8277 finished
Mar 04 21:14:14 pve1 pveproxy[982]: starting 1 worker(s)
Mar 04 21:14:14 pve1 pveproxy[982]: worker 22258 started
Mar 04 21:17:01 pve1 CRON[22766]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 04 21:17:01 pve1 CRON[22767]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Mar 04 21:17:01 pve1 CRON[22766]: pam_unix(cron:session): session closed for user root
Mar 04 21:19:11 pve1 kernel: perf: interrupt took too long (3132 > 3128), lowering kernel.perf_event_max_sample_rate to 63000
Mar 04 21:20:50 pve1 pvedaemon[21621]: VM 102 qmp command failed - VM 102 qmp command ‹ guest-shutdown › failed - got timeout
Mar 04 21:20:50 pve1 pvedaemon[21621]: VM quit/powerdown failed
Mar 04 21:20:50 pve1 pvedaemon[962]: root@pam end task UPID:pve1:00005475:0009F489:67C75E4A:qmshutdown:102:root@pam: VM quit/powerdown failed
Mar 04 21:22:14 pve1 smartd[623]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 55 to 54
Mar 04 21:22:28 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 21:33:42 pve1 pvedaemon[963]: root@pam starting task UPID:pve1:000064DF:000C0C98:67C763A6:vncshell::root@pam:
Mar 04 21:33:42 pve1 pvedaemon[25823]: starting termproxy UPID:pve1:000064DF:000C0C98:67C763A6:vncshell::root@pam:
Mar 04 21:33:42 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Mar 04 21:33:42 pve1 login[25826]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Mar 04 21:33:42 pve1 systemd-logind[632]: New session 8 of user root.
Mar 04 21:33:42 pve1 systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Mar 04 21:33:42 pve1 systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0…
Mar 04 21:33:42 pve1 systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Mar 04 21:33:42 pve1 systemd[1]: Starting user@0.service - User Manager for UID 0…
Mar 04 21:33:42 pve1 (systemd)[25832]: pam_unix(systemd-user:session): session opened for user root(uid=0) by (uid=0)
Mar 04 21:33:42 pve1 systemd[25832]: Queued start job for default target default.target.
Mar 04 21:33:42 pve1 systemd[25832]: Created slice app.slice - User Application Slice.
Mar 04 21:33:42 pve1 systemd[25832]: Reached target paths.target - Paths.
Mar 04 21:33:42 pve1 systemd[25832]: Reached target timers.target - Timers.
Mar 04 21:33:42 pve1 systemd[25832]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Mar 04 21:33:42 pve1 systemd[25832]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 04 21:33:42 pve1 systemd[25832]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Mar 04 21:33:42 pve1 systemd[25832]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Mar 04 21:33:42 pve1 systemd[25832]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Mar 04 21:33:42 pve1 systemd[25832]: Reached target sockets.target - Sockets.
Mar 04 21:33:42 pve1 systemd[25832]: Reached target basic.target - Basic System.
Mar 04 21:33:42 pve1 systemd[25832]: Reached target default.target - Main User Target.
Mar 04 21:33:42 pve1 systemd[25832]: Startup finished in 190ms.
Mar 04 21:33:42 pve1 systemd[1]: Started user@0.service - User Manager for UID 0.
Mar 04 21:33:42 pve1 systemd[1]: Started session-8.scope - Session 8 of User root.
Mar 04 21:33:42 pve1 login[25848]: ROOT LOGIN on ‹ /dev/pts/0 ›
Mar 04 21:36:58 pve1 systemd[1]: session-8.scope: Deactivated successfully.
Mar 04 21:36:58 pve1 systemd-logind[632]: Session 8 logged out. Waiting for processes to exit.
Mar 04 21:36:58 pve1 systemd-logind[632]: Removed session 8.
Mar 04 21:36:58 pve1 pvedaemon[963]: root@pam end task UPID:pve1:000064DF:000C0C98:67C763A6:vncshell::root@pam: OK
Mar 04 21:37:08 pve1 systemd[1]: Stopping user@0.service - User Manager for UID 0…
Mar 04 21:37:08 pve1 systemd[25832]: Activating special unit exit.target…
Mar 04 21:37:08 pve1 systemd[25832]: Stopped target default.target - Main User Target.
Mar 04 21:37:08 pve1 systemd[25832]: Stopped target basic.target - Basic System.
Mar 04 21:37:08 pve1 systemd[25832]: Stopped target paths.target - Paths.
Mar 04 21:37:08 pve1 systemd[25832]: Stopped target sockets.target - Sockets.
Mar 04 21:37:08 pve1 systemd[25832]: Stopped target timers.target - Timers.
Mar 04 21:37:08 pve1 systemd[25832]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Mar 04 21:37:08 pve1 systemd[25832]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Mar 04 21:37:08 pve1 systemd[25832]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Mar 04 21:37:08 pve1 systemd[25832]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Mar 04 21:37:08 pve1 systemd[25832]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Mar 04 21:37:08 pve1 systemd[25832]: Removed slice app.slice - User Application Slice.
Mar 04 21:37:08 pve1 systemd[25832]: Reached target shutdown.target - Shutdown.
Mar 04 21:37:08 pve1 systemd[25832]: Finished systemd-exit.service - Exit the Session.
Mar 04 21:37:08 pve1 systemd[25832]: Reached target exit.target - Exit the Session.
Mar 04 21:37:08 pve1 systemd[1]: user@0.service: Deactivated successfully.
Mar 04 21:37:08 pve1 systemd[1]: Stopped user@0.service - User Manager for UID 0.
Mar 04 21:37:08 pve1 systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0…
Mar 04 21:37:08 pve1 systemd[1]: run-user-0.mount: Deactivated successfully.
Mar 04 21:37:08 pve1 systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Mar 04 21:37:08 pve1 systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Mar 04 21:37:08 pve1 systemd[1]: Removed slice user-0.slice - User Slice of UID 0.
Mar 04 21:37:28 pve1 pvedaemon[962]: root@pam successful auth for user ‹ root@pam ›
Journaux
Alors le plus simple aurait été soit de publier le fichier soit de donner que le morceau de log intéressant.
Tu fais régulièrement les maj de ton proxmox ?
Merci pour les conseils du fichier.mais j’ai ce soucis
Non il y a longtemps que j’ai fait une mise à jour.
Tu penses que je peux les faire maintenant ?
Boboss
Il suffit de rechercher I/O error dans ce log : vu le nombre, très probablement un problème disque
Donc un changement de disque s’impose.
Merci de vos conseils
Boboss
