Disk Enclosures
1748252 Members
3891 Online
108760 Solutions
New Discussion юеВ

Re: [MSA1000] I2C Write Failure Chassis NVRAM

 
ьЖбьдАьДЭ
New Member

[MSA1000] I2C Write Failure Chassis NVRAM

I Have one MSA1000.
RP4440(HP-UX 11.11) system connected to MSA1000 directly.

MSA1000 Has Two Major Problems !!!!

First!
-- 31 I2C Write failure chassis NVRAM.
During boot-up, LCD Pannel displays above messages.
What's the problem ? and How can I sovle the problem? (.... need a hardware replace?)

Second!
-- 03 Critical Lock-up Detected. Code=F112h.
After above message, HP-UX System Operation Halting and any command does not work.
What's the problem ? and How can I sovle the problem ?


MSA1000 Controller Configuration is like that!!!

CLI> show tech_support

CLI> show version
Firmware version: 4.48 build 342
Hardware Revision: 7 [AutoRev: 0x010000]
Internal EMU Rev: 1.86 (P34420BHAQW01Y)

CLI> show globals

Global Parameters:
System Name:
Rebuild Priority: medium
Expand Priority: medium

Total Cache: 256MB
50% Read Cache: 128MB
50% Write Cache: 128MB

Temperature:
EMU: 24 Celsius, 75 Fahrenheit
PS1: 32 Celsius, 89 Fahrenheit
PS2: 35 Celsius, 95 Fahrenheit

CLI> show acl

ACL is disabled. To enable ACL use 'add acl'.

CLI> show connections

Connection Name: rp4440
Host WWNN = 50060B00-0030932B
Host WWPN = 50060B00-0030932A
Profile Name = HP
Unit Offset = 0
Controller 1 Port 1 Status = Online

CLI> show disks
box,bay bus,ID Size Speed Units
Disk101 1,01 0,00 146.8 GB 160 MB/s 0, 1
Disk102 1,02 0,01 146.8 GB 160 MB/s 0, 1
Disk103 1,03 0,02 146.8 GB 160 MB/s 0, 1
Disk108 1,08 1,00 146.8 GB 160 MB/s 0, 1
Disk109 1,09 1,01 146.8 GB 160 MB/s 0, 1
Disk110 1,10 1,02 146.8 GB 160 MB/s 0, 1

Notes:
The speed is the currently negotiated speed to the disk. This may
be less than the maximum speed supported by the device due to bus
faults, loss of signal integrity, etc.

CLI> show units

Unit 0:
In PDLA mode, Unit 0 is Lun 1; In VSA mode, Unit 0 is Lun 0.
Unit Identifier : 0
Device Identifier : 600805F3-00118350-731ECDE0-47C10000
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Parity Init Status: Complete
6 Data Disk(s) used by lun 0:
Disk101: Box 1, Bay 01, (SCSI bus 0, SCSI id 0)
Disk102: Box 1, Bay 02, (SCSI bus 0, SCSI id 1)
Disk103: Box 1, Bay 03, (SCSI bus 0, SCSI id 2)
Disk108: Box 1, Bay 08, (SCSI bus 1, SCSI id 0)
Disk109: Box 1, Bay 09, (SCSI bus 1, SCSI id 1)
Disk110: Box 1, Bay 10, (SCSI bus 1, SCSI id 2)
Spare Disk(s) used by lun 0:
No spare drive is designated.
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5)
stripe_size=16kB
Logical Volume Capacity : 30,718MB

Unit 1:
In PDLA mode, Unit 1 is Lun 2; In VSA mode, Unit 1 is Lun 1.
Unit Identifier : 1
Device Identifier : 600805F3-00118350-FBADC240-488E0001
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Parity Init Status: Complete
6 Data Disk(s) used by lun 1:
Disk101: Box 1, Bay 01, (SCSI bus 0, SCSI id 0)
Disk102: Box 1, Bay 02, (SCSI bus 0, SCSI id 1)
Disk103: Box 1, Bay 03, (SCSI bus 0, SCSI id 2)
Disk108: Box 1, Bay 08, (SCSI bus 1, SCSI id 0)
Disk109: Box 1, Bay 09, (SCSI bus 1, SCSI id 1)
Disk110: Box 1, Bay 10, (SCSI bus 1, SCSI id 2)
Spare Disk(s) used by lun 1:
No spare drive is designated.
Logical Volume Raid Level: DISTRIBUTED PARITY FAULT TOLERANCE (Raid 5)
stripe_size=16kB
Logical Volume Capacity : 669,348MB

CLI> show this_controller
Controller:
MSA1000(c) Compaq P56350HX3S30SE Software 4.48 Build 342 Hardware 7
Controller Identifier:
NODE_ID = 500805F3-00118350
SCSI_VERSION = SCSI-3
Supported Redundancy Mode: Active/Standby
Current Redundancy Mode: Not Redundant (No Failure)
Device Port SCSI address 6
Terminal speed for the CLI is set to 19200.
Host Port_1:
REPORTED PORT_ID 500805F3-00118351
PORT_1_TOPOLOGY = Arbitrated Loop
Hard Addressing is enabled.
Loop ID = 1, AL-PA = 0xE8
Cache:
128 megabyte read cache 128 megabyte write cache Version 2
Cache is GOOD, and Cache is enabled.
No unflushed data in cache
Battery:
Module #1 is fully charged and turned off.
Controller Up Time:
0 Days 00 Hours 13 Minutes 51 Seconds

CLI> show other_controller
Other controller is not present or fully started.

CLI> show cacheinfo
00014307 LINES: NOT SET
00000007 LINES: LINE_LOCK
Minimum DMA CDB count since last check: 1019

CLI>
Invalid CLI command.

CLI> show eventlog
TIME CLASS SUB DETL MESSAGE
0000003F 0001 0004 0000 Controller removed: 0




3 REPLIES 3
Sameer_Nirmal
Honored Contributor

Re: [MSA1000] I2C Write Failure Chassis NVRAM

Jefferson Humber
Honored Contributor

Re: [MSA1000] I2C Write Failure Chassis NVRAM

I would say it's a duff controller and/or cache module.

The 2nd message I believe is generated to halt the controller in it's tracks before any permanent damage to the data on the disks can occur. I received the 2nd message myself once after a F/W issue was discovered.
I like a clean bowl & Never go with the zero
ьЖбьдАьДЭ
New Member

Re: [MSA1000] I2C Write Failure Chassis NVRAM

I solved this problem !!!

I set "System Name" like this.

CLI> set globals system_name="MSA1000"


And I did reboot the controller, then "31 I2C Write failure chassis NVRAM" message disappered !!!

Thank you very much all your replys !!!