node fails to start after updating kernel to 6.8.12-4

n0x0n

Member
Jan 20, 2022
29
2
8
Homelab setting, pve 8.2.7, root on zfs, node has 3 disks,
I updated one of my nodes this evening and it didn't come up again. Quick look showed that it just stopped after it found sdb. Ctrl-C dropped me to an initrd shell. I just rebooted into 6.8.12-3 and it booted fine.

Taken from the successful 6.8.12-3 boot, this is where the newer kernel just stopped booting
Code:
[    3.245303] sd 7:0:0:0: Attached scsi generic sg1 type 0
[    3.248864] sd 7:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[    3.249219] sd 7:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[    3.253878]  sdb: sdb1
[    3.254494] sd 7:0:0:0: [sdb] Attached SCSI disk


It's already late in my timezone and I'm quite sleepy so I won't investigate until tomorrow.
Happy to look for info if someone tells me where to dig.
 
Last edited:
Updated a second node, just some things I realized, maybe that's interesting for someone:
  • update-initramfs for 6.8.12-4 took a really long time. Same happened yesterday on the other node: It took like 3-5 minutes!
  • Building a new initrd usually takes ~30 seconds or so. Load on the machine was normal during that time, too
 

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 yours easily in our online shop.

Buy now!