- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- HPAE312A fiber insert hung the entire server
HPE EVA Storage
1753935
Members
9817
Online
108810
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2009 05:02 AM
06-13-2009 05:02 AM
HPAE312A fiber insert hung the entire server
Hi,
I am doing migration and assign Clariion LUN to the host with HBA HPAE312A. As long as I plug the fiber to port 1 the entire server will hung. Any idea what's the issue
I am doing migration and assign Clariion LUN to the host with HBA HPAE312A. As long as I plug the fiber to port 1 the entire server will hung. Any idea what's the issue
abc
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2009 05:54 AM
06-13-2009 05:54 AM
Re: HPAE312A fiber insert hung the entire server
Jun 11 03:49:03 kernel: qla2xxx 0000:13:00.1: LIP reset occured (f84f).
Jun 11 03:49:04 kernel: qla2xxx 0000:13:00.1: LIP occured (f84f).
Jun 11 03:49:04 kernel: qla2xxx 0000:13:00.1: LOOP UP detected (2 Gbps).
Jun 11 03:49:04 kernel: Vendor: DGC Model: LUNZ Rev: 0219
Jun 11 03:49:04 kernel: Type: Direct-Access ANSI SCSI revision: 04
Jun 11 03:49:04 kernel: sda : READ CAPACITY failed.
Jun 11 03:49:04 kernel: sda : status=1, message=00, host=0, driver=08
Jun 11 03:49:04 kernel: sd: Current: sense key: Illegal Request
Jun 11 03:49:04 kernel: Add. Sense: Logical unit not supported
Jun 11 03:49:04 kernel:
Jun 11 03:49:04 kernel: sda: test WP failed, assume Write Enabled
Jun 11 03:49:04 kernel: sda: asking for cache data failed
Jun 11 03:49:04 kernel: sda: assuming drive cache: write through
Jun 11 03:49:04 kernel: sda : READ CAPACITY failed.
Jun 11 03:49:04 kernel: sda : status=1, message=00, host=0, driver=08
Jun 11 03:49:04 kernel: sd: Current: sense key: Illegal Request
Jun 11 03:49:04 kernel: Add. Sense: Logical unit not supported
Jun 11 03:49:04 kernel:
Jun 11 03:49:04 kernel: sda: test WP failed, assume Write Enabled
Jun 11 03:49:04 kernel: sda: asking for cache data failed
Jun 11 03:49:04 kernel: sda: assuming drive cache: write through
Jun 11 03:49:04 kernel: sda:end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: Dev sda: unable to read RDB block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: unable to read partition table
Jun 11 03:49:04 kernel: sd 1:0:0:0: Attached scsi disk sda
I have another machine also connect to the same array without any issue. Both machine are configure in loop mode. No switch involve. Is it possible that loop id must be different in this case?
Jun 11 03:49:04 kernel: qla2xxx 0000:13:00.1: LIP occured (f84f).
Jun 11 03:49:04 kernel: qla2xxx 0000:13:00.1: LOOP UP detected (2 Gbps).
Jun 11 03:49:04 kernel: Vendor: DGC Model: LUNZ Rev: 0219
Jun 11 03:49:04 kernel: Type: Direct-Access ANSI SCSI revision: 04
Jun 11 03:49:04 kernel: sda : READ CAPACITY failed.
Jun 11 03:49:04 kernel: sda : status=1, message=00, host=0, driver=08
Jun 11 03:49:04 kernel: sd: Current: sense key: Illegal Request
Jun 11 03:49:04 kernel: Add. Sense: Logical unit not supported
Jun 11 03:49:04 kernel:
Jun 11 03:49:04 kernel: sda: test WP failed, assume Write Enabled
Jun 11 03:49:04 kernel: sda: asking for cache data failed
Jun 11 03:49:04 kernel: sda: assuming drive cache: write through
Jun 11 03:49:04 kernel: sda : READ CAPACITY failed.
Jun 11 03:49:04 kernel: sda : status=1, message=00, host=0, driver=08
Jun 11 03:49:04 kernel: sd: Current: sense key: Illegal Request
Jun 11 03:49:04 kernel: Add. Sense: Logical unit not supported
Jun 11 03:49:04 kernel:
Jun 11 03:49:04 kernel: sda: test WP failed, assume Write Enabled
Jun 11 03:49:04 kernel: sda: asking for cache data failed
Jun 11 03:49:04 kernel: sda: assuming drive cache: write through
Jun 11 03:49:04 kernel: sda:end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: Dev sda: unable to read RDB block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: end_request: I/O error, dev sda, sector 0
Jun 11 03:49:04 kernel: Buffer I/O error on device sda, logical block 0
Jun 11 03:49:04 kernel: unable to read partition table
Jun 11 03:49:04 kernel: sd 1:0:0:0: Attached scsi disk sda
I have another machine also connect to the same array without any issue. Both machine are configure in loop mode. No switch involve. Is it possible that loop id must be different in this case?
abc
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP