- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ML370 SA641 Reassign spare?
ProLiant Servers (ML,DL,SL)
1748216
Members
4089
Online
108759
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
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-21-2009 05:03 AM
тАО06-21-2009 05:03 AM
ML370 SA641 Reassign spare?
I recently had a drive fail on my ML 370 Raid 5 and the spare kicked in. Everything worked like it was supposed to, which is a good thing!
Now I have replaced the failed drive with another, but the acu (v 7.15.19) shows the array still in failure mode and the replacement as unassigned drive and is still working with the original spare as the 3rd drive.
How can I reassign the new drive(s) (picked up 2 drives) as spare(s)?
Any help would be appreciated.
Denis
Now I have replaced the failed drive with another, but the acu (v 7.15.19) shows the array still in failure mode and the replacement as unassigned drive and is still working with the original spare as the 3rd drive.
How can I reassign the new drive(s) (picked up 2 drives) as spare(s)?
Any help would be appreciated.
Denis
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2009 03:04 AM
тАО06-22-2009 03:04 AM
Re: ML370 SA641 Reassign spare?
Hi Denis,
As per the screenshot, I see that SCSI ID 0, 1 and 6 are part of the array. I am not sure how this array was created. Usually it should have been SCSI ID 0, 1 and 2.
The Smart Array controller and the backplane will assign the lowest SCSI ID which is free/availabel, when a new drive is installed.
As the IDs used were 0,1,3 and 6. When a new drive was installed it has taken SCSI ID 2 which was free and when a second new drive was installed it has taken up SCSI ID 5 which was free.
At the given scenario the best option is to backup the data and re-create the array with drives with SCSI ID 0,1 and 2.
In older harddrives there was an option to hardset the SCSI ID on the Harddrive. If that option is available on this Harddrive you could manually set the ID to 6 and install it to pick the drive as part of the array. To check if this harddrive has jumpers, remove the hotplug caddy. Once the hotplug caddy is removed you should see the jumpers on the harddrive. Set the jumper to ID 6 and fix the harddrive back in the caddy and you should be good to go.
Refer the below link on how the jumper pins to be set, this is not for the same hardrive but would help you to figure out.
http://www.hitachigst.com/hdd/support/drvs/drvsjum.htm
Regards,
Raj.
As per the screenshot, I see that SCSI ID 0, 1 and 6 are part of the array. I am not sure how this array was created. Usually it should have been SCSI ID 0, 1 and 2.
The Smart Array controller and the backplane will assign the lowest SCSI ID which is free/availabel, when a new drive is installed.
As the IDs used were 0,1,3 and 6. When a new drive was installed it has taken SCSI ID 2 which was free and when a second new drive was installed it has taken up SCSI ID 5 which was free.
At the given scenario the best option is to backup the data and re-create the array with drives with SCSI ID 0,1 and 2.
In older harddrives there was an option to hardset the SCSI ID on the Harddrive. If that option is available on this Harddrive you could manually set the ID to 6 and install it to pick the drive as part of the array. To check if this harddrive has jumpers, remove the hotplug caddy. Once the hotplug caddy is removed you should see the jumpers on the harddrive. Set the jumper to ID 6 and fix the harddrive back in the caddy and you should be good to go.
Refer the below link on how the jumper pins to be set, this is not for the same hardrive but would help you to figure out.
http://www.hitachigst.com/hdd/support/drvs/drvsjum.htm
Regards,
Raj.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-22-2009 04:30 AM
тАО06-22-2009 04:30 AM
Re: ML370 SA641 Reassign spare?
Raj
Thanks for the response. I was afraid of something like that.
The culprit drive is an HP and I don't see any way it could have been hard set, but I'll watch that closer in the future.
Denis
Thanks for the response. I was afraid of something like that.
The culprit drive is an HP and I don't see any way it could have been hard set, but I'll watch that closer in the future.
Denis
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