Hello
yes i try to add new pool on A.. see attachement
Hello
yes i try to add new pool on A.. see attachement
I can think of two possibility or workaround here,
1> Remove the un-used SSD half of the slot and then try to create the Virtual DIsk Group with SAS drives as you want in Pool A. It's possible that Controller is thinking SSD drive available in system without Performance Tier License so it's not allowing to create new VDG. So after you create the new VDG in Pool A then insert the SSD and try to configure SSD read-cache
2> Delete the existing SSD read-cache VDG from Pool B and then remove all SSD drives half of each slot. Then try to create the Virtual DIsk Group with SAS drives as you want in Pool A. After you create the new VDG in Pool A then insert back both SSD and try to configure SSD read-cache one in Pool A and another for Pool B
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************
tks so much it's work
i remove cache from pool B, next create virtual storage and add cache to pool A and B
tks so so much
Hello
we have MSA 2040 and 2 controller.
I have Virtual pool installed, on B with free read cache function.
I want to add another pool on A, but system said that i must add licence...
i don't know if i forgot something or don't do the good step.
i try too add pool with group disk ?
Moderator Message:This post was moved as a new topic from the following old discussion.
In Pool B it looks like there are two Virtual DIsk Group. Out of them one is used as Read Cache so that one created with SSD drive. What about other VDG ?
Now in Pool A what type of drive you want to use to create new Virtual Disk Group ? is it SAS drives or SSD ?
Can you please provide me the below output,
# show disks
# show pools
# show disk-groups
You cannot create virtual disk groups that contain SSDs without the Performance tier license. You can have SSDs in a fault tolerant Disk Group as a Performance Tier or as a non-fault tolerant (up to 2 disks) Disk Group as Read Cache. But neither pool can have both a Performance Tier and a Read Cache. For example, pool A can have a Performance Tier and pool B can have a Read Cache.
Note any license required for the System level and it's not specific to any Pool.
You must have tried to create VDG and got error because there is bydefault two Pools exist. If you are unable to see another Pool that's because there is no VDG exist for that Pool.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
first tks for reply
See attachement for command
so we have 8 avalaible disks and 1 ssd. I want to create new pool with this 8 disks, and add read cache with ssd to this pool.
Thanks for providing the outputs.
Are you not able to create new Virtual Disk Group with all 8 SAS drives ? at the time of VDG creation you need to select Pool A where you want to associate this new VDG.
After that you can create SSD Read-cache VDG with the available SSD drive and associate it with Pool A
If you are getting any error then please share the screenshot.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Hello
yes i try to add new pool on A.. see attachement
I can think of two possibility or workaround here,
1> Remove the un-used SSD half of the slot and then try to create the Virtual DIsk Group with SAS drives as you want in Pool A. It's possible that Controller is thinking SSD drive available in system without Performance Tier License so it's not allowing to create new VDG. So after you create the new VDG in Pool A then insert the SSD and try to configure SSD read-cache
2> Delete the existing SSD read-cache VDG from Pool B and then remove all SSD drives half of each slot. Then try to create the Virtual DIsk Group with SAS drives as you want in Pool A. After you create the new VDG in Pool A then insert back both SSD and try to configure SSD read-cache one in Pool A and another for Pool B
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************
tks so much it's work
i remove cache from pool B, next create virtual storage and add cache to pool A and B
tks so so much
Nice to know that your issue got resolved. Kindly mark this forum as resolved so that others can also get the solution who are all following this.
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************************
Hi, community.
I'm looking a document "HPE MSA Storage Configuration and Best Practices for VMware vSphere"
Oddly enough, this document is no longer available on the HPE site ((
So, any help are greatly appreciated.
hi
this is what I have
"HPE MSA 2040 Storage Configuration and Best Practices for VMware vSphere"
If you want tell where to upload it
Regards
Give a KUDO if this helps
Please find the links which may help you,
https://cdn.cnetcontent.com/23/a5/23a5c5bb-a5aa-4022-935b-be99b17b713f.pdf
Hope this helps!
Regards
Subhajit
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************************
Good day MSA Community! I have two short questions about the use of HPE Insight Remote Support (IRS) with MSA.
I appreciate your feedback and if would like to learn more about IRS, you can visit: https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=REMOTESUPPORT
Thanks!
/Kipp
I had a couple of days ago 1 HDs on the virtual disk failing. The virtual disk is on raid 5+0 and had a spare. After replacing the hard drives, it started to reconstruct the Raid and looks like failed yesterday, by giving me another error and by presenting 1HDs as "Leftover". After searching on google, i cleaned the metadata of these hard drives and presented them again to the virtual disk and the reconstruction started again.
However it looks like during the night the reconstruction failed and for some reason the whole Virtual Disk went Offline!
recon operation in 80% going to failed
please help me how solved this problem
ombined SC Event Log
Event SN, Date/Time, Code,Sev,Ctrlr, Description
B1 2018-08-12 09:09:42 118 I B Cache parameters have been changed for a volume. (volume: vm-300GB_v001, SN: 00c0ffd84a510000688b375a01000000) (cache optimization: standard, prefetch: 512KB, write-back cache: on)
B2 2018-08-12 09:09:44 19 I B A rescan-bus operation was done. (number of disks that were found: 14, number of enclosures that were found: 1) (rescan reason code: 29)
A2 2018-08-12 09:10:49 19 I A A rescan-bus operation was done. (number of disks that were found: 14, number of enclosures that were found: 1) (rescan reason code: 4)
B3 2018-08-12 09:10:49 41 I B A spare disk drive has been added to a vdisk. (vdisk: vm-300GB) (disk: channel: 0, ID: 2, SN: 6SE2V9L900009133SU0T, enclosure: 1, slot: 3)
A3 2018-08-12 09:10:51 19 I A A rescan-bus operation was done. (number of disks that were found: 14, number of enclosures that were found: 1) (rescan reason code: 4)
B4 2018-08-12 09:10:51 9 I B A spare disk kicked in for a critical vdisk. (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000) (disk: channel: 0, ID: 2, SN: 6SE2V9L900009133SU0T, enclosure: 1, slot: 3)
B5 2018-08-12 09:10:51 37 I B Vdisk reconstruct started. (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000) (disk: channel: 0, ID: 2, SN: 6SE2V9L900009133SU0T, enclosure: 1, slot: 3)
B6 2018-08-12 11:23:57 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd84a510000688b375a01000000) It comprises 1% of cache space.
B7 2018-08-12 11:23:57 18 W B Vdisk reconstruct failed. Command failed. (error code: 1). (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000)
B8 2018-08-12 11:23:57 172 W B A vdisk was quarantined. (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000)
##*************************************##
SC Event Log -- Controller A
Event SN, Date/Time, Code,Sev,Ctrlr, Description
A1 2018-08-12 09:09:44 19 I A A rescan-bus operation was done. (number of disks that were found: 14, number of enclosures that were found: 1) (rescan reason code: 29)
A2 2018-08-12 09:10:49 19 I A A rescan-bus operation was done. (number of disks that were found: 14, number of enclosures that were found: 1) (rescan reason code: 4)
A3 2018-08-12 09:10:51 19 I A A rescan-bus operation was done. (number of disks that were found: 14, number of enclosures that were found: 1) (rescan reason code: 4)
##*************************************##
SC Event Log -- Controller B
Event SN, Date/Time, Code,Sev,Ctrlr, Description
B1 2018-08-12 09:09:42 118 I B Cache parameters have been changed for a volume. (volume: vm-300GB_v001, SN: 00c0ffd84a510000688b375a01000000) (cache optimization: standard, prefetch: 512KB, write-back cache: on)
B2 2018-08-12 09:09:44 19 I B A rescan-bus operation was done. (number of disks that were found: 14, number of enclosures that were found: 1) (rescan reason code: 29)
B3 2018-08-12 09:10:49 41 I B A spare disk drive has been added to a vdisk. (vdisk: vm-300GB) (disk: channel: 0, ID: 2, SN: 6SE2V9L900009133SU0T, enclosure: 1, slot: 3)
B4 2018-08-12 09:10:51 9 I B A spare disk kicked in for a critical vdisk. (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000) (disk: channel: 0, ID: 2, SN: 6SE2V9L900009133SU0T, enclosure: 1, slot: 3)
B5 2018-08-12 09:10:51 37 I B Vdisk reconstruct started. (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000) (disk: channel: 0, ID: 2, SN: 6SE2V9L900009133SU0T, enclosure: 1, slot: 3)
B6 2018-08-12 11:23:57 44 W B Unwritable cache data exists for a volume. (volume: , SN: 00c0ffd84a510000688b375a01000000) It comprises 1% of cache space.
B7 2018-08-12 11:23:57 18 W B Vdisk reconstruct failed. Command failed. (error code: 1). (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000)
B8 2018-08-12 11:23:57 172 W B A vdisk was quarantined. (vdisk: vm-300GB, SN: 00c0ffd84a510000cf89375a00000000)
##*************************************##
SC Error/Warning Log
i uploaded the system logs
Hi Guys,
I hope someone can help. I have an old HP SAN MSA2312i. 1 disk failed. I replaced the disk (Disk 5 in RAID5) with a new disk. I cleared the META DATA and Added the disk as spare. The rebuild started and after a while 2 disk become on status LEFTOVR. I thought the new disk is a defect one and I buyed a second new disk. This give also this message. In the log I see :
Vdisk reconstruct failed. Command failed. (error code: 1). (vdisk: VDISK_RAID5, SN: )
Can someone help?
Thanks a lot
M. Narjis
Dear sir
I exteneded the Vdisk ( 4 Disks ) by added new 1 disk to Raid0.
I need to shrink Vdisk to old status (3 Disks )
Hello
Below link can be helpful for you to resolve this issue:
Link: Click here to access the page for HPE P2000/MSA 2000 SAN Array Systems - How to Decrease Volume Size.
If this helps you with your issue, please click the thumb to register a Kudo.
If it resolves the issue, please consider marking it as an Accepted Solution.
Thanks and Regards,
I am an HPE employee
Hello,
The first drive that failed - what slot was it in? If there was a spare drive already assigned, the vdisk should have used the spare drive to reconstruct.
Since the drive in slot 1.3 failed to reconstruct there is likely another drive that is reporting errors. There is not enough information in what you posted to be able to tell the original failed drive, the reconstuction target drive, and what drives are currently in leftover or failed.
With the cache status showing there is unwritten data, you will need to verify which vdisk that cache is for and whether it is needed or not. Be sure you can access all the volumes before you consider next steps.
If you can take a backup of the vdisks, you should do that immediately. I also suggest that instead of trying to troubleshoot such a critical issue on a forum, you should engage support so they can review logs and make further recommendations in order to protect and recover your vdisk.
I do not see any logs attach to the forum.
Cheers,
Shawn