topic Re: HP P2000 G3 iSCSI strange events in log in Disk Enclosures

HP P2000 G3 iSCSI strange events in log

kdmal — Thu, 26 Dec 2013 10:56:59 GMT

Hello,

We have HP P2000 G3 iSCSI, firmware: TS250P003

2-3 times per day in log:

2013-12-25 21:28:06 [019] #B163: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 18, number of enclosures that were found: 2) (rescan reason: initiated by internal logic, rescan reason code: 27)

2013-12-25 21:28:04 [019] #A191: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 18, number of enclosures that were found: 2) (rescan reason: initiated by internal logic, rescan reason code: 27)
2013-12-25 21:28:04 [275] #A190: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL A PHY was enabled. (enclosure: 1, module (enabled path to this disk): B, disk slot: 5)
2013-12-25 21:28:04 [310] #A189: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan.
2013-12-25 21:28:01 [275] #B162: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL A PHY was enabled. (enclosure: 1, module (enabled path to this disk): B, disk slot: 5)
2013-12-25 21:28:01 [310] #B161: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan.
2013-12-25 21:27:57 [211] #B160: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 1, number of elements: 124, expanders: 2, native levels: 0, partner levels: 2, device PHYs: 20)
2013-12-25 21:27:57 [211] #B159: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 0, number of elements: 124, expanders: 2, native levels: 2, partner levels: 0, device PHYs: 20)
2013-12-25 21:27:56 [211] #A188: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 1, number of elements: 124, expanders: 2, native levels: 0, partner levels: 2, device PHYs: 20)
2013-12-25 21:27:56 [211] #A187: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 0, number of elements: 124, expanders: 2, native levels: 2, partner levels: 0, device PHYs: 20)
2013-12-25 20:53:49 [274] #B158: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B WARNING A PHY was disabled. (enclosure: 1, module (disabled path to this disk): B, disk slot: 5, reason: Disabled because of empty disk slot)
2013-12-25 20:53:49 [310] #B157: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan.
2013-12-25 20:53:48 [274] #A184: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A WARNING A PHY was disabled. (enclosure: 1, module (disabled path to this disk): B, disk slot: 5, reason: Disabled because of empty disk slot)
2013-12-25 20:53:48 [310] #A183: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan.
2013-12-25 20:53:35 [211] #B156: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 0, number of elements: 122, expanders: 2, native levels: 2, partner levels: 0, device PHYs: 19)
2013-12-25 20:53:34 [211] #A182: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 1, number of elements: 122, expanders: 2, native levels: 0, partner levels: 2, device PHYs: 19)
2013-12-25 19:21:25 [019] #B155: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 18, number of enclosures that were found: 2) (rescan reason: initiated by internal logic, rescan reason code: 27)
2013-12-25 19:21:24 [019] #A181: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 18, number of enclosures that were found: 2) (rescan reason: initiated by internal logic, rescan reason code: 27)
2013-12-25 19:21:24 [275] #A180: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL A PHY was enabled. (enclosure: 1, module (enabled path to this disk): B, disk slot: 5)
2013-12-25 19:21:24 [310] #A179: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan.
2013-12-25 19:21:20 [275] #B154: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL A PHY was enabled. (enclosure: 1, module (enabled path to this disk): B, disk slot: 5)
2013-12-25 19:21:20 [310] #B153: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed
2013-12-25 19:21:16 [211] #B152: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 1, number of elements: 124, expanders: 2, native levels: 0, partner levels: 2, device PHYs: 20)
2013-12-25 19:21:16 [211] #B151: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 0, number of elements: 124, expanders: 2, native levels: 2, partner levels: 0, device PHYs: 20)
2013-12-25 19:21:15 [211] #A178: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 1, number of elements: 124, expanders: 2, native levels: 0, partner levels: 2, device PHYs: 20)
2013-12-25 19:21:15 [211] #A177: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 0, number of elements: 124, expanders: 2, native levels: 2, partner levels: 0, device PHYs: 20)
2013-12-25 19:16:02 [274] #B150: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B WARNING A PHY was disabled. (enclosure: 1, module (disabled path to this disk): B, disk slot: 5, reason: Disabled because of empty disk slot)
2013-12-25 19:16:02 [310] #B149: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan.
2013-12-25 19:16:01 [274] #A176: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A WARNING A PHY was disabled. (enclosure: 1, module (disabled path to this disk): B, disk slot: 5, reason: Disabled because of empty disk slot)
2013-12-25 19:16:01 [310] #A175: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan.
2013-12-25 19:15:48 [211] #A174: P2000 G3 iSCSI Array SN#00C0FF19766C Controller A INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 1, number of elements: 122, expanders: 2, native levels: 0, partner levels: 2, device PHYs: 19)
2013-12-25 19:15:48 [211] #B148: P2000 G3 iSCSI Array SN#00C0FF19766C Controller B INFORMATIONAL The SAS topology changed (components were added or removed). (Channel: 0, number of elements: 122, expanders: 2, native levels: 2, partner levels: 0, device PHYs: 19)

vDisk contains hdd in slot 5 and work correct at this time (LED blinking, raid not degraded)

P.S. This thread has been moved from Disk-Based Systems > Disk to Disk Array. - HP Forum Moderator

Re: HP P2000 G3 iSCSI странные записи в журнале работы

Maiko-I — Thu, 26 Dec 2013 09:35:11 GMT

Hello kdmal,

We would like to encourage that this discussion should be continued in English language as this forums is a English construct-based communities as per the rules of participation (Rules(9) *see below for the url). Your post in English format will definitely help your other fellow participants to well-understand the issues and help you out regarding this.
* http://h30499.www3.hp.com/t5/custom/page/page-id/hp.rulespage
HP Forums also supports few other languages for the same where you can select the language option located at the top right side of the EBC main page.

Re: HP P2000 G3 iSCSI strange events in log

Johan Guldmyr — Thu, 26 Dec 2013 14:39:27 GMT

Hi,

thanks for translating :)

See

http://h20566.www2.hp.com/portal/site/hpsc/template.BINARYPORTLET/public/kb/docDisplay/resource.process/?spf_p.tpst=kbDocDisplay_ws_BI&spf_p.rid_kbDocDisplay=docDisplayResURL&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.rst_kbDocDisplay=wsrp-resourceState%3DdocId%253Demr_na-c02520788-7%257CdocLocale%253D&javax.portlet.endCacheTok=com.vignette.cachetoken

the "HP P2000 G3 MSA System Event Descriptions Reference Guide" and event 274.

See the part of proposed actions to take after a rescan (#A175).

Re: HP P2000 G3 iSCSI strange events in log

kdmal — Thu, 26 Dec 2013 15:11:52 GMT

Thanks for link to "Event Descriptions Reference Guide"

At this moment (19:00), last event:

2013-12-26 14:32:22 A PHY was disabled. (enclosure: 1, module (disabled path to this disk): B, disk slot: 5, reason: Disabled because of empty disk slot)

Slot empty > 4 hours (its last event)

Enclosure view, for this disk (see attachment):

Health: OK

Status: Not present

Current owner: A

Physically disk present in slot

Well, can its mean - when disk change owner controller (from B to A, or A to B) - this event logged?

Re: HP P2000 G3 iSCSI strange events in log

Johan Guldmyr — Thu, 26 Dec 2013 17:18:07 GMT

It seems to follow that pattern, with the events being reported by controller A -> B -> B -> A -> A -> B etc.

I see that the disk is a global spare, do you have more than one vdisk? Perhaps the spare is being swapped between vdisks that are owned by two different controllers? Generally vdisks are owned by a controller, not individual disks. But I guess it boils down to the disk but then all disks in that vdisk ought to move between controllers.

Re: HP P2000 G3 iSCSI strange events in log

kdmal — Thu, 26 Dec 2013 19:10:10 GMT

array have 2 vDisks (vd-raid5, vd-raid10), disk in slot 1.5 was originally in vd-raid5, global spare in 2.6

after this events we replace 1.5 from vd-raid5 to 2.6

array was purchased in dec.2013, and started in pre-prod instance 21.dec.2013. this events showing on the first day of use

Re: HP P2000 G3 iSCSI strange events in log

kdmal — Thu, 26 Dec 2013 19:34:06 GMT

Im reboot ctrl B, and 1.5 change status from Not present to Up

Seems as ctrl A not notify ctrl B about transfered disk between controllers. After reboot ctrl B reread configuration from A and change status to A

Re: HP P2000 G3 iSCSI strange events in log

Johan Guldmyr — Thu, 26 Dec 2013 20:16:06 GMT

With such a new array you might want to contact HP support as well, especially if you suspect a problem in the firmware.