- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- Re: msa1000 strangeness after upgrading to fw 4.48
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
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
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
тАО06-27-2006 02:21 PM
тАО06-27-2006 02:21 PM
Re: msa1000 strangeness after upgrading to fw 4.48
EMU
Backplane
MSA1000 Controller
Can all of these be replaced in one operation? Any thoughts about which is most likely the culprit?
Where is the array information stored? On the drives and on the controller, right? Is it possible to 'backup' this information somehow?
Thanks again for all the assistance.
RS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2006 03:31 PM
тАО06-27-2006 03:31 PM
Re: msa1000 strangeness after upgrading to fw 4.48
The EMU controls environmental status plus handles some drive events. Example hot remove and hot add.
Look at the show tech_support, your LUNs are not showing a drive fault of any kind. If you experience a drive fault, the would be line added to the faulty disk in your LUN.
Just as a safety precaution, locate the cpqacuxe.exe or hpacuxe.exe. At a cmd prompt, under the directory of the executible. issue the cmd.
cpqacuxe -c
This will capture your servers Array configuration plus the MSA's. The file created will be acucapt.ini
cpqacuxe -h will popup a help screen.
If needed you can edit out the embedded Smart Array configuration information, leaving the MSA information. execute, cpqacuxe -i acucapt.ini This will recreate your configuration back to the original state.
It's difficult to say exactly if it is the backplane or the EMU. The only thing I can think of on the backplane that could cause something like this is perhaps one of the resistors in a RNET, used for the SCSI terminators either opened or shorted with another resistor in the RNET.
Tomorrow I'll do a little more digging. I would be interested in capturing this equipment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 12:53 AM
тАО06-28-2006 12:53 AM
Re: msa1000 strangeness after upgrading to fw 4.48
This how I interpret that information. Several suggestions have been made to pull one of the affected drives and let the array rebuild. It doesn't seem that this is likely to be a solution. In fact, it seems that this could be counterproductive given the extremely long rebuild time (?? hours) when the overall hardware state is supspect.
I have backed up the array configuration information from all 4 servers accessing this SAN using a local instance of cpqacuexe.exe on each server. Can you give me the 10 cent rundown on how this might be useful in case something goes awry during the equipment swap?
>Tomorrow I'll do a little more digging. I >would be interested in capturing this >equipment.
Thanks. I would be interested in sending it to you. Do you or I have to do anything to redirect it from the normal process once the faulty hardware has been identified?
RS
PS Just to make sure I understand, say for instance we brought in a completely new MSA1000 and populated it with our current drives. Theoretically that would start up and be usable, right? Sorry for all the questions. I'm new to HP land (though customer service like this is making me glad I came over!)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 01:37 AM
тАО06-28-2006 01:37 AM
Re: msa1000 strangeness after upgrading to fw 4.48
Eventhough you have two drives with amber lights. Your system is still up and functional, yes?
If you do try the hot remove and insert, move your rebuild priority to medium or high.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 02:40 AM
тАО06-28-2006 02:40 AM
Re: msa1000 strangeness after upgrading to fw 4.48
I really don't want to pull a drive if we don't have to.
Regarding the theory of how the device operates, what would happen if I took all of those drives and put them into a different MSA1000? Would the array be retained? I'm not asking because I want a new MSA1000. I truly just want to understand how far the system is designed to go before losing the data.
Thanks,
RS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 04:56 AM
тАО06-28-2006 04:56 AM
Re: msa1000 strangeness after upgrading to fw 4.48
Any chance you pulled the controller and reinserted it. If so, could you have bent a pin.
If able, power down everything and pull the controller. Look at the backplane connector for bent pins or look at the controller connector for messed up holes.
Still stumped.
By having the RIS data on the drives you can take a LUN and move it to another Smart Array device and still perserve everything. There are some backwards compatibility with older SA controllers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 05:29 AM
тАО06-28-2006 05:29 AM
Re: msa1000 strangeness after upgrading to fw 4.48
>By having the RIS data on the drives you can take a LUN and move it to another Smart Array device and still perserve everything.
This is why I asked about the "Error occurred reading RIS copy" messages. Does this mean that the array information on the drives is corrupted? If that's the case, should the swap of the controller only be as a last resort?
Here is a snippet from the ADU report. The entire report is attached.
SLOT 2 (ID 65536) MSA1000 Array Controller ERROR REPORT:
Error occurred reading RIS copy from SCSI Port 1 Drive ID 0
Error occurred reading RIS copy from SCSI Port 1 Drive ID 1
Error occurred reading RIS copy from SCSI Port 1 Drive ID 2
Error occurred reading RIS copy from SCSI Port 1 Drive ID 3
Error occurred reading RIS copy from SCSI Port 1 Drive ID 4
Error occurred reading RIS copy from SCSI Port 1 Drive ID 8
Error occurred reading RIS copy from SCSI Port 1 Drive ID 13
Error occurred reading RIS copy from SCSI Port 2 Drive ID 0
Error occurred reading RIS copy from SCSI Port 2 Drive ID 1
Error occurred reading RIS copy from SCSI Port 2 Drive ID 2
Error occurred reading RIS copy from SCSI Port 2 Drive ID 3
Error occurred reading RIS copy from SCSI Port 2 Drive ID 4
Error occurred reading RIS copy from SCSI Port 2 Drive ID 8
Error occurred reading RIS copy from SCSI Port 2 Drive ID 13
What would make the RIS copy of each drive unreadable? Does this point to a specific piece of hardware such as the EMU?
Thanks for working so hard on this.
RS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 08:55 AM
тАО06-28-2006 08:55 AM
Re: msa1000 strangeness after upgrading to fw 4.48
Thanks,
RS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 09:43 AM
тАО06-28-2006 09:43 AM
Re: msa1000 strangeness after upgrading to fw 4.48
I've looked over the backplane schmetic. If it was a backplane issue, I would expect other problems. Especially accessing your LUNs.
Tell the FE, that I work in the MSA development. Myself and a FW engineer would like to get our hands on the faulty component.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 09:47 AM
тАО06-28-2006 09:47 AM
Re: msa1000 strangeness after upgrading to fw 4.48
The first thing he wants to try is to change the read/write cache distribution, so we'll do that then start on the hardware.
Wish us luck...
RS