- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- MSA2324i G2 LEFTOVR drive oddity
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
01-12-2016 03:07 AM
01-12-2016 03:07 AM
MSA2324i G2 LEFTOVR drive oddity
Hi folks,
MSA2000i, firmware M114P01 (latest G2 I think) failed a drive in one of its R5 vdisks, electrical death so it just disappeared from the SMU and CLI. I replaced it with a similar 300gb drive and added the replacement into the spare pool. Reconstruction took over and lasted 10 minutes before stopping and kicking the drive out to LEFTOVR state. Since this was a brand new drive I cleared the disk metadata and re-added it to the spare pool. Same result.
I bought an identical model and firmware-level drive (EG0300FAWHV, HPDF) which matched the other 5 drives in the vdisk and the same thing happens.
Any clues? The logs just say 'unknown reason, have a look in the troubleshooting guide' which just says to clear metadata. I don't want to destroy and rebuild this vdisk if at all possible since there's a 1.1TB reporting server using it. The controllers obviously know the replacement drive SHOULD be added to this vdisk since they attempt reconstruction, but why the failure?
Cheers