Plantages Proxmox

Dapolux · Mars 3, 2024, 5:19

Bonjour,

Cela fait une dizaine de jours que j’ai des plantages de proxmox (tout à coup plus aucune vm ne répond, l’interface proxmox n’est pas accessible, obligé de hardreset le nuc pour que tout redémarre).

D’un point de vue installation, j’ai mon proxmox installé sur un NUC (i5, 24g de RAM, 1 SSD de 240gb avec proxmox, les images et les volumes des VM, puis 1 SSD 1T avec les volumes des containers LXC, et une Coral). En fonctionnement de croisière, j’utilise 1vm, et 5 CT LXC. Jusqu’a il y a 10 jours, je n’avai jamais eu de plantage de proxmox.

Après plusieurs recherches et tests, j’ai l’impression que j’ai un problème hardware:
(Exemple de cette après midi, avec plantage a 16h48, et redémarrage a 17h08)

Extrait des logs jusqu'a 16h48

Mar 03 16:31:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:31:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:31:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:32:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:32:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:32:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:33:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:33:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:33:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:34:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:34:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:34:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:35:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:35:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:35:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:36:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:36:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:36:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:37:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:37:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:37:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:38:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:38:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:38:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:39:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:39:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:39:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:40:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:40:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:40:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:41:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:41:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:41:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:42:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:42:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:42:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:42:56 proxmox pvedaemon[1012]: root@pam successful auth for user ‹ dapolux@pam ›
Mar 03 16:43:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:43:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:43:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:44:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:44:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:44:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:45:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:45:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:45:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:45:46 proxmox kernel: usb 1-9: reset full-speed USB device number 6 using xhci_hcd
Mar 03 16:45:46 proxmox kernel: usb 1-3: reset full-speed USB device number 7 using xhci_hcd
Mar 03 16:45:46 proxmox kernel: usb 1-4: reset full-speed USB device number 10 using xhci_hcd
Mar 03 16:45:47 proxmox kernel: usb 1-2: reset full-speed USB device number 3 using xhci_hcd
Mar 03 16:45:47 proxmox kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Mar 03 16:45:54 proxmox kernel: usb 1-9: reset full-speed USB device number 6 using xhci_hcd
Mar 03 16:45:55 proxmox kernel: usb 1-3: reset full-speed USB device number 7 using xhci_hcd
Mar 03 16:45:55 proxmox kernel: usb 1-4: reset full-speed USB device number 10 using xhci_hcd
Mar 03 16:45:55 proxmox kernel: usb 1-2: reset full-speed USB device number 3 using xhci_hcd
Mar 03 16:45:56 proxmox kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Mar 03 16:45:59 proxmox kernel: usb 1-3: USB disconnect, device number 7
Mar 03 16:46:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:46:00 proxmox QEMU[1046]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Mar 03 16:46:00 proxmox QEMU[1046]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Mar 03 16:46:00 proxmox kernel: usb 1-3: new full-speed USB device number 11 using xhci_hcd
Mar 03 16:46:00 proxmox kernel: usb 1-3: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=82.41
Mar 03 16:46:00 proxmox kernel: usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 03 16:46:00 proxmox kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
Mar 03 16:46:00 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status…
Mar 03 16:46:00 proxmox systemd[1]: Reached target Bluetooth.
Mar 03 16:46:00 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Mar 03 16:46:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:46:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:46:02 proxmox systemd[1]: Stopped target Bluetooth.
Mar 03 16:46:02 proxmox kernel: Bluetooth: hci0: urb 0000000074d52e5c failed to resubmit (2)
Mar 03 16:46:02 proxmox kernel: usb 1-3: reset full-speed USB device number 11 using xhci_hcd
Mar 03 16:46:07 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Mar 03 16:46:34 proxmox QEMU[1046]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Mar 03 16:46:34 proxmox QEMU[1046]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Mar 03 16:46:34 proxmox kernel: usb 1-4: USB disconnect, device number 10
Mar 03 16:46:34 proxmox kernel: usb 1-4: new full-speed USB device number 12 using xhci_hcd
Mar 03 16:46:35 proxmox kernel: usb 1-4: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Mar 03 16:46:35 proxmox kernel: usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 03 16:46:35 proxmox kernel: cdc_acm 1-4:1.0: ttyACM0: USB ACM device
Mar 03 16:46:36 proxmox kernel: usb 1-4: reset full-speed USB device number 12 using xhci_hcd
Mar 03 16:46:52 proxmox pvedaemon[1011]: root@pam successful auth for user ‹ ha_audit@pve ›
Mar 03 16:47:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:47:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:47:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:48:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 16:48:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 16:48:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 16:48:01 proxmox kernel: BUG: Bad page map in process pve-firewall pte:00000009 pmd:55ccfa067
Mar 03 16:48:01 proxmox kernel: page:00000000043864ad refcount:1 mapcount:-1 mapping:0000000000000000 index:0x0 pfn:0x0
Mar 03 16:48:01 proxmox kernel: flags: 0x7ffffc0001000(reserved)
Mar 03 16:48:01 proxmox kernel: raw: 0007ffffc0001000 ffffc490c0000008 ffffc490c0000008 0000000000000000
Mar 03 16:48:01 proxmox kernel: raw: 0000000000000000 0000000000000000 00000001fffffffe 0000000000000000
Mar 03 16:48:01 proxmox kernel: page dumped because: bad pte
Mar 03 16:48:01 proxmox kernel: addr:00007f5b8977b000 vm_flags:08100073 anon_vma:ffff8c4f2a90d2c0 mapping:0000000000000000 index:7f5b8977b
Mar 03 16:48:01 proxmox kernel: file:(null) fault:0x0 mmap:0x0 readpage:0x0
Mar 03 16:48:01 proxmox kernel: CPU: 0 PID: 2808802 Comm: pve-firewall Tainted: P O 5.11.22-1-pve #1
Mar 03 16:48:01 proxmox kernel: Hardware name: Default string Default string/Default string, BIOS 5.12 11/10/2018
Mar 03 16:48:01 proxmox kernel: Call Trace:
Mar 03 16:48:01 proxmox kernel: dump_stack+0x70/0x8b
Mar 03 16:48:01 proxmox kernel: print_bad_pte.cold+0x9b/0xbc
Mar 03 16:48:01 proxmox kernel: unmap_page_range+0x8a8/0xe40
Mar 03 16:48:01 proxmox kernel: unmap_single_vma+0x7f/0xf0
Mar 03 16:48:01 proxmox kernel: unmap_vmas+0x77/0xf0
Mar 03 16:48:01 proxmox kernel: exit_mmap+0xb4/0x200
Mar 03 16:48:01 proxmox kernel: mmput+0x5f/0x140
Mar 03 16:48:01 proxmox kernel: begin_new_exec+0x4e0/0xa30
Mar 03 16:48:01 proxmox kernel: load_elf_binary+0x764/0x17f0
Mar 03 16:48:01 proxmox kernel: ? __kernel_read+0x19d/0x2c0
Mar 03 16:48:01 proxmox kernel: ? aa_get_task_label+0x49/0xd0
Mar 03 16:48:01 proxmox kernel: ? ima_bprm_check+0x89/0xb0
Mar 03 16:48:01 proxmox kernel: bprm_execve+0x27f/0x660
Mar 03 16:48:01 proxmox kernel: do_execveat_common+0x192/0x1c0
Mar 03 16:48:01 proxmox kernel: __x64_sys_execve+0x39/0x50
Mar 03 16:48:01 proxmox kernel: do_syscall_64+0x38/0x90
Mar 03 16:48:01 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 03 16:48:01 proxmox kernel: RIP: 0033:0x7f5b94146fc7
Mar 03 16:48:01 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7f5b94146f9d.
Mar 03 16:48:01 proxmox kernel: RSP: 002b:00007fff6fe9d618 EFLAGS: 00000203 ORIG_RAX: 000000000000003b
Mar 03 16:48:01 proxmox kernel: RAX: ffffffffffffffda RBX: 000055920ff5a010 RCX: 00007f5b94146fc7
Mar 03 16:48:01 proxmox kernel: RDX: 000055920ff58ca0 RSI: 000055920ff59f40 RDI: 00007fff6fe9d620
Mar 03 16:48:01 proxmox kernel: RBP: 00007fff6fe9d6b0 R08: 000000000000000e R09: 000055920b42ce6a
Mar 03 16:48:01 proxmox kernel: R10: fffffffffffff7e6 R11: 0000000000000203 R12: 000055920ff59f40
Mar 03 16:48:01 proxmox kernel: R13: 000055920ff58ca0 R14: 00007fff6fe9d620 R15: 000055920b42ce65
Mar 03 16:48:01 proxmox kernel: BUG: Bad page state in process pve-firewall pfn:00000
Mar 03 16:48:01 proxmox kernel: page:00000000043864ad refcount:0 mapcount:-1 mapping:0000000000000000 index:0x0 pfn:0x0
Mar 03 16:48:01 proxmox kernel: flags: 0x7ffffc0000000()
Mar 03 16:48:01 proxmox kernel: raw: 0007ffffc0000000 dead000000000100 dead000000000122 0000000000000000
Mar 03 16:48:01 proxmox kernel: raw: 0000000000000000 0000000000000000 00000000fffffffe 0000000000000000
Mar 03 16:48:01 proxmox kernel: page dumped because: nonzero mapcount
Mar 03 16:48:01 proxmox kernel: Modules linked in: tcp_diag inet_diag iptable_nat xt_REDIRECT nf_conntrack_netlink xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat overlay nf_tables veth ebtable_filter ebtables ip_set ip6table_raw iptable_raw ip6table_filter ip6_tables iptable_filter bpfilter bonding tls softdog nfnetlink_log nfnetlink zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) snd_hda_codec_hdmi zcommon(PO) znvpair(PO) snd_hda_codec_realtek spl(O) snd_hda_codec_generic vhost_net ledtrig_audio vhost snd_soc_skl vhost_iotlb tap snd_soc_sst_ipc snd_soc_sst_dsp ib_iser snd_hda_ext_core snd_soc_acpi_intel_match rdma_cm snd_soc_acpi iw_cm snd_hda_intel ib_cm snd_intel_dspcfg soundwire_intel ib_core soundwire_generic_allocation soundwire_cadence iscsi_tcp snd_hda_codec libiscsi_tcp libiscsi snd_hda_core snd_hwdep scsi_transport_iscsi soundwire_bus x86_pkg_temp_thermal ath9k
Mar 03 16:48:01 proxmox kernel: intel_powerclamp ath9k_common coretemp snd_soc_core ath9k_hw snd_compress kvm_intel ath3k ac97_bus crct10dif_pclmul ath btusb ghash_clmulni_intel snd_pcm_dmaengine aesni_intel btrtl mei_hdcp intel_rapl_msr mac80211 snd_pcm crypto_simd btbcm cryptd btintel snd_timer glue_helper cfg80211 snd bluetooth rapl processor_thermal_device ecdh_generic libarc4 ftdi_sio ecc cp210x apex(O) soundcore processor_thermal_rfim cdc_acm intel_cstate usbserial gasket(O) processor_thermal_mbox processor_thermal_rapl ee1004 mei_me intel_rapl_common bmc150_accel_i2c mei intel_xhci_usb_role_switch intel_soc_dts_iosf intel_pch_thermal pcspkr bmc150_accel_core industrialio_triggered_buffer efi_pstore intel_wmi_thunderbolt kfifo_buf int3400_thermal industrialio mac_hid int3403_thermal acpi_thermal_rel int340x_thermal_zone acpi_pad i915 vfio_mdev mdev drm_kms_helper cec rc_core i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt kvm vfio_pci vfio_virqfd irqbypass vfio_iommu_type1 vfio drm sunrpc
Mar 03 16:48:01 proxmox kernel: ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c xhci_pci xhci_pci_renesas crc32_pclmul i2c_i801 ahci r8169 i2c_hid i2c_smbus realtek xhci_hcd libahci wmi hid video
Mar 03 16:48:01 proxmox kernel: CPU: 0 PID: 2808802 Comm: pve-firewall Tainted: P B O 5.11.22-1-pve #1
Mar 03 16:48:01 proxmox kernel: Hardware name: Default string Default string/Default string, BIOS 5.12 11/10/2018
Mar 03 16:48:01 proxmox kernel: Call Trace:
Mar 03 16:48:01 proxmox kernel: dump_stack+0x70/0x8b
Mar 03 16:48:01 proxmox kernel: bad_page.cold+0x63/0x94
Mar 03 16:48:01 proxmox kernel: check_free_page_bad+0x69/0x70
Mar 03 16:48:01 proxmox kernel: free_pcppages_bulk+0x177/0x2b0
Mar 03 16:48:01 proxmox kernel: free_unref_page_commit+0xad/0xd0
Mar 03 16:48:01 proxmox kernel: free_unref_page_list+0x155/0x1d0
Mar 03 16:48:01 proxmox kernel: release_pages+0x163/0x480
Mar 03 16:48:01 proxmox kernel: free_pages_and_swap_cache+0xb8/0xd0
Mar 03 16:48:01 proxmox kernel: tlb_finish_mmu+0x89/0x1f0
Mar 03 16:48:01 proxmox kernel: exit_mmap+0xdc/0x200
Mar 03 16:48:01 proxmox kernel: mmput+0x5f/0x140
Mar 03 16:48:01 proxmox kernel: begin_new_exec+0x4e0/0xa30
Mar 03 16:48:01 proxmox kernel: load_elf_binary+0x764/0x17f0
Mar 03 16:48:01 proxmox kernel: ? __kernel_read+0x19d/0x2c0
Mar 03 16:48:01 proxmox kernel: ? aa_get_task_label+0x49/0xd0
Mar 03 16:48:01 proxmox kernel: ? ima_bprm_check+0x89/0xb0
Mar 03 16:48:01 proxmox kernel: bprm_execve+0x27f/0x660
Mar 03 16:48:01 proxmox kernel: do_execveat_common+0x192/0x1c0
Mar 03 16:48:01 proxmox kernel: __x64_sys_execve+0x39/0x50
Mar 03 16:48:01 proxmox kernel: do_syscall_64+0x38/0x90
Mar 03 16:48:01 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 03 16:48:01 proxmox kernel: RIP: 0033:0x7f5b94146fc7
Mar 03 16:48:01 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7f5b94146f9d.
Mar 03 16:48:01 proxmox kernel: RSP: 002b:00007fff6fe9d618 EFLAGS: 00000203 ORIG_RAX: 000000000000003b
Mar 03 16:48:01 proxmox kernel: RAX: ffffffffffffffda RBX: 000055920ff5a010 RCX: 00007f5b94146fc7
Mar 03 16:48:01 proxmox kernel: RDX: 000055920ff58ca0 RSI: 000055920ff59f40 RDI: 00007fff6fe9d620
Mar 03 16:48:01 proxmox kernel: RBP: 00007fff6fe9d6b0 R08: 000000000000000e R09: 000055920b42ce6a
Mar 03 16:48:01 proxmox kernel: R10: fffffffffffff7e6 R11: 0000000000000203 R12: 000055920ff59f40
Mar 03 16:48:01 proxmox kernel: R13: 000055920ff58ca0 R14: 00007fff6fe9d620 R15: 000055920b42ce65
Mar 03 16:48:01 proxmox kernel: BUG: Bad rss-counter state mm:00000000bf1c30ec type:MM_FILEPAGES val:-1
Mar 03 16:48:03 proxmox kernel: BUG: Bad page map in process python3 pte:00000009 pmd:55cc6a067
Mar 03 16:48:03 proxmox kernel: page:00000000043864ad refcount:0 mapcount:-1 mapping:0000000000000000 index:0x0 pfn:0x0
Mar 03 16:48:03 proxmox kernel: flags: 0x7ffffc0000000()
Mar 03 16:48:03 proxmox kernel: raw: 0007ffffc0000000 dead000000000100 dead000000000122 0000000000000000
Mar 03 16:48:03 proxmox kernel: raw: 0000000000000000 0000000000000000 00000000fffffffe 0000000000000000
Mar 03 16:48:03 proxmox kernel: page dumped because: bad pte
Mar 03 16:48:03 proxmox kernel: addr:00007feeec77b000 vm_flags:08000071 anon_vma:0000000000000000 mapping:ffff8c4f18055158 index:166
Mar 03 16:48:03 proxmox kernel: file:_ufuncs.cpython-39-x86_64-linux-gnu.so fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Mar 03 16:48:03 proxmox kernel: CPU: 3 PID: 2809366 Comm: python3 Tainted: P B O 5.11.22-1-pve #1
Mar 03 16:48:03 proxmox kernel: Hardware name: Default string Default string/Default string, BIOS 5.12 11/10/2018
Mar 03 16:48:03 proxmox kernel: Call Trace:
Mar 03 16:48:03 proxmox kernel: dump_stack+0x70/0x8b
Mar 03 16:48:03 proxmox kernel: print_bad_pte.cold+0x9b/0xbc
Mar 03 16:48:03 proxmox kernel: unmap_page_range+0x8a8/0xe40
Mar 03 16:48:03 proxmox kernel: unmap_single_vma+0x7f/0xf0
Mar 03 16:48:03 proxmox kernel: unmap_vmas+0x77/0xf0
Mar 03 16:48:03 proxmox kernel: exit_mmap+0xb4/0x200
Mar 03 16:48:03 proxmox kernel: mmput+0x5f/0x140
Mar 03 16:48:03 proxmox kernel: begin_new_exec+0x4e0/0xa30
Mar 03 16:48:03 proxmox kernel: load_elf_binary+0x764/0x17f0
Mar 03 16:48:03 proxmox kernel: ? __kernel_read+0x19d/0x2c0
Mar 03 16:48:03 proxmox kernel: ? aa_get_task_label+0x49/0xd0
Mar 03 16:48:03 proxmox kernel: ? ima_bprm_check+0x89/0xb0
Mar 03 16:48:03 proxmox kernel: bprm_execve+0x27f/0x660
Mar 03 16:48:03 proxmox kernel: do_execveat_common+0x192/0x1c0
Mar 03 16:48:03 proxmox kernel: __x64_sys_execve+0x39/0x50
Mar 03 16:48:03 proxmox kernel: do_syscall_64+0x38/0x90
Mar 03 16:48:03 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 03 16:48:03 proxmox kernel: RIP: 0033:0x7fef05ae58d7
Mar 03 16:48:03 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7fef05ae58ad.
Mar 03 16:48:03 proxmox kernel: RSP: 002b:00007feec0ff5048 EFLAGS: 00000246 ORIG_RAX: 000000000000003b
Mar 03 16:48:03 proxmox kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fef05ae58d7
Mar 03 16:48:03 proxmox kernel: RDX: 000000000150fb50 RSI: 00007feeec120450 RDI: 00007feef1be5d50
Mar 03 16:48:03 proxmox kernel: RBP: 00007feeec120450 R08: 0000000000000007 R09: 0000000000000000
Mar 03 16:48:03 proxmox kernel: R10: 00007fef05a24601 R11: 0000000000000246 R12: 0000000000000007
Mar 03 16:48:03 proxmox kernel: R13: 00007feeec0e3f90 R14: 0000000000000000 R15: 000000000000004f
Mar 03 16:48:03 proxmox kernel: BUG: Bad rss-counter state mm:00000000bc851ac0 type:MM_FILEPAGES val:-1
Mar 03 16:48:05 proxmox kernel: BUG: Bad page map in process ffprobe pte:00000009 pmd:55cc06067
Mar 03 16:48:05 proxmox kernel: page:00000000043864ad refcount:-1 mapcount:-2 mapping:0000000000000000 index:0x0 pfn:0x0
Mar 03 16:48:05 proxmox kernel: flags: 0x7ffffc0000000()
Mar 03 16:48:05 proxmox kernel: raw: 0007ffffc0000000 dead000000000100 dead000000000122 0000000000000000
Mar 03 16:48:05 proxmox kernel: raw: 0000000000000000 0000000000000000 fffffffffffffffd 0000000000000000
Mar 03 16:48:05 proxmox kernel: page dumped because: bad pte
Mar 03 16:48:05 proxmox kernel: addr:00005579dbd7b000 vm_flags:08000875 anon_vma:0000000000000000 mapping:ffff8c4f18085158 index:140a
Mar 03 16:48:05 proxmox kernel: file:ffprobe fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Mar 03 16:48:05 proxmox kernel: CPU: 6 PID: 2809894 Comm: ffprobe Tainted: P B O 5.11.22-1-pve #1
Mar 03 16:48:05 proxmox kernel: Hardware name: Default string Default string/Default string, BIOS 5.12 11/10/2018
Mar 03 16:48:05 proxmox kernel: Call Trace:
Mar 03 16:48:05 proxmox kernel: dump_stack+0x70/0x8b
Mar 03 16:48:05 proxmox kernel: print_bad_pte.cold+0x9b/0xbc
Mar 03 16:48:05 proxmox kernel: unmap_page_range+0x8a8/0xe40
Mar 03 16:48:05 proxmox kernel: unmap_single_vma+0x7f/0xf0
Mar 03 16:48:05 proxmox kernel: unmap_vmas+0x77/0xf0
Mar 03 16:48:05 proxmox kernel: exit_mmap+0xb4/0x200
Mar 03 16:48:05 proxmox kernel: mmput+0x5f/0x140
Mar 03 16:48:05 proxmox kernel: do_exit+0x31b/0xa30
Mar 03 16:48:05 proxmox kernel: do_group_exit+0x3b/0xb0
Mar 03 16:48:05 proxmox kernel: __x64_sys_exit_group+0x18/0x20
Mar 03 16:48:05 proxmox kernel: do_syscall_64+0x38/0x90
Mar 03 16:48:05 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 03 16:48:05 proxmox kernel: RIP: 0033:0x7fa758cf9209
Mar 03 16:48:05 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7fa758cf91df.
Mar 03 16:48:05 proxmox kernel: RSP: 002b:00007ffc4ce7c528 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
Mar 03 16:48:05 proxmox kernel: RAX: ffffffffffffffda RBX: 00007fa758df39e0 RCX: 00007fa758cf9209
Mar 03 16:48:05 proxmox kernel: RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
Mar 03 16:48:05 proxmox kernel: RBP: 0000000000000000 R08: fffffffffffffdf0 R09: 00007ffc4ce7c41f
Mar 03 16:48:05 proxmox kernel: R10: 00007ffc4ce7c370 R11: 0000000000000246 R12: 00007fa758df39e0
Mar 03 16:48:05 proxmox kernel: R13: 0000000000000000 R14: 00007fa758df92c8 R15: 00007fa758df92e0
Mar 03 16:48:05 proxmox kernel: BUG: Bad rss-counter state mm:000000001faf7721 type:MM_FILEPAGES val:-1
Mar 03 16:48:13 proxmox kernel: BUG: Bad page map in process pvestatd pte:00000009 pmd:55ccb2067
Mar 03 16:48:13 proxmox kernel: page:00000000043864ad refcount:-2 mapcount:-3 mapping:0000000000000000 index:0x0 pfn:0x0
Mar 03 16:48:13 proxmox kernel: flags: 0x7ffffc0000000()
Mar 03 16:48:13 proxmox kernel: raw: 0007ffffc0000000 dead000000000100 dead000000000122 0000000000000000
Mar 03 16:48:13 proxmox kernel: raw: 0000000000000000 0000000000000000 fffffffefffffffc 0000000000000000
Mar 03 16:48:13 proxmox kernel: page dumped because: bad pte
Mar 03 16:48:13 proxmox kernel: addr:00007f462137b000 vm_flags:08000071 anon_vma:0000000000000000 mapping:ffff8c4c42335158 index:285
Mar 03 16:48:13 proxmox kernel: file:libcrypto.so.1.1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Mar 03 16:48:13 proxmox kernel: CPU: 4 PID: 2811760 Comm: pvestatd Tainted: P B O 5.11.22-1-pve #1
Mar 03 16:48:13 proxmox kernel: Hardware name: Default string Default string/Default string, BIOS 5.12 11/10/2018
Mar 03 16:48:13 proxmox kernel: Call Trace:
Mar 03 16:48:13 proxmox kernel: dump_stack+0x70/0x8b
Mar 03 16:48:13 proxmox kernel: print_bad_pte.cold+0x9b/0xbc
Mar 03 16:48:13 proxmox kernel: unmap_page_range+0x8a8/0xe40
Mar 03 16:48:13 proxmox kernel: unmap_single_vma+0x7f/0xf0
Mar 03 16:48:13 proxmox kernel: unmap_vmas+0x77/0xf0
Mar 03 16:48:13 proxmox kernel: exit_mmap+0xb4/0x200
Mar 03 16:48:13 proxmox kernel: mmput+0x5f/0x140
Mar 03 16:48:13 proxmox kernel: begin_new_exec+0x4e0/0xa30
Mar 03 16:48:13 proxmox kernel: load_elf_binary+0x764/0x17f0
Mar 03 16:48:13 proxmox kernel: ? __kernel_read+0x19d/0x2c0
Mar 03 16:48:13 proxmox kernel: ? aa_get_task_label+0x49/0xd0
Mar 03 16:48:13 proxmox kernel: ? ima_bprm_check+0x89/0xb0
Mar 03 16:48:13 proxmox kernel: bprm_execve+0x27f/0x660
Mar 03 16:48:13 proxmox kernel: do_execveat_common+0x192/0x1c0
Mar 03 16:48:13 proxmox kernel: __x64_sys_execve+0x39/0x50
Mar 03 16:48:13 proxmox kernel: do_syscall_64+0x38/0x90
Mar 03 16:48:13 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 03 16:48:13 proxmox kernel: RIP: 0033:0x7f46218ecfc7
Mar 03 16:48:13 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7f46218ecf9d.
Mar 03 16:48:13 proxmox kernel: RSP: 002b:00007ffe750f8198 EFLAGS: 00000247 ORIG_RAX: 000000000000003b
Mar 03 16:48:13 proxmox kernel: RAX: ffffffffffffffda RBX: 0000565076d7e380 RCX: 00007f46218ecfc7
Mar 03 16:48:13 proxmox kernel: RDX: 0000565076d66e90 RSI: 0000565076dad440 RDI: 00007ffe750f81a0
Mar 03 16:48:13 proxmox kernel: RBP: 00007ffe750f8230 R08: 0000000000000009 R09: 0000565072425e6f
Mar 03 16:48:13 proxmox kernel: R10: fffffffffffff7e6 R11: 0000000000000247 R12: 0000565076dad440
Mar 03 16:48:13 proxmox kernel: R13: 0000565076d66e90 R14: 00007ffe750f81a0 R15: 0000565072425e6b
Mar 03 16:48:13 proxmox kernel: BUG: Bad rss-counter state mm:00000000eda07046 type:MM_FILEPAGES val:-1
Mar 03 16:48:13 proxmox kernel: BUG: Bad page map in process pvestatd pte:00000009 pmd:55ccb2067
Mar 03 16:48:13 proxmox kernel: page:00000000043864ad refcount:-3 mapcount:-4 mapping:0000000000000000 index:0x0 pfn:0x0
Mar 03 16:48:13 proxmox kernel: flags: 0x7ffffc0000000()
Mar 03 16:48:13 proxmox kernel: raw: 0007ffffc0000000 dead000000000100 dead000000000122 0000000000000000
Mar 03 16:48:13 proxmox kernel: raw: 0000000000000000 0000000000000000 fffffffdfffffffb 0000000000000000
Mar 03 16:48:13 proxmox kernel: page dumped because: bad pte
Mar 03 16:48:13 proxmox kernel: addr:00007f462137b000 vm_flags:08000071 anon_vma:0000000000000000 mapping:ffff8c4c42335158 index:285
Mar 03 16:48:13 proxmox kernel: file:libcrypto.so.1.1 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Mar 03 16:48:13 proxmox kernel: CPU: 6 PID: 2811762 Comm: pvestatd Tainted: P B O 5.11.22-1-pve #1
Mar 03 16:48:13 proxmox kernel: Hardware name: Default string Default string/Default string, BIOS 5.12 11/10/2018
Mar 03 16:48:13 proxmox kernel: Call Trace:
Mar 03 16:48:13 proxmox kernel: dump_stack+0x70/0x8b
Mar 03 16:48:13 proxmox kernel: print_bad_pte.cold+0x9b/0xbc
Mar 03 16:48:13 proxmox kernel: unmap_page_range+0x8a8/0xe40
Mar 03 16:48:13 proxmox kernel: unmap_single_vma+0x7f/0xf0
Mar 03 16:48:13 proxmox kernel: unmap_vmas+0x77/0xf0
Mar 03 16:48:13 proxmox kernel: exit_mmap+0xb4/0x200
Mar 03 16:48:13 proxmox kernel: mmput+0x5f/0x140
Mar 03 16:48:13 proxmox kernel: begin_new_exec+0x4e0/0xa30
Mar 03 16:48:13 proxmox kernel: load_elf_binary+0x764/0x17f0
Mar 03 16:48:13 proxmox kernel: ? __kernel_read+0x19d/0x2c0
Mar 03 16:48:13 proxmox kernel: ? aa_get_task_label+0x49/0xd0
Mar 03 16:48:13 proxmox kernel: ? ima_bprm_check+0x89/0xb0
Mar 03 16:48:13 proxmox kernel: bprm_execve+0x27f/0x660
Mar 03 16:48:13 proxmox kernel: do_execveat_common+0x192/0x1c0
Mar 03 16:48:13 proxmox kernel: __x64_sys_execve+0x39/0x50
Mar 03 16:48:13 proxmox kernel: do_syscall_64+0x38/0x90
Mar 03 16:48:13 proxmox kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 03 16:48:13 proxmox kernel: RIP: 0033:0x7f46218ecfc7
Mar 03 16:48:13 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x7f46218ecf9d.
Mar 03 16:48:13 proxmox kernel: RSP: 002b:00007ffe750f8198 EFLAGS: 00000247 ORIG_RAX: 000000000000003b
Mar 03 16:48:13 proxmox kernel: RAX: ffffffffffffffda RBX: 0000565076d63a60 RCX: 00007f46218ecfc7
Mar 03 16:48:13 proxmox kernel: RDX: 0000565076d66e90 RSI: 0000565076d7e820 RDI: 00007ffe750f81a0
Mar 03 16:48:13 proxmox kernel: RBP: 00007ffe750f8230 R08: 0000000000000009 R09: 0000565072425e6f
Mar 03 16:48:13 proxmox kernel: R10: fffffffffffff7e6 R11: 0000000000000247 R12: 0000565076d7e820
Mar 03 16:48:13 proxmox kernel: R13: 0000565076d66e90 R14: 00007ffe750f81a0 R15: 0000565072425e6b
Mar 03 16:48:13 proxmox kernel: BUG: Bad rss-counter state mm:000000001373e557 type:MM_FILEPAGES val:-1
– Reboot –
Mar 03 17:08:17 proxmox kernel: Linux version 5.11.22-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.11.22-2 (Fri, 02 Jul 2021 16:22:45 +0200) ()

Exemple:
failed command: WRITE FPDMA QUEUED
==> Serait-ce une problème de disque dur? (au quel cas le quel?)

J’ai aussi pas mal de proxmox kernel: Code: Unable to access opcode bytes at RIP qui me font penser que ça pourrait être la ram.

Des idées?

Dapolux · Mars 3, 2024, 5:23

Et voici les logs après le reboot:

Extrait des logs a partir de 17h08

Mar 03 16:48:13 proxmox kernel: BUG: Bad rss-counter state mm:000000001373e557 type:MM_FILEPAGES val:-1
– Reboot –
Mar 03 17:08:17 proxmox kernel: Linux version 5.11.22-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.11.22-2 (Fri, 02 Jul 2021 16:22:45 +0200) ()
Mar 03 17:08:17 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.22-1-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt pcie_aspm=off initcall_blacklist=sysfb_init
Mar 03 17:08:17 proxmox kernel: KERNEL supported cpus:
Mar 03 17:08:17 proxmox kernel: Intel GenuineIntel
Mar 03 17:08:17 proxmox kernel: AMD AuthenticAMD
Mar 03 17:08:17 proxmox kernel: Hygon HygonGenuine
Mar 03 17:08:17 proxmox kernel: Centaur CentaurHauls
Mar 03 17:08:17 proxmox kernel: zhaoxin Shanghai
Mar 03 17:08:17 proxmox kernel: Intel Spectre v2 broken microcode detected; disabling Speculation Control
Mar 03 17:08:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x001: ‹ x87 floating point registers ›
Mar 03 17:08:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x002: ‹ SSE registers ›
Mar 03 17:08:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x004: ‹ AVX registers ›
Mar 03 17:08:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x008: ‹ MPX bounds registers ›
Mar 03 17:08:17 proxmox kernel: x86/fpu: Supporting XSAVE feature 0x010: ‹ MPX CSR ›
Mar 03 17:08:17 proxmox kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Mar 03 17:08:17 proxmox kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Mar 03 17:08:17 proxmox kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Mar 03 17:08:17 proxmox kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using ‹ compacted › format.
Mar 03 17:08:17 proxmox kernel: BIOS-provided physical RAM map:
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000076f2bfff] usable
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000076f2c000-0x0000000076f2cfff] ACPI NVS
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000076f2d000-0x0000000076f2dfff] reserved
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000076f2e000-0x000000007eaa8fff] usable
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x000000007eaa9000-0x000000007f6eefff] reserved
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x000000007f6ef000-0x000000007facefff] usable
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x000000007facf000-0x000000007fb5efff] ACPI NVS
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x000000007fb5f000-0x000000007ff5dfff] reserved
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x000000007ff5e000-0x000000007fffefff] type 20
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x000000007ffff000-0x000000007fffffff] usable
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar 03 17:08:17 proxmox kernel: BIOS-e820: [mem 0x0000000100000000-0x0000000673ffffff] usable
Mar 03 17:08:17 proxmox kernel: NX (Execute Disable) protection: active
Mar 03 17:08:17 proxmox kernel: efi: EFI v2.60 by American Megatrends
Mar 03 17:08:17 proxmox kernel: efi: ACPI 2.0=0x7facf000 ACPI=0x7facf000 SMBIOS=0x7febd000 SMBIOS 3.0=0x7febc000 ESRT=0x7d673598 MEMATTR=0x7b7c3018
Mar 03 17:08:17 proxmox kernel: secureboot: Secure boot could not be determined (mode 0)
Mar 03 17:08:17 proxmox kernel: SMBIOS 3.1.1 present.
Mar 03 17:08:17 proxmox kernel: DMI: Default string Default string/Default string, BIOS 5.12 11/10/2018
Mar 03 17:08:17 proxmox kernel: tsc: Detected 1800.000 MHz processor
Mar 03 17:08:17 proxmox kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Mar 03 17:08:17 proxmox kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 03 17:08:17 proxmox kernel: last_pfn = 0x674000 max_arch_pfn = 0x400000000
Mar 03 17:08:17 proxmox kernel: MTRR default type: write-back
Mar 03 17:08:17 proxmox kernel: MTRR fixed ranges enabled:
Mar 03 17:08:17 proxmox kernel: 00000-9FFFF write-back
Mar 03 17:08:17 proxmox kernel: A0000-BFFFF uncachable
Mar 03 17:08:17 proxmox kernel: C0000-FFFFF write-protect
Mar 03 17:08:17 proxmox kernel: MTRR variable ranges enabled:
Mar 03 17:08:17 proxmox kernel: 0 base 00C0000000 mask 7FC0000000 uncachable
Mar 03 17:08:17 proxmox kernel: 1 base 00A0000000 mask 7FE0000000 uncachable
Mar 03 17:08:17 proxmox kernel: 2 base 0090000000 mask 7FF0000000 uncachable
Mar 03 17:08:17 proxmox kernel: 3 base 008C000000 mask 7FFC000000 uncachable
Mar 03 17:08:17 proxmox kernel: 4 base 008A000000 mask 7FFE000000 uncachable
Mar 03 17:08:17 proxmox kernel: 5 base 0089000000 mask 7FFF000000 uncachable
Mar 03 17:08:17 proxmox kernel: 6 base 0088800000 mask 7FFF800000 uncachable
Mar 03 17:08:17 proxmox kernel: 7 base 2000000000 mask 7000000000 uncachable
Mar 03 17:08:17 proxmox kernel: 8 disabled
Mar 03 17:08:17 proxmox kernel: 9 disabled
Mar 03 17:08:17 proxmox kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
Mar 03 17:08:17 proxmox kernel: last_pfn = 0x80000 max_arch_pfn = 0x400000000
Mar 03 17:08:17 proxmox kernel: esrt: Reserving ESRT space from 0x000000007d673598 to 0x000000007d6735d0.
Mar 03 17:08:17 proxmox kernel: e820: update [mem 0x7d673000-0x7d673fff] usable ==> reserved
Mar 03 17:08:17 proxmox kernel: check: Scanning 1 areas for low memory corruption
Mar 03 17:08:17 proxmox kernel: Using GB pages for direct mapping
Mar 03 17:08:17 proxmox kernel: secureboot: Secure boot could not be determined (mode 0)
Mar 03 17:08:17 proxmox kernel: RAMDISK: [mem 0x310f5000-0x34871fff]
Mar 03 17:08:17 proxmox kernel: ACPI: Early table checksum verification disabled
Mar 03 17:08:17 proxmox kernel: ACPI: RSDP 0x000000007FACF000 000024 (v02 ALASKA)
Mar 03 17:08:17 proxmox kernel: ACPI: XSDT 0x000000007FACF0B0 0000E4 (v01 ALASKA A M I 01072009 AMI 00010013)
Mar 03 17:08:17 proxmox kernel: ACPI: FACP 0x000000007FAF8C80 000114 (v06 ALASKA A M I 01072009 AMI 00010013)
Mar 03 17:08:17 proxmox kernel: ACPI: DSDT 0x000000007FACF230 029A4B (v02 ALASKA A M I 01072009 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: FACS 0x000000007FB5EF00 000040
Mar 03 17:08:17 proxmox kernel: ACPI: APIC 0x000000007FAF8D98 0000BC (v03 ALASKA A M I 01072009 AMI 00010013)
Mar 03 17:08:17 proxmox kernel: ACPI: FPDT 0x000000007FAF8E58 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
Mar 03 17:08:17 proxmox kernel: ACPI: FIDT 0x000000007FAF8EA0 00009C (v01 ALASKA A M I 01072009 AMI 00010013)
Mar 03 17:08:17 proxmox kernel: ACPI: MCFG 0x000000007FAF8F40 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FAF8F80 000359 (v01 SataRe SataTabl 00001000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FAF92E0 00A420 (v02 DptfTa DptfTabl 00001000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB03700 001DC6 (v02 GddvDu GddvDumm 00001000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB054C8 003158 (v02 SaSsdt SaSsdt 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: HPET 0x000000007FB08620 000038 (v01 INTEL KBL-ULT 00000001 MSFT 0000005F)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB08658 000902 (v02 INTEL Ther_Rvp 00001000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB08F60 000724 (v02 INTEL xh_kbl-r 00000000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: UEFI 0x000000007FB09688 000042 (v01 ALASKA A M I 00000002 01000013)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB096D0 0017AE (v02 CpuRef CpuSsdt 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: LPIT 0x000000007FB0AE80 000094 (v01 INTEL KBL-ULT 00000000 MSFT 0000005F)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB0AF18 000141 (v02 INTEL HdaDsp 00000000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB0B060 00029F (v02 INTEL sensrhub 00000000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB0B300 003002 (v02 INTEL PtidDevc 00001000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0x000000007FB0E308 00050F (v02 INTEL TbtTypeC 00000000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: DBGP 0x000000007FB0E818 000034 (v01 INTEL 00000002 MSFT 0000005F)
Mar 03 17:08:17 proxmox kernel: ACPI: DBG2 0x000000007FB0E850 000054 (v00 INTEL 00000002 MSFT 0000005F)
Mar 03 17:08:17 proxmox kernel: ACPI: DMAR 0x000000007FB0E8A8 0000A8 (v01 INTEL EDK2 00000001 INTL 00000001)
Mar 03 17:08:17 proxmox kernel: ACPI: ASF! 0x000000007FB0E950 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
Mar 03 17:08:17 proxmox kernel: ACPI: WSMT 0x000000007FB0E9F0 000028 (v01 ALASKA A M I 01072009 AMI 00010013)
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving FACP table memory at [mem 0x7faf8c80-0x7faf8d93]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving DSDT table memory at [mem 0x7facf230-0x7faf8c7a]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving FACS table memory at [mem 0x7fb5ef00-0x7fb5ef3f]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving APIC table memory at [mem 0x7faf8d98-0x7faf8e53]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving FPDT table memory at [mem 0x7faf8e58-0x7faf8e9b]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving FIDT table memory at [mem 0x7faf8ea0-0x7faf8f3b]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving MCFG table memory at [mem 0x7faf8f40-0x7faf8f7b]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7faf8f80-0x7faf92d8]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7faf92e0-0x7fb036ff]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb03700-0x7fb054c5]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb054c8-0x7fb0861f]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving HPET table memory at [mem 0x7fb08620-0x7fb08657]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb08658-0x7fb08f59]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb08f60-0x7fb09683]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving UEFI table memory at [mem 0x7fb09688-0x7fb096c9]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb096d0-0x7fb0ae7d]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving LPIT table memory at [mem 0x7fb0ae80-0x7fb0af13]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb0af18-0x7fb0b058]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb0b060-0x7fb0b2fe]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb0b300-0x7fb0e301]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving SSDT table memory at [mem 0x7fb0e308-0x7fb0e816]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving DBGP table memory at [mem 0x7fb0e818-0x7fb0e84b]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving DBG2 table memory at [mem 0x7fb0e850-0x7fb0e8a3]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving DMAR table memory at [mem 0x7fb0e8a8-0x7fb0e94f]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving ASF! table memory at [mem 0x7fb0e950-0x7fb0e9ef]
Mar 03 17:08:17 proxmox kernel: ACPI: Reserving WSMT table memory at [mem 0x7fb0e9f0-0x7fb0ea17]
Mar 03 17:08:17 proxmox kernel: ACPI: Local APIC address 0xfee00000
Mar 03 17:08:17 proxmox kernel: No NUMA configuration found
Mar 03 17:08:17 proxmox kernel: Faking a node at [mem 0x0000000000000000-0x0000000673ffffff]
Mar 03 17:08:17 proxmox kernel: NODE_DATA(0) allocated [mem 0x673fd6000-0x673ffffff]
Mar 03 17:08:17 proxmox kernel: Zone ranges:
Mar 03 17:08:17 proxmox kernel: DMA [mem 0x0000000000001000-0x0000000000ffffff]
Mar 03 17:08:17 proxmox kernel: DMA32 [mem 0x0000000001000000-0x00000000ffffffff]
Mar 03 17:08:17 proxmox kernel: Normal [mem 0x0000000100000000-0x0000000673ffffff]
Mar 03 17:08:17 proxmox kernel: Device empty
Mar 03 17:08:17 proxmox kernel: Movable zone start for each node
Mar 03 17:08:17 proxmox kernel: Early memory node ranges
Mar 03 17:08:17 proxmox kernel: node 0: [mem 0x0000000000001000-0x0000000000057fff]
Mar 03 17:08:17 proxmox kernel: node 0: [mem 0x0000000000059000-0x000000000009dfff]
Mar 03 17:08:17 proxmox kernel: node 0: [mem 0x0000000000100000-0x0000000076f2bfff]
Mar 03 17:08:17 proxmox kernel: node 0: [mem 0x0000000076f2e000-0x000000007eaa8fff]
Mar 03 17:08:17 proxmox kernel: node 0: [mem 0x000000007f6ef000-0x000000007facefff]
Mar 03 17:08:17 proxmox kernel: node 0: [mem 0x000000007ffff000-0x000000007fffffff]
Mar 03 17:08:17 proxmox kernel: node 0: [mem 0x0000000100000000-0x0000000673ffffff]
Mar 03 17:08:17 proxmox kernel: Initmem setup node 0 [mem 0x0000000000001000-0x0000000673ffffff]
Mar 03 17:08:17 proxmox kernel: On node 0 totalpages: 6237732
Mar 03 17:08:17 proxmox kernel: DMA zone: 64 pages used for memmap
Mar 03 17:08:17 proxmox kernel: DMA zone: 23 pages reserved
Mar 03 17:08:17 proxmox kernel: DMA zone: 3996 pages, LIFO batch:0
Mar 03 17:08:17 proxmox kernel: DMA zone: 28772 pages in unavailable ranges
Mar 03 17:08:17 proxmox kernel: DMA32 zone: 8059 pages used for memmap
Mar 03 17:08:17 proxmox kernel: DMA32 zone: 515720 pages, LIFO batch:63
Mar 03 17:08:17 proxmox kernel: DMA32 zone: 4472 pages in unavailable ranges
Mar 03 17:08:17 proxmox kernel: Normal zone: 89344 pages used for memmap
Mar 03 17:08:17 proxmox kernel: Normal zone: 5718016 pages, LIFO batch:63
Mar 03 17:08:17 proxmox kernel: Normal zone: 16384 pages in unavailable ranges
Mar 03 17:08:17 proxmox kernel: Reserving Intel graphics memory at [mem 0x89000000-0x8affffff]
Mar 03 17:08:17 proxmox kernel: ACPI: PM-Timer IO Port: 0x1808
Mar 03 17:08:17 proxmox kernel: ACPI: Local APIC address 0xfee00000
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Mar 03 17:08:17 proxmox kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
Mar 03 17:08:17 proxmox kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Mar 03 17:08:17 proxmox kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Mar 03 17:08:17 proxmox kernel: ACPI: IRQ0 used by override.
Mar 03 17:08:17 proxmox kernel: ACPI: IRQ9 used by override.
Mar 03 17:08:17 proxmox kernel: Using ACPI (MADT) for SMP configuration information
Mar 03 17:08:17 proxmox kernel: ACPI: HPET id: 0x8086a201 base: 0xfed00000
Mar 03 17:08:17 proxmox kernel: TSC deadline timer available
Mar 03 17:08:17 proxmox kernel: smpboot: Allowing 8 CPUs, 0 hotplug CPUs
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x0009e000-0x000fffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x76f2c000-0x76f2cfff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x76f2d000-0x76f2dfff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x7d673000-0x7d673fff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x7eaa9000-0x7f6eefff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x7facf000-0x7fb5efff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x7fb5f000-0x7ff5dfff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x7ff5e000-0x7fffefff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x80000000-0x8affffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0x8b000000-0xdfffffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xe0000000-0xefffffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xf0000000-0xfdffffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfe000000-0xfe010fff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfe011000-0xfebfffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfed00000-0xfed00fff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfed01000-0xfedfffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Mar 03 17:08:17 proxmox kernel: PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]
Mar 03 17:08:17 proxmox kernel: [mem 0x8b000000-0xdfffffff] available for PCI devices
Mar 03 17:08:17 proxmox kernel: Booting paravirtualized kernel on bare hardware
Mar 03 17:08:17 proxmox kernel: clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
Mar 03 17:08:17 proxmox kernel: setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
Mar 03 17:08:17 proxmox kernel: percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u262144
Mar 03 17:08:17 proxmox kernel: pcpu-alloc: s192512 r8192 d28672 u262144 alloc=1*2097152
Mar 03 17:08:17 proxmox kernel: pcpu-alloc: [0] 0 1 2 3 4 5 6 7
Mar 03 17:08:17 proxmox kernel: Built 1 zonelists, mobility grouping on. Total pages: 6140242
Mar 03 17:08:17 proxmox kernel: Policy zone: Normal
Mar 03 17:08:17 proxmox kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.11.22-1-pve root=/dev/mapper/pve-root ro quiet intel_iommu=on iommu=pt pcie_aspm=off initcall_blacklist=sysfb_init
Mar 03 17:08:17 proxmox kernel: DMAR: IOMMU enabled
Mar 03 17:08:17 proxmox kernel: PCIe ASPM is disabled
Mar 03 17:08:17 proxmox kernel: blacklisting initcall sysfb_init
Mar 03 17:08:17 proxmox kernel: Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
Mar 03 17:08:17 proxmox kernel: Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
Mar 03 17:08:17 proxmox kernel: mem auto-init: stack:off, heap alloc:on, heap free:off
Mar 03 17:08:17 proxmox kernel: Memory: 24304688K/24950928K available (16393K kernel code, 3464K rwdata, 9924K rodata, 2664K init, 6012K bss, 645980K reserved, 0K cma-reserved)
Mar 03 17:08:17 proxmox kernel: random: get_random_u64 called from __kmem_cache_create+0x29/0x550 with crng_init=0
Mar 03 17:08:17 proxmox kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
Mar 03 17:08:17 proxmox kernel: Kernel/User page tables isolation: enabled
Mar 03 17:08:17 proxmox kernel: ftrace: allocating 47238 entries in 185 pages
Mar 03 17:08:17 proxmox kernel: ftrace: allocated 185 pages with 5 groups
Mar 03 17:08:17 proxmox kernel: rcu: Hierarchical RCU implementation.
Mar 03 17:08:17 proxmox kernel: rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
Mar 03 17:08:17 proxmox kernel: Rude variant of Tasks RCU enabled.
Mar 03 17:08:17 proxmox kernel: Tracing variant of Tasks RCU enabled.
Mar 03 17:08:17 proxmox kernel: rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Mar 03 17:08:17 proxmox kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
Mar 03 17:08:17 proxmox kernel: NR_IRQS: 524544, nr_irqs: 2048, preallocated irqs: 16
Mar 03 17:08:17 proxmox kernel: random: crng done (trusting CPU’s manufacturer)
Mar 03 17:08:17 proxmox kernel: Console: colour dummy device 80x25
Mar 03 17:08:17 proxmox kernel: printk: console [tty0] enabled
Mar 03 17:08:17 proxmox kernel: ACPI: Core revision 20201113
Mar 03 17:08:17 proxmox kernel: clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns
Mar 03 17:08:17 proxmox kernel: APIC: Switch to symmetric I/O mode setup
Mar 03 17:08:17 proxmox kernel: DMAR: Host address width 39
Mar 03 17:08:17 proxmox kernel: DMAR: DRHD base: 0x000000fed90000 flags: 0x0
Mar 03 17:08:17 proxmox kernel: DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e
Mar 03 17:08:17 proxmox kernel: DMAR: DRHD base: 0x000000fed91000 flags: 0x1
Mar 03 17:08:17 proxmox kernel: DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da
Mar 03 17:08:17 proxmox kernel: DMAR: RMRR base: 0x0000007f044000 end: 0x0000007f063fff
Mar 03 17:08:17 proxmox kernel: DMAR: RMRR base: 0x00000088800000 end: 0x0000008affffff
Mar 03 17:08:17 proxmox kernel: DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
Mar 03 17:08:17 proxmox kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000
Mar 03 17:08:17 proxmox kernel: DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping.
Mar 03 17:08:17 proxmox kernel: DMAR-IR: Enabled IRQ remapping in x2apic mode
Mar 03 17:08:17 proxmox kernel: x2apic enabled
Mar 03 17:08:17 proxmox kernel: Switched APIC routing to cluster x2apic.
Mar 03 17:08:17 proxmox kernel: …TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Mar 03 17:08:17 proxmox kernel: clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x19f2297dd97, max_idle_ns: 440795236593 ns
Mar 03 17:08:17 proxmox kernel: Calibrating delay loop (skipped), value calculated using timer frequency… 3600.00 BogoMIPS (lpj=7200000)
Mar 03 17:08:17 proxmox kernel: pid_max: default: 32768 minimum: 301
Mar 03 17:08:17 proxmox kernel: LSM: Security Framework initializing
Mar 03 17:08:17 proxmox kernel: Yama: becoming mindful.
Mar 03 17:08:17 proxmox kernel: AppArmor: AppArmor initialized
Mar 03 17:08:17 proxmox kernel: Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Mar 03 17:08:17 proxmox kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Mar 03 17:08:17 proxmox kernel: mce: CPU0: Thermal monitoring enabled (TM1)
Mar 03 17:08:17 proxmox kernel: process: using mwait in idle threads
Mar 03 17:08:17 proxmox kernel: Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8
Mar 03 17:08:17 proxmox kernel: Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4
Mar 03 17:08:17 proxmox kernel: Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Mar 03 17:08:17 proxmox kernel: Spectre V2 : Mitigation: Full generic retpoline
Mar 03 17:08:17 proxmox kernel: Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Mar 03 17:08:17 proxmox kernel: Speculative Store Bypass: Vulnerable
Mar 03 17:08:17 proxmox kernel: SRBDS: Vulnerable: No microcode
Mar 03 17:08:17 proxmox kernel: MDS: Vulnerable: Clear CPU buffers attempted, no microcode
Mar 03 17:08:17 proxmox kernel: Freeing SMP alternatives memory: 40K
Mar 03 17:08:17 proxmox kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1934
Mar 03 17:08:17 proxmox kernel: smpboot: CPU0: Intel(R) Core™ i5-8250U CPU @ 1.60GHz (family: 0x6, model: 0x8e, stepping: 0xa)
Mar 03 17:08:17 proxmox kernel: Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver.
Mar 03 17:08:17 proxmox kernel: … version: 4
Mar 03 17:08:17 proxmox kernel: … bit width: 48
Mar 03 17:08:17 proxmox kernel: … generic registers: 4
Mar 03 17:08:17 proxmox kernel: … value mask: 0000ffffffffffff
Mar 03 17:08:17 proxmox kernel: … max period: 00007fffffffffff
Mar 03 17:08:17 proxmox kernel: … fixed-purpose events: 3
Mar 03 17:08:17 proxmox kernel: … event mask: 000000070000000f
Mar 03 17:08:17 proxmox kernel: rcu: Hierarchical SRCU implementation.
Mar 03 17:08:17 proxmox kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
Mar 03 17:08:17 proxmox kernel: smp: Bringing up secondary CPUs …
Mar 03 17:08:17 proxmox kernel: x86: Booting SMP configuration:
Mar 03 17:08:17 proxmox kernel: … node #0, CPUs: #1 #2 #3 #4
Mar 03 17:08:17 proxmox kernel: MDS CPU bug present and SMT on, data leak possible. See MDS - Microarchitectural Data Sampling — The Linux Kernel documentation for more details.
Mar 03 17:08:17 proxmox kernel: #5 #6 #7
Mar 03 17:08:17 proxmox kernel: smp: Brought up 1 node, 8 CPUs
Mar 03 17:08:17 proxmox kernel: smpboot: Max logical packages: 1
Mar 03 17:08:17 proxmox kernel: smpboot: Total of 8 processors activated (28800.00 BogoMIPS)
Mar 03 17:08:17 proxmox kernel: devtmpfs: initialized
Mar 03 17:08:17 proxmox kernel: x86/mm: Memory block size: 128MB
Mar 03 17:08:17 proxmox kernel: PM: Registering ACPI NVS region [mem 0x76f2c000-0x76f2cfff] (4096 bytes)
Mar 03 17:08:17 proxmox kernel: PM: Registering ACPI NVS region [mem 0x7facf000-0x7fb5efff] (589824 bytes)
Mar 03 17:08:17 proxmox kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Mar 03 17:08:17 proxmox kernel: futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
Mar 03 17:08:17 proxmox kernel: pinctrl core: initialized pinctrl subsystem
Mar 03 17:08:17 proxmox kernel: PM: RTC time: 16:08:06, date: 2024-03-03
Mar 03 17:08:17 proxmox kernel: NET: Registered protocol family 16
Mar 03 17:08:17 proxmox kernel: DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations
Mar 03 17:08:17 proxmox kernel: DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Mar 03 17:08:17 proxmox kernel: DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Mar 03 17:08:17 proxmox kernel: audit: initializing netlink subsys (disabled)
Mar 03 17:08:17 proxmox kernel: audit: type=2000 audit(1709482086.044:1): state=initialized audit_enabled=0 res=1
Mar 03 17:08:17 proxmox kernel: thermal_sys: Registered thermal governor ‹ fair_share ›
Mar 03 17:08:17 proxmox kernel: thermal_sys: Registered thermal governor ‹ bang_bang ›
Mar 03 17:08:17 proxmox kernel: thermal_sys: Registered thermal governor ‹ step_wise ›
Mar 03 17:08:17 proxmox kernel: thermal_sys: Registered thermal governor ‹ user_space ›
Mar 03 17:08:17 proxmox kernel: thermal_sys: Registered thermal governor ‹ power_allocator ›
Mar 03 17:08:17 proxmox kernel: EISA bus registered
Mar 03 17:08:17 proxmox kernel: cpuidle: using governor ladder
Mar 03 17:08:17 proxmox kernel: cpuidle: using governor menu
Mar 03 17:08:17 proxmox kernel: ACPI: bus type PCI registered
Mar 03 17:08:17 proxmox kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Mar 03 17:08:17 proxmox kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
Mar 03 17:08:17 proxmox kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
Mar 03 17:08:17 proxmox kernel: PCI: Using configuration type 1 for base access
Mar 03 17:08:17 proxmox kernel: ENERGY_PERF_BIAS: Set to ‹ normal ›, was ‹ performance ›
Mar 03 17:08:17 proxmox kernel: Kprobes globally optimized
Mar 03 17:08:17 proxmox kernel: HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
Mar 03 17:08:17 proxmox kernel: HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
Mar 03 17:08:17 proxmox kernel: ACPI: Added _OSI(Module Device)
Mar 03 17:08:17 proxmox kernel: ACPI: Added _OSI(Processor Device)
Mar 03 17:08:17 proxmox kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Mar 03 17:08:17 proxmox kernel: ACPI: Added _OSI(Processor Aggregator Device)
Mar 03 17:08:17 proxmox kernel: ACPI: Added _OSI(Linux-Dell-Video)
Mar 03 17:08:17 proxmox kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Mar 03 17:08:17 proxmox kernel: ACPI: Added OSI(Linux-HPI-Hybrid-Graphics)
Mar 03 17:08:17 proxmox kernel: ACPI: 12 ACPI AML tables successfully acquired and loaded
Mar 03 17:08:17 proxmox kernel: ACPI: Dynamic OEM Table Load:
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0xFFFF8F9D40CBC000 00058B (v02 PmRef Cpu0Ist 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: _PR.PR00: _OSC native thermal LVT Acked
Mar 03 17:08:17 proxmox kernel: ACPI: Dynamic OEM Table Load:
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0xFFFF8F9D412A9400 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: Dynamic OEM Table Load:
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0xFFFF8F9D4137F780 0000BA (v02 PmRef Cpu0Hwp 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: Dynamic OEM Table Load:
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0xFFFF8F9D40CB8800 000628 (v02 PmRef HwpLvt 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: Dynamic OEM Table Load:
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0xFFFF8F9D4125D000 000D14 (v02 PmRef ApIst 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: Dynamic OEM Table Load:
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0xFFFF8F9D412AD800 000317 (v02 PmRef ApHwp 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: Dynamic OEM Table Load:
Mar 03 17:08:17 proxmox kernel: ACPI: SSDT 0xFFFF8F9D412AF400 00030A (v02 PmRef ApCst 00003000 INTL 20160422)
Mar 03 17:08:17 proxmox kernel: ACPI: Interpreter enabled
Mar 03 17:08:17 proxmox kernel: ACPI: (supports S0 S3 S4 S5)
Mar 03 17:08:17 proxmox kernel: ACPI: Using IOAPIC for interrupt routing
Mar 03 17:08:17 proxmox kernel: PCI: Using host bridge windows from ACPI; if necessary, use « pci=nocrs » and report a bug
Mar 03 17:08:17 proxmox kernel: ACPI: Enabled 6 GPEs in block 00 to 7F
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
Mar 03 17:08:17 proxmox kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig Segments MSI HPX-Type3]
Mar 03 17:08:17 proxmox kernel: acpi PNP0A08:00: _OSC: not requesting OS control; OS requires [ExtendedConfig ASPM ClockPM MSI]
Mar 03 17:08:17 proxmox kernel: PCI host bridge to bus 0000:00
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: root bus resource [bus 00-fe]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000fffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: root bus resource [mem 0x8b000000-0xdfffffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: root bus resource [mem 0x2000000000-0x2fffffffff window]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:00.0: [8086:5914] type 00 class 0x060000
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: [8086:5917] type 00 class 0x030000
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: reg 0x10: [mem 0x2ffe000000-0x2ffeffffff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: reg 0x18: [mem 0x2fe0000000-0x2fefffffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: reg 0x20: [io 0xf000-0xf03f]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:04.0: [8086:1903] type 00 class 0x118000
Mar 03 17:08:17 proxmox kernel: pci 0000:00:04.0: reg 0x10: [mem 0x2fff020000-0x2fff027fff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:08.0: [8086:1911] type 00 class 0x088000
Mar 03 17:08:17 proxmox kernel: pci 0000:00:08.0: reg 0x10: [mem 0x2fff02f000-0x2fff02ffff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330
Mar 03 17:08:17 proxmox kernel: pci 0000:00:14.0: reg 0x10: [mem 0x2fff010000-0x2fff01ffff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Mar 03 17:08:17 proxmox kernel: pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000
Mar 03 17:08:17 proxmox kernel: pci 0000:00:14.2: reg 0x10: [mem 0x2fff02e000-0x2fff02efff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000
Mar 03 17:08:17 proxmox kernel: pci 0000:00:16.0: reg 0x10: [mem 0x2fff02d000-0x2fff02dfff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:16.0: PME# supported from D3hot
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: [8086:9d03] type 00 class 0x010601
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: reg 0x10: [mem 0xdff04000-0xdff05fff]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: reg 0x14: [mem 0xdff07000-0xdff070ff]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: reg 0x18: [io 0xf090-0xf097]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: reg 0x1c: [io 0xf080-0xf083]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: reg 0x20: [io 0xf060-0xf07f]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: reg 0x24: [mem 0xdff06000-0xdff067ff]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: PME# supported from D3hot
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: [8086:9d13] type 01 class 0x060400
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: Intel SPT PCH root port ACS workaround enabled
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: [8086:9d14] type 01 class 0x060400
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: Intel SPT PCH root port ACS workaround enabled
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: [8086:9d18] type 01 class 0x060400
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: Intel SPT PCH root port ACS workaround enabled
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.0: [8086:9d4e] type 00 class 0x060100
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.2: reg 0x10: [mem 0xdff00000-0xdff03fff]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040300
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.3: reg 0x10: [mem 0x2fff028000-0x2fff02bfff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.3: reg 0x20: [mem 0x2fff000000-0x2fff00ffff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.3: PME# supported from D3hot D3cold
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.4: reg 0x10: [mem 0x2fff02c000-0x2fff02c0ff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.4: reg 0x20: [io 0xf040-0xf05f]
Mar 03 17:08:17 proxmox kernel: pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
Mar 03 17:08:17 proxmox kernel: pci 0000:01:00.0: reg 0x10: [io 0xe000-0xe0ff]
Mar 03 17:08:17 proxmox kernel: pci 0000:01:00.0: reg 0x18: [mem 0x2ff0204000-0x2ff0204fff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:01:00.0: reg 0x20: [mem 0x2ff0200000-0x2ff0203fff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:01:00.0: supports D1 D2
Mar 03 17:08:17 proxmox kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: bridge window [io 0xe000-0xefff]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: bridge window [mem 0x2ff0200000-0x2ff02fffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:02:00.0: [168c:0034] type 00 class 0x028000
Mar 03 17:08:17 proxmox kernel: pci 0000:02:00.0: reg 0x10: [mem 0xdfe00000-0xdfe7ffff 64bit]
Mar 03 17:08:17 proxmox kernel: pci 0000:02:00.0: reg 0x30: [mem 0xdfe80000-0xdfe8ffff pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:02:00.0: supports D1
Mar 03 17:08:17 proxmox kernel: pci 0000:02:00.0: PME# supported from D0 D1 D3hot
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: PCI bridge to [bus 02]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: bridge window [mem 0xdfe00000-0xdfefffff]
Mar 03 17:08:17 proxmox kernel: pci 0000:03:00.0: [1ac1:089a] type 00 class 0x0000ff
Mar 03 17:08:17 proxmox kernel: pci 0000:03:00.0: reg 0x10: [mem 0x2ff0100000-0x2ff0103fff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:03:00.0: reg 0x18: [mem 0x2ff0000000-0x2ff00fffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: PCI bridge to [bus 03]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: bridge window [mem 0x2ff0000000-0x2ff01fffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 03 17:08:17 proxmox kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15)
Mar 03 17:08:17 proxmox kernel: iommu: Default domain type: Passthrough (set via kernel command line)
Mar 03 17:08:17 proxmox kernel: SCSI subsystem initialized
Mar 03 17:08:17 proxmox kernel: libata version 3.00 loaded.
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: vgaarb: bridge control possible
Mar 03 17:08:17 proxmox kernel: vgaarb: loaded
Mar 03 17:08:17 proxmox kernel: ACPI: bus type USB registered
Mar 03 17:08:17 proxmox kernel: usbcore: registered new interface driver usbfs
Mar 03 17:08:17 proxmox kernel: usbcore: registered new interface driver hub
Mar 03 17:08:17 proxmox kernel: usbcore: registered new device driver usb
Mar 03 17:08:17 proxmox kernel: pps_core: LinuxPPS API ver. 1 registered
Mar 03 17:08:17 proxmox kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti giometti@linux.it
Mar 03 17:08:17 proxmox kernel: PTP clock support registered
Mar 03 17:08:17 proxmox kernel: EDAC MC: Ver: 3.0.0
Mar 03 17:08:17 proxmox kernel: Registered efivars operations
Mar 03 17:08:17 proxmox kernel: NetLabel: Initializing
Mar 03 17:08:17 proxmox kernel: NetLabel: domain hash size = 128
Mar 03 17:08:17 proxmox kernel: NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO
Mar 03 17:08:17 proxmox kernel: NetLabel: unlabeled traffic allowed by default
Mar 03 17:08:17 proxmox kernel: PCI: Using ACPI for IRQ routing
Mar 03 17:08:17 proxmox kernel: PCI: pci_cache_line_size set to 64 bytes
Mar 03 17:08:17 proxmox kernel: e820: reserve RAM buffer [mem 0x00058000-0x0005ffff]
Mar 03 17:08:17 proxmox kernel: e820: reserve RAM buffer [mem 0x0009e000-0x0009ffff]
Mar 03 17:08:17 proxmox kernel: e820: reserve RAM buffer [mem 0x76f2c000-0x77ffffff]
Mar 03 17:08:17 proxmox kernel: e820: reserve RAM buffer [mem 0x7d673000-0x7fffffff]
Mar 03 17:08:17 proxmox kernel: e820: reserve RAM buffer [mem 0x7eaa9000-0x7fffffff]
Mar 03 17:08:17 proxmox kernel: e820: reserve RAM buffer [mem 0x7facf000-0x7fffffff]
Mar 03 17:08:17 proxmox kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Mar 03 17:08:17 proxmox kernel: hpet0: 8 comparators, 64-bit 24.000000 MHz counter
Mar 03 17:08:17 proxmox kernel: clocksource: Switched to clocksource tsc-early
Mar 03 17:08:17 proxmox kernel: VFS: Disk quotas dquot_6.6.0
Mar 03 17:08:17 proxmox kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Mar 03 17:08:17 proxmox kernel: AppArmor: AppArmor Filesystem Enabled
Mar 03 17:08:17 proxmox kernel: pnp: PnP ACPI init
Mar 03 17:08:17 proxmox kernel: system 00:00: [io 0x0a00-0x0a2f] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:00: [io 0x0a30-0x0a3f] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:00: [io 0x0a40-0x0a4f] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 03 17:08:17 proxmox kernel: system 00:01: [io 0x0680-0x069f] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:01: [io 0xffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:01: [io 0xffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:01: [io 0xffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:01: [io 0x1800-0x18fe] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:01: [io 0x164e-0x164f] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 03 17:08:17 proxmox kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Mar 03 17:08:17 proxmox kernel: system 00:03: [io 0x1854-0x1857] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xfed10000-0xfed17fff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xfed18000-0xfed18fff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xfed19000-0xfed19fff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xe0000000-0xefffffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xfed20000-0xfed3ffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xfed90000-0xfed93fff] could not be reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xfed45000-0xfed8ffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xff000000-0xffffffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xfee00000-0xfeefffff] could not be reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: [mem 0xdffe0000-0xdfffffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 03 17:08:17 proxmox kernel: system 00:05: [mem 0xfd000000-0xfdabffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:05: [mem 0xfdad0000-0xfdadffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:05: [mem 0xfdb00000-0xfdffffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:05: [mem 0xfe000000-0xfe01ffff] could not be reserved
Mar 03 17:08:17 proxmox kernel: system 00:05: [mem 0xfe036000-0xfe03bfff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:05: [mem 0xfe03d000-0xfe3fffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:05: [mem 0xfe410000-0xfe7fffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 03 17:08:17 proxmox kernel: system 00:06: [io 0xff00-0xfffe] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 03 17:08:17 proxmox kernel: system 00:07: [mem 0xfdaf0000-0xfdafffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:07: [mem 0xfdae0000-0xfdaeffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:07: [mem 0xfdac0000-0xfdacffff] has been reserved
Mar 03 17:08:17 proxmox kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 03 17:08:17 proxmox kernel: pnp: PnP ACPI: found 8 devices
Mar 03 17:08:17 proxmox kernel: clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Mar 03 17:08:17 proxmox kernel: NET: Registered protocol family 2
Mar 03 17:08:17 proxmox kernel: IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Mar 03 17:08:17 proxmox kernel: tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
Mar 03 17:08:17 proxmox kernel: TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
Mar 03 17:08:17 proxmox kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
Mar 03 17:08:17 proxmox kernel: TCP: Hash tables configured (established 262144 bind 65536)
Mar 03 17:08:17 proxmox kernel: MPTCP token hash table entries: 32768 (order: 7, 786432 bytes, linear)
Mar 03 17:08:17 proxmox kernel: UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
Mar 03 17:08:17 proxmox kernel: UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
Mar 03 17:08:17 proxmox kernel: NET: Registered protocol family 1
Mar 03 17:08:17 proxmox kernel: NET: Registered protocol family 44
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: PCI bridge to [bus 01]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: bridge window [io 0xe000-0xefff]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: bridge window [mem 0x2ff0200000-0x2ff02fffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: PCI bridge to [bus 02]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: bridge window [mem 0xdfe00000-0xdfefffff]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: PCI bridge to [bus 03]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: bridge window [mem 0x2ff0000000-0x2ff01fffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000fffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: resource 7 [mem 0x8b000000-0xdfffffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: resource 8 [mem 0xfd000000-0xfe7fffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:00: resource 9 [mem 0x2000000000-0x2fffffffff window]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:01: resource 2 [mem 0x2ff0200000-0x2ff02fffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:02: resource 1 [mem 0xdfe00000-0xdfefffff]
Mar 03 17:08:17 proxmox kernel: pci_bus 0000:03: resource 2 [mem 0x2ff0000000-0x2ff01fffff 64bit pref]
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Mar 03 17:08:17 proxmox kernel: PCI: CLS 64 bytes, default 64
Mar 03 17:08:17 proxmox kernel: Trying to unpack rootfs image as initramfs…
Mar 03 17:08:17 proxmox kernel: Freeing initrd memory: 56820K
Mar 03 17:08:17 proxmox kernel: DMAR: No ATSR found
Mar 03 17:08:17 proxmox kernel: DMAR: dmar0: Using Queued invalidation
Mar 03 17:08:17 proxmox kernel: DMAR: dmar1: Using Queued invalidation
Mar 03 17:08:17 proxmox kernel: pci 0000:00:00.0: Adding to iommu group 0
Mar 03 17:08:17 proxmox kernel: pci 0000:00:02.0: Adding to iommu group 1
Mar 03 17:08:17 proxmox kernel: pci 0000:00:04.0: Adding to iommu group 2
Mar 03 17:08:17 proxmox kernel: pci 0000:00:08.0: Adding to iommu group 3
Mar 03 17:08:17 proxmox kernel: pci 0000:00:14.0: Adding to iommu group 4
Mar 03 17:08:17 proxmox kernel: pci 0000:00:14.2: Adding to iommu group 4
Mar 03 17:08:17 proxmox kernel: pci 0000:00:16.0: Adding to iommu group 5
Mar 03 17:08:17 proxmox kernel: pci 0000:00:17.0: Adding to iommu group 6
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.0: Adding to iommu group 7
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1c.4: Adding to iommu group 8
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1d.0: Adding to iommu group 9
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.0: Adding to iommu group 10
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.2: Adding to iommu group 10
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.3: Adding to iommu group 10
Mar 03 17:08:17 proxmox kernel: pci 0000:00:1f.4: Adding to iommu group 10
Mar 03 17:08:17 proxmox kernel: pci 0000:01:00.0: Adding to iommu group 11
Mar 03 17:08:17 proxmox kernel: pci 0000:02:00.0: Adding to iommu group 12
Mar 03 17:08:17 proxmox kernel: pci 0000:03:00.0: Adding to iommu group 13
Mar 03 17:08:17 proxmox kernel: DMAR: Intel(R) Virtualization Technology for Directed I/O
Mar 03 17:08:17 proxmox kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Mar 03 17:08:17 proxmox kernel: software IO TLB: mapped [mem 0x00000000777c3000-0x000000007b7c3000] (64MB)
Mar 03 17:08:17 proxmox kernel: check: Scanning for low memory corruption every 60 seconds
Mar 03 17:08:17 proxmox kernel: initcall sysfb_init blacklisted
Mar 03 17:08:17 proxmox kernel: Initialise system trusted keyrings
Mar 03 17:08:17 proxmox kernel: Key type blacklist registered
Mar 03 17:08:17 proxmox kernel: workingset: timestamp_bits=36 max_order=23 bucket_order=0
Mar 03 17:08:17 proxmox kernel: zbud: loaded
Mar 03 17:08:17 proxmox kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Mar 03 17:08:17 proxmox kernel: fuse: init (API version 7.33)
Mar 03 17:08:17 proxmox kernel: integrity: Platform Keyring initialized
Mar 03 17:08:17 proxmox kernel: Key type asymmetric registered
Mar 03 17:08:17 proxmox kernel: Asymmetric key parser ‹ x509 › registered
Mar 03 17:08:17 proxmox kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
Mar 03 17:08:17 proxmox kernel: io scheduler mq-deadline registered
Mar 03 17:08:17 proxmox kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Mar 03 17:08:17 proxmox kernel: intel_idle: MWAIT substates: 0x11142120
Mar 03 17:08:17 proxmox kernel: intel_idle: v0.5.1 model 0x8E
Mar 03 17:08:17 proxmox kernel: intel_idle: Local APIC timer is reliable in all C-states
Mar 03 17:08:17 proxmox kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
Mar 03 17:08:17 proxmox kernel: ACPI: Sleep Button [SLPB]
Mar 03 17:08:17 proxmox kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Mar 03 17:08:17 proxmox kernel: ACPI: Power Button [PWRB]
Mar 03 17:08:17 proxmox kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Mar 03 17:08:17 proxmox kernel: ACPI: Power Button [PWRF]
Mar 03 17:08:17 proxmox kernel: smpboot: Estimated ratio of average max frequency by base frequency (times 1024): 1934
Mar 03 17:08:17 proxmox kernel: [Firmware Bug]: No valid trip found
Mar 03 17:08:17 proxmox kernel: [Firmware Bug]: No valid trip found
Mar 03 17:08:17 proxmox kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Mar 03 17:08:17 proxmox kernel: Linux agpgart interface v0.103
Mar 03 17:08:17 proxmox kernel: loop: module loaded
Mar 03 17:08:17 proxmox kernel: libphy: Fixed MDIO Bus: probed
Mar 03 17:08:17 proxmox kernel: tun: Universal TUN/TAP device driver, 1.6
Mar 03 17:08:17 proxmox kernel: PPP generic driver version 2.4.2
Mar 03 17:08:17 proxmox kernel: i8042: PNP: No PS/2 controller found.
Mar 03 17:08:17 proxmox kernel: mousedev: PS/2 mouse device common for all mice
Mar 03 17:08:17 proxmox kernel: rtc_cmos 00:02: RTC can wake from S4
Mar 03 17:08:17 proxmox kernel: rtc_cmos 00:02: registered as rtc0
Mar 03 17:08:17 proxmox kernel: rtc_cmos 00:02: setting system clock to 2024-03-03T16:08:11 UTC (1709482091)
Mar 03 17:08:17 proxmox kernel: rtc_cmos 00:02: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Mar 03 17:08:17 proxmox kernel: i2c /dev entries driver
Mar 03 17:08:17 proxmox kernel: device-mapper: uevent: version 1.0.3
Mar 03 17:08:17 proxmox kernel: device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Probing EISA bus 0
Mar 03 17:08:17 proxmox kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Mar 03 17:08:17 proxmox kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Mar 03 17:08:17 proxmox kernel: platform eisa.0: EISA: Detected 0 cards
Mar 03 17:08:17 proxmox kernel: intel_pstate: Intel P-state driver initializing
Mar 03 17:08:17 proxmox kernel: intel_pstate: HWP enabled
Mar 03 17:08:17 proxmox kernel: ledtrig-cpu: registered to indicate activity on CPUs
Mar 03 17:08:17 proxmox kernel: EFI Variables Facility v0.08 2004-May-17
Mar 03 17:08:17 proxmox kernel: intel_pmc_core INT33A1:00: initialized
Mar 03 17:08:17 proxmox kernel: drop_monitor: Initializing network drop monitor service
Mar 03 17:08:17 proxmox kernel: NET: Registered protocol family 10
Mar 03 17:08:17 proxmox kernel: Segment Routing with IPv6
Mar 03 17:08:17 proxmox kernel: NET: Registered protocol family 17
Mar 03 17:08:17 proxmox kernel: Bridge firewalling registered
Mar 03 17:08:17 proxmox kernel: Key type dns_resolver registered
Mar 03 17:08:17 proxmox kernel: microcode: sig=0x806ea, pf=0x80, revision=0x7c
Mar 03 17:08:17 proxmox kernel: microcode: Microcode Update Driver: v2.2.
Mar 03 17:08:17 proxmox kernel: IPI shorthand broadcast: enabled
Mar 03 17:08:17 proxmox kernel: sched_clock: Marking stable (4393950176, 734687)->(4404836869, -10152006)
Mar 03 17:08:17 proxmox kernel: registered taskstats version 1
Mar 03 17:08:17 proxmox kernel: Loading compiled-in X.509 certificates
Mar 03 17:08:17 proxmox kernel: zswap: loaded using pool lzo/zbud
Mar 03 17:08:17 proxmox kernel: Key type ._fscrypt registered
Mar 03 17:08:17 proxmox kernel: Key type .fscrypt registered
Mar 03 17:08:17 proxmox kernel: Key type fscrypt-provisioning registered
Mar 03 17:08:17 proxmox kernel: Key type encrypted registered
Mar 03 17:08:17 proxmox kernel: AppArmor: AppArmor sha1 policy hashing enabled
Mar 03 17:08:17 proxmox kernel: ima: No TPM chip found, activating TPM-bypass!
Mar 03 17:08:17 proxmox kernel: ima: Allocated hash algorithm: sha1
Mar 03 17:08:17 proxmox kernel: ima: No architecture policies found
Mar 03 17:08:17 proxmox kernel: evm: Initialising EVM extended attributes:
Mar 03 17:08:17 proxmox kernel: evm: security.selinux
Mar 03 17:08:17 proxmox kernel: evm: security.SMACK64
Mar 03 17:08:17 proxmox kernel: evm: security.SMACK64EXEC
Mar 03 17:08:17 proxmox kernel: evm: security.SMACK64TRANSMUTE
Mar 03 17:08:17 proxmox kernel: evm: security.SMACK64MMAP
Mar 03 17:08:17 proxmox kernel: evm: security.apparmor
Mar 03 17:08:17 proxmox kernel: evm: security.ima
Mar 03 17:08:17 proxmox kernel: evm: security.capability
Mar 03 17:08:17 proxmox kernel: evm: HMAC attrs: 0x1
Mar 03 17:08:17 proxmox kernel: PM: Magic number: 0:966:134
Mar 03 17:08:17 proxmox kernel: acpi INT3472:00: hash matches
Mar 03 17:08:17 proxmox kernel: acpi PNP0C02:06: hash matches
Mar 03 17:08:17 proxmox kernel: acpi device:09: hash matches
Mar 03 17:08:17 proxmox kernel: RAS: Correctable Errors collector initialized.
Mar 03 17:08:17 proxmox kernel: Freeing unused decrypted memory: 2036K
Mar 03 17:08:17 proxmox kernel: Freeing unused kernel image (initmem) memory: 2664K
Mar 03 17:08:17 proxmox kernel: Write protecting the kernel read-only data: 28672k
Mar 03 17:08:17 proxmox kernel: Freeing unused kernel image (text/rodata gap) memory: 2036K
Mar 03 17:08:17 proxmox kernel: Freeing unused kernel image (rodata/data gap) memory: 316K
Mar 03 17:08:17 proxmox kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Mar 03 17:08:17 proxmox kernel: x86/mm: Checking user space page tables
Mar 03 17:08:17 proxmox kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
Mar 03 17:08:17 proxmox kernel: Run /init as init process
Mar 03 17:08:17 proxmox kernel: with arguments:
Mar 03 17:08:17 proxmox kernel: /init
Mar 03 17:08:17 proxmox kernel: with environment:
Mar 03 17:08:17 proxmox kernel: HOME=/
Mar 03 17:08:17 proxmox kernel: TERM=linux
Mar 03 17:08:17 proxmox kernel: BOOT_IMAGE=/boot/vmlinuz-5.11.22-1-pve
Mar 03 17:08:17 proxmox kernel: intel_iommu=on
Mar 03 17:08:17 proxmox kernel: initcall_blacklist=sysfb_init
Mar 03 17:08:17 proxmox kernel: hid: raw HID events driver (C) Jiri Kosina
Mar 03 17:08:17 proxmox kernel: r8169 0000:01:00.0: enabling device (0000 → 0003)
Mar 03 17:08:17 proxmox kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set
Mar 03 17:08:17 proxmox kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar 03 17:08:17 proxmox kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
Mar 03 17:08:17 proxmox kernel: ahci 0000:00:17.0: version 3.0
Mar 03 17:08:17 proxmox kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0000000081109810
Mar 03 17:08:17 proxmox kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
Mar 03 17:08:17 proxmox kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.11
Mar 03 17:08:17 proxmox kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar 03 17:08:17 proxmox kernel: usb usb1: Product: xHCI Host Controller
Mar 03 17:08:17 proxmox kernel: usb usb1: Manufacturer: Linux 5.11.22-1-pve xhci-hcd
Mar 03 17:08:17 proxmox kernel: usb usb1: SerialNumber: 0000:00:14.0
Mar 03 17:08:17 proxmox kernel: hub 1-0:1.0: USB hub found
Mar 03 17:08:17 proxmox kernel: hub 1-0:1.0: 12 ports detected
Mar 03 17:08:17 proxmox kernel: libphy: r8169: probed
Mar 03 17:08:17 proxmox kernel: r8169 0000:01:00.0 eth0: RTL8168evl/8111evl, 00:e0:4c:68:0c:06, XID 2c9, IRQ 125
Mar 03 17:08:17 proxmox kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
Mar 03 17:08:17 proxmox kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar 03 17:08:17 proxmox kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
Mar 03 17:08:17 proxmox kernel: xhci_hcd 0000:00:14.0: Host supports USB 3.0 SuperSpeed
Mar 03 17:08:17 proxmox kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.11
Mar 03 17:08:17 proxmox kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Mar 03 17:08:17 proxmox kernel: usb usb2: Product: xHCI Host Controller
Mar 03 17:08:17 proxmox kernel: usb usb2: Manufacturer: Linux 5.11.22-1-pve xhci-hcd
Mar 03 17:08:17 proxmox kernel: usb usb2: SerialNumber: 0000:00:14.0
Mar 03 17:08:17 proxmox kernel: hub 2-0:1.0: USB hub found
Mar 03 17:08:17 proxmox kernel: hub 2-0:1.0: 6 ports detected
Mar 03 17:08:17 proxmox kernel: usb: port power management may be unreliable
Mar 03 17:08:17 proxmox kernel: ahci 0000:00:17.0: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
Mar 03 17:08:17 proxmox kernel: ahci 0000:00:17.0: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst
Mar 03 17:08:17 proxmox kernel: scsi host0: ahci
Mar 03 17:08:17 proxmox kernel: scsi host1: ahci
Mar 03 17:08:17 proxmox kernel: ata1: SATA max UDMA/133 abar m2048@0xdff06000 port 0xdff06100 irq 126
Mar 03 17:08:17 proxmox kernel: ata2: SATA max UDMA/133 abar m2048@0xdff06000 port 0xdff06180 irq 126
Mar 03 17:08:17 proxmox kernel: r8169 0000:01:00.0 enp1s0: renamed from eth0
Mar 03 17:08:17 proxmox kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 03 17:08:17 proxmox kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 03 17:08:17 proxmox kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:08:17 proxmox kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:08:17 proxmox kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:08:17 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:08:17 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:08:17 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:08:17 proxmox kernel: ata1.00: ATA-9: BT58SSD10M, 1105V52P, max UDMA/133
Mar 03 17:08:17 proxmox kernel: ata1.00: 500118192 sectors, multi 8: LBA48 NCQ (depth 32), AA
Mar 03 17:08:17 proxmox kernel: ata2.00: ATA-11: PNY 1TB SATA SSD, H221215a, max UDMA/133
Mar 03 17:08:17 proxmox kernel: ata2.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32), AA
Mar 03 17:08:17 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:08:17 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:08:17 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:08:17 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:08:17 proxmox kernel: i2c i2c-0: 2/4 memory slots populated (from DMI)
Mar 03 17:08:17 proxmox kernel: i2c i2c-0: Successfully instantiated SPD at 0x50
Mar 03 17:08:17 proxmox kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:08:17 proxmox kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:08:17 proxmox kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:08:17 proxmox kernel: i2c i2c-0: Successfully instantiated SPD at 0x52
Mar 03 17:08:17 proxmox kernel: ata1.00: configured for UDMA/133
Mar 03 17:08:17 proxmox kernel: usb 1-1: new full-speed USB device number 2 using xhci_hcd
Mar 03 17:08:17 proxmox kernel: scsi 0:0:0:0: Direct-Access ATA BT58SSD10M V52P PQ: 0 ANSI: 5
Mar 03 17:08:17 proxmox kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Mar 03 17:08:17 proxmox kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
Mar 03 17:08:17 proxmox kernel: sd 0:0:0:0: [sda] Write Protect is off
Mar 03 17:08:17 proxmox kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar 03 17:08:17 proxmox kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
Mar 03 17:08:17 proxmox kernel: scsi 1:0:0:0: Direct-Access ATA PNY 1TB SATA SSD 215a PQ: 0 ANSI: 5
Mar 03 17:08:17 proxmox kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Mar 03 17:08:17 proxmox kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Mar 03 17:08:17 proxmox kernel: sd 1:0:0:0: [sdb] Write Protect is off
Mar 03 17:08:17 proxmox kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Mar 03 17:08:17 proxmox kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
Mar 03 17:08:17 proxmox kernel: sda: sda1 sda2 sda3
Mar 03 17:08:17 proxmox kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Mar 03 17:08:17 proxmox kernel: sdb: sdb1
Mar 03 17:08:17 proxmox kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Mar 03 17:08:17 proxmox kernel: usb 1-1: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Mar 03 17:08:17 proxmox kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 03 17:08:17 proxmox kernel: usb 1-1: Product: Sonoff Zigbee 3.0 USB Dongle Plus
Mar 03 17:08:17 proxmox kernel: usb 1-1: Manufacturer: Silicon Labs
Mar 03 17:08:17 proxmox kernel: usb 1-1: SerialNumber: 0001
Mar 03 17:08:17 proxmox kernel: usb 1-2: new full-speed USB device number 3 using xhci_hcd
Mar 03 17:08:17 proxmox kernel: tsc: Refined TSC clocksource calibration: 1799.999 MHz
Mar 03 17:08:17 proxmox kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x19f228ab7a2, max_idle_ns: 440795289252 ns
Mar 03 17:08:17 proxmox kernel: clocksource: Switched to clocksource tsc
Mar 03 17:08:17 proxmox kernel: usb 1-2: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Mar 03 17:08:17 proxmox kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 03 17:08:17 proxmox kernel: usb 1-2: Product: RFXtrx433
Mar 03 17:08:17 proxmox kernel: usb 1-2: Manufacturer: RFXCOM
Mar 03 17:08:17 proxmox kernel: usb 1-2: SerialNumber: A11YHQLP
Mar 03 17:08:17 proxmox kernel: usb 1-3: new full-speed USB device number 4 using xhci_hcd
Mar 03 17:08:17 proxmox kernel: usb 1-3: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=82.41
Mar 03 17:08:17 proxmox kernel: usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 03 17:08:17 proxmox kernel: usb 1-4: new full-speed USB device number 5 using xhci_hcd
Mar 03 17:08:17 proxmox kernel: usb 1-4: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Mar 03 17:08:17 proxmox kernel: usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 03 17:08:17 proxmox kernel: usb 1-7: new low-speed USB device number 6 using xhci_hcd
Mar 03 17:08:17 proxmox kernel: usb 1-7: New USB device found, idVendor=046d, idProduct=c00e, bcdDevice=11.10
Mar 03 17:08:17 proxmox kernel: usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 03 17:08:17 proxmox kernel: usb 1-7: Product: USB-PS/2 Optical Mouse
Mar 03 17:08:17 proxmox kernel: usb 1-7: Manufacturer: Logitech
Mar 03 17:08:17 proxmox kernel: usbcore: registered new interface driver usbhid
Mar 03 17:08:17 proxmox kernel: usbhid: USB HID core driver
Mar 03 17:08:17 proxmox kernel: usbcore: registered new interface driver usbmouse
Mar 03 17:08:17 proxmox kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:046D:C00E.0001/input/input3
Mar 03 17:08:17 proxmox kernel: hid-generic 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:14.0-7/input0
Mar 03 17:08:17 proxmox kernel: usb 1-9: new full-speed USB device number 7 using xhci_hcd
Mar 03 17:08:17 proxmox kernel: usb 1-9: string descriptor 0 read error: -22
Mar 03 17:08:17 proxmox kernel: usb 1-9: New USB device found, idVendor=0930, idProduct=021c, bcdDevice= 0.01
Mar 03 17:08:17 proxmox kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 03 17:08:17 proxmox kernel: fbcon: Taking over console
Mar 03 17:08:17 proxmox kernel: raid6: avx2x4 gen() 21365 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: avx2x4 xor() 18228 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: avx2x2 gen() 37295 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: avx2x2 xor() 21939 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: avx2x1 gen() 31625 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: avx2x1 xor() 19241 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: sse2x4 gen() 15394 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: sse2x4 xor() 9235 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: sse2x2 gen() 15609 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: sse2x2 xor() 9500 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: sse2x1 gen() 13222 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: sse2x1 xor() 6472 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: using algorithm avx2x2 gen() 37295 MB/s
Mar 03 17:08:17 proxmox kernel: raid6: … xor() 21939 MB/s, rmw enabled
Mar 03 17:08:17 proxmox kernel: raid6: using avx2x2 recovery algorithm
Mar 03 17:08:17 proxmox kernel: xor: automatically using best checksumming function avx
Mar 03 17:08:17 proxmox kernel: Btrfs loaded, crc32c=crc32c-intel, zoned=yes
Mar 03 17:08:17 proxmox kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 03 17:08:17 proxmox systemd: Inserted module ‹ autofs4 ›
Mar 03 17:08:17 proxmox systemd: systemd 247.3-6 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
Mar 03 17:08:17 proxmox systemd: Detected architecture x86-64.
Mar 03 17:08:17 proxmox systemd: Set hostname to .
Mar 03 17:08:17 proxmox systemd: Queued start job for default target Graphical Interface.
Mar 03 17:08:17 proxmox systemd: Created slice system-getty.slice.
Mar 03 17:08:17 proxmox systemd: Created slice system-modprobe.slice.
Mar 03 17:08:17 proxmox systemd: Created slice system-postfix.slice.
Mar 03 17:08:17 proxmox systemd: Created slice User and Session Slice.
Mar 03 17:08:17 proxmox systemd: Started Dispatch Password Requests to Console Directory Watch.
Mar 03 17:08:17 proxmox systemd: Started Forward Password Requests to Wall Directory Watch.
Mar 03 17:08:17 proxmox systemd: Set up automount Arbitrary Executable File Formats File System Automount Point.
Mar 03 17:08:17 proxmox systemd: Reached target ceph target allowing to start/stop all ceph-fuse@.service instances at once.
Mar 03 17:08:17 proxmox systemd: Reached target ceph target allowing to start/stop all ceph@.service instances at once.
Mar 03 17:08:17 proxmox systemd: Reached target Local Encrypted Volumes.
Mar 03 17:08:17 proxmox systemd: Reached target Paths.
Mar 03 17:08:17 proxmox systemd: Reached target Slices.
Mar 03 17:08:17 proxmox systemd: Reached target System Time Set.
Mar 03 17:08:17 proxmox systemd: Listening on Device-mapper event daemon FIFOs.
Mar 03 17:08:17 proxmox systemd: Listening on LVM2 poll daemon socket.
Mar 03 17:08:17 proxmox systemd: Listening on RPCbind Server Activation Socket.
Mar 03 17:08:17 proxmox systemd: Listening on Syslog Socket.
Mar 03 17:08:17 proxmox systemd: Listening on fsck to fsckd communication Socket.
Mar 03 17:08:17 proxmox systemd: Listening on initctl Compatibility Named Pipe.
Mar 03 17:08:17 proxmox systemd: Listening on Journal Audit Socket.
Mar 03 17:08:17 proxmox systemd: Listening on Journal Socket (/dev/log).
Mar 03 17:08:17 proxmox systemd: Listening on Journal Socket.
Mar 03 17:08:17 proxmox systemd: Listening on udev Control Socket.
Mar 03 17:08:17 proxmox systemd: Listening on udev Kernel Socket.
Mar 03 17:08:17 proxmox systemd: Mounting Huge Pages File System…
Mar 03 17:08:17 proxmox systemd: Mounting POSIX Message Queue File System…
Mar 03 17:08:17 proxmox systemd: Mounting RPC Pipe File System…
Mar 03 17:08:17 proxmox systemd: Mounting Kernel Debug File System…
Mar 03 17:08:17 proxmox systemd: Mounting Kernel Trace File System…
Mar 03 17:08:17 proxmox systemd: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
Mar 03 17:08:17 proxmox systemd: Starting Set the console keyboard layout…
Mar 03 17:08:17 proxmox systemd: Starting Create list of static device nodes for the current kernel…
Mar 03 17:08:17 proxmox systemd: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling…
Mar 03 17:08:17 proxmox systemd: Starting Load Kernel Module configfs…
Mar 03 17:08:17 proxmox systemd: Starting Load Kernel Module drm…
Mar 03 17:08:17 proxmox systemd: Starting Load Kernel Module fuse…
Mar 03 17:08:17 proxmox systemd: Condition check resulted in Set Up Additional Binary Formats being skipped.
Mar 03 17:08:17 proxmox systemd: Condition check resulted in File System Check on Root Device being skipped.
Mar 03 17:08:17 proxmox systemd: Starting Journal Service…
Mar 03 17:08:17 proxmox systemd: Starting Load Kernel Modules…
Mar 03 17:08:17 proxmox systemd: Starting Remount Root and Kernel File Systems…
Mar 03 17:08:17 proxmox systemd: Starting Coldplug All udev Devices…
Mar 03 17:08:17 proxmox systemd: Mounted Huge Pages File System.
Mar 03 17:08:17 proxmox systemd: Mounted POSIX Message Queue File System.
Mar 03 17:08:17 proxmox systemd: Mounted Kernel Debug File System.
Mar 03 17:08:17 proxmox systemd: Mounted Kernel Trace File System.
Mar 03 17:08:17 proxmox systemd: Finished Set the console keyboard layout.
Mar 03 17:08:17 proxmox systemd: Finished Create list of static device nodes for the current kernel.
Mar 03 17:08:17 proxmox systemd: modprobe@configfs.service: Succeeded.
Mar 03 17:08:17 proxmox systemd: Finished Load Kernel Module configfs.
Mar 03 17:08:17 proxmox systemd: modprobe@fuse.service: Succeeded.
Mar 03 17:08:17 proxmox systemd: Finished Load Kernel Module fuse.
Mar 03 17:08:17 proxmox systemd: Mounting FUSE Control File System…
Mar 03 17:08:17 proxmox systemd: Mounting Kernel Configuration File System…
Mar 03 17:08:17 proxmox systemd: Mounted FUSE Control File System.
Mar 03 17:08:17 proxmox systemd: Mounted Kernel Configuration File System.
Mar 03 17:08:17 proxmox kernel: RPC: Registered named UNIX socket transport module.
Mar 03 17:08:17 proxmox kernel: RPC: Registered udp transport module.
Mar 03 17:08:17 proxmox kernel: RPC: Registered tcp transport module.
Mar 03 17:08:17 proxmox kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Mar 03 17:08:17 proxmox systemd: Mounted RPC Pipe File System.
Mar 03 17:08:17 proxmox systemd: modprobe@drm.service: Succeeded.
Mar 03 17:08:17 proxmox systemd: Finished Load Kernel Module drm.
Mar 03 17:08:17 proxmox kernel: EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
Mar 03 17:08:17 proxmox systemd: Finished Remount Root and Kernel File Systems.
Mar 03 17:08:17 proxmox systemd: Condition check resulted in Rebuild Hardware Database being skipped.
Mar 03 17:08:17 proxmox systemd: Condition check resulted in Platform Persistent Storage Archival being skipped.
Mar 03 17:08:17 proxmox systemd: Starting Load/Save Random Seed…
Mar 03 17:08:17 proxmox systemd: Starting Create System Users…
Mar 03 17:08:17 proxmox kernel: VFIO - User Level meta-driver version: 0.3
Mar 03 17:08:17 proxmox systemd: Started Device-mapper event daemon.
Mar 03 17:08:17 proxmox systemd: Finished Load/Save Random Seed.
Mar 03 17:08:17 proxmox systemd: Condition check resulted in First Boot Complete being skipped.
Mar 03 17:08:17 proxmox systemd-journald[416]: Journal started
Mar 03 17:08:17 proxmox systemd-journald[416]: Runtime Journal (/run/log/journal/33b8beee431c4726b9f0c6997a94c1ae) is 8.0M, max 238.3M, 230.3M free.
Mar 03 17:08:17 proxmox systemd-modules-load[418]: Inserted module ‹ vfio ›
Mar 03 17:08:17 proxmox dmeventd[429]: dmeventd ready for processing.
Mar 03 17:08:17 proxmox systemd-modules-load[418]: Inserted module ‹ vfio_pci ›
Mar 03 17:08:17 proxmox systemd[1]: Starting Flush Journal to Persistent Storage…
Mar 03 17:08:17 proxmox systemd: Started Journal Service.
Mar 03 17:08:17 proxmox systemd[1]: Finished Create System Users.
Mar 03 17:08:17 proxmox systemd[1]: Starting Create Static Device Nodes in /dev…
Mar 03 17:08:17 proxmox systemd-journald[416]: Time spent on flushing to /var/log/journal/33b8beee431c4726b9f0c6997a94c1ae is 19.467ms for 892 entries.
Mar 03 17:08:17 proxmox systemd-journald[416]: System Journal (/var/log/journal/33b8beee431c4726b9f0c6997a94c1ae) is 3.9G, max 4.0G, 55.8M free.
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Mar 03 17:08:18 proxmox lvm[411]: 10 logical volume(s) in volume group « pve » monitored
Mar 03 17:08:18 proxmox lvm[429]: Monitoring thin pool pve-data-tpool.
Mar 03 17:08:18 proxmox systemd[1]: Finished Coldplug All udev Devices.
Mar 03 17:08:18 proxmox systemd[1]: Starting Helper to synchronize boot up for ifupdown…
Mar 03 17:08:18 proxmox systemd[1]: Starting Wait for udev To Complete Device Initialization…
Mar 03 17:08:18 proxmox systemd[1]: Finished Create Static Device Nodes in /dev.
Mar 03 17:08:18 proxmox systemd[1]: Starting Rule-based Manager for Device Events and Files…
Mar 03 17:08:18 proxmox systemd-udevd[439]: /etc/udev/rules.d/65-apex.rules:2 Invalid key/value pair, ignoring.
Mar 03 17:08:18 proxmox systemd[1]: Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 03 17:08:18 proxmox systemd[1]: Reached target Local File Systems (Pre).
Mar 03 17:08:18 proxmox systemd[1]: Started Rule-based Manager for Device Events and Files.
Mar 03 17:08:18 proxmox systemd[1]: Finished Flush Journal to Persistent Storage.
Mar 03 17:08:18 proxmox systemd-udevd[452]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:08:18 proxmox kernel: input: PC Speaker as /devices/platform/pcspkr/input/input4
Mar 03 17:08:18 proxmox systemd-udevd[452]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:18 proxmox kernel: pstore: Using crash dump compression: deflate
Mar 03 17:08:18 proxmox kernel: gasket: loading out-of-tree module taints kernel.
Mar 03 17:08:18 proxmox kernel: ee1004 0-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
Mar 03 17:08:18 proxmox kernel: ee1004 0-0052: 512 byte EE1004-compliant SPD EEPROM, read-only
Mar 03 17:08:18 proxmox kernel: usbcore: registered new interface driver usbserial_generic
Mar 03 17:08:18 proxmox kernel: usbserial: USB Serial support registered for generic
Mar 03 17:08:18 proxmox kernel: mei_me 0000:00:16.0: enabling device (0004 → 0006)
Mar 03 17:08:18 proxmox kernel: cdc_acm 1-4:1.0: ttyACM0: USB ACM device
Mar 03 17:08:18 proxmox kernel: usbcore: registered new interface driver cdc_acm
Mar 03 17:08:18 proxmox kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Mar 03 17:08:18 proxmox kernel: RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
Mar 03 17:08:18 proxmox kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
Mar 03 17:08:18 proxmox kernel: RAPL PMU: hw unit of domain package 2^-14 Joules
Mar 03 17:08:18 proxmox kernel: RAPL PMU: hw unit of domain dram 2^-14 Joules
Mar 03 17:08:18 proxmox kernel: RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
Mar 03 17:08:18 proxmox kernel: apex 0000:03:00.0: enabling device (0000 → 0002)
Mar 03 17:08:18 proxmox kernel: usbcore: registered new interface driver cp210x
Mar 03 17:08:18 proxmox kernel: usbserial: USB Serial support registered for cp210x
Mar 03 17:08:18 proxmox kernel: cp210x 1-1:1.0: cp210x converter detected
Mar 03 17:08:18 proxmox kernel: pstore: Registered efi as persistent store backend
Mar 03 17:08:18 proxmox kernel: usb 1-1: cp210x converter now attached to ttyUSB0
Mar 03 17:08:18 proxmox kernel: Bluetooth: Core ver 2.22
Mar 03 17:08:18 proxmox kernel: NET: Registered protocol family 31
Mar 03 17:08:18 proxmox kernel: Bluetooth: HCI device and connection manager initialized
Mar 03 17:08:18 proxmox kernel: Bluetooth: HCI socket layer initialized
Mar 03 17:08:18 proxmox kernel: Bluetooth: L2CAP socket layer initialized
Mar 03 17:08:18 proxmox kernel: Bluetooth: SCO socket layer initialized
Mar 03 17:08:18 proxmox kernel: usbcore: registered new interface driver ftdi_sio
Mar 03 17:08:18 proxmox kernel: usbserial: USB Serial support registered for FTDI USB Serial Device
Mar 03 17:08:18 proxmox kernel: ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected
Mar 03 17:08:18 proxmox kernel: proc_thermal 0000:00:04.0: enabling device (0000 → 0002)
Mar 03 17:08:18 proxmox kernel: usb 1-2: Detected FT232RL
Mar 03 17:08:18 proxmox kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Mar 03 17:08:18 proxmox kernel: usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB1
Mar 03 17:08:18 proxmox kernel: cfg80211: Loaded X.509 cert ‹ sforshee: 00b28ddf47aef9cea7 ›
Mar 03 17:08:18 proxmox kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Mar 03 17:08:18 proxmox kernel: cfg80211: failed to load regulatory.db
Mar 03 17:08:18 proxmox kernel: proc_thermal 0000:00:04.0: Creating sysfs group for PROC_THERMAL_PCI
Mar 03 17:08:18 proxmox kernel: intel_rapl_common: Found RAPL domain package
Mar 03 17:08:18 proxmox kernel: intel_rapl_common: Found RAPL domain dram
Mar 03 17:08:18 proxmox systemd-udevd[452]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:18 proxmox kernel: cryptd: max_cpu_qlen set to 1000
Mar 03 17:08:18 proxmox systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP
Mar 03 17:08:18 proxmox kernel: [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
Mar 03 17:08:18 proxmox kernel: ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no)
Mar 03 17:08:18 proxmox kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Mar 03 17:08:18 proxmox kernel: AVX2 version of gcm_enc/dec engaged.
Mar 03 17:08:18 proxmox kernel: AES CTR mode by8 optimization enabled
Mar 03 17:08:18 proxmox kernel: usbcore: registered new interface driver btusb
Mar 03 17:08:18 proxmox kernel: Bluetooth: hci0: unexpected event for opcode 0x0000
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mar 03 17:08:18 proxmox kernel: intel_rapl_common: Found RAPL domain package
Mar 03 17:08:18 proxmox kernel: intel_rapl_common: Found RAPL domain core
Mar 03 17:08:18 proxmox kernel: intel_rapl_common: Found RAPL domain uncore
Mar 03 17:08:18 proxmox kernel: intel_rapl_common: Found RAPL domain dram
Mar 03 17:08:18 proxmox systemd[1]: Created slice system-lvm2\x2dpvscan.slice.
Mar 03 17:08:18 proxmox systemd[1]: Starting LVM event activation on device 8:3…
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mar 03 17:08:18 proxmox systemd[1]: Found device PNY_1TB_SATA_SSD 1.
Mar 03 17:08:18 proxmox kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Mar 03 17:08:18 proxmox udevadm[438]: systemd-udev-settle.service is deprecated. Please fix zfs-import-cache.service, zfs-import-scan.service not to pull it in.
Mar 03 17:08:18 proxmox systemd[1]: Reached target Bluetooth.
Mar 03 17:08:18 proxmox lvm[567]: pvscan[567] PV /dev/sda3 online, VG pve is complete.
Mar 03 17:08:18 proxmox lvm[567]: pvscan[567] VG pve skip autoactivation.
Mar 03 17:08:18 proxmox systemd[1]: Mounting Mount storage ‹ PNY_SSD_1T › under /mnt/pve…
Mar 03 17:08:18 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status…
Mar 03 17:08:18 proxmox kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Mar 03 17:08:18 proxmox kernel: usb 1-9: Direct firmware load for ar3k/AthrBT_0x11020000.dfu failed with error -2
Mar 03 17:08:18 proxmox kernel: Bluetooth: Patch file not found ar3k/AthrBT_0x11020000.dfu
Mar 03 17:08:18 proxmox kernel: Bluetooth: Loading patch file failed
Mar 03 17:08:18 proxmox kernel: ath3k: probe of 1-9:1.0 failed with error -2
Mar 03 17:08:18 proxmox kernel: usbcore: registered new interface driver ath3k
Mar 03 17:08:18 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Mar 03 17:08:18 proxmox systemd[1]: Found device /dev/pve/swap.
Mar 03 17:08:18 proxmox systemd[1]: Activating swap /dev/pve/swap…
Mar 03 17:08:18 proxmox kernel: ath9k 0000:02:00.0: enabling device (0000 → 0002)
Mar 03 17:08:18 proxmox systemd[1]: Finished LVM event activation on device 8:3.
Mar 03 17:08:18 proxmox kernel: ath: EEPROM regdomain: 0x6a
Mar 03 17:08:18 proxmox kernel: ath: EEPROM indicates we should expect a direct regpair map
Mar 03 17:08:18 proxmox kernel: ath: Country alpha2 being used: 00
Mar 03 17:08:18 proxmox kernel: ath: Regpair used: 0x6a
Mar 03 17:08:18 proxmox kernel: ieee80211 phy0: Selected rate control algorithm ‹ minstrel_ht ›
Mar 03 17:08:18 proxmox kernel: ieee80211 phy0: Atheros AR9462 Rev:2 mem=0xffffb28fc0c00000, irq=16
Mar 03 17:08:18 proxmox systemd-modules-load[418]: Failed to insert module ‹ kvmgt ›: No such device
Mar 03 17:08:18 proxmox systemd-modules-load[418]: Failed to find module ‹ xengt ›
Mar 03 17:08:18 proxmox systemd[1]: Activated swap /dev/pve/swap.
Mar 03 17:08:18 proxmox kernel: Adding 7340028k swap on /dev/mapper/pve-swap. Priority:-2 extents:1 across:7340028k SSFS
Mar 03 17:08:18 proxmox systemd[1]: Reached target Swap.
Mar 03 17:08:18 proxmox systemd-udevd[449]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:08:18 proxmox systemd-udevd[449]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:18 proxmox kernel: ath9k 0000:02:00.0 wlp2s0: renamed from wlan0
Mar 03 17:08:18 proxmox kernel: Loading iSCSI transport class v2.0-870.
Mar 03 17:08:18 proxmox systemd-modules-load[418]: Inserted module ‹ iscsi_tcp ›
Mar 03 17:08:18 proxmox kernel: iscsi: registered transport (tcp)
Mar 03 17:08:18 proxmox systemd-udevd[463]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:08:18 proxmox systemd-udevd[463]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:18 proxmox kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 → 0002)
Mar 03 17:08:18 proxmox kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
Mar 03 17:08:18 proxmox systemd-modules-load[418]: Inserted module ‹ ib_iser ›
Mar 03 17:08:18 proxmox kernel: iscsi: registered transport (iser)
Mar 03 17:08:18 proxmox kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC892: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
Mar 03 17:08:18 proxmox kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Mar 03 17:08:18 proxmox kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
Mar 03 17:08:18 proxmox kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
Mar 03 17:08:18 proxmox kernel: snd_hda_codec_realtek hdaudioC0D0: inputs:
Mar 03 17:08:18 proxmox kernel: snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
Mar 03 17:08:18 proxmox systemd-modules-load[418]: Inserted module ‹ vhost_net ›
Mar 03 17:08:18 proxmox kernel: znvpair: module license ‹ CDDL › taints kernel.
Mar 03 17:08:18 proxmox kernel: Disabling lock debugging due to kernel taint
Mar 03 17:08:18 proxmox kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input6
Mar 03 17:08:18 proxmox kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input7
Mar 03 17:08:18 proxmox kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
Mar 03 17:08:18 proxmox kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
Mar 03 17:08:18 proxmox kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
Mar 03 17:08:18 proxmox systemd[1]: Reached target Sound Card.
Mar 03 17:08:18 proxmox systemd[1]: Finished Helper to synchronize boot up for ifupdown.
Mar 03 17:08:18 proxmox systemd[1]: Finished Wait for udev To Complete Device Initialization.
Mar 03 17:08:18 proxmox systemd[1]: Condition check resulted in Import ZFS pools by cache file being skipped.
Mar 03 17:08:18 proxmox systemd[1]: Condition check resulted in Import ZFS pools by device scanning being skipped.
Mar 03 17:08:18 proxmox systemd[1]: Reached target ZFS pool import target.
Mar 03 17:08:18 proxmox systemd[1]: Condition check resulted in Mount ZFS filesystems being skipped.
Mar 03 17:08:18 proxmox systemd[1]: Condition check resulted in Wait for ZFS Volume (zvol) links in /dev being skipped.
Mar 03 17:08:18 proxmox systemd[1]: Reached target ZFS volumes are ready.
Mar 03 17:08:18 proxmox systemd-modules-load[418]: Inserted module ‹ zfs ›
Mar 03 17:08:18 proxmox kernel: ZFS: Loaded module v2.0.4-pve1, ZFS pool version 5000, ZFS filesystem version 5
Mar 03 17:08:18 proxmox systemd[1]: Finished Load Kernel Modules.
Mar 03 17:08:18 proxmox systemd[1]: Starting Apply Kernel Variables…
Mar 03 17:08:18 proxmox systemd[1]: Finished Apply Kernel Variables.
Mar 03 17:08:20 proxmox kernel: EXT4-fs (sdb1): recovery complete
Mar 03 17:08:20 proxmox kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 03 17:08:20 proxmox systemd[1]: Mounted Mount storage ‹ PNY_SSD_1T › under /mnt/pve.
Mar 03 17:08:20 proxmox systemd[1]: Reached target Local File Systems.
Mar 03 17:08:20 proxmox systemd[1]: Starting Load AppArmor profiles…
Mar 03 17:08:20 proxmox systemd[1]: Starting Set console font and keymap…
Mar 03 17:08:20 proxmox systemd[1]: Starting Network initialization…
Mar 03 17:08:20 proxmox systemd[1]: Starting Preprocess NFS configuration…
Mar 03 17:08:20 proxmox systemd[1]: Starting Proxmox VE Login Banner…
Mar 03 17:08:20 proxmox systemd[1]: Starting Proxmox VE firewall logger…
Mar 03 17:08:20 proxmox systemd[1]: Starting Commit Proxmox VE network changes…
Mar 03 17:08:20 proxmox systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Mar 03 17:08:20 proxmox systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Mar 03 17:08:20 proxmox systemd[1]: Starting Create Volatile Files and Directories…
Mar 03 17:08:20 proxmox systemd[1]: Finished Set console font and keymap.
Mar 03 17:08:20 proxmox systemd[1]: nfs-config.service: Succeeded.
Mar 03 17:08:20 proxmox systemd[1]: Finished Preprocess NFS configuration.
Mar 03 17:08:20 proxmox systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped.
Mar 03 17:08:20 proxmox systemd[1]: Condition check resulted in RPC security service for NFS server being skipped.
Mar 03 17:08:20 proxmox systemd[1]: Reached target NFS client services.
Mar 03 17:08:20 proxmox mv[615]: /bin/mv: cannot stat ‹ /etc/network/interfaces.new ›: No such file or directory
Mar 03 17:08:20 proxmox apparmor.systemd[604]: Restarting AppArmor
Mar 03 17:08:20 proxmox apparmor.systemd[604]: Reloading AppArmor profiles
Mar 03 17:08:20 proxmox systemd[1]: Finished Commit Proxmox VE network changes.
Mar 03 17:08:20 proxmox networking[606]: networking: Configuring network interfaces
Mar 03 17:08:20 proxmox pvefw-logger[630]: starting pvefw logger
Mar 03 17:08:20 proxmox systemd[1]: Started Proxmox VE firewall logger.
Mar 03 17:08:20 proxmox systemd[1]: Finished Create Volatile Files and Directories.
Mar 03 17:08:20 proxmox systemd[1]: Starting RPC bind portmap service…
Mar 03 17:08:20 proxmox systemd[1]: Starting Update UTMP about System Boot/Shutdown…
Mar 03 17:08:20 proxmox systemd[1]: Started RPC bind portmap service.
Mar 03 17:08:20 proxmox systemd[1]: Reached target RPC Port Mapper.
Mar 03 17:08:20 proxmox systemd[1]: Finished Update UTMP about System Boot/Shutdown.
Mar 03 17:08:20 proxmox audit[632]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/lxc-start » pid=632 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.692:2): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/lxc-start » pid=632 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[638]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lsb_release » pid=638 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[631]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe » pid=631 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[631]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe//kmod » pid=631 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.696:3): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lsb_release » pid=638 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.696:4): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe » pid=631 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.696:5): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« nvidia_modprobe//kmod » pid=631 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[634]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/man » pid=634 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[634]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« man_filter » pid=634 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[634]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« man_groff » pid=634 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.700:6): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/bin/man » pid=634 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.700:7): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« man_filter » pid=634 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.700:8): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« man_groff » pid=634 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[636]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/sbin/chronyd » pid=636 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.704:9): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« /usr/sbin/chronyd » pid=636 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[633]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« tcpdump » pid=633 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.708:10): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« tcpdump » pid=633 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[637]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default » pid=637 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[637]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-cgns » pid=637 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[637]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-with-mounting » pid=637 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox audit[637]: AVC apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default-with-nesting » pid=637 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox systemd[1]: Finished Load AppArmor profiles.
Mar 03 17:08:20 proxmox systemd[1]: Reached target System Initialization.
Mar 03 17:08:20 proxmox systemd[1]: Started Daily Cleanup of Temporary Directories.
Mar 03 17:08:20 proxmox systemd[1]: Listening on D-Bus System Message Bus Socket.
Mar 03 17:08:20 proxmox systemd[1]: Reached target Sockets.
Mar 03 17:08:20 proxmox systemd[1]: Reached target Basic System.
Mar 03 17:08:20 proxmox kernel: audit: type=1400 audit(1709482100.712:11): apparmor=« STATUS » operation=« profile_load » profile=« unconfined » name=« lxc-container-default » pid=637 comm=« apparmor_parser »
Mar 03 17:08:20 proxmox systemd[1]: Started D-Bus System Message Bus.
Mar 03 17:08:20 proxmox systemd[1]: Starting Remove Stale Online ext4 Metadata Check Snapshots…
Mar 03 17:08:20 proxmox systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.
Mar 03 17:08:20 proxmox systemd[1]: Starting Kernel Samepage Merging (KSM) Tuning Daemon…
Mar 03 17:08:20 proxmox systemd[1]: Starting Initialize hardware monitoring sensors…
Mar 03 17:08:20 proxmox systemd[1]: Started FUSE filesystem for LXC.
Mar 03 17:08:20 proxmox systemd[1]: Starting Proxmox VE LXC Syscall Daemon…
Mar 03 17:08:20 proxmox systemd[1]: Starting PVE Qemu Event Daemon…
Mar 03 17:08:20 proxmox systemd[1]: Starting System Logging Service…
Mar 03 17:08:20 proxmox systemd[1]: Starting Self Monitoring and Reporting Technology (SMART) Daemon…
Mar 03 17:08:20 proxmox systemd[1]: Starting User Login Management…
Mar 03 17:08:20 proxmox systemd[1]: Started Proxmox VE watchdog multiplexer.
Mar 03 17:08:20 proxmox systemd[1]: Starting ZFS file system shares…
Mar 03 17:08:20 proxmox systemd[1]: Started ZFS Event Daemon (zed).
Mar 03 17:08:20 proxmox systemd[1]: Started Kernel Samepage Merging (KSM) Tuning Daemon.
Mar 03 17:08:20 proxmox systemd[1]: Started PVE Qemu Event Daemon.
Mar 03 17:08:20 proxmox systemd[1]: e2scrub_reap.service: Succeeded.
Mar 03 17:08:20 proxmox systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Mar 03 17:08:20 proxmox systemd[1]: Started Proxmox VE LXC Syscall Daemon.
Mar 03 17:08:20 proxmox watchdog-mux[654]: Watchdog driver ‹ Software Watchdog ›, version 0
Mar 03 17:08:20 proxmox kernel: softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
Mar 03 17:08:20 proxmox kernel: softdog: soft_reboot_cmd= soft_active_on_boot=0
Mar 03 17:08:20 proxmox sensors[672]: pch_skylake-virtual-0
Mar 03 17:08:20 proxmox sensors[672]: Adapter: Virtual device
Mar 03 17:08:20 proxmox sensors[672]: temp1: +35.0Â°C
Mar 03 17:08:20 proxmox sensors[672]: coretemp-isa-0000
Mar 03 17:08:20 proxmox sensors[672]: Adapter: ISA adapter
Mar 03 17:08:20 proxmox sensors[672]: Package id 0: +41.0Â°C (high = +100.0Â°C, crit = +100.0Â°C)
Mar 03 17:08:20 proxmox sensors[672]: Core 0: +39.0Â°C (high = +100.0Â°C, crit = +100.0Â°C)
Mar 03 17:08:20 proxmox sensors[672]: Core 1: +40.0Â°C (high = +100.0Â°C, crit = +100.0Â°C)
Mar 03 17:08:20 proxmox sensors[672]: Core 2: +41.0Â°C (high = +100.0Â°C, crit = +100.0Â°C)
Mar 03 17:08:20 proxmox sensors[672]: Core 3: +41.0Â°C (high = +100.0Â°C, crit = +100.0Â°C)
Mar 03 17:08:20 proxmox systemd[1]: Finished Initialize hardware monitoring sensors.
Mar 03 17:08:20 proxmox lxcfs[645]: Running constructor lxcfs_init to reload liblxcfs
Mar 03 17:08:20 proxmox lxcfs[645]: mount namespace: 5
Mar 03 17:08:20 proxmox lxcfs[645]: hierarchies:
Mar 03 17:08:20 proxmox lxcfs[645]: 0: fd: 6: cpuset,cpu,io,memory,hugetlb,pids,rdma
Mar 03 17:08:20 proxmox lxcfs[645]: Kernel supports pidfds
Mar 03 17:08:20 proxmox lxcfs[645]: Kernel does not support swap accounting
Mar 03 17:08:20 proxmox lxcfs[645]: api_extensions:
Mar 03 17:08:20 proxmox lxcfs[645]: - cgroups
Mar 03 17:08:20 proxmox lxcfs[645]: - sys_cpu_online
Mar 03 17:08:20 proxmox lxcfs[645]: - proc_cpuinfo
Mar 03 17:08:20 proxmox lxcfs[645]: - proc_diskstats
Mar 03 17:08:20 proxmox lxcfs[645]: - proc_loadavg
Mar 03 17:08:20 proxmox lxcfs[645]: - proc_meminfo
Mar 03 17:08:20 proxmox lxcfs[645]: - proc_stat
Mar 03 17:08:20 proxmox lxcfs[645]: - proc_swaps
Mar 03 17:08:20 proxmox lxcfs[645]: - proc_uptime
Mar 03 17:08:20 proxmox lxcfs[645]: - shared_pidns
Mar 03 17:08:20 proxmox lxcfs[645]: - cpuview_daemon
Mar 03 17:08:20 proxmox lxcfs[645]: - loadavg_daemon
Mar 03 17:08:20 proxmox lxcfs[645]: - pidfds
Mar 03 17:08:20 proxmox systemd-logind[653]: New seat seat0.
Mar 03 17:08:20 proxmox systemd-logind[653]: Watching system buttons on /dev/input/event2 (Power Button)
Mar 03 17:08:20 proxmox systemd-logind[653]: Watching system buttons on /dev/input/event1 (Power Button)
Mar 03 17:08:20 proxmox systemd-logind[653]: Watching system buttons on /dev/input/event0 (Sleep Button)
Mar 03 17:08:20 proxmox systemd[1]: Finished ZFS file system shares.
Mar 03 17:08:20 proxmox systemd[1]: Reached target ZFS startup target.
Mar 03 17:08:20 proxmox smartd[651]: smartd 7.2 2020-12-30 r5155 [x86_64-linux-5.11.22-1-pve] (local build)
Mar 03 17:08:20 proxmox smartd[651]: Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Mar 03 17:08:20 proxmox smartd[651]: Opened configuration file /etc/smartd.conf
Mar 03 17:08:20 proxmox dbus-daemon[641]: [system] AppArmor D-Bus mediation is enabled
Mar 03 17:08:20 proxmox systemd[1]: Started User Login Management.
Mar 03 17:08:20 proxmox smartd[651]: Drive: DEVICESCAN, implied ‹ -a › Directive on line 21 of file /etc/smartd.conf
Mar 03 17:08:20 proxmox smartd[651]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sda, type changed from ‹ scsi › to ‹ sat ›
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sda [SAT], opened
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sda [SAT], BT58SSD10M, S/N:BM06051A00055, WWN:0-000000-000000000, FW:1105V52P, 256 GB
Mar 03 17:08:20 proxmox rsyslogd[648]: imuxsock: Acquired UNIX socket ‹ /run/systemd/journal/syslog › (fd 3) from systemd. [v8.2102.0]
Mar 03 17:08:20 proxmox rsyslogd[648]: [origin software=« rsyslogd » swVersion=« 8.2102.0 » x-pid=« 648 » x-info=« https://www.rsyslog.com »] start
Mar 03 17:08:20 proxmox systemd[1]: Started System Logging Service.
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sda [SAT], not found in smartd database.
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sda [SAT], is SMART capable. Adding to « monitor » list.
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.BT58SSD10M-BM06051A00055.ata.state
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb, type changed from ‹ scsi › to ‹ sat ›
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], opened
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], PNY 1TB SATA SSD, S/N:PNF25232018370900098, WWN:5-f8db4c-252300098, FW:H221215a, 1.00 TB
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], not found in smartd database.
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], can’t monitor Current_Pending_Sector count - no Attribute 197
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], can’t monitor Offline_Uncorrectable count - no Attribute 198
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], is SMART capable. Adding to « monitor » list.
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.PNY_1TB_SATA_SSD-PNF25232018370900098.ata.state
Mar 03 17:08:20 proxmox smartd[651]: Monitoring 2 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 38 to 40
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.BT58SSD10M-BM06051A00055.ata.state
Mar 03 17:08:20 proxmox smartd[651]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.PNY_1TB_SATA_SSD-PNF25232018370900098.ata.state
Mar 03 17:08:20 proxmox systemd[1]: Started Self Monitoring and Reporting Technology (SMART) Daemon.
Mar 03 17:08:20 proxmox zed[658]: ZFS Event Daemon 2.0.5-pve1~bpo10+1 (PID 658)
Mar 03 17:08:20 proxmox zed[658]: Processing events since eid=0
Mar 03 17:08:21 proxmox systemd[1]: Finished Proxmox VE Login Banner.
Mar 03 17:08:21 proxmox systemd-udevd[463]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:21 proxmox kernel: vmbr0: port 1(enp1s0) entered blocking state
Mar 03 17:08:21 proxmox kernel: vmbr0: port 1(enp1s0) entered disabled state
Mar 03 17:08:21 proxmox kernel: device enp1s0 entered promiscuous mode
Mar 03 17:08:21 proxmox kernel: RTL8211E Gigabit Ethernet r8169-100:00: attached PHY driver (mii_bus:phy_addr=r8169-100:00, irq=IGNORE)
Mar 03 17:08:21 proxmox kernel: r8169 0000:01:00.0 enp1s0: Link is Down
Mar 03 17:08:21 proxmox kernel: vmbr0: port 1(enp1s0) entered blocking state
Mar 03 17:08:21 proxmox kernel: vmbr0: port 1(enp1s0) entered forwarding state
Mar 03 17:08:22 proxmox systemd[1]: Finished Network initialization.
Mar 03 17:08:22 proxmox systemd[1]: Reached target Network.
Mar 03 17:08:22 proxmox systemd[1]: Reached target Network is Online.
Mar 03 17:08:22 proxmox systemd[1]: Starting chrony, an NTP client/server…
Mar 03 17:08:22 proxmox systemd[1]: Started Glances.
Mar 03 17:08:22 proxmox systemd[1]: Starting iSCSI initiator daemon (iscsid)…
Mar 03 17:08:22 proxmox systemd[1]: Started LXC Container Monitoring Daemon.
Mar 03 17:08:22 proxmox systemd[1]: Starting LXC network bridge setup…
Mar 03 17:08:22 proxmox systemd[1]: Starting Postfix Mail Transport Agent (instance -)…
Mar 03 17:08:22 proxmox systemd[1]: Starting Map RBD devices…
Mar 03 17:08:22 proxmox systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
Mar 03 17:08:22 proxmox systemd[1]: Starting OpenBSD Secure Shell server…
Mar 03 17:08:22 proxmox systemd[1]: Finished Map RBD devices.
Mar 03 17:08:22 proxmox kernel: bpfilter: Loaded bpfilter_umh pid 770
Mar 03 17:08:22 proxmox unknow: Started bpfilter
Mar 03 17:08:22 proxmox systemd[1]: Finished LXC network bridge setup.
Mar 03 17:08:22 proxmox iscsid[760]: iSCSI logger with pid=780 started!
Mar 03 17:08:22 proxmox systemd[1]: Started iSCSI initiator daemon (iscsid).
Mar 03 17:08:22 proxmox systemd[1]: Starting Login to default iSCSI targets…
Mar 03 17:08:22 proxmox chronyd[802]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Mar 03 17:08:22 proxmox chronyd[802]: Frequency 13.974 +/- 0.024 ppm read from /var/lib/chrony/chrony.drift
Mar 03 17:08:22 proxmox sshd[798]: Server listening on 0.0.0.0 port 22.
Mar 03 17:08:22 proxmox systemd[1]: Started OpenBSD Secure Shell server.
Mar 03 17:08:22 proxmox sshd[798]: Server listening on :: port 22.
Mar 03 17:08:22 proxmox chronyd[802]: Using right/UTC timezone to obtain leap second data
Mar 03 17:08:22 proxmox chronyd[802]: Loaded seccomp filter
Mar 03 17:08:22 proxmox systemd[1]: Started chrony, an NTP client/server.
Mar 03 17:08:22 proxmox systemd[1]: Reached target System Time Synchronized.
Mar 03 17:08:22 proxmox systemd[1]: Started Daily apt download activities.
Mar 03 17:08:22 proxmox systemd[1]: Started Daily apt upgrade and clean activities.
Mar 03 17:08:22 proxmox systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems.
Mar 03 17:08:22 proxmox systemd[1]: Started Discard unused blocks once a week.
Mar 03 17:08:22 proxmox systemd[1]: Started Daily rotation of log files.
Mar 03 17:08:22 proxmox systemd[1]: Started Daily man-db regeneration.
Mar 03 17:08:22 proxmox systemd[1]: Started Daily PVE download activities.
Mar 03 17:08:22 proxmox systemd[1]: Started Proxmox VE replication runner.
Mar 03 17:08:22 proxmox systemd[1]: Reached target Timers.
Mar 03 17:08:22 proxmox iscsiadm[804]: iscsiadm: No records found
Mar 03 17:08:22 proxmox systemd[1]: Finished Login to default iSCSI targets.
Mar 03 17:08:22 proxmox systemd[1]: Reached target Remote File Systems (Pre).
Mar 03 17:08:22 proxmox systemd[1]: Reached target Remote File Systems.
Mar 03 17:08:22 proxmox systemd[1]: Reached target PVE Storage Target.
Mar 03 17:08:22 proxmox systemd[1]: Finished Availability of block devices.
Mar 03 17:08:22 proxmox systemd[1]: Starting LSB: disk temperature monitoring daemon…
Mar 03 17:08:22 proxmox systemd[1]: Starting LXC Container Initialization and Autoboot Code…
Mar 03 17:08:22 proxmox systemd[1]: Starting LSB: start or stop rrdcached…
Mar 03 17:08:22 proxmox systemd[1]: Starting Permit User Sessions…
Mar 03 17:08:22 proxmox systemd[1]: Starting LSB: start and stop vzeventd…
Mar 03 17:08:22 proxmox systemd[1]: Finished Permit User Sessions.
Mar 03 17:08:22 proxmox audit[821]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« /usr/bin/lxc-start » pid=821 comm=« apparmor_parser »
Mar 03 17:08:22 proxmox systemd[1]: Started Getty on tty1.
Mar 03 17:08:22 proxmox systemd[1]: Reached target Login Prompts.
Mar 03 17:08:22 proxmox systemd[1]: Started LSB: start and stop vzeventd.
Mar 03 17:08:22 proxmox systemd[1]: Starting LSB: OpenVZ startup script…
Mar 03 17:08:22 proxmox systemd[1]: Started LSB: disk temperature monitoring daemon.
Mar 03 17:08:22 proxmox vz[838]: Running kernel is not an OpenVZ kernel
Mar 03 17:08:22 proxmox systemd[1]: Started LSB: OpenVZ startup script.
Mar 03 17:08:22 proxmox audit[832]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default » pid=832 comm=« apparmor_parser »
Mar 03 17:08:22 proxmox audit[832]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default-cgns » pid=832 comm=« apparmor_parser »
Mar 03 17:08:22 proxmox audit[832]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default-with-mounting » pid=832 comm=« apparmor_parser »
Mar 03 17:08:22 proxmox audit[832]: AVC apparmor=« STATUS » operation=« profile_replace » info=« same as current profile, skipping » profile=« unconfined » name=« lxc-container-default-with-nesting » pid=832 comm=« apparmor_parser »
Mar 03 17:08:22 proxmox systemd[1]: Finished LXC Container Initialization and Autoboot Code.
Mar 03 17:08:22 proxmox rrdcached[810]: rrdcached started.
Mar 03 17:08:22 proxmox systemd[1]: Started LSB: start or stop rrdcached.
Mar 03 17:08:22 proxmox systemd[1]: Starting The Proxmox VE cluster filesystem…
Mar 03 17:08:22 proxmox kernel: vmbr0: port 1(enp1s0) entered disabled state
Mar 03 17:08:22 proxmox postfix/postfix-script[931]: warning: symlink leaves directory: /etc/postfix/./makedefs.out
Mar 03 17:08:22 proxmox postfix/postfix-script[967]: starting the Postfix mail system
Mar 03 17:08:22 proxmox postfix/master[969]: daemon started – version 3.5.6, configuration /etc/postfix
Mar 03 17:08:22 proxmox systemd[1]: Started Postfix Mail Transport Agent (instance -).
Mar 03 17:08:22 proxmox systemd[1]: Starting Postfix Mail Transport Agent…
Mar 03 17:08:22 proxmox systemd[1]: Finished Postfix Mail Transport Agent.
Mar 03 17:08:23 proxmox iscsid[780]: iSCSI daemon with pid=781 started!
Mar 03 17:08:23 proxmox kernel: apex 0000:03:00.0: Apex performance not throttled due to temperature
Mar 03 17:08:23 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Mar 03 17:08:23 proxmox systemd[1]: Started The Proxmox VE cluster filesystem.
Mar 03 17:08:23 proxmox systemd[1]: Condition check resulted in Corosync Cluster Engine being skipped.
Mar 03 17:08:23 proxmox systemd[1]: Started Regular background program processing daemon.
Mar 03 17:08:23 proxmox systemd[1]: Starting Proxmox VE firewall…
Mar 03 17:08:23 proxmox cron[979]: (CRON) INFO (pidfile fd = 3)
Mar 03 17:08:23 proxmox systemd[1]: Starting PVE API Daemon…
Mar 03 17:08:23 proxmox systemd[1]: Starting PVE Status Daemon…
Mar 03 17:08:23 proxmox cron[979]: (CRON) INFO (Running @reboot jobs)
Mar 03 17:08:24 proxmox pve-firewall[987]: starting server
Mar 03 17:08:24 proxmox pvestatd[989]: starting server
Mar 03 17:08:24 proxmox systemd[1]: Started Proxmox VE firewall.
Mar 03 17:08:24 proxmox systemd[1]: Started PVE Status Daemon.
Mar 03 17:08:24 proxmox kernel: r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx
Mar 03 17:08:24 proxmox kernel: vmbr0: port 1(enp1s0) entered blocking state
Mar 03 17:08:24 proxmox kernel: vmbr0: port 1(enp1s0) entered forwarding state
Mar 03 17:08:24 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Mar 03 17:08:24 proxmox pvedaemon[1012]: starting server
Mar 03 17:08:24 proxmox pvedaemon[1012]: starting 3 worker(s)
Mar 03 17:08:24 proxmox pvedaemon[1012]: worker 1013 started
Mar 03 17:08:24 proxmox pvedaemon[1012]: worker 1014 started
Mar 03 17:08:24 proxmox pvedaemon[1012]: worker 1015 started
Mar 03 17:08:24 proxmox systemd[1]: Started PVE API Daemon.
Mar 03 17:08:25 proxmox systemd[1]: Starting PVE Cluster HA Resource Manager Daemon…
Mar 03 17:08:25 proxmox systemd[1]: Starting PVE API Proxy Server…
Mar 03 17:08:25 proxmox pve-ha-crm[1020]: starting server
Mar 03 17:08:25 proxmox pve-ha-crm[1020]: status change startup => wait_for_quorum
Mar 03 17:08:25 proxmox systemd[1]: Started PVE Cluster HA Resource Manager Daemon.
Mar 03 17:08:26 proxmox pveproxy[1021]: starting server
Mar 03 17:08:26 proxmox pveproxy[1021]: starting 3 worker(s)
Mar 03 17:08:26 proxmox pveproxy[1021]: worker 1022 started
Mar 03 17:08:26 proxmox pveproxy[1021]: worker 1023 started
Mar 03 17:08:26 proxmox pveproxy[1021]: worker 1024 started
Mar 03 17:08:26 proxmox systemd[1]: Started PVE API Proxy Server.
Mar 03 17:08:26 proxmox systemd[1]: Starting PVE Local HA Resource Manager Daemon…
Mar 03 17:08:26 proxmox systemd[1]: Starting PVE SPICE Proxy Server…
Mar 03 17:08:26 proxmox spiceproxy[1027]: starting server
Mar 03 17:08:26 proxmox spiceproxy[1027]: starting 1 worker(s)
Mar 03 17:08:26 proxmox spiceproxy[1027]: worker 1028 started
Mar 03 17:08:26 proxmox systemd[1]: Started PVE SPICE Proxy Server.
Mar 03 17:08:26 proxmox kernel: usb 1-5: new low-speed USB device number 8 using xhci_hcd
Mar 03 17:08:26 proxmox pve-ha-lrm[1029]: starting server
Mar 03 17:08:26 proxmox pve-ha-lrm[1029]: status change startup => wait_for_agent_lock
Mar 03 17:08:26 proxmox kernel: usb 1-5: New USB device found, idVendor=1241, idProduct=1603, bcdDevice= 2.80
Mar 03 17:08:26 proxmox kernel: usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 03 17:08:26 proxmox kernel: usb 1-5: Product: USB Keyboard
Mar 03 17:08:26 proxmox kernel: usb 1-5: Manufacturer:
Mar 03 17:08:26 proxmox kernel: input: USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/0003:1241:1603.0002/input/input11
Mar 03 17:08:26 proxmox systemd[1]: Started PVE Local HA Resource Manager Daemon.
Mar 03 17:08:26 proxmox systemd[1]: Starting PVE guests…
Mar 03 17:08:26 proxmox kernel: hid-generic 0003:1241:1603.0002: input,hidraw1: USB HID v1.10 Keyboard [ USB Keyboard] on usb-0000:00:14.0-5/input0
Mar 03 17:08:26 proxmox kernel: input: USB Keyboard System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:1241:1603.0003/input/input12
Mar 03 17:08:26 proxmox kernel: input: USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.1/0003:1241:1603.0003/input/input13
Mar 03 17:08:26 proxmox kernel: hid-generic 0003:1241:1603.0003: input,hidraw2: USB HID v1.10 Device [ USB Keyboard] on usb-0000:00:14.0-5/input1
Mar 03 17:08:26 proxmox kernel: usbcore: registered new interface driver usbkbd
Mar 03 17:08:26 proxmox systemd-logind[653]: Watching system buttons on /dev/input/event12 ( USB Keyboard System Control)
Mar 03 17:08:26 proxmox systemd-logind[653]: Watching system buttons on /dev/input/event11 ( USB Keyboard)
Mar 03 17:08:27 proxmox pve-guests[1033]: root@pam starting task UPID:proxmox:0000040C:000007F6:65E4A07B:startall::root@pam:
Mar 03 17:08:27 proxmox pvesh[1033]: Starting VM 400
Mar 03 17:08:27 proxmox pve-guests[1036]: root@pam starting task UPID:proxmox:0000040D:000007F8:65E4A07B:qmstart:400:root@pam:
Mar 03 17:08:27 proxmox pve-guests[1037]: start VM 400: UPID:proxmox:0000040D:000007F8:65E4A07B:qmstart:400:root@pam:
Mar 03 17:08:28 proxmox systemd[1]: Created slice qemu.slice.
Mar 03 17:08:28 proxmox systemd[1]: Started 400.scope.
Mar 03 17:08:28 proxmox kernel: 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 03 17:08:28 proxmox systemd-udevd[449]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:28 proxmox kernel: device tap400i0 entered promiscuous mode
Mar 03 17:08:28 proxmox systemd-udevd[463]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:28 proxmox systemd-udevd[463]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:28 proxmox systemd-udevd[449]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 1(fwln400i0) entered blocking state
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 1(fwln400i0) entered disabled state
Mar 03 17:08:28 proxmox kernel: device fwln400i0 entered promiscuous mode
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 1(fwln400i0) entered blocking state
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 1(fwln400i0) entered forwarding state
Mar 03 17:08:28 proxmox kernel: vmbr0: port 2(fwpr400p0) entered blocking state
Mar 03 17:08:28 proxmox kernel: vmbr0: port 2(fwpr400p0) entered disabled state
Mar 03 17:08:28 proxmox kernel: device fwpr400p0 entered promiscuous mode
Mar 03 17:08:28 proxmox kernel: vmbr0: port 2(fwpr400p0) entered blocking state
Mar 03 17:08:28 proxmox kernel: vmbr0: port 2(fwpr400p0) entered forwarding state
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 2(tap400i0) entered blocking state
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 2(tap400i0) entered disabled state
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 2(tap400i0) entered blocking state
Mar 03 17:08:28 proxmox kernel: fwbr400i0: port 2(tap400i0) entered forwarding state
Mar 03 17:08:28 proxmox kernel: ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
Mar 03 17:08:28 proxmox kernel: ftdi_sio 1-2:1.0: device disconnected
Mar 03 17:08:28 proxmox kernel: cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
Mar 03 17:08:28 proxmox kernel: cp210x 1-1:1.0: device disconnected
Mar 03 17:08:28 proxmox systemd[1]: Starting Load/Save RF Kill Switch Status…
Mar 03 17:08:28 proxmox systemd[1]: Stopped target Bluetooth.
Mar 03 17:08:28 proxmox systemd[1]: Started Load/Save RF Kill Switch Status.
Mar 03 17:08:32 proxmox chronyd[802]: Selected source 162.159.200.1 (2.debian.pool.ntp.org)
Mar 03 17:08:32 proxmox chronyd[802]: System clock TAI offset set to 37 seconds
Mar 03 17:08:32 proxmox pvesh[1033]: Starting CT 901
Mar 03 17:08:32 proxmox pve-guests[1036]: root@pam starting task UPID:proxmox:00000443:000009ED:65E4A080:vzstart:901:root@pam:
Mar 03 17:08:32 proxmox pve-guests[1091]: starting CT 901: UPID:proxmox:00000443:000009ED:65E4A080:vzstart:901:root@pam:
Mar 03 17:08:32 proxmox systemd[1]: Created slice PVE LXC Container Slice.
Mar 03 17:08:32 proxmox systemd[1]: Started PVE LXC Container: 901.
Mar 03 17:08:33 proxmox kernel: loop0: detected capacity change from 0 to 20971520
Mar 03 17:08:33 proxmox kernel: EXT4-fs warning (device loop0): ext4_multi_mount_protect:320: MMP interval 42 higher than expected, please wait.

Mar 03 17:08:33 proxmox systemd[1]: systemd-rfkill.service: Succeeded.
Mar 03 17:08:36 proxmox kernel: usb 1-9: reset full-speed USB device number 7 using xhci_hcd
Mar 03 17:08:36 proxmox kernel: usb 1-3: reset full-speed USB device number 4 using xhci_hcd
Mar 03 17:08:36 proxmox kernel: usb 1-4: reset full-speed USB device number 5 using xhci_hcd
Mar 03 17:08:37 proxmox kernel: usb 1-2: reset full-speed USB device number 3 using xhci_hcd
Mar 03 17:08:37 proxmox kernel: usb 1-1: reset full-speed USB device number 2 using xhci_hcd
Mar 03 17:08:38 proxmox kernel: [00] BAD 00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
Mar 03 17:08:38 proxmox kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Mar 03 17:08:38 proxmox kernel: [00] BAD ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 97
Mar 03 17:08:38 proxmox kernel: fbcon: i915drmfb (fb0) is primary device
Mar 03 17:08:38 proxmox kernel: Console: switching to colour frame buffer device 128x48
Mar 03 17:08:38 proxmox kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Mar 03 17:09:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 17:09:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 17:09:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 17:09:15 proxmox QEMU[1051]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Mar 03 17:09:15 proxmox QEMU[1051]: kvm: libusb_release_interface: -4 [NO_DEVICE]
Mar 03 17:09:15 proxmox kernel: usb 1-4: USB disconnect, device number 5
Mar 03 17:09:15 proxmox kernel: usb 1-4: new full-speed USB device number 9 using xhci_hcd
Mar 03 17:09:15 proxmox kernel: usb 1-4: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Mar 03 17:09:15 proxmox kernel: usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Mar 03 17:09:15 proxmox kernel: cdc_acm 1-4:1.0: ttyACM0: USB ACM device
Mar 03 17:09:17 proxmox kernel: usb 1-4: reset full-speed USB device number 9 using xhci_hcd
Mar 03 17:09:18 proxmox kernel: EXT4-fs (loop0): 1 orphan inode deleted
Mar 03 17:09:18 proxmox kernel: EXT4-fs (loop0): recovery complete
Mar 03 17:09:18 proxmox kernel: EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 03 17:09:18 proxmox audit[1256]: AVC apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-901_</var/lib/lxc> » pid=1256 comm=« apparmor_parser »
Mar 03 17:09:18 proxmox kernel: kauditd_printk_skb: 8 callbacks suppressed
Mar 03 17:09:18 proxmox kernel: audit: type=1400 audit(1709482158.285:20): apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-901_</var/lib/lxc> » pid=1256 comm=« apparmor_parser »
Mar 03 17:09:18 proxmox systemd-udevd[1243]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:09:18 proxmox systemd-udevd[1243]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:09:18 proxmox systemd-udevd[1243]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:09:18 proxmox systemd-udevd[1243]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:09:18 proxmox systemd-udevd[1244]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:09:18 proxmox systemd-udevd[1244]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:09:18 proxmox kernel: fwbr901i0: port 1(fwln901i0) entered blocking state
Mar 03 17:09:18 proxmox kernel: fwbr901i0: port 1(fwln901i0) entered disabled state
Mar 03 17:09:18 proxmox kernel: device fwln901i0 entered promiscuous mode
Mar 03 17:09:18 proxmox kernel: fwbr901i0: port 1(fwln901i0) entered blocking state
Mar 03 17:09:18 proxmox kernel: fwbr901i0: port 1(fwln901i0) entered forwarding state
Mar 03 17:09:18 proxmox kernel: vmbr0: port 3(fwpr901p0) entered blocking state
Mar 03 17:09:18 proxmox kernel: vmbr0: port 3(fwpr901p0) entered disabled state
Mar 03 17:09:18 proxmox kernel: device fwpr901p0 entered promiscuous mode
Mar 03 17:09:18 proxmox kernel: vmbr0: port 3(fwpr901p0) entered blocking state
Mar 03 17:09:18 proxmox kernel: vmbr0: port 3(fwpr901p0) entered forwarding state
Mar 03 17:09:18 proxmox kernel: fwbr901i0: port 2(veth901i0) entered blocking state
Mar 03 17:09:18 proxmox kernel: fwbr901i0: port 2(veth901i0) entered disabled state
Mar 03 17:09:18 proxmox kernel: device veth901i0 entered promiscuous mode
Mar 03 17:09:18 proxmox kernel: eth0: renamed from vethhlS7aK
Mar 03 17:09:19 proxmox pvestatd[989]: modified cpu set for lxc/901: 0-1
Mar 03 17:09:19 proxmox pvestatd[989]: status update time (44.781 seconds)
Mar 03 17:09:19 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/local-lvm: -1
Mar 03 17:09:19 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/local: -1
Mar 03 17:09:19 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/SSD2: -1
Mar 03 17:09:19 proxmox pvesh[1033]: Starting CT 902
Mar 03 17:09:19 proxmox pve-guests[1036]: root@pam starting task UPID:proxmox:00000537:00001C4B:65E4A0AF:vzstart:902:root@pam:
Mar 03 17:09:19 proxmox pve-guests[1335]: starting CT 902: UPID:proxmox:00000537:00001C4B:65E4A0AF:vzstart:902:root@pam:
Mar 03 17:09:19 proxmox systemd[1]: Started PVE LXC Container: 902.
Mar 03 17:09:20 proxmox kernel: loop1: detected capacity change from 0 to 20971520
Mar 03 17:09:20 proxmox kernel: EXT4-fs warning (device loop1): ext4_multi_mount_protect:320: MMP interval 42 higher than expected, please wait.

Mar 03 17:09:23 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 03 17:09:23 proxmox kernel: fwbr901i0: port 2(veth901i0) entered blocking state
Mar 03 17:09:23 proxmox kernel: fwbr901i0: port 2(veth901i0) entered forwarding state
Mar 03 17:09:26 proxmox kernel: Initializing XFRM netlink socket
Mar 03 17:09:26 proxmox kernel: docker0: port 1(veth0c020c1) entered blocking state
Mar 03 17:09:26 proxmox kernel: docker0: port 1(veth0c020c1) entered disabled state
Mar 03 17:09:26 proxmox kernel: device veth0c020c1 entered promiscuous mode
Mar 03 17:09:26 proxmox kernel: docker0: port 1(veth0c020c1) entered blocking state
Mar 03 17:09:26 proxmox kernel: docker0: port 1(veth0c020c1) entered forwarding state
Mar 03 17:09:26 proxmox kernel: docker0: port 1(veth0c020c1) entered disabled state
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 1(veth1b7c80c) entered blocking state
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 1(veth1b7c80c) entered disabled state
Mar 03 17:09:26 proxmox kernel: device veth1b7c80c entered promiscuous mode
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 1(veth1b7c80c) entered blocking state
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 1(veth1b7c80c) entered forwarding state
Mar 03 17:09:26 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-045f24fd3ec3: link becomes ready
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 1(veth1b7c80c) entered disabled state
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 2(veth7946805) entered blocking state
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 2(veth7946805) entered disabled state
Mar 03 17:09:26 proxmox kernel: device veth7946805 entered promiscuous mode
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 2(veth7946805) entered blocking state
Mar 03 17:09:26 proxmox kernel: br-045f24fd3ec3: port 2(veth7946805) entered forwarding state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 3(veth3d0c152) entered blocking state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 3(veth3d0c152) entered disabled state
Mar 03 17:09:27 proxmox kernel: device veth3d0c152 entered promiscuous mode
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 3(veth3d0c152) entered blocking state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 3(veth3d0c152) entered forwarding state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 2(veth7946805) entered disabled state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 3(veth3d0c152) entered disabled state
Mar 03 17:09:27 proxmox kernel: eth0: renamed from veth46b8968
Mar 03 17:09:27 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1b7c80c: link becomes ready
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 1(veth1b7c80c) entered blocking state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 1(veth1b7c80c) entered forwarding state
Mar 03 17:09:27 proxmox kernel: eth0: renamed from veth93a2a78
Mar 03 17:09:27 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth0c020c1: link becomes ready
Mar 03 17:09:27 proxmox kernel: docker0: port 1(veth0c020c1) entered blocking state
Mar 03 17:09:27 proxmox kernel: docker0: port 1(veth0c020c1) entered forwarding state
Mar 03 17:09:27 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 03 17:09:27 proxmox kernel: eth0: renamed from veth71af166
Mar 03 17:09:27 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3d0c152: link becomes ready
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 3(veth3d0c152) entered blocking state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 3(veth3d0c152) entered forwarding state
Mar 03 17:09:27 proxmox kernel: eth0: renamed from vethac832a5
Mar 03 17:09:27 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7946805: link becomes ready
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 2(veth7946805) entered blocking state
Mar 03 17:09:27 proxmox kernel: br-045f24fd3ec3: port 2(veth7946805) entered forwarding state
Mar 03 17:09:33 proxmox pvedaemon[1015]: root@pam successful auth for user ‹ ha_audit@pve ›
Mar 03 17:09:38 proxmox chronyd[802]: Selected source 162.19.224.29 (2.debian.pool.ntp.org)
Mar 03 17:10:00 proxmox systemd[1]: Starting Proxmox VE replication runner…

Dapolux · Mars 3, 2024, 5:24

La suite

Mar 03 17:10:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 17:10:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 17:10:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 17:10:05 proxmox kernel: EXT4-fs (loop1): warning: mounting fs with errors, running e2fsck is recommended
Mar 03 17:10:05 proxmox kernel: EXT4-fs (loop1): Errors on filesystem, clearing orphan list.

Mar 03 17:10:05 proxmox kernel: EXT4-fs (loop1): recovery complete
Mar 03 17:10:05 proxmox kernel: EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 03 17:10:05 proxmox audit[2822]: AVC apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-902_</var/lib/lxc> » pid=2822 comm=« apparmor_parser »
Mar 03 17:10:05 proxmox kernel: audit: type=1400 audit(1709482205.384:21): apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-902_</var/lib/lxc> » pid=2822 comm=« apparmor_parser »
Mar 03 17:10:05 proxmox systemd-udevd[2827]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:05 proxmox systemd-udevd[2827]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:10:05 proxmox systemd-udevd[2827]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:05 proxmox systemd-udevd[2827]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:05 proxmox systemd-udevd[2829]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:05 proxmox systemd-udevd[2829]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:10:05 proxmox kernel: fwbr902i0: port 1(fwln902i0) entered blocking state
Mar 03 17:10:05 proxmox kernel: fwbr902i0: port 1(fwln902i0) entered disabled state
Mar 03 17:10:05 proxmox kernel: device fwln902i0 entered promiscuous mode
Mar 03 17:10:05 proxmox kernel: fwbr902i0: port 1(fwln902i0) entered blocking state
Mar 03 17:10:05 proxmox kernel: fwbr902i0: port 1(fwln902i0) entered forwarding state
Mar 03 17:10:05 proxmox kernel: vmbr0: port 4(fwpr902p0) entered blocking state
Mar 03 17:10:05 proxmox kernel: vmbr0: port 4(fwpr902p0) entered disabled state
Mar 03 17:10:05 proxmox kernel: device fwpr902p0 entered promiscuous mode
Mar 03 17:10:05 proxmox kernel: vmbr0: port 4(fwpr902p0) entered blocking state
Mar 03 17:10:05 proxmox kernel: vmbr0: port 4(fwpr902p0) entered forwarding state
Mar 03 17:10:05 proxmox kernel: fwbr902i0: port 2(veth902i0) entered blocking state
Mar 03 17:10:05 proxmox kernel: fwbr902i0: port 2(veth902i0) entered disabled state
Mar 03 17:10:05 proxmox kernel: device veth902i0 entered promiscuous mode
Mar 03 17:10:05 proxmox kernel: eth0: renamed from vethu32Qsl
Mar 03 17:10:06 proxmox pveproxy[1022]: proxy detected vanished client connection
Mar 03 17:10:06 proxmox pvestatd[989]: status update time (36.778 seconds)
Mar 03 17:10:06 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/local-lvm: -1
Mar 03 17:10:06 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/SSD2: -1
Mar 03 17:10:06 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/local: -1
Mar 03 17:10:06 proxmox pvesh[1033]: Starting CT 903
Mar 03 17:10:06 proxmox pve-guests[1036]: root@pam starting task UPID:proxmox:00000B6E:00002EA9:65E4A0DE:vzstart:903:root@pam:
Mar 03 17:10:06 proxmox pve-guests[2926]: starting CT 903: UPID:proxmox:00000B6E:00002EA9:65E4A0DE:vzstart:903:root@pam:
Mar 03 17:10:06 proxmox systemd[1]: Started PVE LXC Container: 903.
Mar 03 17:10:07 proxmox kernel: loop2: detected capacity change from 0 to 20971520
Mar 03 17:10:07 proxmox kernel: EXT4-fs warning (device loop2): ext4_multi_mount_protect:320: MMP interval 42 higher than expected, please wait.

Mar 03 17:10:08 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 03 17:10:08 proxmox kernel: fwbr902i0: port 2(veth902i0) entered blocking state
Mar 03 17:10:08 proxmox kernel: fwbr902i0: port 2(veth902i0) entered forwarding state
Mar 03 17:10:18 proxmox kernel: br-b48ed13f4f07: port 1(vethb726618) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-b48ed13f4f07: port 1(vethb726618) entered disabled state
Mar 03 17:10:18 proxmox kernel: device vethb726618 entered promiscuous mode
Mar 03 17:10:18 proxmox kernel: br-b48ed13f4f07: port 1(vethb726618) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-b48ed13f4f07: port 1(vethb726618) entered forwarding state
Mar 03 17:10:18 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-b48ed13f4f07: link becomes ready
Mar 03 17:10:18 proxmox kernel: br-b48ed13f4f07: port 1(vethb726618) entered disabled state
Mar 03 17:10:18 proxmox kernel: br-676c4fb05ea4: port 1(vethd1c1ebd) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-676c4fb05ea4: port 1(vethd1c1ebd) entered disabled state
Mar 03 17:10:18 proxmox kernel: device vethd1c1ebd entered promiscuous mode
Mar 03 17:10:18 proxmox kernel: br-676c4fb05ea4: port 1(vethd1c1ebd) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-676c4fb05ea4: port 1(vethd1c1ebd) entered forwarding state
Mar 03 17:10:18 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-676c4fb05ea4: link becomes ready
Mar 03 17:10:18 proxmox kernel: br-676c4fb05ea4: port 1(vethd1c1ebd) entered disabled state
Mar 03 17:10:18 proxmox kernel: docker0: port 1(veth9eef95f) entered blocking state
Mar 03 17:10:18 proxmox kernel: docker0: port 1(veth9eef95f) entered disabled state
Mar 03 17:10:18 proxmox kernel: device veth9eef95f entered promiscuous mode
Mar 03 17:10:18 proxmox kernel: docker0: port 1(veth9eef95f) entered blocking state
Mar 03 17:10:18 proxmox kernel: docker0: port 1(veth9eef95f) entered forwarding state
Mar 03 17:10:18 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 03 17:10:18 proxmox kernel: docker0: port 1(veth9eef95f) entered disabled state
Mar 03 17:10:18 proxmox kernel: br-3b1473ec66d8: port 1(veth5ef211f) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-3b1473ec66d8: port 1(veth5ef211f) entered disabled state
Mar 03 17:10:18 proxmox kernel: device veth5ef211f entered promiscuous mode
Mar 03 17:10:18 proxmox kernel: br-3b1473ec66d8: port 1(veth5ef211f) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-3b1473ec66d8: port 1(veth5ef211f) entered forwarding state
Mar 03 17:10:18 proxmox kernel: br-3b1473ec66d8: port 1(veth5ef211f) entered disabled state
Mar 03 17:10:18 proxmox kernel: br-b1546a225671: port 1(veth1e254cb) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-b1546a225671: port 1(veth1e254cb) entered disabled state
Mar 03 17:10:18 proxmox kernel: device veth1e254cb entered promiscuous mode
Mar 03 17:10:18 proxmox kernel: br-b1546a225671: port 1(veth1e254cb) entered blocking state
Mar 03 17:10:18 proxmox kernel: br-b1546a225671: port 1(veth1e254cb) entered forwarding state
Mar 03 17:10:18 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-b1546a225671: link becomes ready
Mar 03 17:10:18 proxmox kernel: br-b1546a225671: port 1(veth1e254cb) entered disabled state
Mar 03 17:10:19 proxmox kernel: eth0: renamed from veth98e74ed
Mar 03 17:10:19 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1e254cb: link becomes ready
Mar 03 17:10:19 proxmox kernel: br-b1546a225671: port 1(veth1e254cb) entered blocking state
Mar 03 17:10:19 proxmox kernel: br-b1546a225671: port 1(veth1e254cb) entered forwarding state
Mar 03 17:10:19 proxmox kernel: eth0: renamed from veth802bec8
Mar 03 17:10:19 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9eef95f: link becomes ready
Mar 03 17:10:19 proxmox kernel: docker0: port 1(veth9eef95f) entered blocking state
Mar 03 17:10:19 proxmox kernel: docker0: port 1(veth9eef95f) entered forwarding state
Mar 03 17:10:19 proxmox kernel: eth0: renamed from veth0677498
Mar 03 17:10:19 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5ef211f: link becomes ready
Mar 03 17:10:19 proxmox kernel: br-3b1473ec66d8: port 1(veth5ef211f) entered blocking state
Mar 03 17:10:19 proxmox kernel: br-3b1473ec66d8: port 1(veth5ef211f) entered forwarding state
Mar 03 17:10:19 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-3b1473ec66d8: link becomes ready
Mar 03 17:10:20 proxmox kernel: eth0: renamed from veth80ce3fa
Mar 03 17:10:20 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd1c1ebd: link becomes ready
Mar 03 17:10:20 proxmox kernel: br-676c4fb05ea4: port 1(vethd1c1ebd) entered blocking state
Mar 03 17:10:20 proxmox kernel: br-676c4fb05ea4: port 1(vethd1c1ebd) entered forwarding state
Mar 03 17:10:20 proxmox kernel: eth0: renamed from vethe932e2f
Mar 03 17:10:20 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethb726618: link becomes ready
Mar 03 17:10:20 proxmox kernel: br-b48ed13f4f07: port 1(vethb726618) entered blocking state
Mar 03 17:10:20 proxmox kernel: br-b48ed13f4f07: port 1(vethb726618) entered forwarding state
Mar 03 17:10:52 proxmox kernel: EXT4-fs (loop2): 2 orphan inodes deleted
Mar 03 17:10:52 proxmox kernel: EXT4-fs (loop2): recovery complete
Mar 03 17:10:52 proxmox kernel: EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 03 17:10:52 proxmox audit[5318]: AVC apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-903_</var/lib/lxc> » pid=5318 comm=« apparmor_parser »
Mar 03 17:10:52 proxmox kernel: audit: type=1400 audit(1709482252.752:22): apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-903_</var/lib/lxc> » pid=5318 comm=« apparmor_parser »
Mar 03 17:10:52 proxmox systemd-udevd[5323]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:52 proxmox systemd-udevd[5323]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:10:53 proxmox systemd-udevd[5325]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:10:53 proxmox systemd-udevd[5325]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:53 proxmox systemd-udevd[5323]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:53 proxmox systemd-udevd[5325]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:10:53 proxmox kernel: fwbr903i0: port 1(fwln903i0) entered blocking state
Mar 03 17:10:53 proxmox kernel: fwbr903i0: port 1(fwln903i0) entered disabled state
Mar 03 17:10:53 proxmox kernel: device fwln903i0 entered promiscuous mode
Mar 03 17:10:53 proxmox kernel: fwbr903i0: port 1(fwln903i0) entered blocking state
Mar 03 17:10:53 proxmox kernel: fwbr903i0: port 1(fwln903i0) entered forwarding state
Mar 03 17:10:53 proxmox kernel: vmbr0: port 5(fwpr903p0) entered blocking state
Mar 03 17:10:53 proxmox kernel: vmbr0: port 5(fwpr903p0) entered disabled state
Mar 03 17:10:53 proxmox kernel: device fwpr903p0 entered promiscuous mode
Mar 03 17:10:53 proxmox kernel: vmbr0: port 5(fwpr903p0) entered blocking state
Mar 03 17:10:53 proxmox kernel: vmbr0: port 5(fwpr903p0) entered forwarding state
Mar 03 17:10:53 proxmox kernel: fwbr903i0: port 2(veth903i0) entered blocking state
Mar 03 17:10:53 proxmox kernel: fwbr903i0: port 2(veth903i0) entered disabled state
Mar 03 17:10:53 proxmox kernel: device veth903i0 entered promiscuous mode
Mar 03 17:10:53 proxmox kernel: eth0: renamed from vethBbJqgV
Mar 03 17:10:53 proxmox pvestatd[989]: modified cpu set for lxc/902: 2,5
Mar 03 17:10:53 proxmox pvesh[1033]: Starting CT 905
Mar 03 17:10:53 proxmox pve-guests[1036]: root@pam starting task UPID:proxmox:00001512:00004107:65E4A10D:vzstart:905:root@pam:
Mar 03 17:10:53 proxmox pve-guests[5394]: starting CT 905: UPID:proxmox:00001512:00004107:65E4A10D:vzstart:905:root@pam:
Mar 03 17:10:53 proxmox systemd[1]: Started PVE LXC Container: 905.
Mar 03 17:10:54 proxmox kernel: loop3: detected capacity change from 0 to 83886080
Mar 03 17:10:54 proxmox kernel: EXT4-fs warning (device loop3): ext4_multi_mount_protect:320: MMP interval 42 higher than expected, please wait.

Mar 03 17:10:56 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 03 17:10:56 proxmox kernel: fwbr903i0: port 2(veth903i0) entered blocking state
Mar 03 17:10:56 proxmox kernel: fwbr903i0: port 2(veth903i0) entered forwarding state
Mar 03 17:10:56 proxmox kernel: IPv4: martian source 255.255.255.255 from 192.168.1.5, on dev eth0
Mar 03 17:10:56 proxmox kernel: ll header: 00000000: ff ff ff ff ff ff 74 ac b9 96 30 a0 08 00
Mar 03 17:11:00 proxmox pvedaemon[1014]: root@pam successful auth for user ‹ dapolux@pam ›
Mar 03 17:11:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 17:11:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 17:11:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 17:11:04 proxmox kernel: br-9c8490b70020: port 1(vethe308bd6) entered blocking state
Mar 03 17:11:04 proxmox kernel: br-9c8490b70020: port 1(vethe308bd6) entered disabled state
Mar 03 17:11:04 proxmox kernel: device vethe308bd6 entered promiscuous mode
Mar 03 17:11:04 proxmox kernel: br-9c8490b70020: port 1(vethe308bd6) entered blocking state
Mar 03 17:11:04 proxmox kernel: br-9c8490b70020: port 1(vethe308bd6) entered forwarding state
Mar 03 17:11:04 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-9c8490b70020: link becomes ready
Mar 03 17:11:04 proxmox kernel: br-9c8490b70020: port 1(vethe308bd6) entered disabled state
Mar 03 17:11:04 proxmox kernel: docker0: port 1(veth94b9486) entered blocking state
Mar 03 17:11:04 proxmox kernel: docker0: port 1(veth94b9486) entered disabled state
Mar 03 17:11:04 proxmox kernel: device veth94b9486 entered promiscuous mode
Mar 03 17:11:04 proxmox kernel: docker0: port 1(veth94b9486) entered blocking state
Mar 03 17:11:04 proxmox kernel: docker0: port 1(veth94b9486) entered forwarding state
Mar 03 17:11:04 proxmox kernel: docker0: port 1(veth94b9486) entered disabled state
Mar 03 17:11:05 proxmox kernel: br-9c8490b70020: port 2(veth086c4ba) entered blocking state
Mar 03 17:11:05 proxmox kernel: br-9c8490b70020: port 2(veth086c4ba) entered disabled state
Mar 03 17:11:05 proxmox kernel: device veth086c4ba entered promiscuous mode
Mar 03 17:11:05 proxmox kernel: br-9c8490b70020: port 2(veth086c4ba) entered blocking state
Mar 03 17:11:05 proxmox kernel: br-9c8490b70020: port 2(veth086c4ba) entered forwarding state
Mar 03 17:11:05 proxmox kernel: br-9c8490b70020: port 2(veth086c4ba) entered disabled state
Mar 03 17:11:05 proxmox kernel: eth0: renamed from veth9d85b1e
Mar 03 17:11:05 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth94b9486: link becomes ready
Mar 03 17:11:05 proxmox kernel: docker0: port 1(veth94b9486) entered blocking state
Mar 03 17:11:05 proxmox kernel: docker0: port 1(veth94b9486) entered forwarding state
Mar 03 17:11:05 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 03 17:11:06 proxmox kernel: eth0: renamed from vethd85162c
Mar 03 17:11:06 proxmox kernel: eth0: renamed from veth92ecfcd
Mar 03 17:11:06 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe308bd6: link becomes ready
Mar 03 17:11:06 proxmox kernel: br-9c8490b70020: port 1(vethe308bd6) entered blocking state
Mar 03 17:11:06 proxmox kernel: br-9c8490b70020: port 1(vethe308bd6) entered forwarding state
Mar 03 17:11:06 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth086c4ba: link becomes ready
Mar 03 17:11:06 proxmox kernel: br-9c8490b70020: port 2(veth086c4ba) entered blocking state
Mar 03 17:11:06 proxmox kernel: br-9c8490b70020: port 2(veth086c4ba) entered forwarding state
Mar 03 17:11:09 proxmox kernel: ata2.00: exception Emask 0x50 SAct 0x100020 SErr 0x480900 action 0x6 frozen
Mar 03 17:11:09 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:11:09 proxmox kernel: ata2: SError: { UnrecovData HostInt 10B8B Handshk }
Mar 03 17:11:09 proxmox kernel: ata2.00: failed command: READ FPDMA QUEUED
Mar 03 17:11:09 proxmox kernel: ata2.00: cmd 60/18:28:08:35:28/00:00:02:00:00/40 tag 5 ncq dma 12288 in
res 40/00:a0:98:9c:e0/00:00:07:00:00/40 Emask 0x50 (ATA bus error)
Mar 03 17:11:09 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:11:09 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:11:09 proxmox kernel: ata2.00: cmd 61/08:a0:98:9c:e0/00:00:07:00:00/40 tag 20 ncq dma 4096 out
res 40/00:a0:98:9c:e0/00:00:07:00:00/40 Emask 0x50 (ATA bus error)
Mar 03 17:11:09 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:11:09 proxmox kernel: ata2: hard resetting link
Mar 03 17:11:10 proxmox kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 03 17:11:10 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:11:10 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:11:10 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:11:10 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:11:10 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:11:10 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:11:10 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:11:10 proxmox kernel: sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Mar 03 17:11:10 proxmox kernel: sd 1:0:0:0: [sdb] tag#5 Sense Key : Illegal Request [current]
Mar 03 17:11:10 proxmox kernel: sd 1:0:0:0: [sdb] tag#5 Add. Sense: Unaligned write command
Mar 03 17:11:10 proxmox kernel: sd 1:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 02 28 35 08 00 00 18 00
Mar 03 17:11:10 proxmox kernel: blk_update_request: I/O error, dev sdb, sector 36189448 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Mar 03 17:11:10 proxmox kernel: ata2: EH complete
Mar 03 17:11:34 proxmox pveproxy[1023]: proxy detected vanished client connection
Mar 03 17:11:39 proxmox kernel: EXT4-fs (loop3): 13 orphan inodes deleted
Mar 03 17:11:39 proxmox kernel: EXT4-fs (loop3): recovery complete
Mar 03 17:11:39 proxmox kernel: EXT4-fs (loop3): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 03 17:11:39 proxmox audit[14380]: AVC apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-905_</var/lib/lxc> » pid=14380 comm=« apparmor_parser »
Mar 03 17:11:39 proxmox kernel: audit: type=1400 audit(1709482299.703:23): apparmor=« STATUS » operation=« profile_load » profile=« /usr/bin/lxc-start » name=« lxc-905_</var/lib/lxc> » pid=14380 comm=« apparmor_parser »
Mar 03 17:11:39 proxmox systemd-udevd[14386]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:11:39 proxmox systemd-udevd[14386]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:11:40 proxmox systemd-udevd[14386]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:11:40 proxmox systemd-udevd[14386]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:11:40 proxmox systemd-udevd[14388]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:11:40 proxmox systemd-udevd[14388]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:11:40 proxmox kernel: fwbr905i0: port 1(fwln905i0) entered blocking state
Mar 03 17:11:40 proxmox kernel: fwbr905i0: port 1(fwln905i0) entered disabled state
Mar 03 17:11:40 proxmox kernel: device fwln905i0 entered promiscuous mode
Mar 03 17:11:40 proxmox kernel: fwbr905i0: port 1(fwln905i0) entered blocking state
Mar 03 17:11:40 proxmox kernel: fwbr905i0: port 1(fwln905i0) entered forwarding state
Mar 03 17:11:40 proxmox kernel: vmbr0: port 6(fwpr905p0) entered blocking state
Mar 03 17:11:40 proxmox kernel: vmbr0: port 6(fwpr905p0) entered disabled state
Mar 03 17:11:40 proxmox kernel: device fwpr905p0 entered promiscuous mode
Mar 03 17:11:40 proxmox kernel: vmbr0: port 6(fwpr905p0) entered blocking state
Mar 03 17:11:40 proxmox kernel: vmbr0: port 6(fwpr905p0) entered forwarding state
Mar 03 17:11:40 proxmox kernel: fwbr905i0: port 2(veth905i0) entered blocking state
Mar 03 17:11:40 proxmox kernel: fwbr905i0: port 2(veth905i0) entered disabled state
Mar 03 17:11:40 proxmox kernel: device veth905i0 entered promiscuous mode
Mar 03 17:11:40 proxmox kernel: eth0: renamed from vethbrW7cM
Mar 03 17:11:40 proxmox pvestatd[989]: status update time (83.994 seconds)
Mar 03 17:11:40 proxmox pvestatd[989]: modified cpu set for lxc/903: 6-7
Mar 03 17:11:40 proxmox pve-guests[1033]: root@pam end task UPID:proxmox:0000040C:000007F6:65E4A07B:startall::root@pam: OK
Mar 03 17:11:40 proxmox systemd[1]: Finished PVE guests.
Mar 03 17:11:40 proxmox systemd[1]: Reached target Multi-User System.
Mar 03 17:11:40 proxmox systemd[1]: Reached target Graphical Interface.
Mar 03 17:11:40 proxmox systemd[1]: Starting Update UTMP about System Runlevel Changes…
Mar 03 17:11:40 proxmox systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Mar 03 17:11:40 proxmox systemd[1]: Finished Update UTMP about System Runlevel Changes.
Mar 03 17:11:40 proxmox systemd[1]: Startup finished in 4.217s (firmware) + 7.784s (loader) + 9.918s (kernel) + 3min 23.647s (userspace) = 3min 45.567s.
Mar 03 17:11:43 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 03 17:11:43 proxmox kernel: fwbr905i0: port 2(veth905i0) entered blocking state
Mar 03 17:11:43 proxmox kernel: fwbr905i0: port 2(veth905i0) entered forwarding state
Mar 03 17:11:52 proxmox kernel: br-ee0fa267ad13: port 1(vethc614c3c) entered blocking state
Mar 03 17:11:52 proxmox kernel: br-ee0fa267ad13: port 1(vethc614c3c) entered disabled state
Mar 03 17:11:52 proxmox kernel: device vethc614c3c entered promiscuous mode
Mar 03 17:11:52 proxmox kernel: br-ee0fa267ad13: port 1(vethc614c3c) entered blocking state
Mar 03 17:11:52 proxmox kernel: br-ee0fa267ad13: port 1(vethc614c3c) entered forwarding state
Mar 03 17:11:52 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-51227156584a: link becomes ready
Mar 03 17:11:52 proxmox kernel: br-51227156584a: port 1(veth9e8ca7c) entered disabled state
Mar 03 17:11:52 proxmox kernel: docker0: port 1(vetha80af39) entered blocking state
Mar 03 17:11:52 proxmox kernel: docker0: port 1(vetha80af39) entered disabled state
Mar 03 17:11:52 proxmox kernel: device vetha80af39 entered promiscuous mode
Mar 03 17:11:52 proxmox kernel: docker0: port 1(vetha80af39) entered blocking state
Mar 03 17:11:52 proxmox kernel: docker0: port 1(vetha80af39) entered forwarding state
Mar 03 17:11:52 proxmox kernel: docker0: port 1(vetha80af39) entered disabled state
Mar 03 17:11:54 proxmox kernel: eth0: renamed from vethb9d7f09
Mar 03 17:11:54 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9e8ca7c: link becomes ready
Mar 03 17:11:54 proxmox kernel: br-51227156584a: port 1(veth9e8ca7c) entered blocking state
Mar 03 17:11:54 proxmox kernel: br-51227156584a: port 1(veth9e8ca7c) entered forwarding state
Mar 03 17:11:54 proxmox kernel: eth0: renamed from vethaedb07b
Mar 03 17:11:54 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha80af39: link becomes ready
Mar 03 17:11:54 proxmox kernel: docker0: port 1(vetha80af39) entered blocking state
Mar 03 17:11:54 proxmox kernel: docker0: port 1(vetha80af39) entered forwarding state
Mar 03 17:11:54 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 03 17:11:54 proxmox kernel: eth0: renamed from veth9699117
Mar 03 17:11:54 proxmox kernel: eth0: renamed from veth35185b6
Mar 03 17:11:54 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethead782f: link becomes ready
Mar 03 17:11:54 proxmox kernel: br-0bc34a0d234d: port 1(vethead782f) entered blocking state
Mar 03 17:11:54 proxmox kernel: br-0bc34a0d234d: port 1(vethead782f) entered forwarding state
Mar 03 17:11:54 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethc614c3c: link becomes ready
Mar 03 17:11:54 proxmox kernel: br-ee0fa267ad13: port 1(vethc614c3c) entered blocking state
Mar 03 17:11:54 proxmox kernel: br-ee0fa267ad13: port 1(vethc614c3c) entered forwarding state
Mar 03 17:12:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 17:12:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 17:12:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 17:12:29 proxmox kernel: ata2.00: exception Emask 0x10 SAct 0x7e40000 SErr 0x400100 action 0x6 frozen
Mar 03 17:12:29 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:12:29 proxmox kernel: ata2: SError: { UnrecovData Handshk }
Mar 03 17:12:29 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:12:29 proxmox kernel: ata2.00: cmd 61/18:90:28:2d:81/00:00:0e:00:00/40 tag 18 ncq dma 12288 out
res 40/00:90:28:2d:81/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:12:29 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:12:29 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:12:29 proxmox kernel: ata2.00: cmd 61/08:c8:b8:4a:81/00:00:0e:00:00/40 tag 25 ncq dma 4096 out
res 40/00:90:28:2d:81/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:12:29 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:12:29 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:12:29 proxmox kernel: ata2.00: cmd 61/90:d0:08:46:7a/00:00:09:00:00/40 tag 26 ncq dma 73728 out
res 40/00:90:28:2d:81/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:12:29 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:12:29 proxmox kernel: ata2: hard resetting link
Mar 03 17:12:29 proxmox kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 03 17:12:29 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:12:29 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:12:29 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:12:29 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:12:29 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:12:29 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:12:29 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:12:29 proxmox kernel: ata2: EH complete
Mar 03 17:13:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 17:13:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 17:13:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 17:13:40 proxmox pvedaemon[1013]: root@pam successful auth for user ‹ dapolux@pam ›
Mar 03 17:14:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 17:14:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 17:14:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 17:14:00 proxmox kernel: ata2.00: exception Emask 0x10 SAct 0x7ffe01e7 SErr 0x400100 action 0x6 frozen
Mar 03 17:14:00 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:14:00 proxmox kernel: ata2: SError: { UnrecovData Handshk }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:00:38:ef:fd/00:00:0d:00:00/40 tag 0 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:00 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:08:08:98:39/00:00:08:00:00/40 tag 1 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:00 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:10:20:98:39/00:00:08:00:00/40 tag 2 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:00 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:28:58:98:39/00:00:08:00:00/40 tag 5 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:00 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:30:78:48:3a/00:00:08:00:00/40 tag 6 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:00 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:38:b0:5f:3a/00:00:08:00:00/40 tag 7 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:00 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:40:80:a8:3a/00:00:08:00:00/40 tag 8 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:00 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:00 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:00 proxmox kernel: ata2.00: cmd 61/08:88:00:08:e4/00:00:07:00:00/40 tag 17 ncq dma 4096 out
res 40/00:40:80:a8:3a/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:01 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:01 proxmox kernel: ata2: hard resetting link
Mar 03 17:14:01 proxmox kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Mar 03 17:14:01 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:14:01 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:14:01 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:14:01 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:14:01 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:14:01 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:14:01 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:14:01 proxmox kernel: ata2: EH complete
Mar 03 17:14:04 proxmox kernel: ata2: limiting SATA link speed to 3.0 Gbps
Mar 03 17:14:04 proxmox kernel: ata2.00: exception Emask 0x10 SAct 0x800 SErr 0x400100 action 0x6 frozen
Mar 03 17:14:04 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:14:04 proxmox kernel: ata2: SError: { UnrecovData Handshk }
Mar 03 17:14:04 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:14:04 proxmox kernel: ata2.00: cmd 61/68:58:58:ce:79/00:00:09:00:00/40 tag 11 ncq dma 53248 out
res 40/00:58:58:ce:79/00:00:09:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:14:04 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:14:04 proxmox kernel: ata2: hard resetting link
Mar 03 17:14:04 proxmox kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Mar 03 17:14:04 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:14:04 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:14:04 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:14:04 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:14:04 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:14:04 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:14:04 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:14:04 proxmox kernel: ata2: EH complete
Mar 03 17:14:07 proxmox pvedaemon[1015]: dapolux@pam starting task UPID:proxmox:00013487:00008CBE:65E4A1CF:vzstart:904:dapolux@pam:
Mar 03 17:14:07 proxmox pvedaemon[78983]: starting CT 904: UPID:proxmox:00013487:00008CBE:65E4A1CF:vzstart:904:dapolux@pam:
Mar 03 17:14:07 proxmox pvedaemon[78983]: explicitly configured lxc.apparmor.profile overrides the following settings: features:nesting
Mar 03 17:14:07 proxmox systemd[1]: Started PVE LXC Container: 904.
Mar 03 17:14:08 proxmox kernel: loop4: detected capacity change from 0 to 23068672
Mar 03 17:14:08 proxmox kernel: EXT4-fs warning (device loop4): ext4_multi_mount_protect:320: MMP interval 42 higher than expected, please wait.

Mar 03 17:14:51 proxmox kernel: EXT4-fs (loop4): 1 orphan inode deleted
Mar 03 17:14:51 proxmox kernel: EXT4-fs (loop4): recovery complete
Mar 03 17:14:51 proxmox kernel: EXT4-fs (loop4): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 03 17:14:52 proxmox systemd-udevd[99929]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:14:52 proxmox systemd-udevd[99929]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:14:52 proxmox systemd-udevd[99929]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:14:52 proxmox systemd-udevd[99929]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:14:52 proxmox systemd-udevd[99932]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mar 03 17:14:52 proxmox systemd-udevd[99932]: Using default interface naming scheme ‹ v247 ›.
Mar 03 17:14:52 proxmox kernel: fwbr904i0: port 1(fwln904i0) entered blocking state
Mar 03 17:14:52 proxmox kernel: fwbr904i0: port 1(fwln904i0) entered disabled state
Mar 03 17:14:52 proxmox kernel: device fwln904i0 entered promiscuous mode
Mar 03 17:14:52 proxmox kernel: fwbr904i0: port 1(fwln904i0) entered blocking state
Mar 03 17:14:52 proxmox kernel: fwbr904i0: port 1(fwln904i0) entered forwarding state
Mar 03 17:14:52 proxmox kernel: vmbr0: port 7(fwpr904p0) entered blocking state
Mar 03 17:14:52 proxmox kernel: vmbr0: port 7(fwpr904p0) entered disabled state
Mar 03 17:14:52 proxmox kernel: device fwpr904p0 entered promiscuous mode
Mar 03 17:14:52 proxmox kernel: vmbr0: port 7(fwpr904p0) entered blocking state
Mar 03 17:14:52 proxmox kernel: vmbr0: port 7(fwpr904p0) entered forwarding state
Mar 03 17:14:52 proxmox kernel: fwbr904i0: port 2(veth904i0) entered blocking state
Mar 03 17:14:52 proxmox kernel: fwbr904i0: port 2(veth904i0) entered disabled state
Mar 03 17:14:52 proxmox kernel: device veth904i0 entered promiscuous mode
Mar 03 17:14:52 proxmox kernel: eth0: renamed from vethHpgbtB
Mar 03 17:14:52 proxmox pvedaemon[1015]: dapolux@pam end task UPID:proxmox:00013487:00008CBE:65E4A1CF:vzstart:904:dapolux@pam: OK
Mar 03 17:14:53 proxmox pvestatd[989]: status update time (43.306 seconds)
Mar 03 17:14:53 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/SSD2: -1
Mar 03 17:14:53 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/local: -1
Mar 03 17:14:53 proxmox pmxcfs[910]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/proxmox/local-lvm: -1
Mar 03 17:14:55 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 03 17:14:55 proxmox kernel: fwbr904i0: port 2(veth904i0) entered blocking state
Mar 03 17:14:55 proxmox kernel: fwbr904i0: port 2(veth904i0) entered forwarding state
Mar 03 17:14:56 proxmox pvedaemon[1013]: root@pam successful auth for user ‹ dapolux@pam ›
Mar 03 17:15:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 03 17:15:00 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 03 17:15:00 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 03 17:15:04 proxmox kernel: ata2.00: exception Emask 0x10 SAct 0x1 SErr 0x400100 action 0x6 frozen
Mar 03 17:15:04 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:15:04 proxmox kernel: ata2: SError: { UnrecovData Handshk }
Mar 03 17:15:04 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:04 proxmox kernel: ata2.00: cmd 61/08:00:10:28:af/00:00:02:00:00/40 tag 0 ncq dma 4096 out
res 40/00:00:10:28:af/00:00:02:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:04 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:04 proxmox kernel: ata2: hard resetting link
Mar 03 17:15:05 proxmox kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Mar 03 17:15:05 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:15:05 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:15:05 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:15:05 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:15:05 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:15:05 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:15:05 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:15:05 proxmox kernel: ata2: EH complete
Mar 03 17:15:05 proxmox kernel: docker0: port 1(veth8c79c64) entered blocking state
Mar 03 17:15:05 proxmox kernel: docker0: port 1(veth8c79c64) entered disabled state
Mar 03 17:15:05 proxmox kernel: device veth8c79c64 entered promiscuous mode
Mar 03 17:15:05 proxmox kernel: docker0: port 1(veth8c79c64) entered blocking state
Mar 03 17:15:05 proxmox kernel: docker0: port 1(veth8c79c64) entered forwarding state
Mar 03 17:15:05 proxmox kernel: docker0: port 1(veth8c79c64) entered disabled state
Mar 03 17:15:05 proxmox kernel: br-e14ea4ff0b15: port 1(vethaeaf6a3) entered blocking state
Mar 03 17:15:05 proxmox kernel: br-e14ea4ff0b15: port 1(vethaeaf6a3) entered disabled state
Mar 03 17:15:05 proxmox kernel: device vethaeaf6a3 entered promiscuous mode
Mar 03 17:15:05 proxmox kernel: br-e14ea4ff0b15: port 1(vethaeaf6a3) entered blocking state
Mar 03 17:15:05 proxmox kernel: br-e14ea4ff0b15: port 1(vethaeaf6a3) entered forwarding state
Mar 03 17:15:05 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br-e14ea4ff0b15: link becomes ready
Mar 03 17:15:05 proxmox kernel: br-e14ea4ff0b15: port 1(vethaeaf6a3) entered disabled state
Mar 03 17:15:06 proxmox kernel: eth0: renamed from veth8803220
Mar 03 17:15:06 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8c79c64: link becomes ready
Mar 03 17:15:06 proxmox kernel: docker0: port 1(veth8c79c64) entered blocking state
Mar 03 17:15:06 proxmox kernel: docker0: port 1(veth8c79c64) entered forwarding state
Mar 03 17:15:06 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
Mar 03 17:15:06 proxmox kernel: eth0: renamed from veth9a78389
Mar 03 17:15:06 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethaeaf6a3: link becomes ready
Mar 03 17:15:06 proxmox kernel: br-e14ea4ff0b15: port 1(vethaeaf6a3) entered blocking state
Mar 03 17:15:06 proxmox kernel: br-e14ea4ff0b15: port 1(vethaeaf6a3) entered forwarding state
Mar 03 17:15:18 proxmox kernel: EXT4-fs (loop1): error count since last fsck: 8
Mar 03 17:15:18 proxmox kernel: EXT4-fs (loop1): initial error at time 1709463680: htree_dirblock_to_tree:993: inode 552996
Mar 03 17:15:18 proxmox kernel: EXT4-fs (loop1): last error at time 1709463680: __ext4_find_entry:1535: inode 552996
Mar 03 17:15:19 proxmox kernel: x86/PAT: frigate.detecto:114585 map pfn RAM range req uncached-minus for [mem 0x427928000-0x42792bfff], got write-back
Mar 03 17:15:20 proxmox kernel: ata2.00: exception Emask 0x10 SAct 0x1 SErr 0x400100 action 0x6 frozen
Mar 03 17:15:20 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:15:20 proxmox kernel: ata2: SError: { UnrecovData Handshk }
Mar 03 17:15:20 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:20 proxmox kernel: ata2.00: cmd 61/10:00:c8:e6:04/00:00:3a:00:00/40 tag 0 ncq dma 8192 out
res 40/00:00:c8:e6:04/00:00:3a:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:20 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:20 proxmox kernel: ata2: hard resetting link
Mar 03 17:15:20 proxmox kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Mar 03 17:15:20 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:15:20 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:15:20 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:15:20 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:15:20 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:15:20 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:15:20 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:15:20 proxmox kernel: ata2: EH complete
Mar 03 17:15:29 proxmox kernel: ata2.00: exception Emask 0x10 SAct 0x8080 SErr 0x400100 action 0x6 frozen
Mar 03 17:15:29 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:15:29 proxmox kernel: ata2: SError: { UnrecovData Handshk }
Mar 03 17:15:29 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:29 proxmox kernel: ata2.00: cmd 61/98:38:d8:43:54/00:00:08:00:00/40 tag 7 ncq dma 77824 out
res 40/00:38:d8:43:54/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:29 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:29 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:29 proxmox kernel: ata2.00: cmd 61/08:78:a8:da:67/00:00:08:00:00/40 tag 15 ncq dma 4096 out
res 40/00:38:d8:43:54/00:00:08:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:29 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:29 proxmox kernel: ata2: hard resetting link
Mar 03 17:15:29 proxmox kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
Mar 03 17:15:29 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:15:29 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:15:29 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:15:29 proxmox kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 03 17:15:29 proxmox kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 03 17:15:29 proxmox kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 03 17:15:29 proxmox kernel: ata2.00: configured for UDMA/133
Mar 03 17:15:29 proxmox kernel: ata2: EH complete
Mar 03 17:15:33 proxmox kernel: ata2: limiting SATA link speed to 1.5 Gbps
Mar 03 17:15:33 proxmox kernel: ata2.00: exception Emask 0x10 SAct 0x80ff7f9f SErr 0x400100 action 0x6 frozen
Mar 03 17:15:33 proxmox kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 03 17:15:33 proxmox kernel: ata2: SError: { UnrecovData Handshk }
Mar 03 17:15:33 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:33 proxmox kernel: ata2.00: cmd 61/08:00:48:f2:20/00:00:0e:00:00/40 tag 0 ncq dma 4096 out
res 40/00:80:60:ea:20/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:33 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:33 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:33 proxmox kernel: ata2.00: cmd 61/30:08:68:f2:20/00:00:0e:00:00/40 tag 1 ncq dma 24576 out
res 40/00:80:60:ea:20/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:33 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:33 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:33 proxmox kernel: ata2.00: cmd 61/08:10:a0:f2:20/00:00:0e:00:00/40 tag 2 ncq dma 4096 out
res 40/00:80:60:ea:20/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:33 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:33 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:33 proxmox kernel: ata2.00: cmd 61/08:18:b0:f2:20/00:00:0e:00:00/40 tag 3 ncq dma 4096 out
res 40/00:80:60:ea:20/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)
Mar 03 17:15:33 proxmox kernel: ata2.00: status: { DRDY }
Mar 03 17:15:33 proxmox kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Mar 03 17:15:33 proxmox kernel: ata2.00: cmd 61/08:20:18:f3:20/00:00:0e:00:00/40 tag 4 ncq dma 4096 out
res 40/00:80:60:ea:20/00:00:0e:00:00/40 Emask 0x10 (ATA bus error)

golfvert · Mars 3, 2024, 5:40

Ca, c’est le file system qui ne va pas bien.

Ca, c’est le réseau qui coince/se décoince.

Ca, c’est le disque dur qui a du mal…

Donc, c’est pas la joie

Proxmox 8 ?
Carte ethernet Realtek ?

Un upgrade récent ? Une nouvelle VM/LXC qui génère du trafic réseau ?

Il faudrait, je pense, commencer par faire un fsck des disques. Déjà, ça devrait régler certains soucis.

Une panne hard est toujours possible, mais, déjà je chercherai du côté d’un éventuel upgrade fait sur proxmox.

Dapolux · Mars 3, 2024, 6:05

Merci @golfvert pour ton aide,

Proxmox 7.0

proxmox-ve: 7.0-2 (running kernel: 5.11.22-1-pve)
pve-manager: 7.0-8 (running version: 7.0-8/b1dbf562)
pve-kernel-5.11: 7.0-3
pve-kernel-helper: 7.0-3
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.0.0-1+pve5
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.1.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-4
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-7
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-2
lxcfs: 4.0.8-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.1-1
proxmox-backup-file-restore: 2.0.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.2-4
pve-cluster: 7.0-3
pve-container: 4.0-5
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.2-4
pve-ha-manager: 3.3-1
pve-i18n: 2.4-1
pve-qemu-kvm: 6.0.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-7
smartmontools: 7.2-pve2
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1~bpo10+1

Yes

Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Kernel driver in use: r8169
Kernel modules: r8169

Pas d’upgrade, pas de nouvelle vm/lxc depuis septembre dernier.

Après avoir eu un gros warning en tentant de le lancer (‹ fsck ›) car les disques sont « montés », je crois que je dois faire autrement. Quelle est la bonne façon de faire? (de ce que je vois sur le net il faut passer via un live cd on dirais)

Vincha · Mars 3, 2024, 7:16

Bonsoir, pour faire un fsck tu as deux façons, la première c’est de le lancer en « dry run » afin de voir ce qui va se passer, ça peut être fait directement après le boot de ta machine.

Si tu as des messages disant qu’il faut réparer, alors la meilleure façon de faire c’est de booter ton serveur avec une image live ( USB / CD-ROM ) en gros fsck ne peut s’exécuter et réparer que sur une filesystem non monté

tu peux aussi faire un test physique de ton disque en lançant la commande suivante

smartctl -t short /dev/<ton_disque>

cela va lancer un test. une fois le teste fini tu peux faire un

smartctl -H /dev/<ton_disque>

pour voir le résultat du test. ( tout cela en root bien entendu )

et pour une analyse exhaustive

smartctl -a /dev/<ton_disque> | less

Dapolux · Mars 3, 2024, 9:53

Bonsoir @Vincha et merci pour ton aide,

Vincha:

tu peux aussi faire un test physique de ton disque en lançant la commande suivante
smartctl -t short /dev/<ton_disque>
cela va lancer un test. une fois le teste fini tu peux faire un
smartctl -H /dev/<ton_disque> 

ça a l’air ok de ce coté là:

root@proxmox:~# smartctl -H /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.22-1-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

root@proxmox:~# smartctl -H /dev/sdb
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.22-1-pve] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

root@proxmox:~# fsck -n /dev/sda
fsck from util-linux 2.36.1
e2fsck 1.46.2 (28-Feb-2021)
Warning!  /dev/sda is in use.
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Found a gpt partition table in /dev/sda
root@proxmox:~# fsck -n /dev/sdb
fsck from util-linux 2.36.1
e2fsck 1.46.2 (28-Feb-2021)
Warning!  /dev/sdb is in use.
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Found a gpt partition table in /dev/sdb

je vais du coup tenter avec une image live sur le serveur.

Dapolux · Mars 3, 2024, 10:56

fsck fait via le live usb, puis redémarrage.

Les WRITE FPDMA QUEUED ont disparu des logs, et le serveur semble démarrer plus vite.
Je vais suivre cela dans les jours a venir et voir si le problème est toujours là, espérons que non :).

Un grand merci pour votre aide!

Dapolux · Mars 4, 2024, 6:00

Bon et bien re plantages aujourd’hui…
Le serveur n’a pas « complètement freezé », mais

les vms/ct sont apparues en grisées avec un « ? » dans proxmox
la vm HA s’est arrêtée toute seule, je la relance puis elle s’arrête a nouveau toute seule, puis impossible de la redémarrer

image2249×123 10.9 KB
impossible de rebooter le serveur via l’interface graphique (bouton « reboot »), ni par ssh avec un sudo reboot. Ca a finalement bien voulu redémarrer avec un sudo reboot -f.

Ce qui m’interpelle dans les logs:

Mar 04 18:42:50 proxmox kernel: EXT4-fs (loop1): error count since last fsck: 8
Mar 04 18:42:50 proxmox kernel: EXT4-fs (loop1): initial error at time 1709463680: htree_dirblock_to_tree:993: inode 552996
Mar 04 18:42:50 proxmox kernel: EXT4-fs (loop1): last error at time 1709463680: __ext4_find_entry:1535: inode 552996

Mar 04 18:44:28 proxmox kernel: EXT4-fs (loop4): error count since last fsck: 3
Mar 04 18:44:28 proxmox kernel: EXT4-fs (loop4): initial error at time 1709572831: __ext4_find_entry:1535: inode 525887
Mar 04 18:44:28 proxmox kernel: EXT4-fs (loop4): last error at time 1709572831: __ext4_find_entry:1535: inode 525887

Ou alors encore:

Logs d'approximativement quand HA est tombé aujourd'hui

Mar 04 11:20:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:20:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:20:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:20:53 proxmox kernel: mariadbd[2528953]: segfault at 5582b6ff7be0 ip 00005582b6ff7be0 sp 00007ffd988e94c0 error 15 in mariadbd[5582b6ff7000+164000]
Mar 04 11:20:53 proxmox kernel: Code: 00 00 c7 64 39 b6 82 55 00 00 f5 64 39 b6 82 55 00 00 23 65 39 b6 82 55 00 00 51 65 39 b6 82 55 00 00 76 65 39 b6 82 55 00 00 65 39 b6 82 55 00 00 2f 68 39 b6 82 55 00 00 92 b3 39 b6 82 55
Mar 04 11:21:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:21:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:21:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:21:15 proxmox kernel: traps: curl[2538358] general protection fault ip:7f6cdabe062d sp:7ffc79700fd8 error:0 in ld-musl-x86_64.so.1[7f6cdabcf000+4c000]
Mar 04 11:21:25 proxmox pvedaemon[1453852]: worker exit
Mar 04 11:21:25 proxmox pvedaemon[1020]: worker 1453852 finished
Mar 04 11:21:25 proxmox pvedaemon[1020]: starting 1 worker(s)
Mar 04 11:21:25 proxmox pvedaemon[1020]: worker 2543536 started
Mar 04 11:21:56 proxmox kernel: mariadbd[2557954]: segfault at 5623 ip 00005622717c731e sp 00007ffca9203150 error 4 in mariadbd[562271238000+609000]
Mar 04 11:21:56 proxmox kernel: Code: 48 85 db 0f 84 f5 00 00 00 48 8d 83 00 01 00 00 45 31 ed 4c 8d 75 cf 49 89 84 24 88 00 00 00 49 8b 44 24 40 4d 89 ef 49 ff c5 <42> 8a 14 28 f6 c2 03 74 04 b0 02 eb 41 80 e2 04 b0 0e 75 3a 44 88
Mar 04 11:22:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:22:00 proxmox pvesr[2559506]: String found where operator expected at /usr/share/perl5/PVE/Network.pm line 59, near « eval { run_command( »"
Mar 04 11:22:00 proxmox pvesr[2559506]: (Missing semicolon on previous line?)
Mar 04 11:22:00 proxmox pvesr[2559506]: Use of /c modifier is meaningless without /g at /usr/share/perl5/PVE/Network.pm line 59.
Mar 04 11:22:00 proxmox pvesr[2559506]: Number found where operator expected at /usr/share/perl5/PVE/Network.pm line 59, near « parent 1 »
Mar 04 11:22:00 proxmox pvesr[2559506]: (Do you need to predeclare parent?)
Mar 04 11:22:00 proxmox pvesr[2559506]: Number found where operator expected at /usr/share/perl5/PVE/Network.pm line 59, near « classid 1 »
Mar 04 11:22:00 proxmox pvesr[2559506]: (Do you need to predeclare classid?)
Mar 04 11:22:00 proxmox pvesr[2559506]: String found where operator expected at /usr/share/perl5/PVE/Network.pm line 59, near « eval { run_command( »"
Mar 04 11:22:00 proxmox pvesr[2559506]: (Missing semicolon on previous line?)
Mar 04 11:22:00 proxmox pvesr[2559506]: Bareword found where operator expected at /usr/share/perl5/PVE/Network.pm line 60, near « $iface parent »
Mar 04 11:22:00 proxmox pvesr[2559506]: (Might be a runaway multi-line « » string starting on line 59)
Mar 04 11:22:00 proxmox pvesr[2559506]: (Missing operator before parent?)
Mar 04 11:22:00 proxmox pvesr[2559506]: Number found where operator expected at /usr/share/perl5/PVE/Network.pm line 60, near « pref 50 »
Mar 04 11:22:00 proxmox pvesr[2559506]: (Do you need to predeclare pref?)
Mar 04 11:22:00 proxmox pvesr[2559506]: Bareword found where operator expected at /usr/share/perl5/PVE/Network.pm line 60, near « 50 u32 »
Mar 04 11:22:00 proxmox pvesr[2559506]: (Missing operator before u32?)
Mar 04 11:22:00 proxmox pvesr[2559506]: String found where operator expected at /usr/share/perl5/PVE/Network.pm line 60, near « eval { run_command( »"
Mar 04 11:22:00 proxmox pvesr[2559506]: (Missing semicolon on previous line?)
Mar 04 11:22:00 proxmox pvesr[2559506]: Bareword found where operator expected at /usr/share/perl5/PVE/Network.pm line 61, near « $iface ingress »
Mar 04 11:22:00 proxmox pvesr[2559506]: (Might be a runaway multi-line « » string starting on line 60)
Mar 04 11:22:00 proxmox pvesr[2559506]: (Missing operator before ingress?)
Mar 04 11:22:00 proxmox pvesr[2559506]: syntax error at /usr/share/perl5/PVE/Network.pm line 59, near « eval { run_command( »"
Mar 04 11:22:00 proxmox pvesr[2559506]: Unknown regexp modifier « /t » at /usr/share/perl5/PVE/Network.pm line 59, at end of line
Mar 04 11:22:00 proxmox pvesr[2559506]: Global symbol « $iface » requires explicit package name (did you forget to declare « my $iface »?) at /usr/share/perl5/PVE/Network.pm line 59.
Mar 04 11:22:00 proxmox pvesr[2559506]: Regexp modifiers « /u » and « /l » are mutually exclusive at /usr/share/perl5/PVE/Network.pm line 59, at end of line
Mar 04 11:22:00 proxmox pvesr[2559506]: Regexp modifiers « /u » and « /l » are mutually exclusive at /usr/share/perl5/PVE/Network.pm line 59, at end of line
Mar 04 11:22:00 proxmox pvesr[2559506]: Global symbol « $iface » requires explicit package name (did you forget to declare « my $iface »?) at /usr/share/perl5/PVE/Network.pm line 60.
Mar 04 11:22:00 proxmox pvesr[2559506]: Regexp modifiers « /u » and « /l » are mutually exclusive at /usr/share/perl5/PVE/Network.pm line 60, at end of line
Mar 04 11:22:00 proxmox pvesr[2559506]: Regexp modifiers « /u » and « /l » are mutually exclusive at /usr/share/perl5/PVE/Network.pm line 60, at end of line
Mar 04 11:22:00 proxmox pvesr[2559506]: Global symbol « $iface » requires explicit package name (did you forget to declare « my $iface »?) at /usr/share/perl5/PVE/Network.pm line 61.
Mar 04 11:22:00 proxmox pvesr[2559506]: Regexp modifiers « /u » and « /l » are mutually exclusive at /usr/share/perl5/PVE/Network.pm line 61, at end of line
Mar 04 11:22:00 proxmox pvesr[2559506]: /usr/share/perl5/PVE/Network.pm has too many errors.
Mar 04 11:22:00 proxmox pvesr[2559506]: Compilation failed in require at /usr/share/perl5/PVE/INotify.pm line 21.
Mar 04 11:22:00 proxmox pvesr[2559506]: BEGIN failed–compilation aborted at /usr/share/perl5/PVE/INotify.pm line 21.
Mar 04 11:22:00 proxmox pvesr[2559506]: Compilation failed in require at /usr/share/perl5/PVE/CLI/pvesr.pm line 9.
Mar 04 11:22:00 proxmox pvesr[2559506]: BEGIN failed–compilation aborted at /usr/share/perl5/PVE/CLI/pvesr.pm line 9.
Mar 04 11:22:00 proxmox pvesr[2559506]: Compilation failed in require at /usr/bin/pvesr line 6.
Mar 04 11:22:00 proxmox pvesr[2559506]: BEGIN failed–compilation aborted at /usr/bin/pvesr line 6.
Mar 04 11:22:00 proxmox systemd[1]: pvesr.service: Main process exited, code=exited, status=255/EXCEPTION
Mar 04 11:22:00 proxmox systemd[1]: pvesr.service: Failed with result ‹ exit-code ›.
Mar 04 11:22:00 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:22:10 proxmox kernel: br-e14ea4ff0b15: port 1(vethe3081ce) entered disabled state
Mar 04 11:22:10 proxmox kernel: veth71f003a: renamed from eth0
Mar 04 11:22:10 proxmox kernel: br-e14ea4ff0b15: port 1(vethe3081ce) entered disabled state
Mar 04 11:22:10 proxmox kernel: device vethe3081ce left promiscuous mode
Mar 04 11:22:10 proxmox kernel: br-e14ea4ff0b15: port 1(vethe3081ce) entered disabled state
Mar 04 11:22:10 proxmox kernel: br-e14ea4ff0b15: port 1(vetha723288) entered blocking state
Mar 04 11:22:10 proxmox kernel: br-e14ea4ff0b15: port 1(vetha723288) entered disabled state
Mar 04 11:22:10 proxmox kernel: device vetha723288 entered promiscuous mode
Mar 04 11:22:10 proxmox kernel: br-e14ea4ff0b15: port 1(vetha723288) entered blocking state
Mar 04 11:22:10 proxmox kernel: br-e14ea4ff0b15: port 1(vetha723288) entered forwarding state
Mar 04 11:22:11 proxmox kernel: eth0: renamed from veth53c10f0
Mar 04 11:22:11 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetha723288: link becomes ready
Mar 04 11:22:16 proxmox kernel: br-e14ea4ff0b15: port 1(vetha723288) entered disabled state
Mar 04 11:22:16 proxmox kernel: veth53c10f0: renamed from eth0
Mar 04 11:22:16 proxmox kernel: br-e14ea4ff0b15: port 1(vetha723288) entered disabled state
Mar 04 11:22:16 proxmox kernel: device vetha723288 left promiscuous mode
Mar 04 11:22:16 proxmox kernel: br-e14ea4ff0b15: port 1(vetha723288) entered disabled state
Mar 04 11:22:16 proxmox kernel: br-e14ea4ff0b15: port 1(veth686381a) entered blocking state
Mar 04 11:22:16 proxmox kernel: br-e14ea4ff0b15: port 1(veth686381a) entered disabled state
Mar 04 11:22:16 proxmox kernel: device veth686381a entered promiscuous mode
Mar 04 11:22:16 proxmox kernel: br-e14ea4ff0b15: port 1(veth686381a) entered blocking state
Mar 04 11:22:16 proxmox kernel: br-e14ea4ff0b15: port 1(veth686381a) entered forwarding state
Mar 04 11:22:16 proxmox kernel: eth0: renamed from veth8c59898
Mar 04 11:22:16 proxmox kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth686381a: link becomes ready
Mar 04 11:22:18 proxmox kernel: x86/PAT: frigate.detecto:2568946 map pfn RAM range req uncached-minus for [mem 0x3e3090000-0x3e3093fff], got write-back
Mar 04 11:22:18 proxmox kernel: python3[2568945]: segfault at 4f6af000 ip 000000004f6af000 sp 00007ffe4fb7f318 error 14
Mar 04 11:22:18 proxmox kernel: Code: Unable to access opcode bytes at RIP 0x4f6aefd6.
Mar 04 11:22:18 proxmox kernel: python3[2569042]: segfault at 900a9 ip 000000000052c7dd sp 00007ffdf034cbe0 error 4 in python3.9[41f000+288000]
Mar 04 11:22:18 proxmox kernel: Code: 85 ed 0f 84 e7 65 f0 ff 49 8b 55 08 f6 82 a9 00 00 00 40 0f 85 04 03 00 00 4c 8b 6b 58 4d 85 ed 0f 84 28 03 00 00 49 8b 4d 08 81 a9 00 00 00 40 0f 85 7e 03 00 00 48 8b 7b 20 48 85 ff 0f 85
Mar 04 11:22:19 proxmox kernel: python3[2569607]: segfault at 0 ip 0000000000000000 sp 00007fff02ccb098 error 14 in python3.9[400000+1f000]
Mar 04 11:22:19 proxmox kernel: Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
Mar 04 11:22:20 proxmox kernel: traps: mariadbd[2570633] general protection fault ip:55789acb4348 sp:7ffee5e0d270 error:0 in mariadbd[55789a725000+609000]
Mar 04 11:22:21 proxmox kernel: mariadbd[2570895]: segfault at 54 ip 00007fa7c59ca3d0 sp 00007ffe55e67278 error 4 in ld-musl-x86_64.so.1[7fa7c5988000+4c000]
Mar 04 11:22:21 proxmox kernel: Code: 56 29 ff ff 48 81 c4 88 00 00 00 89 d8 5b 5d 41 5c 41 5d 41 5e 41 5f c3 64 48 8b 04 25 00 00 00 00 48 8b 80 80 00 00 00 89 ff <48> 8b 04 f8 c3 41 56 41 55 49 89 d5 41 54 49 89 f4 55 48 89 fd 53
Mar 04 11:22:33 proxmox kernel: br-e14ea4ff0b15: port 1(veth686381a) entered disabled state
Mar 04 11:22:33 proxmox kernel: veth8c59898: renamed from eth0
Mar 04 11:22:33 proxmox kernel: br-e14ea4ff0b15: port 1(veth686381a) entered disabled state
Mar 04 11:22:33 proxmox kernel: device veth686381a left promiscuous mode
Mar 04 11:22:33 proxmox kernel: br-e14ea4ff0b15: port 1(veth686381a) entered disabled state
Mar 04 11:22:33 proxmox kernel: br-e14ea4ff0b15: port 1(veth2b25e42) entered blocking state
Mar 04 11:22:33 proxmox kernel: br-e14ea4ff0b15: port 1(veth2b25e42) entered disabled state
Mar 04 11:22:33 proxmox kernel: device veth2b25e42 entered promiscuous mode
Mar 04 11:22:33 proxmox kernel: br-e14ea4ff0b15: port 1(veth2b25e42) entered blocking state
Mar 04 11:22:33 proxmox kernel: br-e14ea4ff0b15: port 1(veth2b25e42) entered forwarding state
Mar 04 11:22:34 proxmox kernel: br-e14ea4ff0b15: port 1(veth2b25e42) entered disabled state
Mar 04 11:22:34 proxmox kernel: device veth2b25e42 left promiscuous mode
Mar 04 11:22:34 proxmox kernel: br-e14ea4ff0b15: port 1(veth2b25e42) entered disabled state
Mar 04 11:23:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:23:01 proxmox kernel: traps: pvesr[2589354] general protection fault ip:55dcf242eae1 sp:7fff1c9b2a78 error:0 in perl[55dcf2386000+184000]
Mar 04 11:23:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=11/SEGV
Mar 04 11:23:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:23:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:23:41 proxmox kernel: kvm[1056]: segfault at 3e ip 00005584b13d7135 sp 00007fced4d8db30 error 4 in qemu-system-x86_64[5584b0eef000+532000]
Mar 04 11:23:41 proxmox kernel: Code: 00 00 00 66 90 53 48 89 fb 48 8b 3f 48 85 ff 75 19 eb 32 66 90 48 c7 47 38 00 00 00 00 e8 f3 da 00 00 48 8b 3b 48 85 ff 74 1b <48> 8b 47 38 48 89 03 48 85 c0 75 df 48 89 5b 08 eb d9 66 0f 1f 84
Mar 04 11:23:41 proxmox kernel: fwbr400i0: port 2(tap400i0) entered disabled state
Mar 04 11:23:41 proxmox kernel: fwbr400i0: port 2(tap400i0) entered disabled state
Mar 04 11:23:41 proxmox systemd[1]: 400.scope: Succeeded.
Mar 04 11:23:41 proxmox systemd[1]: 400.scope: Consumed 4h 50min 31.819s CPU time.
Mar 04 11:23:42 proxmox kernel: traps: qm[2608351] general protection fault ip:5575a18efbb2 sp:7ffe634cb1d0 error:0 in perl[5575a18c0000+184000]
Mar 04 11:24:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:24:01 proxmox pvesr[2617076]: munmap_chunk(): invalid pointer
Mar 04 11:24:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=6/ABRT
Mar 04 11:24:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:24:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:24:11 proxmox pveproxy[2093793]: worker exit
Mar 04 11:24:11 proxmox kernel: pveproxy worker[2093793]: segfault at 12 ip 000055a0cde23fd9 sp 00007fff9cb04650 error 4 in perl[55a0cdd56000+184000]
Mar 04 11:24:11 proxmox kernel: Code: 4e 0c 89 56 08 83 e9 09 83 f9 01 76 14 83 fa 01 76 3f 83 ea 01 89 55 08 48 83 c4 10 5d c3 0f 1f 00 48 8b 70 08 48 85 f6 74 e3 46 0e 10 74 dd 48 c7 40 08 00 00 00 00 8b 56 08 83 fa 01 76 22
Mar 04 11:24:11 proxmox pveproxy[1029]: worker 2093793 finished
Mar 04 11:24:11 proxmox pveproxy[1029]: starting 1 worker(s)
Mar 04 11:24:11 proxmox pveproxy[1029]: worker 2622453 started
Mar 04 11:24:55 proxmox pvedaemon[1020]: worker 2543536 finished
Mar 04 11:24:55 proxmox pvedaemon[1020]: starting 1 worker(s)
Mar 04 11:24:55 proxmox pvedaemon[1020]: worker 2643051 started
Mar 04 11:25:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:25:01 proxmox kernel: pvesr[2645404]: segfault at fffffffffffffffe ip 00007f2186a5873c sp 00007fff2eb82d10 error 5 in libc-2.31.so[7f21869f3000+15a000]
Mar 04 11:25:01 proxmox kernel: Code: 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 83 ec 18 48 8b 05 cd 77 14 00 48 8b 00 48 85 c0 0f 85 81 00 00 00 48 85 ff 74 74 <48> 8b 47 f8 48 8d 77 f0 a8 02 75 38 48 8b 15 29 76 14 00 64 48 83
Mar 04 11:25:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=11/SEGV
Mar 04 11:25:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:25:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:25:08 proxmox kernel: mariadbd-safe[2648946]: segfault at 8500000018 ip 0000561c072983a8 sp 00007fff203f8a40 error 4 in busybox[561c07254000+9c000]
Mar 04 11:25:08 proxmox kernel: Code: 41 57 41 56 49 89 f6 89 d6 41 55 41 54 55 53 89 d3 48 83 ec 58 48 8b 2d ee e2 07 00 64 48 8b 04 25 28 00 00 00 48 89 44 24 48 <48> 8b 47 18 48 8b 7f 10 48 89 05 d9 e1 07 00 48 8b 45 08 48 89 05
Mar 04 11:26:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:26:01 proxmox pvesr[2673794]: malloc(): smallbin double linked list corrupted
Mar 04 11:26:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=6/ABRT
Mar 04 11:26:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:26:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:27:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:27:01 proxmox kernel: pvesr[2702005]: segfault at 561b10315740 ip 0000561b10315740 sp 00007fff06d95508 error 15
Mar 04 11:27:01 proxmox kernel: Code: 00 00 ae 9a 00 00 b8 9a 00 00 01 00 00 00 00 00 00 00 06 04 24 6c 6f 67 69 64 00 00 00 00 00 00 00 00 21 00 00 00 00 00 00 00 <90> b5 25 10 1b 56 00 00 38 1f 31 10 1b 56 00 00 00 2d 31 10 1b 56
Mar 04 11:27:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=11/SEGV
Mar 04 11:27:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:27:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:27:01 proxmox kernel: traps: mariadbd[2702253] general protection fault ip:55e600733348 sp:7ffc1fbf0450 error:0 in mariadbd[55e6001a4000+609000]
Mar 04 11:27:32 proxmox kernel: mariadbd[2716628]: segfault at 1c ip 00007fa90b97971d sp 00007ffe2a9bb240 error 4 in ld-musl-x86_64.so.1[7fa90b967000+4c000]
Mar 04 11:27:32 proxmox kernel: Code: f6 c5 01 75 7b 49 83 bc c7 d0 01 00 00 00 75 70 89 e8 83 c8 01 48 63 c8 49 8b 94 cf d0 01 00 00 49 8b 4c cf 50 48 85 c9 74 0e <8b> 71 18 85 f6 75 0b 8b 49 1c 85 c9 75 04 48 83 c2 03 48 83 fa 0d
Mar 04 11:28:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:28:01 proxmox kernel: pvesr[2730210]: segfault at 12 ip 0000564b5d47bfd9 sp 00007fff57abe4e0 error 4 in perl[564b5d3ae000+184000]
Mar 04 11:28:01 proxmox kernel: Code: 4e 0c 89 56 08 83 e9 09 83 f9 01 76 14 83 fa 01 76 3f 83 ea 01 89 55 08 48 83 c4 10 5d c3 0f 1f 00 48 8b 70 08 48 85 f6 74 e3 46 0e 10 74 dd 48 c7 40 08 00 00 00 00 8b 56 08 83 fa 01 76 22
Mar 04 11:28:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=11/SEGV
Mar 04 11:28:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:28:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:29:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:29:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:29:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:29:12 proxmox kernel: traps: mariadbd[2763884] general protection fault ip:5638aec19348 sp:7ffc3a2b66d0 error:0 in mariadbd[5638ae68a000+609000]
Mar 04 11:30:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:30:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:30:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:30:29 proxmox kernel: traps: mariadbd-safe[2799762] general protection fault ip:7fdbe1ac862d sp:7ffcf29a0868 error:0 in ld-musl-x86_64.so.1[7fdbe1ab7000+4c000]
Mar 04 11:30:31 proxmox kernel: IPv4: martian destination 0.0.0.0 from 192.168.1.127, dev eth0
Mar 04 11:30:31 proxmox kernel: IPv4: martian destination 0.0.0.0 from 192.168.1.127, dev eth0
Mar 04 11:30:33 proxmox kernel: IPv4: martian destination 0.0.0.0 from 192.168.1.126, dev eth0
Mar 04 11:30:33 proxmox kernel: IPv4: martian destination 0.0.0.0 from 192.168.1.126, dev eth0
Mar 04 11:30:35 proxmox pveproxy[2398718]: worker exit
Mar 04 11:30:35 proxmox pveproxy[1029]: worker 2398718 finished
Mar 04 11:30:35 proxmox pveproxy[1029]: starting 1 worker(s)
Mar 04 11:30:35 proxmox pveproxy[1029]: worker 2803108 started
Mar 04 11:31:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:31:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:31:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:31:23 proxmox kernel: mariadbd-safe[2825396]: segfault at 7f39084b3220 ip 00007f39084f969f sp 00007ffde6357b68 error 4 in ld-musl-x86_64.so.1[7f39084e8000+4c000]
Mar 04 11:31:23 proxmox kernel: Code: 80 7f fc 00 74 12 85 d2 74 01 f4 48 63 57 f8 81 fa ff ff 00 00 7f 01 f4 89 d0 c1 e0 04 48 98 48 29 c7 48 8b 47 f0 48 83 ef 10 <48> 39 78 10 74 01 f4 40 8a 78 20 83 e7 1f 39 f7 7d 01 f4 8b 78 18
Mar 04 11:32:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:32:01 proxmox kernel: traps: pvesr[2843102] general protection fault ip:559317271c1f sp:7ffe74b71420 error:0 in perl[55931719d000+184000]
Mar 04 11:32:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=11/SEGV
Mar 04 11:32:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:32:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:32:03 proxmox kernel: mariadbd-safe[2844130]: segfault at 666900007faf ip 000055d2d60629b0 sp 00007ffdb7a0cad0 error 4 in busybox[55d2d601f000+9c000]
Mar 04 11:32:03 proxmox kernel: Code: f8 00 00 00 31 c0 e8 17 af ff ff 48 8b 2d f8 ec 07 00 80 7d 4e 00 0f 85 0b 02 00 00 48 85 db 0f 84 02 02 00 00 e8 fc fe ff ff <8a> 03 3c 0e 77 1f 48 8d 0d 03 9d 05 00 0f b6 d0 48 63 14 91 48 01
Mar 04 11:33:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:33:01 proxmox kernel: pvesr[2871046]: segfault at 55c754000000 ip 00007f6634a4476e sp 00007ffe2663b180 error 4 in libc-2.31.so[7f66349df000+15a000]
Mar 04 11:33:01 proxmox kernel: Code: a8 02 75 38 48 8b 15 29 76 14 00 64 48 83 3a 00 0f 84 9e 00 00 00 48 8d 3d 1f 84 14 00 a8 04 74 0c 48 89 f0 48 25 00 00 00 fc <48> 8b 38 31 d2 48 83 c4 18 e9 a4 c1 ff ff 0f 1f 40 00 8b 15 2e 7b
Mar 04 11:33:01 proxmox systemd[1]: pvesr.service: Main process exited, code=killed, status=11/SEGV
Mar 04 11:33:01 proxmox systemd[1]: pvesr.service: Failed with result ‹ signal ›.
Mar 04 11:33:01 proxmox systemd[1]: Failed to start Proxmox VE replication runner.
Mar 04 11:33:50 proxmox pvedaemon[2369131]: root@pam successful auth for user ‹ dapolux@pam ›
Mar 04 11:33:50 proxmox pvedaemon[2442849]: root@pam successful auth for user ‹ dapolux@pam ›
Mar 04 11:33:51 proxmox pveproxy[2366542]: worker exit
Mar 04 11:33:51 proxmox pveproxy[1029]: worker 2366542 finished
Mar 04 11:33:51 proxmox pveproxy[1029]: starting 1 worker(s)
Mar 04 11:33:51 proxmox pveproxy[1029]: worker 2895145 started
Mar 04 11:34:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:34:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:34:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:35:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:35:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:35:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:35:41 proxmox kernel: pveproxy worker[2895145]: segfault at 4 ip 000055a0cde0f688 sp 00007fff9cb045c0 error 4 in perl[55a0cdd56000+184000]
Mar 04 11:35:41 proxmox kernel: Code: 49 8d 04 d0 eb 1c 0f 1f 40 00 48 8d 4a 01 48 83 c0 08 48 89 0b 48 8b 75 00 48 39 56 18 76 53 48 89 ca 4c 8b 20 4d 85 e4 74 e0 <49> 8b 14 24 48 89 10 48 8b 45 00 48 83 68 10 01 83 bf e4 09 00 00
Mar 04 11:35:41 proxmox pveproxy[1029]: worker 2895145 finished
Mar 04 11:35:41 proxmox pveproxy[1029]: starting 1 worker(s)
Mar 04 11:35:41 proxmox pveproxy[1029]: worker 2947022 started
Mar 04 11:35:51 proxmox kernel: traps: mariadbd[2951460] general protection fault ip:556e9d0db348 sp:7ffcc43c5da0 error:0 in mariadbd[556e9cb4c000+609000]
Mar 04 11:36:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:36:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:36:01 proxmox systemd[1]: Finished Proxmox VE replication runner.
Mar 04 11:36:08 proxmox kernel: mariadbd-safe[2958853]: segfault at 0 ip 00007f4de90a3f81 sp 00007ffc466e3a10 error 4 in ld-musl-x86_64.so.1[7f4de9065000+4c000]
Mar 04 11:36:08 proxmox kernel: Code: f6 c3 07 75 ed 48 ba 01 01 01 01 01 01 01 01 48 63 f8 49 b8 ff fe fe fe fe fe fe fe 49 b9 80 80 80 80 80 80 80 80 48 0f af fa <48> 8b 0b 48 89 ce 4a 8d 14 01 48 f7 d1 48 31 fe 48 21 ca 4a 8d 0c
Mar 04 11:36:35 proxmox systemd[1]: ksmtuned.service: Main process exited, code=killed, status=11/SEGV
Mar 04 11:36:35 proxmox kernel: ksmtuned[666]: segfault at 0 ip 00005645e4eea4c4 sp 00007ffd5c75de00 error 4 in bash[5645e4ed4000+bb000]
Mar 04 11:36:35 proxmox kernel: Code: ff e9 b2 fe ff ff 48 8d 3d e7 71 0a 00 31 c0 e8 e2 d3 ff ff e9 d2 fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 48 89 fd <48> 8b 3f 48 85 ff 74 05 e8 af 9b fe ff 8b 05 d1 af 0e 00 39 05 cf
Mar 04 11:36:35 proxmox systemd[1]: ksmtuned.service: Failed with result ‹ signal ›.
Mar 04 11:36:35 proxmox systemd[1]: ksmtuned.service: Consumed 26.029s CPU time.
Mar 04 11:37:00 proxmox systemd[1]: Starting Proxmox VE replication runner…
Mar 04 11:37:01 proxmox systemd[1]: pvesr.service: Succeeded.
Mar 04 11:37:01 proxmox systemd[1]: Finished Proxmox VE replication runner.

Vincha · Mars 4, 2024, 6:49

Aurais tu bouger ton serveur ou fait quelque chose a l’intérieur ? J’ai cherché sur WRITE FPDMA QUEUED et pas mal de posts parlent de cable sata défectueux.je dis cela à tout hasard.

je te propose la chose suivante , reboot sur ton live CD et vas-y a coups de stress. tu peux stresser le cpu, la mémoire et les disques aussi je crois.

Dapolux · Mars 4, 2024, 7:04

Rien fait dernièrement.
J’ai lu la même chose hier, et en cherchant dans mes cables je n’avais pas de cable « coudé », donc je n’ai pas testé, mais je vais voir pour en acheter un.

ok, je vais essayer

Dapolux · Mars 9, 2024, 8:11

Hello,

Petit retour après quelques jours « sans problèmes ». A priori le problème venait de la RAM.

Le problèmes, persistaient:

J’ai donc lancé un coup de stress de la ram, puis au lancement du stress, plantage:

Ayant ajouté il y a 6 mois une nouvelle barrette de RAM (Crucial de 16go, ajoutée au 8 que j’avais à l’origine), j’ai donc retiré cette RAM, puis relancé, puis la plus de problèmes.

Même si j’ai un peu la flemme, il va falloir que je teste en mettant « que » la nouvelle ram (16g) voir si ça plante bien, puis la renvoyer en SAV (Amazon).

Un grand merci @Vincha et @golfvert pour votre aide!

Ps: Manque de bol, ou coïncidence, c’est a ce même moment que mon CT LXC avec mon contrôleur unifi, est devenu full (espace disque), et a priori ça a corrompu/foiré la bdd correspondante, j’ai donc du faire une réinstallation du CT (l’augmentation de disque seule n’a pas suffit).

golfvert · Mars 9, 2024, 8:15

En général, mettre deux barrettes différentes sur les slots jumelée de la carte mère, c’est un mauvais plan…
Ce n’est peut-être pas la 16Go qui est HS mais la gestion des deux barrettes qui coince.
Virer la 8 et ne mettre que la 16 serait sans doute plus stable.

Vincha · Mars 9, 2024, 10:31

je viens d’en faire les frais avec un nouveau mini pc acheté je ne dirai pas où il crashait apres quelques heures… je l’ai ouvert et oh surprise ! 2 DIMM de 16GB, même marque et modèle mais les chips étaient soudés différemment et sur une dimm il avait des condensateurs et pas sur l’autre…

règle numéro un toujours avoir un kit de mémoire spécialement faites pour fonctionner ensemble.

Cela dit tu as pu mettre le doigt sur le problème grâce à la communauté et ça c’est cool

Dapolux · Mars 9, 2024, 10:48

Peut être en effet, encore des tests à faire :). Sachant que pendant ce genre de tests, tout le système est à l’arrêt.

C’est sur que ce n’est pas le mieux, mais c’est vrai que j’avais pas forcément envi d’acheter 2 barrettes, et que j’ai préféré laisser la 8go plutôt que la retirer. Probablement à tord visiblement, encore que ça a fonctionné pendant 6 mois sans problèmes.

Carrément!