Can you please help us to understand if the issue got resolved or not?
If issue got resolved then how?
Also request you to mark the forum as resolved if there is no more outstanding query from your end on this issue.
This will help for everyone who are all following your forum.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************
Can you please help us to understand if the issue got resolved or not?
If issue got resolved then how?
Also request you to mark the forum as resolved if there is no more outstanding query from your end on this issue.
This will help for everyone who are all following your forum.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
**********************************************************************
Can you please help us to understand if the issue got resolved or not?
If issue got resolved then how?
Also request you to mark the forum as resolved if there is no more outstanding query from your end on this issue.
This will help for everyone who are all following your forum.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************
Can you please help us to understand if the issue got resolved or not?
If issue got resolved then how?
Also request you to mark the forum as resolved if there is no more outstanding query from your end on this issue.
This will help for everyone who are all following your forum.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************
Hi,
Firmware wersion is GL101R001.
Total drive in system is 24.
Vdisks in system is 3 -vd01, vd02, vd03.
I verified and in vd02 not have hardware error any other drive.
This solution with move some working drive for me is very difficult and risk. The vdisk from which the disk move to 1.14 will may be damaged.
In vd01 I have one disk spare and this working spare maybe move to vd02 to 1.14.
What do you think about it?
Can such a test be done on a running MSA or do I have to shut down MSA?
Mr. Subhajit, thank you. As you suggested,
1. backed up the data first
2. remove entire disk group
3. recreate disk group , volume , and mapping
4. solved
Have a nice day.
Yes you can move any spare drive from one location to other location and for that no downtime required. Our objective is to identify if any issue with slot 1.14
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
*************************************************************************
Hi everyone,
We need suggestion about RAID on MSA 2050
currently we have 8 SAS x 900GB and we setup it as follow:
7 SAS as RAID 5 and 1 SAS as Global Spare.
is it safety? Some said RAID 5 was very risky.
Thank you.
I moved spare disk from workin slot to 1.14. Disk filed after moving in slot 1.14
Second problem is that when I moved disk spare to his orginal slot he failed. How to reset disk to factory reset and make him again a spare.
It looks like slot 1.14 is damaged.
At this point it looks like slot 1.14 is bad for which you may have to replace the Chassis.
If the drive back to it's original slot and shows as failed then only option is to physically re-seat the drive to get proper state of the drive. If you have any other system then you can check this drive health there as well. If possible take downtime and do a proper power cycle of the entire system. Give it a last try so that if slot 1.14 and other drive get fixed. It's very important that you update all firmware for all of the components as well.
There are few more things, Controller firmware is very old and inactive as below you can see,
I don't know the drive model also and in which firmware drives are running.
We can avoid many issues by updating firmwares time to time.
You can check the below links to get all firmwares,
https://h41111.www4.hpe.com/storage/msafirmware.html
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-a00041326en_us
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04315770&lang=en-us&cc=us
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
***********************************************************************
RAID you need to configure based on your requirement and capacity to afford this.
MSA2050 supports RAID 1, 5, 6 and 10
Now RAID 1 and 5 VDG both can sustain upto one drive failure. In case of RAID 6 and 10 VDG it can sustain upto 2 drive fail.
I am not discussing all pros & cons for different RAID levels as that will be different topics.
Here you need to choose RAID for VDG based on your business requirement and you need to check you need more space or you need more redundancy. RAID 1 and 5 will be less redundant compare to RAID 6 and 10
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS!thumb below!
***********************************************************************
How to re-seat the drive to get proper state of the drive.?
In another system disk works, is ok.
If I replace the chassis the configuration array will be lost? I have two controllers.
Hi,
We had a power problem in enclosure 3 of our MSA2000 G3
After replacement of the power, we now have an issue with the SAS cannels
We see the following
Unhealthy Component
-------------------
Component ID: Enclosure 4, Expansion Module B, Out Expansion Port
Health: Degraded
Health Reason: The enclosure expansion port is degraded; some, but not all, of the PHY lanes can support activity.
Health Recommendation: - Check the SAS expansion cable between enclosures connected through the indicated port, and replace the cable if necessary.\n- If this does not correct the problem, check that the modules at each end of the cable are powered up and have good health; replace any faulty controller module or expansion module.
Unhealthy Component
-------------------
Component ID: Enclosure 3, Expansion Module A, In Expansion Port
Health: Degraded
Health Reason: The enclosure expansion port is degraded; some, but not all, of the PHY lanes can support activity.
Health Recommendation: - Check the SAS expansion cable between enclosures connected through the indicated port, and replace the cable if necessary.\n- If this does not correct the problem, check that the modules at each end of the cable are powered up and have good health; replace any faulty controller module or expansion module.
Unhealthy Component
-------------------
Component ID: Enclosure 3, Expansion Module B, In Expansion Port
Health: Degraded
Health Reason: The enclosure expansion port is degraded; some, but not all, of the PHY lanes can support activity.
Health Recommendation: - Check the SAS expansion cable between enclosures connected through the indicated port, and replace the cable if necessary.\n- If this does not correct the problem, check that the modules at each end of the cable are powered up and have good health; replace any faulty controller module or expansion module.
Unhealthy Component
-------------------
Component ID: Enclosure 2, Expansion Module A, Out Expansion Port
Health: Degraded
Health Reason: The enclosure expansion port is degraded; some, but not all, of the PHY lanes can support activity.
Health Recommendation: - Check the SAS expansion cable between enclosures connected through the indicated port, and replace the cable if necessary.\n- If this does not correct the problem, check that the modules at each end of the cable are powered up and have good health; replace any faulty controller module or expansion module.
So, on enclosure 3 both IN ports on the IOMS are 'faulty' and on enclosure 4 one SAS OUT port and on Enclosure one SAS OUT port (but on the other side). This would imply enclosure 3 cannot be properly reached, but the MSA seems to be working fine.
If we look further down on the log we see the following
U12-6G Degraded A subcomponent of this component is unhealthy. - No action is required. for enclosure 2, 3 and 4.
What could be causing this please. We have reseated the SAS cables
You just have to physically remove the drive from the slot. Half of the slot or bay is enough. Give 1min and then put it back.
Then check in CLI and SMU about the state of the drive.
As you have mentioned this drive looks fine in other system so I would suggest you to try power cycle of the MSA before you go for Chassis replacement.
Regarding Chassis replacement, you should have everything intact. Only there may be chance of losing mapping information. All vdisk and volumes information available and saved in drive metadata. As there is no controller getting replaced then all should be fine. You can anyway capture MSA log before go for any kind of replacement activity.
Hope this helps!
Regards
Subhajit
I am an HPE employee
If you feel this was helpful please click the KUDOS! thumb below!
*********************************************************************
Hello,
If the disk works in another system then there are a couple of steps you can take.
Both your array and your drives need upgrading. There are several drive types that have a critical firmware upgrade that prevents a premature failure from occurring. You need to get those drives upgraded quickly! Your array is also running a version of code that has several improvements in drive error handling and reporting.
If you have another system that works with the drive you should review the drive errors in that system before continuing to swap the drive back into the original system. It sounds as if that drive might have thrown errors. WIthout a full log review it is impossible to determine whether the drive has predictive failure or UREs and how close the drive is to failure.
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
Hello,
Due to the power issue you may have either caused the backend SAS map to be rebuilt or incorrectly scanned. There are a couple of things you can try.
Check and verify the cables are correctly seated. I have seen where work is done in the rack and bumping a SAS cable has caused a loss of the path or disconnected an enclosure.
Or try the following:
This will rebuild your backend SAS map. If the issue persists you may want to log a support case and have the logs reviewed or IOMs replaced.
Cheers,
Shawn
I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.
Hi.
Need to add more disk for more preformance to our MSA 2052.
Current setup: 2-tier, 1 pool only (A)
6 800GB SSD RAID6 (no spare) (HPE MSA 2052 SAN Dual Controller SFF Storage)
10 4TB MDL RAID6 + 2 spare (HPE MSA 2050 LFF disk enclosure)
Connected to 6 hosts with a total of 86 (mail, file, sql, web, everything) vm.
Should I go for 4 more SSD, total 10 or add enclosure with 10k SAS (raid6 or 10?) and create 3-tier?
10 disks is max in same tier on raid6 (power of 2)? I don´t beleve in raid5.
Pool B is saved for a later time with the other free half of main unit with ssd + mdl/10k enclosure
/Patrik
gehter with HPE we isolated the problem
On two IO Modules we found a SAS channel being disabled due to internal errors, so instead of 4 active channels per port there were only 3. One module had an issue on channel 3 on the Ingress port the other on channel 0 on the Egress port.
Both IO modules will be replaced.
This is visivble in the config log,
Hello!
I have 3 disk groups on my MSA 2050 and going to remove 1 group. I do it by the way that described in manual and VDRAIN process starts. So, all data from removing disk group not going to be deleted, it's just roaming to other disk group. But I do not need these data ! I want to clear, purge it at all! Is it possible, without deleting all pool? Or may be it is possible to delete disk group without VDRAIN?
Thank You.
