- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: P2000 MSA 6Gb SAS Scrub errors
HPE EVA Storage
1752777
Members
6186
Online
108789
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
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
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
03-06-2011 09:57 AM
03-06-2011 09:57 AM
P2000 MSA 6Gb SAS Scrub errors
Hello!
Our MSA, Firmware FS200R021, reports the following errors:
A934/207: Scrub fails on vdisk, Number of parity mismatches found: 2
A939/21: Vdisk verification faild. Command faild. (error code 1) 2 errors found.
The vdisk status is FTOL, all disks health is ok. There are no other errors.
As in Event Descriptions Reference Guide described we want to fix these errors.
We log into MSA using manage and execute the following command:
verify vdisk vd01 fix yes
The MSA reports:
Error: invalid or ambiguous parameter fix found.
Error: The command had an invalid parameter or unrecognized parameter. - Invalid or ambiguous parameter found: fix
How can we fix this error?
Our MSA, Firmware FS200R021, reports the following errors:
A934/207: Scrub fails on vdisk, Number of parity mismatches found: 2
A939/21: Vdisk verification faild. Command faild. (error code 1) 2 errors found.
The vdisk status is FTOL, all disks health is ok. There are no other errors.
As in Event Descriptions Reference Guide described we want to fix these errors.
We log into MSA using manage and execute the following command:
verify vdisk vd01 fix yes
The MSA reports:
Error: invalid or ambiguous parameter fix found.
Error: The command had an invalid parameter or unrecognized parameter. - Invalid or ambiguous parameter found: fix
How can we fix this error?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-25-2011 03:59 AM
03-25-2011 03:59 AM
Re: P2000 MSA 6Gb SAS Scrub errors
Hello!
Looks like you are not using the correct syntax.
From the reference guide about the 'fix':
"For details about using this parameter, including the required pass code".
So looks like this is not something you should do by yourself. As far as I remember, you should be careful when using the verify fix.
I would suggest contacting HP Support to get clarifications about this.
Has the error increased or have they stayed at two? If so, maybe a fsck on the file system would be worth trying as well.
Looks like you are not using the correct syntax.
From the reference guide about the 'fix':
"For details about using this parameter, including the required pass code".
So looks like this is not something you should do by yourself. As far as I remember, you should be careful when using the verify fix.
I would suggest contacting HP Support to get clarifications about this.
Has the error increased or have they stayed at two? If so, maybe a fsck on the file system would be worth trying as well.
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