- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Model 12H Problem
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
тАО07-10-2002 03:33 PM
тАО07-10-2002 03:33 PM
We are experiencing a problem on our Model 12H Array. Attached is a portion of our syslog.log file. We tried replacing the X&Y controllers (96MB each) , replaced the cables too and still having problems. One idea was to have the whole baclplane of the Model 12H replaced but somebody told us that
that the reason we're having this problem is because we have below 10% unallocated space left for LUN's. Any help or ideas about this problem will be very much appreciated. Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-10-2002 09:34 PM
тАО07-10-2002 09:34 PM
Re: Model 12H Problem
Having less that 10% unallocated is always bad, since, if this happens, the autoRAID will be migrating from Raid 0/1 to Raid 5 back and forth, yielding to severe performance problems.
Try increasing the free space by inserting a new drive in it. If the drive is bigger than the rest you have, you have to insert 2 such drives in order to obtain the full capacity of it. Otherwise, it would be seen the same size as the other drives.
Dunno whether this will help regarding your problem, but in any case, this should be done.
HTH,
Vince
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2002 06:04 AM
тАО07-11-2002 06:04 AM
Re: Model 12H Problem
I agree with Vincent. However, this problem may be related to a timeout due to longer I/O times becuase you have such a small amount of free space. It can also be cables, patches, termination, or disks. Please see the following:
http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000015663097
While this article relates to dmesg, the result is the same. Also, be sure that you have the latest level of firmware on both the controllers, HBA's, and disks as well as the latest SCSI patches. Do a search in the technical knowledge base on SCSI + lbolt and look at the patches for your O/S.
HTH,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2002 06:28 AM
тАО07-11-2002 06:28 AM
Re: Model 12H Problem
A possible source of the problem is missing resistor packs (or disabled termination by DIP switch) on both host controllers. Typically SCSI buses terminated on only one end will almost work well - the worst kind of problem. I would have your local HP Mr. Goodwrench come out and examine both SCSI controllers in your host computer. (You can pull these yourself, if you like).
I have seen AutoRAID's complete allocated and not exhibit this behavior so I very much doubt that this is your problem. The default timeout of 30 seconds is generally too short; I would immediately set it to 120 seconds (or so) for each LUN using pvchange. You received good advice about upgrading the firmware and don't forget the ARMserver and arraymgr software on the host.
If you still see problems after all this, I would have the backplane replaced.
One final thought - very noisy power.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2002 07:19 AM
тАО07-11-2002 07:19 AM
Re: Model 12H Problem
arraylog -d {slot_id} {array_id} for each disk installed on the array. Most notibly check the end of the report for the "Grown Defect List" This list should be nearly empty if not completely empty. If the list is too long, you might need to replace a disk in your array.
Good Luck.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2002 07:37 AM
тАО07-11-2002 07:37 AM
Re: Model 12H Problem
Thanks for the very swift reply. We had a number of HP guys in here already, when the controllers were replaced and when the power supplies and cables were replaced. Hp shipped us 2 36Gb drives last night and we swapped one in place of one 18 GB. This gave us more than 18Gb of unallocated space for the LUN's. It still gave us all the messages that I included in the syslog and the thing is it took the rebuild finished at around 8:00 this morning and balanced about 4 times already. It only showed ready status for about about 30 secs. and then went back to balancing. This happened 3 times already and right now it is still balancing. I already made a call to HP and it has been escalated already. Any thoughts about this will surely be appreciated. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-11-2002 10:18 AM
тАО07-11-2002 10:18 AM
Re: Model 12H Problem
We've also tried doing a pvchange to change the timeouts to 180 on each individual LUN's (disk device files) and it did not help.
We also did a patch tool with the hp CE's and they did not find anyhthing wrong with our patches, and that they are current too. We also checked the arraymgr and armserver software and they are current too. I will do the arraylog and see what happens. Again, thanks a lot to all of you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2002 12:44 AM
тАО07-12-2002 12:44 AM
Re: Model 12H Problem
what you're seeing is a symptom.
Get the autoraid logs via
logprint
(see the man)
Send the output to your hp rep.
He will load it in the AutoRAID log tool (which he gets from the wtec/lab) This tool will identify common problem.
I would suggest (backup lun) deleting a lun and recreating it. (restore backup)
Perf will increase after this.
Later,
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2002 04:36 AM
тАО07-12-2002 04:36 AM
Re: Model 12H Problem
Why do you think we should re-create the LUN's? Is that just to defrag the array? A CE from Hp will come in and change the backplane, the two SCSI cards, and upgrade the firmware on our Disks to HP04.
Do you think we re-create the LUN's before or after this process? Thanks again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-12-2002 09:26 AM
тАО07-12-2002 09:26 AM
SolutionThe autoraid looses its head if operating for a long time, the maps need to be 'refreshed'..
it's not as if the autoraid is really defragging, but the maps that are maintained in the controllers are more or less fragmented. The fragentation oif these causes perf problems at the controller level, especially when moving data around and calculating the free space for it... fragged up disks sure doesn't help either.
It'd do all my backups and just test it before pulling things apart. The backplane replacement is a long operations, only doo it if you see from log print that a certain disk is hot... ie lots of scsi retries - one screwy disk in the autoraid could mess the whole thing up... i think HP are trying to rule out the backplane before they ask you to replace every disk....
DO THE LOGPRINT!
Later,
Bill