System not boot with "invalid parameter for zfs_scan_issue_strategy" error. Had to rollback

hatred

New Member
Feb 19, 2023
4
0
1
After the update, I could not load Proxmox with the 5.15.85-1 kernel - the invalid parameter for zfs_scan_issue_strategy error appeared. And I get thrown into initramfs I had to roll back to 5.15.83-1, which boots nice.

Please help me to figure out what is this error and how to fix it?

Code:
cat /sys/module/zfs/parameters/zfs_scan_issue_strategy
shows
Code:
0

Code:
cat /etc/modprobe.d/zfs.conf
shows
Code:
options zfs zfs_arc_max=17179869184 zfs_vdev_scrub_max_active=1 zfs_scan_issue_strategy 1
 
Last edited:
Hi,

Code:
options zfs zfs_arc_max=17179869184 zfs_vdev_scrub_max_active=1 zfs_scan_issue_strategy 1
You have a missed an equals sign here between the parameter name (zfs_scan_issue_strategy) and the value (1).

This should actually be:
Code:
options zfs zfs_arc_max=17179869184 zfs_vdev_scrub_max_active=1 zfs_scan_issue_strategy=1
 
Hi,


You have a missed an equals sign here between the parameter name (zfs_scan_issue_strategy) and the value (1).

This should actually be:
Code:
options zfs zfs_arc_max=17179869184 zfs_vdev_scrub_max_active=1 zfs_scan_issue_strategy=1
Thank you! But how can I change it in new kernel?
 
This should fix it for the newer kernel, since it a simple configuration error.
Did you try booting into the newer kernel with this changed?
 
This should fix it for the newer kernel, since it a simple configuration error.
Did you try booting into the newer kernel with this changed?
Yes I tried boot new kernel with this changed, but problem still exists and when I am at initramfs trying to edit /etc/modprobe.d/zfs.conf I see same error (no equation). Maybe I should reinstall new kernel in some way?
 
Yes I tried boot new kernel with this changed, but problem still exists and when I am at initramfs trying to edit /etc/modprobe.d/zfs.conf I see same error (no equation). Maybe I should reinstall new kernel in some way?
Did you run update-initramfs -u -k version for that kernel version? Or run it with all to apply the current settings in /etc/modprobe.d/ to all kernels but then you also change the known-to-work previous ones!
 
  • Like
Reactions: hatred