Bug 782821 - (Netapp CQ247907) QMI 8142 fails to complete initial boot with a Kernel panic when SANbooting Redhat Enterprise Linux 5.7 [NEEDINFO]
Summary: (Netapp CQ247907) QMI 8142 fails to complete initial boot with a Kernel panic...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-18 15:53 UTC by Ian Jackson
Modified: 2014-06-02 13:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:07:37 UTC
Target Upstream Version:
pm-rhel: needinfo? (jaci)


Attachments (Terms of Use)

Description Ian Jackson 2012-01-18 15:53:44 UTC
Description of problem:  After completing the initial install to a SAN LUN, the user is asked to reboot.  When the host comes back up, it begins to boot, then fails with a kernel panic apparently due to the inability to read the boot LUN.

How reproducible:
Everytime

Steps to Reproduce:
1) Map one LUN to the host and configure the Manteo BIOS to set the LUN as a boot device on one path.

2) Fail the alternate controller so that the host can only see the LUN through the primary path.

3) Install Redhat Enterprise Linux 5.7 from CD.  If configured correctly, the mapped LUN should be seen and be selectable as an installation device.

4) Complete the installation and reboot when prompted.

Expected Results:  
The host boots back up and the user is greeted with the "1st boot" screen where initial setup happens.

Actual Results:  
The host begins to boot from the LUN but encounters a kernel panic stopping the host from reaching the 1st boot screen.

Additional info:
From the console before the panic occurs, it appears that the host is unable to read from the mapped lun or see the logical volume group:

	Buffer I/O error on device sda, logical block 0
	Buffer I/O error on device sda, logical block 0
	Reading all physical volumes.  This may take a while…
	/dev/sda: read failed after 0 of 4096 at 0: Input/output error
	/dev/sda: read failed after 0 of 4096 at 80530571264: Input/output error
	/dev/sda: read failed after 0 of 4096 at 80530628608: Input/output error
	/dev/sda: read failed after 0 of 4096 at 4096: Input/output error
	No Volume groups found.
        /dev/sda: read failed after 0 of 4096 at 0: Input/output error
	/dev/sda: read failed after 0 of 4096 at 80530571264: Input/output error
	/dev/sda: read failed after 0 of 4096 at 80530628608: Input/output error
	/dev/sda: read failed after 0 of 4096 at 4096: Input/output error
		Volume group "VolGroup00" not found
	Buffer I/O error on device sda, logical block 19660784
	Buffer I/O error on device sda, logical block 19660784
	Buffer I/O error on device sda, logical block  0
	Buffer I/O error on device sda, logical block  0
	Unable to access resume device (/dev/VolGroup00/LogVol01)
	mount: could not find filesystem '/dev/root'
	setuproot: moving /dev failed: No such file or directory
	setuproot: error mounting /proc: No such file or directory
	setuproot: error mounting /sys: No such file or directory
	switchroot: mount failed: No such file or directory
	Kernel panic - not syncing:  Attempted to kill init!

HBA: Manteo (QMI8142)
	Driver Ver:        8.03.07.03.05.07-k (Inbox)
	Firmware Ver:      5.03.05 (8d4) (Latest)
	Optrom Fcode:      3.09 (Latest)
	Optrom Bios:       2.09 (Latest)
Operating system:  RHEL 5.7 x64

Comment 1 Jes Sorensen 2013-02-15 13:06:28 UTC
This has been sitting idle for a long time - has the problem been resolved in
more recent RHEL5.8+?

Thanks,
Jes

Comment 2 RHEL Program Management 2014-03-07 13:39:12 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 3 RHEL Program Management 2014-06-02 13:07:37 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).


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