Re: Disk with NTDS failing
- From: Pallium <Pallium@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 12 May 2008 00:23:00 -0700
*Sigh*
Sadly, this is not going well.
When I try to restore from my backup, ntbackup says:
[Unrecognized Media]
The backup file contains unrecognized data and cannot be used.
The backup file is 75.8 GB. I have used a commercial utility, BKFRepair, to
look at the .bkf file and that utility can see all the files and folders
inside.
I have searched a bit on this, and some topics have suggested:
1) moving the .bkf file to a local disk (it was on a USB disk. Tried it - no
change)
2) changing permissions so Admins & Backup Operators have full control (did
it - no change)
Suggestions as to how to perform my system state restore?
(I'm getting desperate. It has been 48 hours now, so I'm officially losing
mail.)
-Bryan
"Cliff Galiher" wrote:
If you have a backup, I'd use it. Repairing a corrupt AD is time-consuming,.
error-prone, and not always effective even if you survive the minefields.
As long as you *just* restore the system-state, you won't lose email. What
you may lose, or what may cause you problems:
1) Any programs you've installed since the last system-state backup. They
add things to the registry, and the registry will be reverted. Usually this
means re-installing programs, but in some rare cases can actually cause
instability if the registry was referencing system-level dlls.
2) Any account additions/deletions/changes. If you added users, computers,
or passwords were changed, those changes are gone.
3) Group policy changes. See above.
I'd also bump up the frequency of system-state backups from now on. I know,
hindsight is 20/20, but in the SHORT time I've spent in this newsgroup, I am
genuinely stunned at how often I've seen messages from people with *NO*
backups. If yours is a month old, you seem to be on the winning side of
things. :)
-Cliff
"Pallium" <Pallium@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C914B4B3-5D3D-4636-9459-B9EE92DF1912@xxxxxxxxxxxxxxxx
Thanks Cliff this is good stuff.
The procedure outlined in that KB article assumes you can get AD to start.
For instance, the procedure has you running Ldp.exe. I can only get into
my
server as local Admin - AD won't start if I boot up normally.
My boot drive is F: (A mirrored RAID volume). The failing drive is C:. I
have been able to copy C:\SysVol and C:\NTDS to another drive for
safekeeping.
But without being able to boot normally, I don't think I can do a proper
system state backup.
Your suggestion of "replace the disk and do a system-state restore" sounds
promising. Admittedly, I know little about AD - I know it keeps track of
domains, computers, users, etc. In my case, those things are simple and
static. So I hope that restoring from a month-old backup won't cause too
many
problems.
What I *don't* want is to overwrite my mail and all that other stuff. And
I've never tried a restore from one of these SBS backups. Can you restore
the
"system state" without losing mail, etc?
I clearly do have some corruption - I can't get lsass.exe to start on
normal
boots. When you said "need to do some repairs," can you be more specific?
How
do I do those repairs? If I can do some repairs and get the thing to boot
normally, I could do the SysVol move procedure outlined in that KB
article.
Thanks again for your help Cliff.
-Bryan
"Cliff Galiher" wrote:
You can try moving sysvol with this procedure:
http://support.microsoft.com/kb/842162
But you will also likely need to do some repairs since it sounds as
though
you already have corruption. Worst case, you may have to replace the
disk
(assigning it the same drive letter), do a system-state restore, and
*then*
move sysvol...but with the disk replaced, moving it may no longer be
necessary either.
Any which way, hope this helps, and good luck. Let me know if it works
out...
-Cliff
"Pallium" <Pallium@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D121E07-DB41-4F4E-9E06-D9F9D7E4E186@xxxxxxxxxxxxxxxx
Hi everyone,
I've got an SBS 2003 SP2 server. The disk on which NTDS resides (not
the
boot disk), is failing, and keeping lsass.exe from starting. I can boot
into
Directory Services Restore Mode, logged in as machine Admin.
My AD event log has events indicating that AD can't access its
database,
such as this (event ID 508)
NTDS (412) NTDSA: A request to write to the file "C:\NTDS\temp.edb" at
offset 172032 (0x000000000002a000) for 122880 (0x0001e000) bytes
succeeded,
but took an abnormally long time (122 seconds) to be serviced by the
OS.
This
problem is likely due to faulty hardware. Please contact your hardware
vendor
for further assistance diagnosing the problem.
SO:
How do I move directory services (x:\NTDS) to a different disk? Or if
that
is impossible, recreate it on another disk?
Thanks,
Bryan
- References:
- Disk with NTDS failing
- From: Pallium
- Re: Disk with NTDS failing
- From: Cliff Galiher
- Re: Disk with NTDS failing
- From: Pallium
- Re: Disk with NTDS failing
- From: Cliff Galiher
- Disk with NTDS failing
- Prev by Date: Re: SBS 2003 R2 Exchange/Outlook Licensing
- Next by Date: SBS 2008 wont require antivirus software ?
- Previous by thread: Re: Disk with NTDS failing
- Next by thread: RE: Disk with NTDS failing
- Index(es):
Relevant Pages
|
