Description of problem:
We have observed that when kdump is pointed at non-root disk drive
and later that drive is removed the kernel won't complete booting.
[Non-root because it was on a 32TB machine and there wasn't enough
space on the root drive.)
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
George:
System does not boot means the normal kernel can not boot?
Have you add it to /etc/fstab or somewhere else? I guess systemd is waiting for the mount happens and timeout, is this your case and do you have a console log?
Thanks
Dave
Sorry to say that the log got deleted in a cleanup sweep.
I will work on reproducing this and provide a log.
However, the kernel booted and was doing systemd-udevd stuff
and my memory is that it was hung trying to start kdump.
That said, I've seen kdump fail to start many times without
causing the boot to hang (we get to login); so I am begining
to suspect myself of user error.
Description of problem: We have observed that when kdump is pointed at non-root disk drive and later that drive is removed the kernel won't complete booting. [Non-root because it was on a 32TB machine and there wasn't enough space on the root drive.) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: