proxmox 6.3-3 kernel 5.4.78-2-pve lack libata.force kernel parameter

jsetzer

New Member
Feb 14, 2021
1
0
1
48
Hello,

after installtion pve 6.3-3 with kernel 5.4.78-2-pve I got problemes with two disks connected to ASM1062. (The two SSDs are conntect to Intel chipset, the big data disks are conntected to the ASM1062.) The chip is know for timing problems so I dected and eleminates the errors on ubuntu and debian using libata.force=3:1.5G,4:1.5G kernel parameter.
So I thougth, I only have to add these paramter to the pve grub ...

BUT the pve kernel is not configured (CONFIG_ATA_FORCE) to recognize this parameter.

So I try to build a pve-kernel on my on:
Clone the repository
git clone https://github.com/proxmox/pve-kernel
and update the changelog and manipulate the debian/rules (adding -e CONFIG_ATA_FORCE \)
and call make.

But it is not possible to build the kernel package because the zfsonlinux repository is no accessable (with my github account).

Is there a change to get a pve-kernel with enabled libata.force parameter?
Or how to build a pve kernel on my on?


Thanks for your help,
best regards

Jan Setzer
 

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
6,497
1,121
164
that KConfig was only introduced with kernels >= 5.6, before that libata.force was always baked into the kernel.. its default is also yes, it is likely only disabled in practice for very small architectures where the space savings can be worth it for some use cases..
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!