Bug 188520 - Can boot only on LUN 0 on our SAN, LUN 1-3 make a kernel panic.
Can boot only on LUN 0 on our SAN, LUN 1-3 make a kernel panic.
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: mkinitrd (Show other bugs)
4.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Brian Lane
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-10 16:44 EDT by Jean-Philippe Turcotte
Modified: 2011-07-27 14:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-07-27 13:58:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jean-Philippe Turcotte 2006-04-10 16:44:32 EDT
Description of problem:
 
Our setup is on an IBM e325 Dual (AMD Opetron 248) 8Gig RAM. We use Qlogic FC
card a (QLA2340) and we try to boot on a SAN Maxtronix Janus SA-6641S. We can
only boot on the LUN 0 but when we try to boot on the other LUN the RedHat make
a kernel panic. Our partitions on the SAN are all LVM. Our SAN is divide like
that 2 Array with 2 LUN on each of it. We have 4 LUN (LUN 0-3). When we made our
kickstart installation we have to put in pre% install this command to install on
other LUN then 0: echo "scsi add-single-device 0 0 0 3" > /proc/scsi/scsi (for
LUN 3). If we put nothing in this pre install section RedHat don't see any
drive! Once the kickstart install is completed on the Lun 3 on the boot we have
a kernel panic. I boot with the RedHat rescue cd when the prompt setup Network I
press Ctrl+Alt F2 to get console. From the console I made my command echo "scsi
add-single-device 0 0 0 3" > /proc/scsi/scsi (See Additional Info section) and
after that I came bake to network setup and I complete the rescue boot sequense
to get access of my Lun 3 in /mnt/. What I have to do for change the default
boot LUN?


Version-Release number of selected component (if applicable):

RedHat Entreprise AS 4 Update 3
  
Actual results:

Can only boot on the LUN 0.


Expected results:

Boot on other LUN then the 0.

Additional info:

        Partitions: LVM ext3

	Add-single-device:

		cat /proc/scsi/qla2xxx/0
		...
        	SCSI LUN Information:
         	(Id:Lun)  * - indicates lun is not registered with the OS.
         	( 0: 0): Total reqs 2, Pending reqs 0, flags 0x0*, 0:0:81 00
		( 0: 1): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81 00
		( 0: 2): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81 00
         	( 0: 3): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81 00
		
		echo "scsi add-single-device 0 0 0 3" > /proc/scsi/scsi
		
		cat /proc/scsi/qla2xxx/0
		...
        	SCSI LUN Information:
         	(Id:Lun)  * - indicates lun is not registered with the OS.
         	( 0: 0): Total reqs 2, Pending reqs 0, flags 0x0*, 0:0:81 00
		( 0: 1): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81 00
		( 0: 2): Total reqs 0, Pending reqs 0, flags 0x0*, 0:0:81 00
         	( 0: 3): Total reqs 7, Pending reqs 0, flags 0x0, 0:0:81 00


	Kernel Panic mesage:

       		Reading all physical volumes.  This may take a while...
        	Couldn't find device with uuid ....
        	Couldn't find all physical volumes vor volume group vg0
        	Volume group "vg0" not found
        	ERROR: /bin/lvm exited abnormally
        	mount: error 6 mounting ext3
        	witchroot: mount failed: 22

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