Win2KAS - Can't Login After Drive Failure

[Brian D. McGrew]

Good morning,

Have a whitebox Win2KAS machine that has a single 60GB drive for boot/system
and a 250GB drive for data storage. The later drive failed and has been
replaced. Upon boot after replacing the drive I can no longer login to the
server.

If I hit the machine with Remote Desktop (as I usually) do or if I login
from the console I get the usual Windows is Loading your Personal Settings
immediately followed by Saving Your Personal Settings and I'm back to a
CTRL-ALT-DEL screen again. The same thing happens booting the machine in
safe mode.

What do I do to get around this? I can't login under my user account or the
administrator account? Anyone know what I can do?

TIA,

-b

 

[Pegasus \(MVP\)]

Good morning,

Have a whitebox Win2KAS machine that has a single 60GB drive for boot/system
and a 250GB drive for data storage. The later drive failed and has been
replaced. Upon boot after replacing the drive I can no longer login to the
server.

If I hit the machine with Remote Desktop (as I usually) do or if I login
from the console I get the usual Windows is Loading your Personal Settings
immediately followed by Saving Your Personal Settings and I'm back to a
CTRL-ALT-DEL screen again. The same thing happens booting the machine in
safe mode.

What do I do to get around this? I can't login under my user account or the
administrator account? Anyone know what I can do?

TIA,

-b

Your problem is caused by an incorrect system drive letter.
In your case it's easily fixed:
1. Use psexec.exe (www.sysinternals.com) on some networked
PC to start a Command Prompt on the the problem server.
2. Make a note of the system drive letter, e.g. by typing this
command: set system. Let's assume it's E:.
3. While still on the networked machine, start regedit.
4. Open the server's registry.
5. Navigate to HKLM\SYSTEM\MountedDevices.
6. Rename \DosDevices\E: to DosDevices\C: (assuming
that C: is the correct system drive letter.
7. Reboot the server. Your should have no further problems.

 

[Guest]

It may only be a simple problem with cached profile. If you deleted the
cached profile then try again. other than that try rebuilding the profile by
renaming ntuser.dat on account, remember backup the desktop folder incase

hope you get to the bottom of it, let us know