- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- EVA4400 seems to hang and Levelling is taking tooo...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
10-09-2011 04:09 PM
10-09-2011 04:09 PM
EVA4400 seems to hang and Levelling is taking tooo Looong !!!?
Hi,
While working, we restarted a server and it was taking too long to mount a
file system that is on the EVA2. We check the event log on the EVA and
realized there is one particular event the read "A physical disk drive has
reported a check condition error."
The details of the error log leads to a particular disk, (dencl_num: 2,
bay: 8). However a physical check on the disk does not indicate any fault.
Meanwhile leveling was also going on, and I don't think it is advisable to
ungroup.
Please advice.
Yaboto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2011 09:34 PM
10-09-2011 09:34 PM
Re: EVA4400 seems to hang and Levelling is taking tooo Looong !!!?
Hi, was it only one check condition event? If so most likely this can be disregarded. Unless it was a predictive error, like a mechanical problem.
We would need the ASC/ASCQ to be able to tell what happened. You should be able to find these in the event details.
ASC/ASCQ details: http://t10.org/lists/asc-num.htm
Could your server mount the file system quickly after a reboot?
Leveling is a background service.
If there are no other disks with check conditions then you can ungroup it.
If on the other hand there is reconstruction going on you should be very very careful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2011 03:21 AM
10-10-2011 03:21 AM
Re: EVA4400 seems to hang and Levelling is taking tooo Looong !!!?
Please find bellow therror message:
Event header details:
Event sequence number: 26681
Flags: Time_set Time_synched Primary_Ctlr
Event rev: 3
Event size: 188
Software version: 09534000
Base level: CR18CB
Ctlr model: HSV300
Ctlr handle: 0000-7-8-500508B4-000F681A-00000000-00000000
Report time: 9 Oct, 2011 16:15:22.451680
Location: 0x20189974
Event code: Type: 09 Cac: 00 Num: 02 Scid: 06
Event description: 0x06020009 Severity: Normal -- informational in nature. A physical disk drive has reported a check condition
.
Information packet rev: 07
Information packet type: 09
Information packet size: 0078
Software component: Fibre Channel Services
Corrective action: No action necessary.
Event structure details:
Information packet descriptor:
EIP09 - Fibre Channel Services Physical Disk Drive/Mirror Port Error
An error was encountered while attempting to access a physical disk drive or the mirror port.
Structure: Event
Structure: flags
time_set: TRUE - Time has been set on this HSV300 controller
time_synched: TRUE - Time has been synchronized with all HSV300 controllers in the Storage System
seq_reset: FALSE - Event sequence number reset occurred
outofsequence: FALSE - Event reported out of sequence due to Final Event Block reconciliation or lost host event
requeued: FALSE - Event requeued following restart or resynchronization
labcode: FALSE - Event reported using LAB code
prictrlr: TRUE - Event reported by primary HSV300 controller (Note: Not valid until Storage System primary HSV300 controller is elected)
spsctrlr: FALSE - Single power supply HSV300 controller
End of structure
revision: 3 [0x03] - Structure revision number
count: 188 [0x00BC] - Event specific information size in bytes
sequence_number: 26681 [0x00006839] - Sequence number assigned to the event
sw_version: 09534000 - HSV300 controller software version number string
baselevel_id: CR18CB - HSV300 controller baselevel build string
ctrlr_model_id: HSV300 - HSV300 controller model string
reporting_ctrlr: 0000-7-8-500508B4-000F681A-00000000-00000000 - Storage System Management Interface Handle of HSV300 controller that reported the event
report_time: 9 Oct, 2011 16:15:22.451680 - Time event was reported
report_location: 538483060 [0x20189974] - Location of event report call
Structure: header
Union: u
Structure: ec
eiptype: 9 [0x09] - Event Information Packet Type Code
cac: 0 [0x00] - Corrective Action Code
evnum: 2 [0x02] - Event Number
scid: 6 [0x06] - HSV300 Controller Software Component Identification
End of structure
End of union section
value: 100794377 [0x06020009] - Event Code Value
End of union
End of union
revision: 7 [0x07] - Packet revision number
type: 9 [0x09] - Packet type
count: 120 [0x0078] - Number of bytes in packet
End of structure
device: 52-B4-00-20-01-AF-06-53-00-00-00-00-00-00-00-00 - UUID of physical disk drive associated with the event
cerp_id: DP-1B - HSV300 controller enclosure rear panel Fibre Channel port attached to the physical disk drive or mirror port
exch_type: 3 [0x0003] - Frame exchange type
port: 1 [0x0001] - HSV300 controller internal Fibre Channel port number attached to the physical disk drive or mirror port
al_pa: 218 [0x000000DA] - AL_PA of the physical disk drive or mirror port
dencl_num: 2 [0x0002] - Enclosure where the physical disk drive is located
reserved: 0 [0x0000] - Reserved
rack_num: 0 [0x0000] - Rack where physical disk drive is located
bay: 8 [0x0008] - Enclosure bay where the physical disk drive is located
fed_class: 48 [0x00000030] - Fibre Channel Exchange Descriptor class
Union: cmd
bytes: 88 [0x58]0 [0x00]0 [0x00]47 [0x2F]16 [0x10]0 [0x00]0 [0x00]80 [0x50]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00] - CDB as bytes
End of union section
lw: 788529240 [0x2F000058]1342177296 [0x50000010]0 [0x00000000]0 [0x00000000] - CDB as longwords
End of union section
Structure: cdb10
lba1: 88 [0x58] - Offset 3 -- Logical Block Address[1] byte 4
lba0: 0 [0x00] - Offset 2 -- Logical Block Address[0] byte 3
reserved: 0 [0x00] - Offset 1, Bits 0-4 -- Reserved byte 2
lun: 0 [0x00] - Offset 1, Bits 5-7 -- Logical Unit Number (obsolete method -- unused)
opcode: 47 [0x2F] - Offset 0 -- Operation Code byte 1
length0: 16 [0x10] - Offset 7 -- Length[0] byte 8
reserved6: 0 [0x00] - Offset 6 -- Reserved byte 7
lba3: 0 [0x00] - Offset 5 -- Logical Block Address[3] byte 6
lba2: 80 [0x50] - Offset 4 -- Logical Block Address[2] byte 5
padding: 0 [0x0000] - Offsets 10-11 -- Pad to longword align
control: 0 [0x00] - Offset 9 -- Control byte 10,11
length1: 0 [0x00] - Offset 8 -- Length[1] byte 9
End of structure
union_pad: - Union Element Padding (DO NOT DISPLAY!)
End of union
End of union
Union: error
bytes: 0 [0x00]1 [0x01]0 [0x00]112 [0x70]10 [0x0A]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00]0 [0x00]84 [0x54]1 [0x01]11 [0x0B]0 [0x00]0 [0x00]0 [0x00]0 [0x00] - Sense data as bytes
End of union section
lw: 1879048448 [0x70000100]10 [0x0000000A]0 [0x00000000]184636416 [0x0B015400]0 [0x00000000] - Sense data as longwords
End of union section
Structure: sense_data
info_0: 0 [0x00] - Byte 4
sense_key: 1 [0x01] - Byte 3
reserved_1: FALSE -
ili: FALSE -
eom: FALSE -
filemark: FALSE -
segment: 0 [0x00] - Byte 2
error_code: 112 [0x70] - Byte 1
valid: FALSE -
add_length: 10 [0x0A] - Byte 8-11
info_3: 0 [0x00] - Byte 7
info_2: 0 [0x00] - Byte 6
info_1: 0 [0x00] - Byte 5
cmd_specific: 0 [0x00]0 [0x00]0 [0x00]0 [0x00] - Byte 12-13
bit_ptr: 0 [0x00] - Byte 16
bpv: FALSE -
reserved: 0 [0x00] -
cd: FALSE -
sksv: FALSE -
fru_code: 84 [0x54] - Byte 15
Union: sns
Structure: bytes
asq: 1 [0x01] - Byte 13
: 11 [0x0B] - Byte 12
End of structure
End of union section
asc_asq: 2817 [0x0B01] -
End of union
End of union
big_endian_padding: 0 [0x0000] -
field_ptr: 0 [0x0000] - Byte 17
End of structure
End of union
End of union
Structure: enclosures[1]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 2 [0x02] - Enclosure number
End of structure
Structure: enclosures[0]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 3 [0x03] - Enclosure number
End of structure
Structure: enclosures[3]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 99 [0x63] - Enclosure number
End of structure
Structure: enclosures[2]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 1 [0x01] - Enclosure number
End of structure
Structure: enclosures[5]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 99 [0x63] - Enclosure number
End of structure
Structure: enclosures[4]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 99 [0x63] - Enclosure number
End of structure
Structure: enclosures[7]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 99 [0x63] - Enclosure number
End of structure
Structure: enclosures[6]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 99 [0x63] - Enclosure number
End of structure
unused: 0 [0x0000] -
Structure: enclosures[8]
rack_num: 0 [0x00] - Rack were enclosure is located
dencl_num: 0 [0x00] - Enclosure number
End of structure
bypassb: 0 [0x0000] - Mask showing bypass state for each slot in a shelf
bypassa: 0 [0x0000] - Mask showing bypass state for each slot in a shelf
drv_fw_rev: HP03 - The FW revision on the drive
End of structure
Salient data:
Event: Severity: Normal -- informational in nature. A physical disk drive has reported a check condition error.
Action: No action necessary.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2011 03:35 AM
10-10-2011 03:35 AM
Re: EVA4400 seems to hang and Levelling is taking tooo Looong !!!?
But I presume it's these entries that could help us:
sense_key: 1 [0x01] - Byte 3
asq: 1 [0x01] - Byte 13
: 11 [0x0B] - Byte 12
asc_asq: 2817 [0x0B01] -
But how to make this into understandable form such as: ASC/ASCQ? For example 11/00 for 'unrecovered read error' ? Is that what the 11 there means? I do not know..
If it's an 11/00 and you've only seen it once, then that's not enough to cause concern. It could be that you see this read error once and not again for a long time.