Re: Ack! Power-outage, corrupted SATA Mirror

Tech-Archive recommends: Fix windows errors by optimizing your registry




"Xandros" <Xandros@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F03A98D-715D-48F6-BC4F-8278F2081178@xxxxxxxxxxxxxxxx
Hi all,

I'm just looking for a bit of insight into a problem that I am currently
facing...

A couple of days ago, we had a power outage and an LCS test server (Server
2003)running an SATA RAID1 (not on the UPS) came down hard. Upon booting
it
up, it would get through POST and just as it started to show the blinking
cursor at the top left of the screen, it would just go black and not go
any
further. I figured that the server must have been in the middle of
writing
data to the mirrrored drive when it came down and corrupted the second
drive.
I disconnected one drive and rebooted, hoping that it would be able to
boot
up off of just one drive... I got the customary notification that Windows
had not shut down properly and that it would check the drive for errors.
Of
course it did and when the drive got to the logon screen, an lsass.exe
system
error popped up and indicated the following:

"Security Accounts Manager initialization failed because of the follow
error: A device attached to the system is not functioning. Error status:
0xc0000001. Please click ok to shutdown this system and reboot into safe
mode, check the event log for more detailed information"

When I go into safe mode, I get the exact same error and have no option
boot
to acknowledge the error and reboot. I've researched this error and it
appears that the SAM no longer contains the credentials in order to be
able
to authenticate a logon to the server, therefore a corrupt registry?
When I try to boot off of the other drive, I get the following error:

"Windows could not start because the following file is missing or corrupt:
\Windows\system32\config\system"
Yet another indication of a corrupt registry?

Of course there is no backup of the System State data, so it's not
possible
to carry through with the recovery procedures as laid out by Microsoft...
or
is there a way?

Is it possible that the information is still recoverable? What if I
installed another OS on an IDE drive? Would it be possible to navigate
through to where this information is located, save it and then try to do
recover the SAM as described in the following link?
http://support.microsoft.com/?kbid=316751
Which of course appears to only apply to WindowsXP Pro and 2000...

I suspect that I am facing a re-install, however any helpful tips would be
greatly appreciated!

Thanks!

I would disconnect the main disk and attempt to boot off
a floppy boot disk with the mirror hard disk:
- Format a floppy disk on some other Win2000/XP PC.
Don't do it on a Win9x PC - it won't work.
- Copy these files from the \i386 folder of your Server CD to A:\
ntldr
ntdetect.com
- Copy c:\boot.ini to the floppy disk.


.



Relevant Pages

  • Re: Help with Reinstalling...
    ... Install the new controller in a slot, boot the server and install the ... Do a FULL backup of your entire SBS 2003 server using the built-in SBS ... I took it out, broke mirror, replace disk set up new mirror ...
    (microsoft.public.windows.server.sbs)
  • Re: rebuild 240v from scratch
    ... >>> disk bootable, I would boot from it and dd from one disk to the other. ... >> of METADEVICE databases on server b. ... >> find a metadb on server B to resolve it to a physical partition. ...
    (comp.unix.solaris)
  • Re: Unable to boot to existing 2003 server
    ... Formatted a floppy using 2003 server. ... Could not read from selected boot disk. ...
    (microsoft.public.windows.server.general)
  • Re: sbs2003 and mirrored drive failure. Help!
    ... So they replaced sbs with server std and exchange. ... boot from Ghost 2003 CD or Ghost boot floppies ... Remove the shadow disk from the server and keep it in a safe place ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs2003 and mirrored drive failure. Help!
    ... Attach an external USB drive to the server ... boot from Ghost 2003 CD or Ghost boot floppies ... Remove the shadow disk from the server and keep it in a safe place ...
    (microsoft.public.windows.server.sbs)