Hi all,

Inherited a server running VMWare (standard build not HP) and I've got a drive with a amber failure light in the Storageworks array.

Given it's running VMWare O/S there is no ACU and iLo 3 doesn't give me anything to work with so..

My questions are;

1. Does the above support hot-swop capability? I don't have information about the SAS RAID card installed unfortunately..

2. Is there any way of booting into media that will give me the ACU? Ideally I want to take a look at the RAID status before pulling a drive - all of the lights on other drives are flashing blue (although they are so dim it's a little hard to tell) but I'd hate to pop a drive and kill the array (it's RAID 10 apparently..)

No error lights on the Storageworks unit at all, just one of the drives

Any advice would really be appreciated as killing this array would cause massive pain..

Regards,

Simon

Here's my situation.  I have a Windows 2003 Server that's currently connected to an EVA array and is using the "HP MPIO DSM Manager."  I've presented a new 3Par disk to the server but it appears as eight separate devices (one/path) rather than one.  I attempted to install the 3Par MPIO driver (1.0.23_780-200072) driver but it fails pretty quickly.  I'm hestitant to uinstall remove the existing DSM manager, fearing what will happen to the EVA disk.  I've restarted and reviewed the pre-reqs but don't see anything obvious.  I've attached a screenshot of the error.



Hi all,

Inherited a server running VMWare (standard build not HP) and I've got a drive with a amber failure light in the Storageworks array.

Given it's running VMWare O/S there is no ACU and iLo 3 doesn't give me anything to work with so..

My questions are;

1. Does the above support hot-swop capability? I don't have information about the SAS RAID card installed unfortunately..

2. Is there any way of booting into media that will give me the ACU? Ideally I want to take a look at the RAID status before pulling a drive - all of the lights on other drives are flashing blue (although they are so dim it's a little hard to tell) but I'd hate to pop a drive and kill the array (it's RAID 10 apparently..)

No error lights on the Storageworks unit at all, just one of the drives

Any advice would really be appreciated as killing this array would cause massive pain..

Regards,

Simon

We had an issue with an aging P2000 MSA G3 with dual combo ICSCI/FC controllers in it. One of the controllers failed. The array has continued to operate normally on one controller (this controller b was running old firmware T201P02 from 2011). A replacement controller was sent. We were told it was downgraded to be close to the existing controller. Partner firmware update was disabled. The replacement controller was placed into slot A. It turns out its running T251R04-01 which is from 2014.

My understanding is that is could be a problem and that no controller with a f/w newer than TS250 should not be placed into the chassis. Currently since the controller running T251R04-01 was inserted it is flagging all the SFF drives in its associated chassis as having an unknown state. It also appears to be constantly rebooting the management controller in b (running T201P02).  Its showing controller B (old firmware) as unavailble on the network. However i was able to ssh into it. It appears that it cannot see anything other then itself. SHOW FRUS just returns nothing and SHOW SYSTEM only returns basic chassis information, most of which is not populated. However the ISCSI ports appear to be online and working so it is operating, just not communucating with anything else.

Can anyone tell me if its safe to enable partner firmware update and allow the new controller running T251R04-01  and allow it to update controller B running T201P02?

The alternative it to take everything down (All the connected hosts) and then power down the storage and remove the controller running T251R04-1 and get it downgraded to a closer firmware before re-inserting.

The main shelf also has 5 x D2700 SAS AJ941A enclosures on it,

I am seeing the following messages....

Error logs…(repeatedly)

 Enclosure event: fault. (enclosure: 1, WWN: 500c0ff0125XXXXX) I/O module A, I/O module status: The firmware version is not compatible, HP SPS-CHASSIS 2028

Warning logs… (repeatedly)

 2016-05-18 06:35:30 B6585 156

The Management Controller was restarted automatically by the Storage Controller for the purpose of error recovery.

2016-05-18 06:35:30 B6584 152

The Storage Controller is not receiving data from the Management Controller. (This is normal during firmware update.)

  Is this what you would expect to see if partner firmware update is off?

#
#
# show system (run from CONTROLLER-A - new firmware)
System Information
------------------
System Name: SXXXXX
System Contact: XX
System Location: XXXXX
System Information: HP P2000 G3 FC iSCSI Combo
Midplane Serial Number: 00XXXXXX
Vendor Name: HP
Product ID: P2000G3 FC/iSCSI
Product Brand: MSA Storage
SCSI Vendor ID: HP
SCSI Product ID: P2000G3 FC/iSCSI
Enclosure Count: 6
Health: Degraded
Health Reason: A subcomponent of this component is unhealthy.
Supported Locales: English (English), Spanish (español), French (français), German (Deutsch), Italian (italiano), Japanese (æ¥æ¬èª), Dutch (Nederlands), Chinese-Simplified (ç®ä½ä¸­æ), Chinese-Traditional (ç¹é«ä¸­æ), Korean (íêµ­ì´)

Unhealthy Component
-------------------
Component ID: Enclosure 1, Current Health: Degraded
Health Reason: The current sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.16
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.6
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended act
Unhealthy Component
-------------------
Component ID: Disk 1.4
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.19
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.24
Health: Degraded Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.11
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.13
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.
Unhealthy Component
-------------------
Component ID: Disk 1.20
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.8
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.3
Health: Degraded
Health Reason: The disk in this sloane may be unhealthy. Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.18
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.12
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component -------------------
Component ID: Disk 1.1
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.7
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.21
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy. Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.9
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.17
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
------------------- Component ID: Disk 1.15
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.2
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.5
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in tponent and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.23
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.22
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.10 Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Disk 1.14
Health: Degraded
Health Reason: The disk in this slot has unknown health. The disk or the midplane may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Controller B, Management Port
Health: Degraded
Health Reason: The network port Ethernet cable is unplugged, or the network is inoperable.
Health Recommendation: - Check that the controller network port is properly connected to the network. - If it is, then check for network problems.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Temperature Loc: lower-IOM B
Health: Degraded
Health Reason: The temperature sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Voltage 5V Loc: lower-IOM B
Health: Degraded
Health Reason: The voltage sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Unhealthy Component
-------------------
Component ID: Enclosure 1, Voltage Health: Degraded
Health Reason: The voltage sensor's status is unknown or its value is unexpected. It may be unhealthy.
Health Recommendation: - Check in the event log for events related to this component and follow the recommended actions for those events.

Success: Command completed successfully. (2016-05-18 07:53:08)

Any advice appreciated. thanks

Adam.

Does anyone have a backup config for an HSV300-S?  We have accidentally completely wiped ours out, we don't need to recover data or anything but we do want this EVA to work again (it's in a test environment).  The management module can't communicate with the controller/switch combination anymore since we cleared it.  A default/factory configuration would be great, but really anything would help us.  Thanks!

Hi All,

Today I have face HP VLS9000 link down issue with both eth0 and eth1 and get message "Can not communicate with DiskArray", late I have restarted the Node with disk Array controller.

link down issue has resolved now but I am getting this message "Reestablishing bonded ethernet interface for eth1" contisuly with below information:

Event Id          : fafed7db-319e-45ca-8751-fb4508efd022

Event Severity    : INFO

Status            : OK

Software Version  : 2.3.1

Affected Component: vls9000-witbe.net->node0->NetworkConfig->eth1

Message           : Reestablishing bonded ethernet interface for eth1

please anyone help me to resolve this issue.

Hi All,

I've just installed  HP Storage D2600 Disk Enclosure that is filled with 12x 3 TB disks, to be used as backup server.

Mostly the file size will be very large greater than 1 GB up to 4-6 TB.

The File system will be NTFS, so I wonder here if anyone can assist me with the best practice for configuring the LUN for the RAID stripe size as per below:



Thanks in advance.

Hi All,

I'm confused with configuring the new LUNs for my backup server purpose, so can anyone here pelase share some explanation as to when to use RAID 6 (ADG) vs. RAID 60 or RAID50 ?

Smart Array P411 In Slot 2

What about sector / track information ?
Does 63 is better / faster than 32 ?

Thanks in advance.

Hi,

Today I have a technician who add a new disk on a raid 5 and he migrate the RAID 5 to RAID 6 ADG.

He made a mistake because we need to ADD a disk to the existing RAID 5 to have more space available.

At this time the server is in production and I want to know if it is possible to migrate to RAID 5 wihout data lost.

The option is selectable in Smart Storage Administrator

Thank you for your ASAP response.

Kind regards

Vincent.

Hi!

HP P2000G3 FC/iSCSI DualController SFF

After firmware upgrade from old TS201P007 to merged version TS230P008 (and new TS250P003, TS251R004 and current TS252P001) i can't define the Explicit Mappings. Only Default Mappings.

I select volume, choose Provisioning -> Explicit Mappings... and see only Default Mappings.

In old TS201P007 version i used Explicit Mappings successfully.

I tried to downgrade firmware, but i can't downgrade to merged-befor version: only to TS230P008.

Whats wrong? How define Explicit Mappings now? Maybe it become the lisensed feature now?

Thanks

When I run Command cmrunnode I found this error in red please help

scodrrb#[/]cmrunnode scodrcc

: Validating network configuration... cmrunnode:

Network validation complete

alidating cluster lock disk ...Unable to convert device to I/O tree node: I/O tree node does not exist. Failed to check cluster lock disks . Done

codrrb#[/]vgdisplay
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4328
VGDA 4
PE Size (Mbytes) 16
Total PE 8636
Alloc PE 8012
Free PE 624
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Cannot display volume group "/dev/ccvg1".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/medvg1".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/ccevavg".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/billvg1".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/billvg2".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/rbevavg".
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg_lock".

Hello and thanks for this excellent forum!

I am helping in the management of an HP MSA P2000 SAN and have an issue with one of the vDisks.

This vDisk is configured in a RAID 6 and recently lost one of its disks.  We contactly a widely known hardware reseller and obtained a replacement disk for it that was deemed compatible by the reseller.

When I removed the bad disk and inserted the new disk, I logged into the SMU and saw that the RAID was rebuilding.  Knowing that this usually takes some time, I logged off and made a note to check on it the next day.

Well, my counterpart notified me that the drive had not turned green the next day and when I logged into the SMU, the vDisk is still showing as a "Degraded" state.  Also, now the drive which is inserted into Controller 1, Slot 10 is now missing and not showing up as an available drive any longer.

I have attached a screenshot of the error log from the rebuild process.  You can see clearly on there that the rebuild did encounter an error, but I don't know what to do next and certainly don't want to continue running in a degraded state.

Thanks in advance for any support that you can provide.  See attached JPG for the error/warning log.

Iused to use the knowledge base here at HP to troubleshoot and research issues; I wonder if it is still somewhere but I will try here

we have power outage

we are good until power outage

no I have a PSU bad

and I have ctrllr unable to read configuration error

I cannot start serviceset set1

segments are unavailable

I cannot find out what segments are

or why they are unavailalbe or what to do about it

I am hoping that if i find a backup config file then I will get back my configuration because I do not see any vtl

at all

how up a creek am I ?

Is it possible to move D2600 (single or cascaded) disk array from one server to another, each containing a SmartArray P812 controller?  Or better yet, connect the D2600 to both servers simultaneously. ie- the P812s are set up the same on each server, and the volume information is on the disk array, it seems like the D2600 could be moved from one server to a backup server without damage to the volume(s).

Hi, I have a 4 disk RAID1/0 array on my internal P410i controller, and have recently attached a StorageWorks via a P420.  The StorageWorks has 8 disks in it which I would like to extend the existing RAID1/0 on the P410i.

Is this possible and how because I cannot for the life of me see how to do it!!

Salutations,

This is my first post on this forum so if this thread is in the wrong section please inform me. Here is the scenario currently I am attempting to set up the A3312A enclosure. I need a little help troubleshooting though, so I begain by setting the bus's for each drive bay i numbered them 0-8 (skipped 7) then I put 4 A3714AM 18.2 gb se hard drives in the unit. I also put a scsi cord from bay a to bay b to bridge the bus's and installed a terminator on the last open slot. I am using a scsi vhdci to lvd cord to connect the array to a proliant dl380 g4. I cannot get the drives to show up. I have tried using multiple cards including a HVD card but cannot get the drives to show up in the bios. Any help would be greatly apprecated. I have a full warehouse of parts at my disposal so if it is beyond configuration and hardware related suggested replacement part numbers would be a great help. 

Thank you, 

B

Hi,

Many error messages in my server running hp-ux 11.11 related to writing to disk.

Sep 29 08:50:00 prod4 vmunix: Synchronous Page I/O error occurred while paging to/from disk

Sep 29 08:50:00 prod4 vmunix: device 0x4000000a, 1K block #38120, 4096 bytes of 4096 bytes not paged, page addr =7f10c00.6e1df000,  bflag =1f, bp = 8adebcc0

Sep 29 08:50:00 prod4 vmunix: Page I/O error(1) while swapping from disk for device 0xffffffff,

Sep 29 08:50:00 prod4 vmunix:   block #33849658, page addr = 7f10c00.6e1df000

Sep 29 08:50:00 prod4 vmunix: Making a range of swap blocks unavailable for future use. Please check

Sep 29 08:50:00 prod4 vmunix: for any possible hardware/firmware errors on the swap

Sep 29 08:50:00 prod4 vmunix: device IMMEDIATELY

thanks for your help.

People,

I'm trying to reconfigure the Strip Size / Full Stripe Size of an existing LUNs, but somehow I've found something that is confusing.

In some of the Logical Drive I mark with the red, when you click on those two logical drives in the screenshot below, the Delete Logical Drive is missing ?



But when you click on the Logical Drive 3 as shown above, the delete button is there.

Does this also means when I need to change the Strip Size / Full Stripe Size of Logical Drive 1,2 and 3 I will need to delete all of them destroying all of the data ?

Any help would be greatly appreciated.

Thanks,

Hi People,

I have attached few D2600 and D2700 DAS to my HP DL 385 G7 using P411, but somehow all of the File System Info shows:

command: fsutil fsinfo ntfsinfo D:

Bytes Per Physical Sector <Not supported>

So I wonder what is the type of the disks in those DAE ?

Thanks in advance.

People,

Can anyone here please assist me with the guide to add additional enclosure to the existing HP Storage D2700 Disk Enclosure AJ941A stack in my HP DL 385 G7 server on P411 Storage Controller ?

Thank you in advance.