[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2018
  • Last Modified:

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


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
DrewBryant1961
Asked:
DrewBryant1961
  • 3
  • 2
1 Solution
 
BembiCEOCommented:
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
 
DrewBryant1961Author Commented:

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
 
BembiCEOCommented:
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
 
DrewBryant1961Author Commented:

A low level format of the drives resolved the issue.
0
 
BembiCEOCommented:
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

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now