- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Critical Lock-up Detected. Code=f112h
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
тАО10-10-2009 07:27 PM
тАО10-10-2009 07:27 PM
- reseated fibre cables
- reseated controllers
and the problem still persists.
Pls advise.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2009 04:52 AM
тАО10-11-2009 04:52 AM
Re: Critical Lock-up Detected. Code=f112h
There were lot of fixes in f/w v5.20 or v7.00 whichever is applicable here.
F/w v4.48 release notes extract:
"Fixes an issue where the MSA1000 array controller could get a ├в Critical Lockup F112h├в
when inserting new disk drives or migrating disk drive from non smart array based SCSI
controllers"
Try reseating the affected controller as well
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2009 05:02 PM
тАО10-12-2009 05:02 PM
Re: Critical Lock-up Detected. Code=f112h
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2009 09:36 PM
тАО10-12-2009 09:36 PM
Re: Critical Lock-up Detected. Code=f112h
Upgrade firmware asap.
MSA will perform better and will be more stable.
You can do it step wise by going to 4.48 and then to 5.20.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-12-2009 11:47 PM
тАО10-12-2009 11:47 PM
Re: Critical Lock-up Detected. Code=f112h
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2009 01:46 AM
тАО10-13-2009 01:46 AM
Re: Critical Lock-up Detected. Code=f112h
But, I would still like to update the controllers to the latest version of active passive firmware which is more stable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2009 04:38 PM
тАО10-13-2009 04:38 PM
Re: Critical Lock-up Detected. Code=f112h
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2009 12:36 AM
тАО10-14-2009 12:36 AM
Re: Critical Lock-up Detected. Code=f112h
Maybe I missed something , Can any one else help Eric on this one?
KunalSahoo, any comments?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2009 02:08 AM
тАО10-14-2009 02:08 AM
Re: Critical Lock-up Detected. Code=f112h
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2009 04:30 PM
тАО10-14-2009 04:30 PM