Kernel Panic When Booting Into FIPS Mode
Sorry if you see this twice, I may have goofed:
Hey,
So I was playing around with trying to get a CentOS 6.5 system FIPS-140 complaint. However, my system panics because it cannot find the hmac file associated with my kernel. It’s basically as what is going on is described in this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id
4 thoughts on - Kernel Panic When Booting Into FIPS Mode
I don’t have expertise on this issue, but it would be interesting if that bit of shell script there were adjusted to also print out the fstab and possibly other diagnostic information relevant to the problem. That way, you might get a clue as to where /boot is coming from. Then again, I’m not even sure if that is something you can edit with your current situation. You did say the system was unbootable. It’s probably an edit you’d need to make while mounting the hard disk from another system, like a live cd for example.
I don’t have expertise on this issue, but it would be interesting if that bit of shell script there were adjusted to also print out the fstab and possibly other diagnostic information relevant to the problem. That way, you might get a clue as to where /boot is coming from. Then again, I’m not even sure if that is something you can edit with your current situation. You did say the system was unbootable. It’s probably an edit you’d need to make while mounting the hard disk from another system, like a live cd for example.
Is /boot a separate filesystem? If so, I would check to see if it is actually mounted as
/boot from the initramfs. It might just be /, at least until the initramfs is unmounted and the root filesystem is mounted on top of it.
That’s what I’d look for.
/boot separate filesystem == it’s / on initial boot
/boot part of / == it’s /boot on initial boot.
–Russell
So as usual, I was skipping a step. I did need to include the bootkernel parameter since /boot was separate from root. It wasn’t getting mounted. Everything seems to be working now.