- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- VA7400 disk failure
Disk Enclosures
1752477
Members
5576
Online
108788
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
Go to solution
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
тАО05-07-2003 09:03 PM
тАО05-07-2003 09:03 PM
Recently we had one disk failure on VA7400. Array has recovered data from redundancy, BUT - SDM gui still shows, that there are hot spares for each redundancy group. WTF ? What action is needed to allocate hot spare for failed disk ? Our VA is in autoraid mode, and using RAID0+1 right now.
Of course we will get new disk ASAP, but I'm worrying about the data and possible downtime ...
Saulius
Of course we will get new disk ASAP, but I'm worrying about the data and possible downtime ...
Saulius
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2003 09:13 PM
тАО05-07-2003 09:13 PM
Solution
Please attach 'armdsp -a' output and I will be able to explain you in details.
In your case rebuild has been completed and there's enough space for this rebuild to complete successfully and space for active hot spare. If you do not see any warnings like 'redundancy lost' then there's enough space for next rebuild. But of course, you should replace failed component ASAP to keep redundancy at initial level
Eugeny
In your case rebuild has been completed and there's enough space for this rebuild to complete successfully and space for active hot spare. If you do not see any warnings like 'redundancy lost' then there's enough space for next rebuild. But of course, you should replace failed component ASAP to keep redundancy at initial level
Eugeny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2003 10:57 PM
тАО05-07-2003 10:57 PM
Re: VA7400 disk failure
Actually I suspect that VA firmware reallocated data, and "made" new hot spare. Because I see in the armdsp output:
CAPACITY USAGE
Total Disk Enclosures:________________2
Redundancy Group:_____________________1
Total Disks:________________________11
Total Physical Size:________________734,329 GB
Allocated to Regular LUNs:__________232,1 GB
Allocated as Business Copies:_______0 bytes
Used as Active Hot Spare:___________66,753 GB
Used for Redundancy:________________169,704 GB
Unallocated (Available for LUNs):___265,77 GB
Redundancy Group:_____________________2
Total Disks:________________________8
Total Physical Size:________________534,057 GB
Allocated to Regular LUNs:__________147 GB
Allocated as Business Copies:_______0 bytes
Used as Active Hot Spare:___________66,753 GB
Used for Redundancy:________________147,86 GB
Unallocated (Available for LUNs):___172,443 GB
Used by Non-Included Disks:___________66,757 GB
CAPACITY USAGE
Total Disk Enclosures:________________2
Redundancy Group:_____________________1
Total Disks:________________________11
Total Physical Size:________________734,329 GB
Allocated to Regular LUNs:__________232,1 GB
Allocated as Business Copies:_______0 bytes
Used as Active Hot Spare:___________66,753 GB
Used for Redundancy:________________169,704 GB
Unallocated (Available for LUNs):___265,77 GB
Redundancy Group:_____________________2
Total Disks:________________________8
Total Physical Size:________________534,057 GB
Allocated to Regular LUNs:__________147 GB
Allocated as Business Copies:_______0 bytes
Used as Active Hot Spare:___________66,753 GB
Used for Redundancy:________________147,86 GB
Unallocated (Available for LUNs):___172,443 GB
Used by Non-Included Disks:___________66,757 GB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2003 02:59 AM
тАО05-08-2003 02:59 AM
Re: VA7400 disk failure
Yes, I believe it should be this way. When disk fails, VA does rebuild, after rebuild it checks if there's a still space for active hot spare (checks unallocated space) and if there's a space, it 'eats' active hotspare space from unallocated area
Eugeny
Eugeny
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