RE: Recovery Problems
- From: KingJ <KingJ@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 29 Apr 2007 13:50:01 -0700
Hi,
I tried this on two different machines, the original one which failed
(dosen't appear to be a hardware failiure, windows install messed up). Both
gave the HAL and NTFS errors.
However, since posting I retried a repair operation on the computer without
identical hardware and as I write this it appears to be going through the GUI
portion of setup, with 24 mins remaining. I'm using an old computer i've dug
out. Hopefully, I can replicate all of the AD stuff to the one that failed?
I've managed to get the failed one to the normal windows 2k3 setup, just
needs to be joined to domain, services installed etc.
When restoring the backups, I used the same name ("server") but left it in
the normal workgroup ("WORKGROUP").
I'm hoping that the install will successfully complete, and then I can
replicate it. Are there any guides to setting up replication? Not something
i've done before.
"johnsanz" wrote:
Something is not adding up... Did you change Hardware? For you to get the.
HAL errors, the backup you're trying to restore must have been taken from a
system with different hardware...
Try this:
1. Reinstall Windows and patch to same SP/Hotfix level as your last backup.
2. Make sure the computer name is the same as in your last backup.
3. Run DCPromo on it and promote it into a new domain/forest with the exact
same NetBIOS and DNS Domain Name as in your last backup.
4. Reboot into DS Restore Mode and then follow steps 4-11 under "Moving a
Windows domain controller installation" in the following KB article to
restore SYSTEM STATE (make sure the NTDS folder is included).
How to move a Windows installation to different hardware
http://support.microsoft.com/kb/249694/en-us
John
"KingJ" wrote:
Hi,
DC Server (which also does Exchange, Files, Print, WWW, SQL etc) went very
wrong (errors with RPC) and I was unable to fix. Therefore, I decided to
start from scratch and use my backups to restore the system state and
exchange data, which had been backued up nightly onto an external hard drive
using Symantec Backup Exec 11d. Anyway, I reinstalled server 2003, installed
some drivers, Service Pack 2 and Backup Exec 11d. I then rebooted into
directory restore mode and restored the system state data from my backup and
rebooted when done. When it rebooted, it gave an error about HAL, refering to
KB263532 I performed a repair operation, which completed successfully until
it rebooted. The computer rebooted, showed windows loading screen and froze
after a while (the blips had gone across the screen serveral times). I left
it for 10 mins, nothing happened so I rebooted it and tried to start in safe
mode. Now, it loaded ok until drvmain.sdb whereupon it crashed and restarted
the system. When trying to load windows at the restart it reports that it
could not start since system32\drivers\ntfs.sys is corrupt. I've tried
repairing again and copying the file from the CD using the recovery console
to fix this but nothing works. This has happened twice on two completely
different computers, including one with an idential configuration to the one
the system state data came from.
If anyone could help it would be greatly appreciated, I cannot afford the
offical microsoft support and restarting from scratch isn't really an option.
I need to fix this from the backups of the system state that i've got!
- Follow-Ups:
- RE: Recovery Problems
- From: KingJ
- RE: Recovery Problems
- Prev by Date: Re: My Network Places basics
- Next by Date: Re: Lists of Active Directory Consultants
- Previous by thread: Re: dfsutil /pktinfo shows wrong DC
- Next by thread: RE: Recovery Problems
- Index(es):
Relevant Pages
|