Network not usable - drops Interfaces all the time - X540-T2

I

idontgetit

New Member
Jan 28, 2025
8
0
1
Hi i am new to this Forum

i came from Networking site and i try to get more knowledge on Virtualization in my Homelab..
first i dont get it why Proxmox has so much issues to get a stable NetworkConfiguration with absolute Standard Network Cards

i mean i have network but i cant Upload an Image or as soon a little load get on it Proxmox will loose its Network Interfaces it is real annoying ....

in this case i use Intel X540-T2

i find so many Reports with Google about that issue but it seems on none of them it gets solved..

could someone help me out ?
maybe post me a good tutorial or site with the most common Commands to do Troubleshooting ?

i now fight since 2 weeks with that to me simple issue that shouldnt exist in first place ;(
i could not solve it and honestly i loose interest in that system more and more but i will fight if i can see progress ...
 
With technology, overcoming frustration is the first step to becoming a master.

First things first, check logs and see if anything is throwing errors have you done that?

View kernel logs
Code: 
dmesg

View system logs
Code: 
journalctl -e

If you have monitor and keyboard to the pve box check the state of the network interfaces when they drop

ip is a nifty tool to do networking stuff. Below command will show you interfaces and their states
Code: 
ip link

To learn more about those tools use the man command or search online for their docs or further examples.
 
Last edited:
Wow thanks for the feedback

I didn't think I would get an answer when I just threw up like that, it wasn't very nice ...

I
will look at it next week and start again
now let it rest for a few days I'll get back to you as soon as I know
know more about the problems
 
at the moment it looks like that..

i cant upload any ISO file bigger than 2GB to the Host..
i tried it over the 10GB Nic PCI Card aswell over the onboard 1Gig Card..

10 Gig = Intel X540
1 Gig = I226-V

also followed the hint to use WINSCP instead and check the TMP Folder for upload
neither it is overloaded nor does WINSCP work same error..

It seems always drop near the same time / size..
but not even one Ping gets lost therefore Network seems to be up

it looks more like Service Hang up or Restart..

only thing that i could find in the log is following

###
Code: 
[ 2827.954212] INFO: task txg_sync:773 blocked for more than 122 seconds.
[ 2827.954236]       Tainted: P           O       6.8.12-7-pve #1
[ 2827.954246] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2827.954259] task:txg_sync        state:D stack:0     pid:773   tgid:773   ppid:2      flags:0x00004000
[ 2827.954276] Call Trace:
[ 2827.954283]  <TASK>
[ 2827.954291]  __schedule+0x42b/0x1500
[ 2827.954309]  schedule+0x33/0x110
[ 2827.954318]  schedule_timeout+0x95/0x170
[ 2827.954327]  ? __pfx_process_timeout+0x10/0x10
[ 2827.954339]  io_schedule_timeout+0x51/0x80
[ 2827.954350]  __cv_timedwait_common+0x140/0x180 [spl]
[ 2827.954375]  ? __pfx_autoremove_wake_function+0x10/0x10
[ 2827.954386]  __cv_timedwait_io+0x19/0x30 [spl]
[ 2827.954402]  zio_wait+0x13a/0x2c0 [zfs]
[ 2827.954730]  dsl_pool_sync+0xce/0x4e0 [zfs]
[ 2827.954962]  spa_sync+0x578/0x1050 [zfs]
[ 2827.955206]  ? spa_txg_history_init_io+0x120/0x130 [zfs]
[ 2827.955411]  txg_sync_thread+0x207/0x3a0 [zfs]
[ 2827.955611]  ? __pfx_txg_sync_thread+0x10/0x10 [zfs]
[ 2827.955810]  ? __pfx_thread_generic_wrapper+0x10/0x10 [spl]
[ 2827.955829]  thread_generic_wrapper+0x5f/0x70 [spl]
[ 2827.955845]  kthread+0xf2/0x120
[ 2827.955854]  ? __pfx_kthread+0x10/0x10
[ 2827.955863]  ret_from_fork+0x47/0x70
[ 2827.955874]  ? __pfx_kthread+0x10/0x10
[ 2827.955882]  ret_from_fork_asm+0x1b/0x30
[ 2827.955893]  </TASK>
###
 
no only that the connection got interrupted..

i i follow the Networkgraph from Windows Taskmanager
it gradually get slower until end a short ramp up and than falling dead...

with that the Proxmox Gui isnt reachable anymore
after 30 seconds of wait i could reconnect again

over the whole time Ping to Proxmox work 100%


that is with both networkcards...
and it doesnt matter if they are connected over switch or directly ( crossover )
 
While doing the upload run journalctl -f on the PVE host, this will tail the journal log during that operation. So run the command, then try the upload, and post the output from journal here.

Also can you post the output of your network interfaces? cat /etc/network/interfaces
 
First Try over 1 Gigabit connection
Code: 
Feb 06 18:50:11 ALIMOX pvestatd[1873]: status update time (20.607 seconds)
Feb 06 18:50:11 ALIMOX pveproxy[1895]: problem with client ::ffff:192.168.60.2; Connection timed out
Feb 06 18:50:11 ALIMOX pve-firewall[1857]: firewall update time (20.534 seconds)
Feb 06 18:50:16 ALIMOX pve-ha-lrm[1903]: loop take too long (31 seconds)
Feb 06 18:53:25 ALIMOX kernel: INFO: task txg_sync:771 blocked for more than 122 seconds.
Feb 06 18:54:01 ALIMOX kernel:       Tainted: P           O       6.8.12-7-pve #1
Feb 06 18:54:01 ALIMOX kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 06 18:54:01 ALIMOX kernel: task:txg_sync        state:D stack:0     pid:771   tgid:771   ppid:2      flags:0x00004000
Feb 06 18:54:01 ALIMOX kernel: Call Trace:
Feb 06 18:54:01 ALIMOX kernel:  <TASK>
Feb 06 18:54:01 ALIMOX kernel:  __schedule+0x42b/0x1500
Feb 06 18:54:01 ALIMOX kernel:  schedule+0x33/0x110
Feb 06 18:54:01 ALIMOX kernel:  schedule_timeout+0x95/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_process_timeout+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  io_schedule_timeout+0x51/0x80
Feb 06 18:54:01 ALIMOX kernel:  __cv_timedwait_common+0x140/0x180 [spl]
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  __cv_timedwait_io+0x19/0x30 [spl]
Feb 06 18:54:01 ALIMOX kernel:  zio_wait+0x13a/0x2c0 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  dsl_pool_sync+0xce/0x4e0 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  spa_sync+0x578/0x1050 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  ? spa_txg_history_init_io+0x120/0x130 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  txg_sync_thread+0x207/0x3a0 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_txg_sync_thread+0x10/0x10 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_thread_generic_wrapper+0x10/0x10 [spl]
Feb 06 18:54:01 ALIMOX kernel:  thread_generic_wrapper+0x5f/0x70 [spl]
Feb 06 18:54:01 ALIMOX kernel:  kthread+0xf2/0x120
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_kthread+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  ret_from_fork+0x47/0x70
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_kthread+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  ret_from_fork_asm+0x1b/0x30
Feb 06 18:54:01 ALIMOX kernel:  </TASK>
Feb 06 18:54:01 ALIMOX kernel: INFO: task pmxcfs:3082 blocked for more than 122 seconds.
Feb 06 18:54:01 ALIMOX kernel:       Tainted: P           O       6.8.12-7-pve #1
Feb 06 18:54:01 ALIMOX kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 06 18:54:01 ALIMOX kernel: task:pmxcfs          state:D stack:0     pid:3082  tgid:1734  ppid:1      flags:0x00004002
Feb 06 18:54:01 ALIMOX kernel: Call Trace:
Feb 06 18:54:01 ALIMOX kernel:  <TASK>
Feb 06 18:54:01 ALIMOX kernel:  __schedule+0x42b/0x1500
Feb 06 18:54:01 ALIMOX kernel:  schedule+0x33/0x110
Feb 06 18:54:01 ALIMOX kernel:  io_schedule+0x46/0x80
Feb 06 18:54:01 ALIMOX kernel:  cv_wait_common+0xac/0x140 [spl]
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  __cv_wait_io+0x18/0x30 [spl]
Feb 06 18:54:01 ALIMOX kernel:  txg_wait_synced_impl+0xe1/0x130 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  txg_wait_synced+0x10/0x60 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  dmu_tx_wait+0x2eb/0x460 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  dmu_tx_assign+0x162/0x510 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zfs_write+0x4a0/0xd70 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zpl_iter_write+0x11b/0x1b0 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  vfs_write+0x2a8/0x480
Feb 06 18:54:01 ALIMOX kernel:  __x64_sys_pwrite64+0xa6/0xd0
Feb 06 18:54:01 ALIMOX kernel:  x64_sys_call+0x2064/0x2480
Feb 06 18:54:01 ALIMOX kernel:  do_syscall_64+0x81/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? do_syscall_64+0x8d/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? exc_page_fault+0x94/0x1b0
Feb 06 18:54:01 ALIMOX kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Feb 06 18:54:01 ALIMOX kernel: RIP: 0033:0x78024e7d3437
Feb 06 18:54:01 ALIMOX kernel: RSP: 002b:0000780222bff110 EFLAGS: 00000297 ORIG_RAX: 0000000000000012
Feb 06 18:54:01 ALIMOX kernel: RAX: ffffffffffffffda RBX: 0000000000000018 RCX: 000078024e7d3437
Feb 06 18:54:01 ALIMOX kernel: RDX: 0000000000000018 RSI: 0000780222bff1b0 RDI: 0000000000000006
Feb 06 18:54:01 ALIMOX kernel: RBP: 0000780222bff1b0 R08: 0000000000000001 R09: 00000000e201fdeb
Feb 06 18:54:01 ALIMOX kernel: R10: 00000000002405d8 R11: 0000000000000297 R12: 00000000002405d8
Feb 06 18:54:01 ALIMOX kernel: R13: 0000000000000006 R14: 00006101b5b61968 R15: 00006101b5b61988
Feb 06 18:54:01 ALIMOX kernel:  </TASK>
Feb 06 18:54:01 ALIMOX kernel: INFO: task pveproxy worker:1894 blocked for more than 122 seconds.
Feb 06 18:54:01 ALIMOX kernel:       Tainted: P           O       6.8.12-7-pve #1
Feb 06 18:54:01 ALIMOX kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 06 18:54:01 ALIMOX kernel: task:pveproxy worker state:D stack:0     pid:1894  tgid:1894  ppid:1893   flags:0x00004002
Feb 06 18:54:01 ALIMOX kernel: Call Trace:
Feb 06 18:54:01 ALIMOX kernel:  <TASK>
Feb 06 18:54:01 ALIMOX kernel:  __schedule+0x42b/0x1500
Feb 06 18:54:01 ALIMOX kernel:  schedule+0x33/0x110
Feb 06 18:54:01 ALIMOX kernel:  io_schedule+0x46/0x80
Feb 06 18:54:01 ALIMOX kernel:  cv_wait_common+0xac/0x140 [spl]
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  __cv_wait_io+0x18/0x30 [spl]
Feb 06 18:54:01 ALIMOX kernel:  txg_wait_synced_impl+0xe1/0x130 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  txg_wait_synced+0x10/0x60 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  dmu_tx_wait+0x2eb/0x460 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  dmu_tx_assign+0x162/0x510 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zfs_write+0x4a0/0xd70 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zpl_iter_write+0x11b/0x1b0 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  vfs_write+0x2a8/0x480
Feb 06 18:54:01 ALIMOX kernel:  ksys_write+0x73/0x100
Feb 06 18:54:01 ALIMOX kernel:  __x64_sys_write+0x19/0x30
Feb 06 18:54:01 ALIMOX kernel:  x64_sys_call+0x200f/0x2480
Feb 06 18:54:01 ALIMOX kernel:  do_syscall_64+0x81/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? syscall_exit_to_user_mode+0x86/0x260
Feb 06 18:54:01 ALIMOX kernel:  ? do_syscall_64+0x8d/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? syscall_exit_to_user_mode+0x86/0x260
Feb 06 18:54:01 ALIMOX kernel:  ? do_syscall_64+0x8d/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? tick_program_event+0x43/0xa0
Feb 06 18:54:01 ALIMOX kernel:  ? hrtimer_interrupt+0x11f/0x250
Feb 06 18:54:01 ALIMOX kernel:  ? irqentry_exit_to_user_mode+0x7b/0x260
Feb 06 18:54:01 ALIMOX kernel:  ? irqentry_exit+0x43/0x50
Feb 06 18:54:01 ALIMOX kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Feb 06 18:54:01 ALIMOX kernel: RIP: 0033:0x7024e2be02c0
Feb 06 18:54:01 ALIMOX kernel: RSP: 002b:00007fff51985908 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Feb 06 18:54:01 ALIMOX kernel: RAX: ffffffffffffffda RBX: 000063cbfc8cb2a0 RCX: 00007024e2be02c0
Feb 06 18:54:01 ALIMOX kernel: RDX: 000000000000006b RSI: 000063cc04e89050 RDI: 0000000000000004
Feb 06 18:54:01 ALIMOX kernel: RBP: 000063cc04e89050 R08: 0000000000000000 R09: 000063cc04e48bd0
Feb 06 18:54:01 ALIMOX kernel: R10: 000063cc04b96d70 R11: 0000000000000202 R12: 000000000000006b
Feb 06 18:54:01 ALIMOX kernel: R13: 000063cbfc8cb2a0 R14: 0000000000000004 R15: 000063cc04e39360
Feb 06 18:54:01 ALIMOX kernel:  </TASK>
Feb 06 18:54:01 ALIMOX kernel: INFO: task pveproxy worker:1895 blocked for more than 122 seconds.
Feb 06 18:54:01 ALIMOX kernel:       Tainted: P           O       6.8.12-7-pve #1
Feb 06 18:54:01 ALIMOX kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 06 18:54:01 ALIMOX kernel: task:pveproxy worker state:D stack:0     pid:1895  tgid:1895  ppid:1893   flags:0x00000002
Feb 06 18:54:01 ALIMOX kernel: Call Trace:
Feb 06 18:54:01 ALIMOX kernel:  <TASK>
Feb 06 18:54:01 ALIMOX kernel:  __schedule+0x42b/0x1500
Feb 06 18:54:01 ALIMOX kernel:  ? dput+0x3f/0x1b0
Feb 06 18:54:01 ALIMOX kernel:  ? get_cached_acl+0x55/0xb0
Feb 06 18:54:01 ALIMOX kernel:  schedule+0x33/0x110
Feb 06 18:54:01 ALIMOX kernel:  cv_wait_common+0x109/0x140 [spl]
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  __cv_wait+0x15/0x30 [spl]
Feb 06 18:54:01 ALIMOX kernel:  zfs_rangelock_enter_impl+0x16b/0x670 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zfs_rangelock_enter+0x11/0x30 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zfs_write+0x23e/0xd70 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  ? rrw_exit+0x72/0x170 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zpl_iter_write+0x11b/0x1b0 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  vfs_write+0x2a8/0x480
Feb 06 18:54:01 ALIMOX kernel:  ksys_write+0x73/0x100
Feb 06 18:54:01 ALIMOX kernel:  __x64_sys_write+0x19/0x30
Feb 06 18:54:01 ALIMOX kernel:  x64_sys_call+0x200f/0x2480
Feb 06 18:54:01 ALIMOX kernel:  do_syscall_64+0x81/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? __count_memcg_events+0x6f/0xe0
Feb 06 18:54:01 ALIMOX kernel:  ? count_memcg_events.constprop.0+0x2a/0x50
Feb 06 18:54:01 ALIMOX kernel:  ? handle_mm_fault+0xad/0x380
Feb 06 18:54:01 ALIMOX kernel:  ? do_user_addr_fault+0x33e/0x660
Feb 06 18:54:01 ALIMOX kernel:  ? irqentry_exit_to_user_mode+0x7b/0x260
Feb 06 18:54:01 ALIMOX kernel:  ? irqentry_exit+0x43/0x50
Feb 06 18:54:01 ALIMOX kernel:  ? exc_page_fault+0x94/0x1b0
Feb 06 18:54:01 ALIMOX kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Feb 06 18:54:01 ALIMOX kernel: RIP: 0033:0x7024e2be02c0
Feb 06 18:54:01 ALIMOX kernel: RSP: 002b:00007fff51985908 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Feb 06 18:54:01 ALIMOX kernel: RAX: ffffffffffffffda RBX: 000063cbfc8cb2a0 RCX: 00007024e2be02c0
Feb 06 18:54:01 ALIMOX kernel: RDX: 000000000000006f RSI: 000063cc04f11f20 RDI: 0000000000000004
Feb 06 18:54:01 ALIMOX kernel: RBP: 000063cc04f11f20 R08: 0000000000000000 R09: 000063cc04e48bd0
Feb 06 18:54:01 ALIMOX kernel: R10: 000063cc04b96d70 R11: 0000000000000202 R12: 000000000000006f
Feb 06 18:54:01 ALIMOX kernel: R13: 000063cbfc8cb2a0 R14: 0000000000000004 R15: 000063cc04e6fe70
Feb 06 18:54:01 ALIMOX kernel:  </TASK>
Feb 06 18:54:01 ALIMOX kernel: INFO: task pveproxy worker:1896 blocked for more than 122 seconds.
Feb 06 18:54:01 ALIMOX kernel:       Tainted: P           O       6.8.12-7-pve #1
Feb 06 18:54:01 ALIMOX kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 06 18:54:01 ALIMOX kernel: task:pveproxy worker state:D stack:0     pid:1896  tgid:1896  ppid:1893   flags:0x00004002
Feb 06 18:54:01 ALIMOX kernel: Call Trace:
Feb 06 18:54:01 ALIMOX kernel:  <TASK>
Feb 06 18:54:01 ALIMOX kernel:  __schedule+0x42b/0x1500
Feb 06 18:54:01 ALIMOX kernel:  ? __tcp_transmit_skb+0xab4/0xe90
Feb 06 18:54:01 ALIMOX kernel:  schedule+0x33/0x110
Feb 06 18:54:01 ALIMOX kernel:  io_schedule+0x46/0x80
Feb 06 18:54:01 ALIMOX kernel:  cv_wait_common+0xac/0x140 [spl]
Feb 06 18:54:01 ALIMOX kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Feb 06 18:54:01 ALIMOX kernel:  __cv_wait_io+0x18/0x30 [spl]
Feb 06 18:54:01 ALIMOX kernel:  txg_wait_synced_impl+0xe1/0x130 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  txg_wait_synced+0x10/0x60 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  dmu_tx_wait+0x2eb/0x460 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  dmu_tx_assign+0x162/0x510 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zfs_write+0x4a0/0xd70 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  zpl_iter_write+0x11b/0x1b0 [zfs]
Feb 06 18:54:01 ALIMOX kernel:  vfs_write+0x2a8/0x480
Feb 06 18:54:01 ALIMOX kernel:  ksys_write+0x73/0x100
Feb 06 18:54:01 ALIMOX kernel:  __x64_sys_write+0x19/0x30
Feb 06 18:54:01 ALIMOX kernel:  x64_sys_call+0x200f/0x2480
Feb 06 18:54:01 ALIMOX kernel:  do_syscall_64+0x81/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? vfs_write+0x325/0x480
Feb 06 18:54:01 ALIMOX kernel:  ? vfs_write+0x325/0x480
Feb 06 18:54:01 ALIMOX kernel:  ? __rseq_handle_notify_resume+0xa5/0x4d0
Feb 06 18:54:01 ALIMOX kernel:  ? syscall_exit_to_user_mode+0x86/0x260
Feb 06 18:54:01 ALIMOX kernel:  ? do_syscall_64+0x8d/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? do_syscall_64+0x8d/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? syscall_exit_to_user_mode+0x86/0x260
Feb 06 18:54:01 ALIMOX kernel:  ? do_syscall_64+0x8d/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? do_syscall_64+0x8d/0x170
Feb 06 18:54:01 ALIMOX kernel:  ? irqentry_exit_to_user_mode+0x7b/0x260
Feb 06 18:54:01 ALIMOX kernel:  ? irqentry_exit+0x43/0x50
Feb 06 18:54:01 ALIMOX kernel:  entry_SYSCALL_64_after_hwframe+0x78/0x80
Feb 06 18:54:01 ALIMOX kernel: RIP: 0033:0x7024e2be02c0
Feb 06 18:54:01 ALIMOX kernel: RSP: 002b:00007fff51985998 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Feb 06 18:54:01 ALIMOX kernel: RAX: ffffffffffffffda RBX: 000063cbfc8cb2a0 RCX: 00007024e2be02c0
Feb 06 18:54:01 ALIMOX kernel: RDX: 0000000000004000 RSI: 000063cc05373a90 RDI: 000000000000000d
Feb 06 18:54:01 ALIMOX kernel: RBP: 0000000000000018 R08: 0000000000000001 R09: 000063cc0513a638
Feb 06 18:54:01 ALIMOX kernel: R10: 000063cc051ae858 R11: 0000000000000202 R12: 000063cc04e48bf8
Feb 06 18:54:01 ALIMOX kernel: R13: 000000000000000d R14: 000063cc04e48be8 R15: 0000000000000000
Feb 06 18:54:01 ALIMOX kernel:  </TASK>
Feb 06 18:54:01 ALIMOX pveproxy[1894]: problem with client ::ffff:192.168.60.2; Broken pipe
Feb 06 18:54:01 ALIMOX pveproxy[1895]: problem with client ::ffff:192.168.60.2; Broken pipe
Feb 06 18:54:01 ALIMOX pveproxy[1896]: problem with client ::ffff:192.168.60.2; Connection timed out
Feb 06 18:54:01 ALIMOX pvestatd[1873]: status update time (169.929 seconds)
Feb 06 18:54:01 ALIMOX pve-firewall[1857]: firewall update time (169.874 seconds)
Feb 06 18:54:06 ALIMOX pve-ha-crm[1892]: loop take too long (120 seconds)
Feb 06 18:54:06 ALIMOX pve-ha-lrm[1903]: loop take too long (175 seconds)

Second Try over 10 Gigabit connection
Code: 
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Feb  6 18:47:10 CET 2025 on pts/0
root@ALIMOX:~# journalctl -f
Feb 06 18:56:27 ALIMOX systemd[3993]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Feb 06 18:56:27 ALIMOX systemd[3993]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Feb 06 18:56:27 ALIMOX systemd[3993]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Feb 06 18:56:27 ALIMOX systemd[3993]: Reached target sockets.target - Sockets.
Feb 06 18:56:27 ALIMOX systemd[3993]: Reached target basic.target - Basic System.
Feb 06 18:56:27 ALIMOX systemd[3993]: Reached target default.target - Main User Target.
Feb 06 18:56:27 ALIMOX systemd[3993]: Startup finished in 143ms.
Feb 06 18:56:27 ALIMOX systemd[1]: Started user@0.service - User Manager for UID 0.
Feb 06 18:56:27 ALIMOX systemd[1]: Started session-5.scope - Session 5 of User root.
Feb 06 18:56:27 ALIMOX login[4008]: ROOT LOGIN  on '/dev/pts/0'
Feb 06 18:58:47 ALIMOX pveproxy[1895]: problem with client ::ffff:192.168.50.2; Connection timed out
Feb 06 18:58:47 ALIMOX pvestatd[1873]: status update time (56.777 seconds)
Feb 06 18:58:47 ALIMOX systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Feb 06 18:58:47 ALIMOX systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Feb 06 18:58:47 ALIMOX systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Feb 06 18:58:47 ALIMOX systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Feb 06 18:58:48 ALIMOX pve-firewall[1857]: firewall update time (66.508 seconds)
Feb 06 18:58:52 ALIMOX pve-ha-crm[1892]: loop take too long (46 seconds)
Feb 06 18:58:52 ALIMOX pve-ha-lrm[1903]: loop take too long (71 seconds)
Feb 06 19:00:44 ALIMOX pveproxy[1895]: problem with client ::ffff:192.168.50.2; Connection timed out
Feb 06 19:00:44 ALIMOX pvestatd[1873]: status update time (47.498 seconds)
Feb 06 19:00:44 ALIMOX pve-firewall[1857]: firewall update time (56.479 seconds)
Feb 06 19:00:49 ALIMOX pve-ha-crm[1892]: loop take too long (42 seconds)
Feb 06 19:00:49 ALIMOX pve-ha-lrm[1903]: loop take too long (61 seconds)
 
Network Config
Code: 
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto ens6f0
iface ens6f0 inet manual

auto enp7s0
iface enp7s0 inet static
        address 192.168.10.4/24
        gateway 192.168.10.1

auto enp10s0
iface enp10s0 inet manual

auto ens6f1
iface ens6f1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.50.10/24
        bridge-ports ens6f0
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet static
        address 192.168.60.10/24
        bridge-ports enp10s0
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*
 
if i understand that ouput it has more to do with an Debian issue ?
or Stroage issue with ZFS ?

has anyone issues if Proxmox is installed on an ZFS Mirror ?
 
i found that issue with try and error..
it seems if Proxmox is installed on my 2 identical SSD with ZFS Mirror --> Issue i cant copy anything to it..
if Proxmox is installed on one of that SSD with EXT4 --> no issues at all ( doesnt matter which of that 2 SSD's )
 
You must log in or register to reply here.
Top Bottom