- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Netservers
- >
- Re: LH4 & 3Si NVRAM & Disk Config Mismatch
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
Forums
Discussions
Discussions
Discussions
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
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
08-12-2002 07:14 AM
08-12-2002 07:14 AM
LH4 & 3Si NVRAM & Disk Config Mismatch
Got the above problem with an LH4 with a 3Si array controller. The controller is running 2 drives internal to LH4 and 6 drives in an expansion bay. All drives are 9Gb.
Tried the following, but to no avail:
1) Repalced 3Si array controller
2) Failed & "re-onlined" all drives
3) Tried to delete "wrong" config but not given the chance - we can only see 1 config!
Has anyone else seen this?
Help!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2002 08:29 AM
08-12-2002 08:29 AM
Re: LH4 & 3Si NVRAM & Disk Config Mismatch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2002 11:44 PM
08-12-2002 11:44 PM
Re: LH4 & 3Si NVRAM & Disk Config Mismatch
That's the problem - we are not getting offered alternative configs!
We can only see 1 config.
However, we have now fixed this issue using the following method - remember that we replaced the array controller in step 1 of my original post.
1) Powerdown server & external array and remove 1 disk
2) power up - if we get NVRAM mismatch issue power down replace drive and repeat step 1 with another drive.
3) Once we received an error other than NVRAM mismatch, replaced that drive (i.e. fitted a brand new drive) and manually rebuilt the array (from the ctrl-m setup)
4) job done
Very long winded and frankly "pants" when compared to Compaq!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2002 06:34 AM
08-13-2002 06:34 AM
Re: LH4 & 3Si NVRAM & Disk Config Mismatch
http://h20004.www2.hp.com/keeper_rnotes/bsdmatrix/matrix50450.html
Here is the link to the 3si controller updates:
http://h20004.www2.hp.com/keeper_rnotes/bsdmatrix/matrix62473.html
Also, HDD firmware is very important:
http://h20004.www2.hp.com/keeper_rnotes/bsdmatrix/matrix65146.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2003 12:25 PM
01-09-2003 12:25 PM
Re: LH4 & 3Si NVRAM & Disk Config Mismatch
We had a very similar problem this morning when we replaced some failing pieces of our raid array on an LH 6000.
We were getting an error message about an unmatched config between disk(s) and NVRAM, and only had one profile in the NetRaid utility too.
To get this going again, I did a new configuration (even though the current configuration looked correct) and redid the mirror sets. After exiting with the correct configuration, the system booted normally.
Creating a new profile with the correct logical disk arrays is definitely a quick way to fix this problem.
-Brian Spisak.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2003 12:34 PM
01-09-2003 12:34 PM