Go Premium for a chance to win a PS4. Enter to Win

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

Environment Variables Changed After nVidia RAID Mirror Broke

I was doing a fan repair on a running IIS Server when I accidentally pulled the SATA cable off of one of two disks of an nVidia RAID. At first I didn't notice the cable was pulled and continued putting the cover on, and when I returned to the monitor for the server I noticed the web site had gone down.

After plugging the SATA cable back in and while rebooting the server, I noticed that both disks were marked as degraded by the nVidia console. When the server rebooted, everything seemed to be okay, other than the fact the mirror was now broken, but I later noticed that although the server was booting to the C Drive, many of the environment variables had been changed the the new I Drive on the now present "second" drive.

The original mirror had three partitions, C,D & E. Now I have two recognized drives with three partitions each, and the second drive has I,J, & K partitions. If I remove the second drive and try to reboot, I can't get past the logon screen, and every time I login it just reverts back to the "hit ctrl alt del" popup, however, if I boot with both drives I can log in, but can't connect to the domain controller.

All I want to do is get my environment variables back the way they were so I can eliminate the second drive and reinitialize the RAID configuration. Can I do this using the recovery console, or is there a better way?

Below is a list of my environment now, I just want "C" to replace "I". Thanks in advance for any help...

ALLUSERSPROFILE=I:\Documents and Settings\All Users
APPDATA=I:\Documents and Settings\Administrator\Application Data
CLIENTNAME=Console
ClusterLog=C:\WINDOWS\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=LISA
ComSpec=I:\WINDOWS\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=D:
HOMEPATH=\WWW
LOGONSERVER=\\LISA
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
Path=C:\imagemagick;;I:\WINDOWS\System32\Wbem;I:\WINDOWS;I:\WINDOWS\system32;C:\
Perl\bin;C:\Perl\site\bin;C:\Program Files\PHP\;C:\Program Files\Easy Software P
roducts\HTMLDOC\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PHPRC=C:\Program Files\PHP\
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 15 Stepping 11, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0f0b
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=Console
SystemDrive=I:
SystemRoot=I:\WINDOWS
TEMP=I:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
TMP=I:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
USERDOMAIN=LISA
USERNAME=Administrator
USERPROFILE=I:\Documents and Settings\Administrator
windir=I:\WINDOWS



0
W00T
Asked:
W00T
1 Solution
 
DavidCommented:
Let it finish doing the rebuild. shut it down, change boot path so that the other disk is primary (as it was before this happened), and then reboot.  It should go back the way it was before.
0
 
W00TAuthor Commented:
The drive I accidentally unplugged was the primary master, so when it rebooted, it set the secondary as the master. I didn't pick up on this fact until I changed the boot drive on the RAID BIOS and the OS Software recognized both drives again. The problem I had after that was that it saw each drive as a separate array and it still wouldn't see them as one drive in the hardware configuration. I just put in a new unformatted drive and everything worked again.

So the main problem was my stupidity in not checking which drive was the boot drive, which is basically what dlethe said to change back. I couldn't do the rebuild until AFTER setting the boot drive and inserting an unformatted secondary drive, however.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

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