RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

Update fields so properly tracked.

Not a showstopper for 7.3.
Needs additional information from George.

Tested this with snap3 and its no longer an issue.