I had to delete the oldest snapshot on a 14 TB volume because the unit stopped iSCSI volumes IO when it ran out of space. I left the most recent snapshot but now I receive this cryptic error; what appropriate steps do I need to take?
ID: A68143
Code: 362
Scheduler: When renaming a snapshot, failed to locate the oldest snapshot,
Additional Information: The scheduler experienced a problem with the indicated task.
Recommeneded Action:
Take Appropriate action based on the indicated problem.
Hi guys
We are using a HPE MSA 2040 in our 2 node failover cluster. Against advice I chose to populate the enclosure with 12 x 1.2TB 10K SAS drives and opted for RAID5. We have 16 virtual machines in use. None of the VMs are particularely stressed. Day to day running is fine, however when I log in to remote desktop on 1 or more VMs it is painfully slow.
For reference, here's the spec of the hosts:
HPE DL380 Gen9, Xeon E5-2630 v4 @2.20GHz, 128GB DDR4, HPE 10G 2 port 546SFP+ (to core switch), HP H241 SAS Controller - 12Gb/s SAS (to MSA)
Is there anything I can do to improve performance? I don't mind adding disks, but I don't fancy major surgery.
Thanks
Tom
Hi,
I currently have an HP 2040 MSA in production. We purchased a 2050 to attach to the production 2040 for expansion. Unfortunately I can't seem to find any documentation on the procedure on how to do this. Would anyone be able to point me in the direction for the steps / instructions for this?
Thanks in advance
hello to all members and good day to you !
13 new SFF 1.2 TB 10K disks have been installed in MSA 2040 , one linear disk group have been configured with raid 6 and two local spares before any data written to it (disk group) and after a short while, one drive dissappeared from management interface slot 18 , tried "show disks detail" command with that drive not shown in the list , the phyisical disk leds are solid green and solid amber , which is not listed in troubleshooting guide, if the disk was degraded and faulty in a normal way, all would be good , but the costumer rightfully requested an explanation, as they fear that this would happen again during production (with short time between failures).
1- you have to read the above to understand the first question, are there any commands that may help with the disk dissappearing from management interface ,or is it just fried , explanation ?
2-are spares automatically enter the active data disks and rebuild or is it manually ?
3-can I add new disks to existing disk groups in MSA ? like in this scenario a faulty disk got replaced by a configuered spare in the group and I want to configure a new disk to replace the spare
and thank you all for your time !
Hello!
I'm currently setting up my new MSA2050. I'm intending to use it over iSCSI from a linux cluster. I cerate my volume, create my initiator with a valid looking iqn, I map them - and then when I try to see this from my linux system I can only see the base LUN, not the volume I created. I have been giong crazy trying top figure this out. I have deleted and recreated everythign many time, in many ways. I've tried making sure everything is named and added to groups, and tried making sure there are no groups. the ouput of iscsiadm --mode discoverydb --type sendtargets --portal (IPADDRESS) --discover is
IPADDRESS:3260,3 iqn.2015-11.com.hpe:storage.msa2050.192450226d
When I point other storgae, everything works as expected. What have I missed?
현재 사용중인 P2000 G3 모델입니다. 점검 중 시스템이벤트를 확인해보니
영문 : Supercapacitor failure. Status : cell 2 voltage is too high (28), State: failure (12) (p2: 3972, p3:0)
한글 : 초고용량 콘덴서가 실패했습니다. 상태: 셀2 권한이 너무 높습니다.
라고 출력되었습니다. 커패시터가 나간것 같은데 스토리지에서 해당사항은 처음 접해보는지라 도움 구해봅니다ㅠㅠ 단순히 커패시터만 교체한다면 해결할 수 있는 문제인가요? P2000 메인보드 메뉴얼을 구할 수 없어 난처합니다ㅠ
이 상황은 어떤 상황이고, 어떻게 해결해야 할까요? 경험자 분들의 많은 도움 부탁드립니다.
-------------------------------------------------
P2000 G3. I checked the system event
English: Supercapacitor failure. Status: cell 2 voltage is too high (28), State: failure (12) (p2: 3972, p3: 0)
Was printed. I think the capacitor is out, but I'm new to storage, so I'm looking for help. Is it a problem that can be solved by simply replacing the capacitors? P2000 Motherboard manual is not available
What is this situation and how do I resolve it? Please give a lot of advice.
I have an MSA 2050 with 14 x 15K 900GB HDDs. From the MSA Gen5 Virtual Storage Technical Reference Guide, I follow the power of 2 for number of drives in a RAID 5 / 6 VDG and create an 8+1 RAID 5 VDG for pool A and a 4+1 RAID 5 VDG for pool B. Alternatively, I can also create two 6+1 RAID 5 VDGs and assign one to pool A and the other to pool B to balance the load across the two controllers.
Since the drives are HDDs that do not come close to exercising the bandwidth limits of the controllers, I want to use the first option of two different power of 2 size VDGs for the two pools. What are considerations that might justify using the second option of two same but not power of 2 size VDGs for the two pools instead of the first option?
I ran the latest firmware on an MSA2040 with SAS connection, and the end result said that only one of two controllers had been successfully updated. However trying the same upgrade again resulted in the software reporting that it was already up to date.
The only difference I am seeing with the new firmware is an informational alert about a volume being over-committed - which I have also seen on an MSA 2050.
Hi, i would like to know if someone can share me the process to add new disk array (6 disk) on a MSA2050 with 2 Group disks running in Production,
Thanks!
Hello,
I have hp msa 2050 with two servers and no switches
i want to user esxi with two san controller
do I have to get two network cards for servers? or I can work with single one with two ports ?
any suggest link to read how to configure it with two configure it ?
digram :
server 1 - port 1 - to san ctr group 1 - a port 1
server 1 - port 2 - to san ctr group 1 - b port 1
server 2 - port 1 - to san ctr group 2 - a port 1
server 2 - port 2 - to san ctr group 2 - b port 1
thanks.
Hello,
I am installing a MSA 1050 SAN 48TB in my datacenter 1.
I was wondering if I should put my second MSA 1050 SAN 48TB in my second data center and replicate data from the first to the second?
Or does an MSA 1050 SAN with dual power supply and controller offer sufficient redundancy?
If the SAN motherboard malfunctions, will the SAN continue to operate?
My question is the following :
Can a SAN with a power supply and a dual controller deal with any hardware problem that happens to it?
thank you !
PS : Sorry for my English
Hi,
We have 2 san MSA 2040 and we are going to sell 1 san MSA. We are going take 8 disques from the sell MSA to put in the remain MSA. All the disks are the same, and we want to add those 8 disks to the pool and extend the storage size.
How can I do that step by step ?
I put all disk in the same order. and I have the 2 quorum and 2 volumes.
How to delete the second volume and have new disks to add to the first volume ? I want to add disks to the first storage.
Dear all,
We have purchased a new SAN storage 2050, and we have set up all the initial configuration. Still, now we facing a issue when we connect the SFP into SAN storage then connect directly to SAN switch but shows error ( SFP is not support ), changed the SFP its still same mistake as well as with recommendation ( valid SFP is supported by configuration this command set-host pre mode ( FC) I did this command but still same. Any solution for this, should we change the SFP model and if yes, which specific. ? Thanks
HPE Pointnext is focused on improving customer experience through self-solve. HPE knowledgebase empowers customers with online solutions like never before!
To further enhance the customer experience through self-solve, we would like to share the following most frequently used solutions in MSA. These Knowledge documents address product issues that are getting logged with HPE.
Self-help solutions for MSA 2040, P2000 G3, 2050 and 1040:
Hello,
I have 2 pools on a MSA 1050: pool A with 1 disk group with 4 SSD disks and pool B with 1 disk group with 7 SAS disks.
On this MSA I have 2 volumes: volume SSD linked to pool A and volume SAS linked to pool B.
I have added 4 SSD disks to the device, and I have created a second disk group on pool A, but, how can I expand the volume SSD to use the new disk group? because the volume have the same available disk space than had before...
Hello,
One of two ProLiant DL 360 Gen9 (exactly same HW setup) servers is spaming event log with error 129, 153 and 5008. Main problem is, that VMs are freezing on this node from cluster and it is not possible to work with them. Source of MPIO is MSA 2040.
NODE A is the problematic one, lets asume there are no VMs running. When I move 1 VM to NODE A, errors start showing up (129, 153, 5008). When I move that VM to another node (good one) no more errors shows up at NODE A.
Then Cissesrv 24607 appeared:
"The event information received from array controller H241 located in server slot 2 was of an unknown or unrecognized class.
An excerpt of the controller message is as follows: Phy Err Thresh Exceeded, DeviceType=254 Port=2E Box=0 Bay=0."
So I started updating all and NODE A, leaving NODE B as it is since it is working well.
NODE A running Win2012R2, System Rom: P89 v2.76 (10/21/2019).
HBA H241 driver: 106.26.0.64
Smart Array P440ar Controller: 106.26.0.64
Found this solution for error 129 and 5008 https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=emr_na-c04584498 but why uninstall WBEM when on other server it is working well?
I would apreciate any help. Thank you! Jaromir
Hi All,
a simple question. Customer needs a migration strategy from a legacy ISCSI array supporting an ESXI 5.5U3 ingfrastructure. Was considering MSA 2050 or 2052 but support matrix shows ESXi 6.0 is the lowest supported (or at least tested) version. Assume if we were to deploy an MSA2050/2 using ISCSI to provide a new storage location that it should most likely work given it's just ISCSI. Appreciate the SPOCK reccomendations are what's been lab-tested. Just wanted to confirm there should be no major gotchas. Plan would be to re-use the MSA elsewhere once the 5.5 environment is decomissioned.. Existing ISCSI array is EOL and at capacity hence the need. Thanks,
Hello everybody,
I received Netapp (Hitachi) hard drives and my technical director asked me to check if we could use them in our MSA bay
The disks look good physically but they come out in an unusable state.
A problem with the FDE (disk encryption).
Has anyone already encountered this problem, and is there a solution to use Netapp disks in MSA arrays (or possibly in HP servers)?
Thank you
