From: "Richard F. Rebel" <rrebel@whenu.com>
To: linux-scsi@vger.kernel.org
Subject: Boot order of LSI MPT Fusion devices controllable?
Date: Tue, 30 Nov 2004 12:20:24 -0500 [thread overview]
Message-ID: <1101835224.1779.1040.camel@rebel.corp.whenu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3110 bytes --]
Hello,
I am running mdk 10.0 with kernel 2.6.3-16 out of box on a dual opteron
250 system. The system has a LSI logic U320 controller with 7 internal
disks on two channels.
We are upgrading our system by adding an identical server and a small
SAN so we can have an active passive failover cluster for MySQL.
I purchased quad port 2gbps fc cards from LSI as I have been very happy
with the performance of the SCSI cards we already own. Upon install,
dmesg shows:
Fusion MPT base driver 3.00.03
Copyright (c) 1999-2003 LSI Logic Corporation
mptbase: Initiating ioc0 bringup
ioc0: FC929X: Capabilities={Initiator,Target,LAN}
mptbase: Initiating ioc1 bringup
ioc1: FC929X: Capabilities={Initiator,Target,LAN}
mptbase: Initiating ioc2 bringup
ioc2: FC929X: Capabilities={Initiator,Target,LAN}
mptbase: Initiating ioc3 bringup
ioc3: FC929X: Capabilities={Initiator,Target,LAN}
mptbase: Initiating ioc4 bringup
ioc4: 53C1030: Capabilities={Initiator}
mptbase: Initiating ioc5 bringup
ioc5: 53C1030: Capabilities={Initiator}
SCSI subsystem initialized
Fusion MPT SCSI Host driver 3.00.03
scsi0 : ioc0: LSIFC929X, FwRev=01010b00h, Ports=1, MaxQ=1023, IRQ=25
scsi1 : ioc1: LSIFC929X, FwRev=01010b00h, Ports=1, MaxQ=1023, IRQ=26
scsi2 : ioc2: LSIFC929X, FwRev=01010b00h, Ports=1, MaxQ=1023, IRQ=27
scsi3 : ioc3: LSIFC929X, FwRev=01010b00h, Ports=1, MaxQ=1023, IRQ=24
scsi4 : ioc4: LSI53C1030, FwRev=01013d00h, Ports=1, MaxQ=255, IRQ=29
Vendor: SEAGATE Model: ST336753LC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 03
Vendor: SEAGATE Model: ST336753LC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 03
Vendor: SEAGATE Model: ST336753LC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 03
Vendor: SEAGATE Model: ST336753LC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 03
scsi5 : ioc5: LSI53C1030, FwRev=01013d00h, Ports=1, MaxQ=255, IRQ=30
Vendor: SEAGATE Model: ST336753LC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 03
Vendor: SEAGATE Model: ST336753LC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 03
Vendor: SEAGATE Model: ST336753LC Rev: 0006
Type: Direct-Access ANSI SCSI revision: 03
Well, the difference is that the fiber channel card seems to boot first,
and thus reorders the scsi bus. If I attach the fiber channel cables to
the switch (making all of our storage visible) and re-probe the scsi bus
by hand using the /dev interface, access to the SAN is fine etc. Upon
reboot with the fc connected, my system panics because now the root
drive is no longer where it thinks it should be (sda is now a device on
the fiber channel switch fabric).
Is there a way to control this process or to mitigate the problem? I
really need the system to boot properly off of local disk whether or not
the fc is connected or the devices available.
Thanks,
Richard F. Rebel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-11-30 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 17:20 Richard F. Rebel [this message]
2004-11-30 17:54 ` Boot order of LSI MPT Fusion devices controllable? Matthew Wilcox
2004-12-01 3:31 ` kwhite
2004-11-30 19:40 ` Christoph Hellwig
2004-11-30 19:43 ` Richard F. Rebel
2004-11-30 19:59 ` Matthew Wilcox
2004-11-30 20:48 ` Mike Anderson
2004-11-30 21:55 ` Richard F. Rebel
-- strict thread matches above, loose matches on Subject: below --
2004-11-30 22:15 todd.reichert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1101835224.1779.1040.camel@rebel.corp.whenu.com \
--to=rrebel@whenu.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox