new install, gui grayed out - task vgs:2789 blocked

[WilliamB]

I have a new install and a few hours after a fresh boot the gui becomes grayed out. I see this following error in syslog.

How to fix?

---
proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.3.18-3-pve: 5.3.18-3

Apr 30 01:13:26 debian0-8 kernel: [15709.628713] INFO: task vgs:2789 blocked for more than 1208 seconds.
Apr 30 01:13:26 debian0-8 kernel: [15709.628754] Tainted: P O 5.3.18-3-pve #1
Apr 30 01:13:26 debian0-8 kernel: [15709.628777] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 30 01:13:26 debian0-8 kernel: [15709.628809] vgs D 0 2789 1292 0x00000000
Apr 30 01:13:26 debian0-8 kernel: [15709.628810] Call Trace:
Apr 30 01:13:26 debian0-8 kernel: [15709.628816] __schedule+0x2bb/0x660
Apr 30 01:13:26 debian0-8 kernel: [15709.628818] ? enqueue_task_fair+0x121/0x450
Apr 30 01:13:26 debian0-8 kernel: [15709.628820] schedule+0x33/0xa0
Apr 30 01:13:26 debian0-8 kernel: [15709.628821] schedule_timeout+0x205/0x300
Apr 30 01:13:26 debian0-8 kernel: [15709.628823] ? ttwu_do_activate+0x5a/0x70
Apr 30 01:13:26 debian0-8 kernel: [15709.628824] wait_for_completion+0xb7/0x140
Apr 30 01:13:26 debian0-8 kernel: [15709.628825] ? wake_up_q+0x80/0x80
Apr 30 01:13:26 debian0-8 kernel: [15709.628828] __flush_work+0x131/0x1e0
Apr 30 01:13:26 debian0-8 kernel: [15709.628829] ? worker_detach_from_pool+0xb0/0xb0
Apr 30 01:13:26 debian0-8 kernel: [15709.628830] ? work_busy+0x90/0x90
Apr 30 01:13:26 debian0-8 kernel: [15709.628831] __cancel_work_timer+0x115/0x190
Apr 30 01:13:26 debian0-8 kernel: [15709.628833] ? exact_lock+0x11/0x20
Apr 30 01:13:26 debian0-8 kernel: [15709.628836] ? kobj_lookup+0xec/0x160
Apr 30 01:13:26 debian0-8 kernel: [15709.628837] cancel_delayed_work_sync+0x13/0x20
Apr 30 01:13:26 debian0-8 kernel: [15709.628838] disk_block_events+0x78/0x80
Apr 30 01:13:26 debian0-8 kernel: [15709.628841] __blkdev_get+0x72/0x560
Apr 30 01:13:26 debian0-8 kernel: [15709.628842] blkdev_get+0xe0/0x140
Apr 30 01:13:26 debian0-8 kernel: [15709.628843] ? blkdev_get_by_dev+0x50/0x50
Apr 30 01:13:26 debian0-8 kernel: [15709.628844] blkdev_open+0x92/0x100
Apr 30 01:13:26 debian0-8 kernel: [15709.628847] do_dentry_open+0x143/0x3a0
Apr 30 01:13:26 debian0-8 kernel: [15709.628848] vfs_open+0x2d/0x30
Apr 30 01:13:26 debian0-8 kernel: [15709.628850] path_openat+0x2d2/0x1570
Apr 30 01:13:26 debian0-8 kernel: [15709.628851] ? aio_read+0xfe/0x150
Apr 30 01:13:26 debian0-8 kernel: [15709.628854] ? __do_page_fault+0x250/0x4c0
Apr 30 01:13:26 debian0-8 kernel: [15709.628856] ? mem_cgroup_try_charge+0x71/0x190
Apr 30 01:13:26 debian0-8 kernel: [15709.628857] do_filp_open+0x93/0x100
Apr 30 01:13:26 debian0-8 kernel: [15709.628859] ? __alloc_fd+0x46/0x150
Apr 30 01:13:26 debian0-8 kernel: [15709.628860] do_sys_open+0x177/0x280
Apr 30 01:13:26 debian0-8 kernel: [15709.628862] ? __x64_sys_io_submit+0xa9/0x190
Apr 30 01:13:26 debian0-8 kernel: [15709.628863] __x64_sys_openat+0x20/0x30
Apr 30 01:13:26 debian0-8 kernel: [15709.628865] do_syscall_64+0x5a/0x130
Apr 30 01:13:26 debian0-8 kernel: [15709.628867] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 30 01:13:26 debian0-8 kernel: [15709.628869] RIP: 0033:0x7f3eaf12e1ae
Apr 30 01:13:26 debian0-8 kernel: [15709.628872] Code: Bad RIP value.
Apr 30 01:13:26 debian0-8 kernel: [15709.628872] RSP: 002b:00007fff6284bf80 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
Apr 30 01:13:26 debian0-8 kernel: [15709.628873] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f3eaf12e1ae
Apr 30 01:13:26 debian0-8 kernel: [15709.628874] RDX: 0000000000044000 RSI: 000055997d501dc0 RDI: 00000000ffffff9c
Apr 30 01:13:26 debian0-8 kernel: [15709.628874] RBP: 00007fff6284c0e0 R08: 000055997d64f000 R09: 0000000000000000
Apr 30 01:13:26 debian0-8 kernel: [15709.628875] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff6284cedf
Apr 30 01:13:26 debian0-8 kernel: [15709.628875] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

 

[Moayad]

Hi,

Please don't double post, my colleague has answered here[0]

[0] https://forum.proxmox.com/threads/n...-for-more-than-1208-seconds.69157/post-310555

 

[WilliamB]

No intention to double post, first one did not show up.

After a day of troubleshooting found an external USB backup drive was causing this. After disconnecting it hasn't happened since.