Solved

Persistent Dell Perc 4e/di configuration of nvram and drive mismatch errors

Posted on 2009-05-07
5
1,979 Views
Last Modified: 2012-05-06

I have  a PE2800 with a Perc 4e/di RAID controller. System has 2 drives (RAID1) and I;m adding a second array with 3 more drives (RAID5).  The RAID 5 set are new drives.

I'm getting above error when the system boots so I cleared the configuration and redefined the arrays via easy config. I initialized the logical volumes and reboot with no issues however any subsequent reboot recreates the same nvram/drive mismatch.

I hope this does not indicate a failing controller.

How do I resolve this?
0
Comment
Question by:DrewBryant1961
  • 3
  • 2
5 Comments
 
LVL 35

Expert Comment

by:Bembi
ID: 24327522
Have you checked, if the boot order in BIOS (Board) has changed? I noticed that some Boards have the issue, that they just select the new device as boot device.
0
 

Author Comment

by:DrewBryant1961
ID: 24327729

The 2 older drives are in slot 0 and 1 in the backplane however this issue occurs even if I remove the 3 new drives and create a single RAID 1 array. Reboot a second time and the mismatch errors reoccur.

If you check things in the perc configuration manager, it will show various combinations of drives in a failed state even new drives with no partitions on them.
0
 
LVL 35

Accepted Solution

by:
Bembi earned 500 total points
ID: 24327875
OK, the message says, that the NVRAM (BIOS of the controller) has different information than these stored on the disk.

For solving this, have a look here, the controller has an option to sync the information:
http://www.cs.uwaterloo.ca/~brecht/servers/docs/PowerEdge-2600/en/Perc4di/UG/trouble.htm

Nevertheless, you should never just plug out devices and reconfigure them. As stated above, there are two information, one in the NVRAM and the other on the disk. Whenever you change the configuration, delete the configuration first within the controller BIOS and the remove the drives.

0
 

Author Comment

by:DrewBryant1961
ID: 24332389

A low level format of the drives resolved the issue.
0
 
LVL 35

Expert Comment

by:Bembi
ID: 24340439
You deleted the controller information on the drives during low level format. This solves the problem of course. Have a look if there is any option to save the configuration. Some controllers explicitely need this to write the configuration to the nvram.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

AWS Glacier is Amazons cheapest storage option and is their answer to a ‘Cold’ storage service.  Customers primarily use this service for archival purposes and storage of infrastructure backups.  Its unlimited storage potential and low storage cost …
Concerto Cloud Services, a provider of fully managed private, public and hybrid cloud solutions, announced today it was named to the 20 Coolest Cloud Infrastructure Vendors Of The 2017 Cloud  (http://www.concertocloud.com/about/in-the-news/2017/02/0…
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
This video teaches viewers how to encrypt an external drive that requires a password to read and edit the drive. All tasks are done in Disk Utility. Plug in the external drive you wish to encrypt: Make sure all previous data on the drive has been …

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question