Bug 838535 - dracut: FATAL: Don't know how to handle 'root=UUID=9fbf2fe5-a20c-...'
dracut: FATAL: Don't know how to handle 'root=UUID=9fbf2fe5-a20c-...'
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: kexec-tools (Show other bugs)
17
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Dave Young
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-09 08:01 EDT by Osamu MATSUMOTO
Modified: 2012-07-10 21:45 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-07-10 21:45:30 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
add rootfs-block module to mkdumprd (948 bytes, patch)
2012-07-09 08:17 EDT, Osamu MATSUMOTO
no flags Details | Diff
Previous patch missed argument. Fix it. (950 bytes, patch)
2012-07-09 08:26 EDT, Osamu MATSUMOTO
no flags Details | Diff

  None (edit)
Description Osamu MATSUMOTO 2012-07-09 08:01:12 EDT
Description of problem:

kernel panic occurs in kdump process which caused by  root filesystem errors.
will fail with the following error message:

dracut: FATAL: Don't know how to handle 'root=UUID=9fbf2fe5-a20c-...'

This message come from init script in kdump's initramfs.

Version-Release number of selected component (if applicable):
kernel 3.3.7
kexec-tools-2.0.3-38.fc17.x86_64

How reproducible:

Steps to Reproduce:
1. Assign root filesystem by UUID 
  my /proc/cmdline is 
BOOT_IMAGE=/boot/vmlinuz-3.3.7-3941.4.fc17.x86_64 root=UUID=9fbf2fe5-a20c-47be-85b0-88b076eec4f8 ro crashkernel=128M rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8
2. use default /etc/sysconfig/kdump , no change comdline argument.
KDUMP_COMMANDLINE=""
3. start kdump service
4. echo 'c' >  /proc/sysrq-trigger 
  
Actual results:

kdump kernel will be panic with following message.

dracut: FATAL: Don't know how to handle 'root=UUID=9fbf2fe5-a20c-...'

Expected results:
mount rootfs and save kernel dump.

Additional info:
I attached patch for this issue.
I think $rootok in init script must be setted by 95rootfs-block/parse-block.sh
So, mkinitrd shuld append rootfs-block as dracut module.
Comment 1 Osamu MATSUMOTO 2012-07-09 08:17:27 EDT
Created attachment 597061 [details]
add rootfs-block module  to mkdumprd
Comment 2 Osamu MATSUMOTO 2012-07-09 08:26:44 EDT
Created attachment 597063 [details]
Previous patch missed argument. Fix it.

Replace argument by s/add/--add/
Comment 3 Dave Young 2012-07-09 22:12:11 EDT
Hi,

I can not reproduce this problem. the rootfs-block is a must have module for dracut. It should be included automatically even without the "--add rootfs-block".

Could you add "-v" instead of "--add rootfs-block", and run: "kdumpctl restart", then post the output here?

Thanks
Comment 4 Osamu MATSUMOTO 2012-07-10 01:16:05 EDT
Hi,

I have tried "-v" to mkdumprd. This affected at running mkdumprd, so touch /etc/kdump.conf and restart kdump service.

Following messages

Jul 10 14:03:10 a04701 kdumpctl[6073]: Detected /etc/kdump.conf or /boot/vmlinuz-3.3.7-3941.4.fc17.x86_64 change
Jul 10 14:03:10 a04701 kdumpctl[6073]: Rebuilding /boot/initramfs-3.3.7-3941.4.fc17.x86_64kdump.img
Jul 10 14:03:10 a04701 kdumpctl[6073]: rpmversion
Jul 10 14:03:10 a04701 kdumpctl[6073]: kernel-modules
Jul 10 14:03:12 a04701 kdumpctl[6073]: I: Possible missing firmware "aic94xx-seq.fw" for kernel module "aic94xx.ko"
Jul 10 14:03:12 a04701 kdumpctl[6073]: I: Possible missing firmware "ql2500_fw.bin" for kernel module "qla2xxx.ko"
Jul 10 14:03:12 a04701 kdumpctl[6073]: I: Possible missing firmware "ql2400_fw.bin" for kernel module "qla2xxx.ko"
Jul 10 14:03:12 a04701 kdumpctl[6073]: I: Possible missing firmware "ql2322_fw.bin" for kernel module "qla2xxx.ko"
Jul 10 14:03:12 a04701 kdumpctl[6073]: I: Possible missing firmware "ql2300_fw.bin" for kernel module "qla2xxx.ko"
Jul 10 14:03:12 a04701 kdumpctl[6073]: I: Possible missing firmware "ql2200_fw.bin" for kernel module "qla2xxx.ko"
Jul 10 14:03:12 a04701 kdumpctl[6073]: I: Possible missing firmware "ql2100_fw.bin" for kernel module "qla2xxx.ko"
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Possible missing firmware "ct2fw.bin" for kernel module "bfa.ko"
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Possible missing firmware "ctfw.bin" for kernel module "bfa.ko"
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Possible missing firmware "cbfw.bin" for kernel module "bfa.ko"
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver nfs_acl
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:13 a04701 kdumpctl[6073]: I: Omitting driver lockd
Jul 10 14:03:14 a04701 kdumpctl[6073]: fstab-sys
Jul 10 14:03:14 a04701 kdumpctl[6073]: udev-rules
Jul 10 14:03:14 a04701 kdumpctl[6073]: I: Skipping udev rule: 50-udev.rules
Jul 10 14:03:14 a04701 kdumpctl[6073]: I: Skipping udev rule: 95-late.rules
Jul 10 14:03:14 a04701 kdumpctl[6073]: I: Skipping udev rule: 50-firmware.rules
Jul 10 14:03:14 a04701 kdumpctl[6073]: base
Jul 10 14:03:15 a04701 kdumpctl[6073]: fs-lib
Jul 10 14:03:15 a04701 kdumpctl[6073]: I: Skipping program xfs_db as it cannot be found and is flagged to be optional
Jul 10 14:03:15 a04701 kdumpctl[6073]: I: Skipping program xfs_check as it cannot be found and is flagged to be optional
Jul 10 14:03:15 a04701 kdumpctl[6073]: I: Skipping program xfs_repair as it cannot be found and is flagged to be optional
Jul 10 14:03:15 a04701 kdumpctl[6073]: I: Skipping program jfs_fsck as it cannot be found and is flagged to be optional
Jul 10 14:03:15 a04701 kdumpctl[6073]: I: Skipping program reiserfsck as it cannot be found and is flagged to be optional
Jul 10 14:03:15 a04701 kdumpctl[6073]: kdumpbase
Jul 10 14:03:15 a04701 kdumpctl[6073]: shutdown
Jul 10 14:03:15 a04701 kdumpctl[6073]: I: *** Including modules done ***
Jul 10 14:03:26 a04701 kdumpctl[6073]: I: Wrote /boot/initramfs-3.3.7-3941.4.fc17.x86_64kdump.img:
Jul 10 14:03:26 a04701 kdumpctl[6073]: I: -rw-r--r-- 1 root root 9559471 Jul 10 14:03 /boot/initramfs-3.3.7-3941.4.fc17.x86_64kdump.img
Jul 10 14:03:26 a04701 kdump: kexec: loaded kdump kernel
Jul 10 14:03:26 a04701 kdumpctl[6073]: Starting kdump:
Jul 10 14:03:26 a04701 kdump: started up

also rootfs-block not included.
% gunzip -c /boot/initramfs-3.3.7-3941.4.fc17.x86_64kdump.img | cpio --list |grep roofs
52076 blocks
%
Comment 5 Dave Young 2012-07-10 02:16:43 EDT
can you tell what version of dracut do you use?
rpm -qa|grep dracut

Also kexec-tools-2.0.3-38 is a little old, can you try below 2.0.3-47?
http://koji.fedoraproject.org/koji/buildinfo?buildID=317113
Comment 6 Osamu MATSUMOTO 2012-07-10 03:31:32 EDT
Hi,

I had checked kexec-tools rawhide version, It's work fine.

https://bugzilla.redhat.com/show_bug.cgi?id=817044

This suggest is fix this issue.

"-m kdumpbase" is not include rootfs-block, but use "--add kdumpbase"
mean including default dracut modules as you indicate.

Thanks!
Comment 7 Dave Young 2012-07-10 21:45:30 EDT
Hi,

latest f17 update already contains this fix, thanks for the test.
Will close this bug.

Note You need to log in before you can comment on or make changes to this bug.