- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Odd san error
Disk Enclosures
1752243
Members
6578
Online
108785
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
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
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
тАО11-24-2008 05:32 AM
тАО11-24-2008 05:32 AM
Odd san error
Everyone I am getting the below:
Nov 24 00:03:09 dallas syslog: CVSDM; MAJOR WARNING Event Code=400; Description=116: Target
Sense Key = 0xff -- Target ASC = 0xff -- Target ASCQ = 0xff -- Target Physical LBA = 0x00 --
The host Pass through request was not successfull. This could be due to a LIP or Hot Reset
of the device.loop/enclosureId/slot : 0x00/0x00/0x81; controller tick : 242100
55600310; serialNum/moduleId/processId : 00PR02C52212/0xb6/0x118; ; Hardware Address=1/0/12/
1/0.97.7.255.1.3.0; FRU Location=JA0/C2; Vendor ID=HP; Model ID=A6218A; Product S/N=00USE000
03XX; Latest information on this event at http://docs.hp.com/hpux/content/hardware/ems/Remot
eMonitor.htm#400
But everything in the armdsp -a command comes back normal. I did get a notification of:
The IBS Production SAN "Good" count should be 112 for all OK status.
The last "Good" count was 112. It is now at 110.
any idea's.
Nov 24 00:03:09 dallas syslog: CVSDM; MAJOR WARNING Event Code=400; Description=116: Target
Sense Key = 0xff -- Target ASC = 0xff -- Target ASCQ = 0xff -- Target Physical LBA = 0x00 --
The host Pass through request was not successfull. This could be due to a LIP or Hot Reset
of the device.loop/enclosureId/slot : 0x00/0x00/0x81; controller tick : 242100
55600310; serialNum/moduleId/processId : 00PR02C52212/0xb6/0x118; ; Hardware Address=1/0/12/
1/0.97.7.255.1.3.0; FRU Location=JA0/C2; Vendor ID=HP; Model ID=A6218A; Product S/N=00USE000
03XX; Latest information on this event at http://docs.hp.com/hpux/content/hardware/ems/Remot
eMonitor.htm#400
But everything in the armdsp -a
The IBS Production SAN "Good" count should be 112 for all OK status.
The last "Good" count was 112. It is now at 110.
any idea's.
There are two types of people in the world, Marines and those who wish they were.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 05:42 AM
тАО11-24-2008 05:42 AM
Re: Odd san error
Hi Adam,
For me, it looks the slot or the device on the slot at 1/0.97.7.255.1.3.0 generate this event and having some issue.
Since this is major warning, it is better to invole HP to do hardware diagnostics.
For me, it looks the slot or the device on the slot at 1/0.97.7.255.1.3.0 generate this event and having some issue.
Since this is major warning, it is better to invole HP to do hardware diagnostics.
Best wishes,
Ganesh.
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 06:15 AM
тАО11-24-2008 06:15 AM
Re: Odd san error
I agree and I am waiting for their callback. I have already opened a case, but I like to resolve issues before they can LOL!
Found this in the armdsp -a command:
Disk at M/D8:
Status:_______________________________Init Failed
Disk State:___________________________Init Failed
Vendor ID:____________________________
Product ID:___________________________
Product Revision:_____________________
Data Capacity:________________________512 bytes (1 blocks)
Block Length:_________________________0 bytes
Address:______________________________118
Node WWN:_____________________________fc
Initialize State:_____________________Failing
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________0000000010059688
Serial Number:________________________3HX0AMNV
Firmware Revision:____________________
But How do I use this information to locate the failing disk? I also see this in the armdsp command
WARNING: A hot plug event has occurred that the controller is still processing
Found this in the armdsp -a command:
Disk at M/D8:
Status:_______________________________Init Failed
Disk State:___________________________Init Failed
Vendor ID:____________________________
Product ID:___________________________
Product Revision:_____________________
Data Capacity:________________________512 bytes (1 blocks)
Block Length:_________________________0 bytes
Address:______________________________118
Node WWN:_____________________________fc
Initialize State:_____________________Failing
Redundancy Group:_____________________65536
Volume Set Serial Number:_____________0000000010059688
Serial Number:________________________3HX0AMNV
Firmware Revision:____________________
But How do I use this information to locate the failing disk? I also see this in the armdsp command
WARNING: A hot plug event has occurred that the controller is still processing
There are two types of people in the world, Marines and those who wish they were.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2008 08:49 AM
тАО11-24-2008 08:49 AM
Re: Odd san error
FINALLY found the bad drive in Launcher. It didn't show up for a while but it is there now. Thanks
There are two types of people in the world, Marines and those who wish they were.
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