- Community Home
- >
- Operating Systems
- >
- Linux
- >
- System Administration
- >
- qla2xxx Errors
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
qla2xxx Errors
(2048 Views)
Reply
Topic Options
- Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
qla2xxx Errors
Post options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
03-10-2011 11:39 AM
hi guys
I got a lot of these errors
Mar 10 06:58:43 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 224fab2 2002.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:08:56 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:12:16 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503b5 2002.
Mar 10 07:12:17 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503cf 2002.
Mar 10 07:12:17 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503d5 2002.
Mar 10 07:12:17 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503d6 2002.
as you see they say scsi(2:0:0) (hundreds a day) but I got few of them but very few for scsi(1:0:1) and scsi(2:0:2)
I really don't know if the they mean the LUN number...
I see these devices(below)
so my questions
1. Can I relate the devices above and the errors?
and also you have any idea what these errors mean?
cat /proc/scsi/scsi
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 31
Vendor: IBM Model: Universal Xport Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 31
Vendor: IBM Model: Universal Xport Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: VirtualDisk Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: VirtualDisk Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: VirtualDisk Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
thanks a lot
I got a lot of these errors
Mar 10 06:58:43 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 224fab2 2002.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:07:20 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:08:56 Warehouse kernel: qla2xxx 0000:24:00.1: Unknown status detected 0x13-0x0.
Mar 10 07:12:16 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503b5 2002.
Mar 10 07:12:17 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503cf 2002.
Mar 10 07:12:17 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503d5 2002.
Mar 10 07:12:17 Warehouse kernel: qla2xxx 0000:24:00.1: scsi(2:0:0): Abort command issued -- 1 22503d6 2002.
as you see they say scsi(2:0:0) (hundreds a day) but I got few of them but very few for scsi(1:0:1) and scsi(2:0:2)
I really don't know if the they mean the LUN number...
I see these devices(below)
so my questions
1. Can I relate the devices above and the errors?
and also you have any idea what these errors mean?
cat /proc/scsi/scsi
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 31
Vendor: IBM Model: Universal Xport Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: 1814 FAStT Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi1 Channel: 00 Id: 00 Lun: 31
Vendor: IBM Model: Universal Xport Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: IBM Model: VirtualDisk Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 01
Vendor: IBM Model: VirtualDisk Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 02
Vendor: IBM Model: VirtualDisk Rev: 0916
Type: Direct-Access ANSI SCSI revision: 05
thanks a lot
Didn't your momma teach you to say thanks!
Re: qla2xxx Errors
Post options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
03-11-2011 06:07 AM
anyone guys?
might a qlogic driver or firmware update?
or Storage issue (path, corrupted luns,...)
might a qlogic driver or firmware update?
or Storage issue (path, corrupted luns,...)
Didn't your momma teach you to say thanks!
Re: qla2xxx Errors
Post options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
03-12-2011 07:29 AM
Messages like "Unknown status detected 0x13-0x0." indicate the driver does not understand what the hardware is trying to tell, so I would first try to update the driver (or the Linux kernel package that contains the qla2xxx driver module) to the latest version available for the distribution.
It's also possible the "unknown status" happems because the firmware is generating wrong status information: the second step would be checking the HBA firmware versions. If updated versions exist, it might be useful to read their Release Notes.
Most major SAN storage manufacturers have very detailed compatibility lists or compatibility information databases. You should check what IBM has to say about your combination of storage system + HBA + OS. The compatibility information might include version recommendations (or even requirements) for driver, kernel, HBA firmware and/or SAN firmware. There might also be configuration requirements: make sure all of these are met.
And yes, the numbers in "scsi(2:0:0)" are indeed the triplet of host:target_id:LUN.
MK
It's also possible the "unknown status" happems because the firmware is generating wrong status information: the second step would be checking the HBA firmware versions. If updated versions exist, it might be useful to read their Release Notes.
Most major SAN storage manufacturers have very detailed compatibility lists or compatibility information databases. You should check what IBM has to say about your combination of storage system + HBA + OS. The compatibility information might include version recommendations (or even requirements) for driver, kernel, HBA firmware and/or SAN firmware. There might also be configuration requirements: make sure all of these are met.
And yes, the numbers in "scsi(2:0:0)" are indeed the triplet of host:target_id:LUN.
MK
MK
Re: qla2xxx Errors
Post options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
03-14-2011 07:06 AM
the thing is
according to this website
http://driverdownloads.qlogic.com/QLogicDriverDown loads_UI/Product_detail.aspx?oemid=224
I have the latest Driver - Firmware for Suse 10 SP2
cat fw_version
4.04.09 [Class 2] [Multi-ID]
cat driver_version
8.02.00.50.10.2-k6
according to this website
http://driverdownloads.qlogic.com/QLogicDriverDown
I have the latest Driver - Firmware for Suse 10 SP2
cat fw_version
4.04.09 [Class 2] [Multi-ID]
cat driver_version
8.02.00.50.10.2-k6
Didn't your momma teach you to say thanks!
Re: qla2xxx Errors
Post options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
03-14-2011 12:28 PM
I'm not very familiar with IBM's storage systems, but apparently IBM's storage compatibility database is called "System Storage Interoperation Centre" (SSIC):
http://www-03.ibm.com/systems/support/storage/ssic /interoperability.wss
The information in your /proc/scsi/scsi listing indicates your storage system identifies itself as "1814 FAStT". With a bit of googling, I see this is apparently one of the IBM DS4xxx series storage systems, perhaps a DS4700?
The SSIC seems to want to know the firmware level of the storage system, so that may be an important factor. Please ask your storage system administrator.
You should get the exact QLogic model number for your HBA cards:
cat /sys/class/fc_host/host*/symbolic_name
MK
http://www-03.ibm.com/systems/support/storage/ssic
The information in your /proc/scsi/scsi listing indicates your storage system identifies itself as "1814 FAStT". With a bit of googling, I see this is apparently one of the IBM DS4xxx series storage systems, perhaps a DS4700?
The SSIC seems to want to know the firmware level of the storage system, so that may be an important factor. Please ask your storage system administrator.
You should get the exact QLogic model number for your HBA cards:
cat /sys/class/fc_host/host*/symbolic_name
MK
MK
