Unsolved

This post is more than 5 years old

23 Posts

34198

February 16th, 2006 15:00

NVRAM mismatch -

Hi all,
I have  a dell PE 2300. I have 5 scsi drives. I have created one logical drive and configured it as Raid 5. Every time i do a restart to this server, it stops at this message
 
"Press a Key to Run configuration utility or to continue"
 
If i press any key i takes me to the Perc 2/sc bios and i can see the logical drive in the "View Disk Configuration" but i cann't see the logical drive in the "View NVRAM configuration" .
 
I think the NVRAM cann't save the logical disk information.
 
How can i fix this, PLEASE HELP ME.
 
 

777 Posts

February 17th, 2006 15:00

Hi Jenefa,

   First look at the objects physical drives and select each drive in turn and press F2 to look at detailed info on the drive, make sure you do not have any media or other errors listed on any of the drives. (if these are found, call Dell tech support, and make a backup of your data.)

  If all is good, then update the F/W on the controller, update the driver. Reboot.

  If error still there power down and disconnect the cable, power back up go in and clear the configuration, power down re-attach the cables power back up and go into configure, view configuration, it should ask you to view nvram or view disk. Selcet view disk, save the displayed configuration. exit and reboot into the BIOS and see if the nvram has the configration stored. If this does not work, you can try going to view configuration seeing the drives in a ready status, and tag them as the same array type that you had previously. DO NOT initialize the array. reboot see if the configuration is retained, and see if you can boot to the O/S. Call tech support if you need assistance with any of this.

 

 

2 Posts

March 8th, 2006 18:00

I had the same issue on a PE 4650. We applied the procedures and it seemed to work, but we still get the same issue when we reboot the server. Why would the NVRAM continuelly loose the logical drive information?

2 Posts

March 8th, 2006 19:00

Would this also cause the OS to hang intermittenly?

777 Posts

March 8th, 2006 19:00

Hi pedsds12,
 
  The answer is of course that you have a failure in the NVRAM circuit, give Dell a call and get it replaced, if you're under warranty, there will be no cost. If not under warranty, you can get the parts from our spare parts department, or have an out of warranty service call created for a tech to provide service to replace the defective controller.
 
  The procedure I gave, had you flash the controller BIOS in case that would fix a BIOS corruption issue.

777 Posts

March 8th, 2006 20:00

  Not too likely, unless you have more than one drive with media errors...and one or more of the errors overlap in the same data stripe on different drives.

  O/S lockups, could be caused by a number of different things, hardware , drivers, F/W or even software. to T/S this, look in the system event logs to see how often this has been happening, see if it's been a steady rate or with increasing frequency, review the application logs to see if there is a particular service, driver, or application related to the lockups. Check the IRQ allocations, Peseudo IRQ's (ones above 15) indicate that you have one or more shared IRQ's, I generally see issues only when the shared IRQ's are on high usage devices, like nicks and SCSI or RAID controllers.

  Some applications might have memory leaks that cause overuse of the page file to the point that 99% of it's I/O is directed to thrashing the page files. in this case the processor will still be active, the hard drives will be going flat out and the system may take 5 minutes to respond to a mouse click or pointer move.

  If you indeed have a hard lockup, see if the system responds to the power off button immediately, or if you have to press and hold the button for 10-15 seconds before it will power off. (That is the H/W power off circuit, means proc is not responding to anything) Reseat all the cables cards and procs...

  At some point if the lockups are fairly steady and often,  you'll want to eliminate S/W as a cause. Perform a parallel install and see if the problem persists on the new install.

0 events found

No Events found!

Top