HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- MSA2000fc Disk unreadable
MSA Storage
1829103
Members
2265
Online
109986
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
Forums
Discussions
Discussions
Discussions
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
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
04-19-2009 04:38 AM
04-19-2009 04:38 AM
MSA2000fc Disk unreadable
Hy there
Last week we had the ollowing desaster: MSA2000fc with redundant Controllers. One VDisk and an associated Snappool assigned to each controller. One controller crashed. With the Web Interface of the second controller we restarted the first one, which seemed to function fine and showed all green afterwards. The Volumes assigned to the first controller appeared at the hosts (all Win2003 Server)as unknown and unreadable. The Volumes of the second controller worked fine with their Server. We restarted the hosts, same result. We moved the ownership from Controller A to B, same result. We rebooted both controllers, same result. We repowered the whole system, same result. We rebooted the whole infrastructure (MSA, fc-switches, hosts), same result. I did a verify on the vdisks, MSA said all fine. We called HP 24/7 support and a technician came with a new controller, changed Controller A, same result. At the end of the day we had to delete all Volumes of Contoller A and set them up again. After retreiving the backup everything worked fine. The HP Technician had no idea how this happened, why Controller B did not overtake and why the disks were unreadable.
Does anyone have an idea how we could avoid such an accident in the future and what could have happened?
Regards
Jan
Last week we had the ollowing desaster: MSA2000fc with redundant Controllers. One VDisk and an associated Snappool assigned to each controller. One controller crashed. With the Web Interface of the second controller we restarted the first one, which seemed to function fine and showed all green afterwards. The Volumes assigned to the first controller appeared at the hosts (all Win2003 Server)as unknown and unreadable. The Volumes of the second controller worked fine with their Server. We restarted the hosts, same result. We moved the ownership from Controller A to B, same result. We rebooted both controllers, same result. We repowered the whole system, same result. We rebooted the whole infrastructure (MSA, fc-switches, hosts), same result. I did a verify on the vdisks, MSA said all fine. We called HP 24/7 support and a technician came with a new controller, changed Controller A, same result. At the end of the day we had to delete all Volumes of Contoller A and set them up again. After retreiving the backup everything worked fine. The HP Technician had no idea how this happened, why Controller B did not overtake and why the disks were unreadable.
Does anyone have an idea how we could avoid such an accident in the future and what could have happened?
Regards
Jan
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP