Ubuntu

Trouble booting kernel 4.13.0-32 generic

Asked by Jim Carey

I've been running 17.10 for a while. When my system updated to the 4.13.0-32 kernel (x86_64), it stopped booting. The splash screen comes up and that's it. No disk activity. When I disabled the splash screen, I could see messages about lvmetad not being connected. The system boots fine with the 4.13.0-31 kernel. I'm not really sure how to debug this. The system disk is encrypted with luks, so I suspect there are no logs to look at (since I never get prompted for the disk password).

I'm hoping the next kernel update fixes this, but what steps can I take to debug this?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

I suggest you report a bug

Revision history for this message
Jim Carey (james-carey) said : 		#2

I would, but I'd like to have a better idea what to include.

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

Just report it and the bug guys will ask you for details as they need them

Can you help with this problem?

Provide an answer of your own, or ask Jim Carey for more information if necessary.

To post a message you must log in.