- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Odd san error
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-24-2008 05:32 AM
11-24-2008 05:32 AM
Odd san error
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.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-24-2008 05:42 AM
11-24-2008 05:42 AM
Re: Odd san error
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.
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-24-2008 06:15 AM
11-24-2008 06:15 AM
Re: Odd san error
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
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-24-2008 08:49 AM
11-24-2008 08:49 AM
Re: Odd san error
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP