693015 – mdadm: No arrays found in config file or automatically

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.

Bug 693015 - mdadm: No arrays found in config file or automatically

Summary: mdadm: No arrays found in config file or automatically

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	kexec-tools
Sub Component:
Version:	6.1
Hardware:	All
OS:	Linux
Priority:	urgent
Severity:	urgent
Target Milestone:	rc
Target Release:	6.1
Assignee:	Cong Wang
QA Contact:	Kernel Dump QE
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2011-04-02 01:47 UTC by Chao Ye
Modified:	2013-09-30 02:23 UTC (History)
CC List:	4 users (show)
Fixed In Version:	kexec-tools-2_0_0-184_el6
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2011-05-19 14:16:36 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2011:0736	0	normal	SHIPPED_LIVE	kexec-tools bug fix update	2011-05-18 18:09:18 UTC

Description Chao Ye 2011-04-02 01:47:45 UTC

Description of problem:
When run kdump tier1 crasherpanic test, kdump failed to mount ext4 partition in second kernel:
========================================================================
Creating Block Devices 
Creating block device loop0 
Creating block device loop1 
Creating block device loop2 
Creating block device loop3 
Creating block device loop4 
Creating block device loop5 
Creating block device loop6 
Creating block device loop7 
Creating block device ram0 
Creating block device ram1 
Creating block device ram10 
Creating block device ram11 
Creating block device ram12 
Creating block device ram13 
Creating block device ram14 
Creating block device ram15 
Creating block device ram2 
Creating block device ram3 
Creating block device ram4 
Creating block device ram5 
Creating block device ram6 
Creating block device ram7 
Creating block device ram8 
Creating block device ram9 
Creating block device sda 
 sda: sda1 sda2 
Creating block device sdb 
 sdb: sdb1 
Creating block device sr0 
mdadm: No arrays found in config file or automatically 
Free memory/Total memory (free %): 90012 / 118608 ( 75.8903 ) 
Saving to the local filesystem UUID=2d8ba697-5c8f-467d-b248-0bdaf0c2106e 
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize] 
		[-I inode_buffer_blocks] [-P process_inode_size] 
		[-l|-L bad_blocks_file] [-C fd] [-j external_journal] 
		[-E extended-options] device 
 
Emergency help: 
 -p                   Automatic repair (no questions) 
 -n                   Make no changes to the filesystem 
 -y                   Assume "yes" to all questions 
 -c                   Check for bad blocks and add them to the badblock list 
 -f                   Force checking even if filesystem is marked clean 
 -v                   Be verbose 
 -b superblock        Use alternative superblock 
 -B blocksize         Force blocksize when looking for superblock 
 -j external_journal  Set location of the external journal 
 -l bad_blocks_file   Add to badblocks list 
 -L bad_blocks_file   Set badblocks list 
mount: can't find /mnt in /etc/fstab 
dropping to initramfs shell 
exiting this shell will reboot your system 
/ # [-- MARK -- Fri Apr  1 01:10:00 2011] 
[-- MARK -- Fri Apr  1 01:15:00 2011] 
[-- MARK -- Fri Apr  1 01:20:00 2011] 
[-- MARK -- Fri Apr  1 01:25:00 2011] 

Version-Release number of selected component (if applicable):
kernel-2.6.32-128
kexec-tools-2.0.0-179

How reproducible:
100%

Steps to Reproduce:
1.Install RHEL6.1-20110330.2
2.Upgrade kexec-tools to 2.0.0-179
3.Trigger crash via crasherpanic
  
Actual results:
kdump failed

Expected results:
vmcore saved

Additional info:
https://beaker.engineering.redhat.com/jobs/68688
https://beaker.engineering.redhat.com/jobs/68718

Comment 4 Cong Wang 2011-04-08 09:20:07 UTC

Fixed:

Saving to the local filesystem UUID=49db2437-0c49-4d8e-ac08-db69c0cbea8e
e2fsck 1.41.12 (17-May-2010)
/dev/mapper/vg_intels3eb101-lv_root: recovering journal
/dev/mapper/vg_intels3eb101-lv_root: clean, 92643/3276800 files, 1103176/13107200 blocks
EXT4-fs (dm-0): mounted filesystem with ordered data mode
Free memory/Total memory (free %): 183484 / 241108 ( 76.1003 )
Loading SELINUX policy
type=1404 audit(1302254349.142:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
type=1403 audit(1302254349.554:3): policy loaded auid=4294967295 ses=4294967295
Copying data                       : [100 %] 
Saving core complete

Comment 8 errata-xmlrpc 2011-05-19 14:16:36 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0736.html

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