- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: MSA1000 Parity and Mirror Initialization probl...
Disk Enclosures
1748112
Members
3435
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-12-2007 10:42 AM
тАО12-12-2007 10:42 AM
MSA1000 Parity and Mirror Initialization problems
I have an MSA1000 storage array running firmware 4.32 build 300. The storage array has 4 LUNs created. 2 are RAID 5 and the other 2 are RAID 0 and RAID 1. The RAID 5 arrays are presented to ESX 3.0.1 servers and the RAID 1 and 0 arrays are presented to a Windows 2003 backup server.
When entering "show units" at the CLI the output shows that both RAID 5 LUNs show "Parity Init Status: 0% complete" and the RAID 1 LUN shows "Mirror Init Status: 0% complete". These LUNs were created a few months ago so I don't think that there is ever going to be any progress. I've raised the rebuild priority to high but that hasn't helped.
My questions are: has anyone seen these problems before? How does this affect the fault tolerance? Anyone have any recommendations?
My next step is likely to upgrade the firmware and restart the MSA but this is part of a 24/7/365 PRD environment. We do notice that the RAID 5 LUNs have poor performance when copying LUN to LUN but users are not complaining. We are planning to move the equipment from the current colo facility to another in the near future so if data is not at risk then I would like to wait until that time to do the firmware upgrade/reboot.
Thanks.
When entering "show units" at the CLI the output shows that both RAID 5 LUNs show "Parity Init Status: 0% complete" and the RAID 1 LUN shows "Mirror Init Status: 0% complete". These LUNs were created a few months ago so I don't think that there is ever going to be any progress. I've raised the rebuild priority to high but that hasn't helped.
My questions are: has anyone seen these problems before? How does this affect the fault tolerance? Anyone have any recommendations?
My next step is likely to upgrade the firmware and restart the MSA but this is part of a 24/7/365 PRD environment. We do notice that the RAID 5 LUNs have poor performance when copying LUN to LUN but users are not complaining. We are planning to move the equipment from the current colo facility to another in the near future so if data is not at risk then I would like to wait until that time to do the firmware upgrade/reboot.
Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 12:48 AM
тАО12-13-2007 12:48 AM
Re: MSA1000 Parity and Mirror Initialization problems
Hi Colin,
As a first step, I would definitely upgrade the firmware to something supported...
If you check the SAN design guide, you'll see that ESX is only supported in heterogeneous environments when using version 5 firmware.
There are also some performance improvements going to 5.20 so it should hopefully make things better. As you're running a 24x7x52 environment, you've hopefully got dual controllers, so there shouldn't be too much impact doing the upgrade.
Latest SAN design guide is here (page 181)
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf
Hope this helps,
Regards,
Rob
As a first step, I would definitely upgrade the firmware to something supported...
If you check the SAN design guide, you'll see that ESX is only supported in heterogeneous environments when using version 5 firmware.
There are also some performance improvements going to 5.20 so it should hopefully make things better. As you're running a 24x7x52 environment, you've hopefully got dual controllers, so there shouldn't be too much impact doing the upgrade.
Latest SAN design guide is here (page 181)
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf
Hope this helps,
Regards,
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-13-2007 01:00 PM
тАО12-13-2007 01:00 PM
Re: MSA1000 Parity and Mirror Initialization problems
Thanks for your reply.
Yes, we do have dual controllers. I read the firmware updating guide and it seems that even with a dual controller configuration we still need to restart the MSA to complete the firmware upgrade so we will need to schedule downtime for the upgrade.
It appears that I need to upgrade from 4.32 to 4.48 then to 5.20, can anyone confirm this?
Anyone know if we are at risk for data loss or are is this just impacting performance?
Thanks.
Yes, we do have dual controllers. I read the firmware updating guide and it seems that even with a dual controller configuration we still need to restart the MSA to complete the firmware upgrade so we will need to schedule downtime for the upgrade.
It appears that I need to upgrade from 4.32 to 4.48 then to 5.20, can anyone confirm this?
Anyone know if we are at risk for data loss or are is this just impacting performance?
Thanks.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP