- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: MSA1000 Disk Replacement - disk is not really ...
HPE EVA Storage
1752598
Members
5299
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
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
06-07-2011 03:23 AM
06-07-2011 03:23 AM
MSA1000 Disk Replacement - disk is not really defect
Hello,
my Question is: how to replace a disk in msa1000 raid 1 array which is not totally defect.
Server is SuSE Linux SLES 9. MSA Software ist 4.48.
Access to MSA is via serial console, grahical ACU (cpqacuxe) or ACU CLI (hpacucli).
Configuration:
CLI> show unit 22
Unit 22:
In PDLA mode, Unit 22 is Lun 23; In VSA mode, Unit 22 is Lun 22.
Unit Identifier : xlims
Device Identifier : 600805F3-000AC5C0-83469AA3-0EB70049
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Mirror Init Status: Complete
2 Data Disk(s) used by lun 22:
Disk207: Box 2, Bay 07, (SCSI bus 2, SCSI id 8)
Disk307: Box 3, Bay 07, (SCSI bus 3, SCSI id 8)
Spare Disk(s) used by lun 22:
Disk213: Box 2, Bay 13, (SCSI bus 2, SCSI id 14)
Disk214: Box 2, Bay 14, (SCSI bus 2, SCSI id 15)
Disk314: Box 3, Bay 14, (SCSI bus 3, SCSI id 15)
Logical Volume Raid Level: MIRROR FAULT TOLERANCE (Raid 1)
stripe_size=256kB
Logical Volume Capacity : 34,726MB
History:
- Disk207 had the red light on (defect).
- Customer removed Disk207 and re-inserted the same disk(!)
- now the Disks amber light flashes
Eventlog:
03D2A20C 0004 0000 0000 Physical drive failure: Box: 2, Bay: 7
03D2A20C 0005 0000 0000 State change on volume: 22
03D2A20C 0005 0000 0000 State change on volume: 22
03D2A20D 0005 0000 0000 State change on volume: 22
03D2A790 0005 0000 0000 State change on volume: 22
03D546D5 0001 0000 0000 Hot-plug drive removed: Box: 2, Bay: 7
03D546E8 0001 0000 0001 Hot-plug drive inserted: Box: 2, Bay: 7
03D546E8 0005 0000 0000 State change on volume: 22
03D546E9 0005 0000 0000 State change on volume: 22
03D54AB2 0005 0000 0000 State change on volume: 22
So, after failure auf Disk207 a rebuild started with one of the spare disks.
After re-inserting the Disk207, again a rebuild started and the spare disk is no more in use.
Now we would like to replace Disk207 without a downtime.
Q1: Can we disable Disk207 so that a rebuild to spare will start before removing the disk)
Q2: For replacement we have a used disk which was formerly part of the MSA1000. Can we use this disk?
my Question is: how to replace a disk in msa1000 raid 1 array which is not totally defect.
Server is SuSE Linux SLES 9. MSA Software ist 4.48.
Access to MSA is via serial console, grahical ACU (cpqacuxe) or ACU CLI (hpacucli).
Configuration:
CLI> show unit 22
Unit 22:
In PDLA mode, Unit 22 is Lun 23; In VSA mode, Unit 22 is Lun 22.
Unit Identifier : xlims
Device Identifier : 600805F3-000AC5C0-83469AA3-0EB70049
Cache Status : Enabled
Max Boot Partition: Enabled
Volume Status : VOLUME OK
Mirror Init Status: Complete
2 Data Disk(s) used by lun 22:
Disk207: Box 2, Bay 07, (SCSI bus 2, SCSI id 8)
Disk307: Box 3, Bay 07, (SCSI bus 3, SCSI id 8)
Spare Disk(s) used by lun 22:
Disk213: Box 2, Bay 13, (SCSI bus 2, SCSI id 14)
Disk214: Box 2, Bay 14, (SCSI bus 2, SCSI id 15)
Disk314: Box 3, Bay 14, (SCSI bus 3, SCSI id 15)
Logical Volume Raid Level: MIRROR FAULT TOLERANCE (Raid 1)
stripe_size=256kB
Logical Volume Capacity : 34,726MB
History:
- Disk207 had the red light on (defect).
- Customer removed Disk207 and re-inserted the same disk(!)
- now the Disks amber light flashes
Eventlog:
03D2A20C 0004 0000 0000 Physical drive failure: Box: 2, Bay: 7
03D2A20C 0005 0000 0000 State change on volume: 22
03D2A20C 0005 0000 0000 State change on volume: 22
03D2A20D 0005 0000 0000 State change on volume: 22
03D2A790 0005 0000 0000 State change on volume: 22
03D546D5 0001 0000 0000 Hot-plug drive removed: Box: 2, Bay: 7
03D546E8 0001 0000 0001 Hot-plug drive inserted: Box: 2, Bay: 7
03D546E8 0005 0000 0000 State change on volume: 22
03D546E9 0005 0000 0000 State change on volume: 22
03D54AB2 0005 0000 0000 State change on volume: 22
So, after failure auf Disk207 a rebuild started with one of the spare disks.
After re-inserting the Disk207, again a rebuild started and the spare disk is no more in use.
Now we would like to replace Disk207 without a downtime.
Q1: Can we disable Disk207 so that a rebuild to spare will start before removing the disk)
Q2: For replacement we have a used disk which was formerly part of the MSA1000. Can we use this disk?
Greetings, Joachim
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2011 04:23 AM
06-12-2011 04:23 AM
Re: MSA1000 Disk Replacement - disk is not really defect
We did not receive any answer.
We replaced the fault disk online:
- physically removed disk207
- msa recogized failure and started rebuild with spare
- waited for rebuild complete (Took about 20 minuted for 36GB disk. Rebuild prio is 50)
- inserted a new disk into slot 207
- msa recogized new disk and started rebuild.
Greetings
-Joachim
We replaced the fault disk online:
- physically removed disk207
- msa recogized failure and started rebuild with spare
- waited for rebuild complete (Took about 20 minuted for 36GB disk. Rebuild prio is 50)
- inserted a new disk into slot 207
- msa recogized new disk and started rebuild.
Greetings
-Joachim
Greetings, Joachim
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