HP MSA P2000 Questions
Greetings.
I'm trying to remove an iSCSI host from our HP MSA P2000 SAN. I'm getting an error that because it is still "discovered", it cannot be removed. Is there a way on the MSA to "refresh" the discovery or do I actually need to restart the MSA to initiate a host scan ? I have our main storage on there connected to another host, so I'd like to avoid restarting it if possible.
Second quick question. On one of our RAID 5 volumes, one of the disks shows as "3.0" Transfer rate, while the remainder show as "6.0". In theory the disks are identical, but maybe not. Is this single spindle in my RAID 5 slowing things down ? I do have spare 6.0Gb disks. Can I just yank it and replace it with a 6 ? I've got 4 disks total on that RAID 5 volume.
Thanks much.
-Stephen
I'm trying to remove an iSCSI host from our HP MSA P2000 SAN. I'm getting an error that because it is still "discovered", it cannot be removed. Is there a way on the MSA to "refresh" the discovery or do I actually need to restart the MSA to initiate a host scan ? I have our main storage on there connected to another host, so I'd like to avoid restarting it if possible.
Second quick question. On one of our RAID 5 volumes, one of the disks shows as "3.0" Transfer rate, while the remainder show as "6.0". In theory the disks are identical, but maybe not. Is this single spindle in my RAID 5 slowing things down ? I do have spare 6.0Gb disks. Can I just yank it and replace it with a 6 ? I've got 4 disks total on that RAID 5 volume.
Thanks much.
-Stephen
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Philip Elder
On question 2: When looking at the individual disk's properties do they match one of the others indicating 6?
ASKER
The properties, model and rev.# are the same. Only the serial numbers vary.
Then, that begs question #3: Is the drive failing, the backplane, firmware flaking out, or other issue happening?
Or, does the drive need to be pulled and re-seated?
Might be a good time to have a chat with their support.
Or, does the drive need to be pulled and re-seated?
Might be a good time to have a chat with their support.
ASKER
There are no errors at all. Just a different speed listed for that drive. I think Andy answered the primary part of that question. The speed probably doesn't make any difference.
ASKER
I'll wait to see if it's automatically "undiscovered". I'm still not sure how it remains "discovered" since the server has been powered off for a day now. Oh well. Thanks for the insight on the disk speeds. All is running well, so I won't mess with it.
It seems to me that there is more going on here than meets the eye. Flaky behaviours are an indication of a problem or problems.
ASKER
Flaky is a relative term. We've got four seemingly identical disks in a RAID 5. There has never been any degradation or data loss. No apparent slowness, lagging, etc. This RAID has been up 24/7 for probably 3 years. Attached are screen shots of each disk. The only noticeable difference is VDISK2, which you can see shows "3" as the speed instead of "6", like the others.
A relative term indeed. :)
Certainly that disk shouldn't be clocked down to 3Gb, probably negotiated the speed wrong at power on. It's disk2, not vdisk2 by the way - it says vdisk in the graphic because it is assigned to a vdisk. Seems to be a lot of unused disks, can I have a couple of them ;)
ASKER
We had an on-prem Exchange server using 10 more of them until recently :-)