Dark26's latest activity
-
DDark26 replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.lacp for the bond also here
-
DDark26 replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.some logs 2026-10-01T14:03:37.449165+02:00 prabackservername01 kernel: bnxt_en 0000:14:00.0 nic0: NIC Link is servername, 25000 Mbps (NRZ) full dservernamelex, Flow control: none 2026-10-01T14:03:37.449179+02:00 prabackservername01 kernel...
-
DDark26 replied to the thread Proxmox VE 9.2.21 - BCM57412 bnxt_en network failure after upgrade to kernel 7.0.14-20-pve.Same problem here. Everything was working with 7.0.14-19, but not with 7.0.14-20. Dell serveur with BCM57414 with Firmware 233.1.135.7
-
DDark26 replied to the thread [SOLVED] Error with file restore on pve with pbsbackup.On the windows drive, the deduplication have been activate. :eek: . I didn't manage the instance so i didn't know that. That's explain the problem with the linux module for ntfs that didn't handle it.:(
-
DDark26 replied to the thread [SOLVED] Error with file restore on pve with pbsbackup.with the comman line i have this error if i try to copy a file from where the partition is mount : i see the file like in the gui but if i try to copy a file : cp toto.pdf /root/ cp: erreur de lecture dans 'toto.pdf': Opération non supportée I...
-
DDark26 replied to the thread [SOLVED] Error with file restore on pve with pbsbackup.i have this message in the /var/log/proxmox-backup/file-restore/qemu.log [2026-09-07T08:00:26.920Z INFO proxmox_restore_daemon::proxmox_restore_daemon::watchdog] Inhibit added: 1 [2026-09-07T08:00:26.921Z ERROR...
-
DDark26 posted the thread [SOLVED] Error with file restore on pve with pbsbackup in Proxmox Backup: Installation and configuration.We try to restore a file from pve with a pbs backup and, the file downloaded is zero byte size. Sometimes after 3 or 4 try, the file is download and sometimes not. The disk is a windows ntfs ou linux it seems the is no linr in the log when...