• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 911
  • Last Modified:

Poweredge 2800

After NVRAM clear the BIOS setup came back with RAID "off" and the server can not boot to Windows. Unfortunately no record of original settings (SCSI only is not working, so it's RAID)
Is there a way to find out and change the setup to the correct RAID (and embedded RAID) settings? Can it cause (more) serious problem to simply set RAID "on"?
Can it be done with PERC? What exactly (what else) saved in NVRAM?
0
TSA888
Asked:
TSA888
  • 4
  • 3
1 Solution
 
PowerEdgeTechIT ConsultantCommented:
Boot to BIOS Setup (F2), Embedded Devices, and set Integrated RAID to RAID Enabled.  You will be greeted with a scary data loss message ... if it was in RAID mode before clearing the NVRAM, then there will be no data loss simply making the switch back.

When clearing the NVRAM, all BIOS settings are reverted to their defaults, which is SCSI Enabled (not RAID).
0
 
TSA888Author Commented:
Thanks.

Is enough to enable RAID. Isn't it necessary to give which type of RAID? (The server has 3 HDD-s)
Is there a way to find out which RAID would be the correct one (e.g. with PERC)?
I still worrying a little bit to cause real data loss by choosing the wrong type of RAID config.
0
 
PowerEdgeTechIT ConsultantCommented:
"Isn't it necessary to give which type of RAID?"

No, once enabled, the RAID controller should already "know" the configuration.  If not, then you are in trouble and will need to attempt to recover it, but that is not common in this situation.  In order to recover, YOU would need to know the exact specifications of the RAID array - or guess.

Maybe we should be asking:  WHY did you clear the NVRAM?
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
TSA888Author Commented:
Wanted to add plus memory, but it was not recognized. Silly me, accepted a 'wise' advice from a forum to clear the NVRAM (no alert for loosing other settings than the memory... not even in Dell documents...)

More info:
On this server the setting went back to "off". With SCSI it starts to recognize the drives, but then does not boot and steps to DHCP and try to boot from there...
That's why I thought it was in RAID. (By the way, the NVRAM jumper is on "default")

I found something about Boot Time BIOS Options - BIOS Configuration Autoselection - Use this option so that if there is a mismatch between the configuration data on the hard drives and that on the NVRAM during the boot process, you can select a method to resolve it. The options are NVRAM, Disk, or User (the default).

Would it help or just stay with your advice and enable RAID?
Sorry to be worried. I know, if I was brave enough to clear the NVRAM, then I should be brave to do as you're advising me... :)
Anything else should be changed back?  konow in Boot sequence the Hard Drive (RAID) should be the first one (at the moment obviously no Hard Drive in the list).
0
 
PowerEdgeTechIT ConsultantCommented:
"Silly me, accepted a 'wise' advice from a forum to clear the NVRAM (no alert for loosing other settings than the memory... not even in Dell documents...)"

Clearing the NVRAM by itself is not bad - it has its place - you just have to understand that it clears the BIOS hardware configuration, forcing it to rebuild on the next boot.  It can help random/odd hardware issues where the BIOS' prejudice for the hardware prevents it from accepting a change.  All BIOS defaults are restored.  This is NOT the same as NVRAM on the controller!

The reason I asked 'why' is perhaps you had a previous problem you were trying to fix for which clearing the NVRAM was not a potential fix (lost RAID configuration, failing drives, etc.) ... just wanted to make sure we ever had a hope of getting this to work.

If you are still getting the NVRAM jumper installed message during POST, then return the jumper to its original position, then boot to BIOS and make the change to RAID Enabled, then 'Y' to accept the change.

If during POST - when the controller starts up - you are getting an NVRAM Mismatch error, then you need to accept the configuration.  Boot to the CTRL-M utility, Configure, View/Add, then save the configuration on exit.
0
 
TSA888Author Commented:
Thanks. This gives some hope. I will let you know, if the problem solved.
0
 
TSA888Author Commented:
Thank you.
The server (up and running again) actually was configured RAID0
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

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