Hello. I'm starting to learn how to use Proxmox in deep.
I've read recent posts that auto_trim is causing problems with the latest kernel: Github issues
I've also been looking at my LOG, and from what I understand the last task it performed before the errors started was: "Workqueue: writeback wb_workfn"
Proxmox version: 8.1.4
Kernel Version: 6.5.11-7-pve
The server, Proxmox installation and SSD disks are new.
The only virtual machine that is working on it is Windows Server 2022.
I followed the installation steps in the Proxmox guide to install this OS and I also installed the VirtIO drivers.
I've attached the hardware options of the virtual machine in a screenshot.
As I have seen and understood in the LOGS, the server froze in the early morning, around 00:37 AM with the last task:
"Jan 29 00:37:05 ml350fit2 kernel: Workqueue: writeback wb_workfn (flush-8:0)" (line 183).
Then it started giving task abort and abort request errors on the SDA hard drive.
At 6:07 AM a forced reset was done and since then it has not caused any problems.
I have checked the SDA SMART several times and done tests and it says it is correct (PASSED)
I would like to know what caused the problem and prevent it from happening again.
Log: Here, is in Drive
I give the moderators permission to edit my post to improve the search to help other users.
Thanks for the help.
I've read recent posts that auto_trim is causing problems with the latest kernel: Github issues
I've also been looking at my LOG, and from what I understand the last task it performed before the errors started was: "Workqueue: writeback wb_workfn"
Proxmox version: 8.1.4
Kernel Version: 6.5.11-7-pve
The server, Proxmox installation and SSD disks are new.
The only virtual machine that is working on it is Windows Server 2022.
I followed the installation steps in the Proxmox guide to install this OS and I also installed the VirtIO drivers.
I've attached the hardware options of the virtual machine in a screenshot.
As I have seen and understood in the LOGS, the server froze in the early morning, around 00:37 AM with the last task:
"Jan 29 00:37:05 ml350fit2 kernel: Workqueue: writeback wb_workfn (flush-8:0)" (line 183).
Then it started giving task abort and abort request errors on the SDA hard drive.
At 6:07 AM a forced reset was done and since then it has not caused any problems.
I have checked the SDA SMART several times and done tests and it says it is correct (PASSED)
I would like to know what caused the problem and prevent it from happening again.
Log: Here, is in Drive
I give the moderators permission to edit my post to improve the search to help other users.
Thanks for the help.
Attachments
Last edited: