Directory enumeration error while fixing File Missing or Corrupt error

  • Thread starter Thread starter T.D. Hilton
  • Start date Start date
T

T.D. Hilton

Hello All,

I've got a server running Windows 2000 Svr SP3. I came in this morning to
find the following error on my screen:

"Windows 2000 could not start because the following file is missing or
corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEMced"

BTW, I know the 'ced' isn't associated with the actual error message.

Anyway, I found a MS article describing how to resolve this problem, but
upon booting the server using the boot floppies and going into the Recovery
Console, I'm unable to see any directories or files and get the following
error:

"An error occurred during directory enumeration".

I'm hoping an praying that I won't have to reformat the entire drive array
from scratch. I've seen documents on various support sites suggesting
running "CHKDSK c: /r" on the drive to repair any bad sectors and hopefully
allowing me to continue with resolving the origional issue. I've also seen
mention that I can simply reinstall Windows 2000 Server and it will
fix/replace the corrupt or missing file(s) and all will be fine. I'm not
willing to take such a chance without hearing from a MS expert.

What do you all recommend in this situation? I thank you all in advance for
your help!

Troy
(e-mail address removed)
 
T.D. Hilton said:
Hello All,

I've got a server running Windows 2000 Svr SP3. I came in this morning to
find the following error on my screen:

"Windows 2000 could not start because the following file is missing or
corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEMced"

BTW, I know the 'ced' isn't associated with the actual error message.

Anyway, I found a MS article describing how to resolve this problem, but
upon booting the server using the boot floppies and going into the Recovery
Console, I'm unable to see any directories or files and get the following
error:

"An error occurred during directory enumeration".

I'm hoping an praying that I won't have to reformat the entire drive array
from scratch. I've seen documents on various support sites suggesting
running "CHKDSK c: /r" on the drive to repair any bad sectors and hopefully
allowing me to continue with resolving the origional issue. I've also seen
mention that I can simply reinstall Windows 2000 Server and it will
fix/replace the corrupt or missing file(s) and all will be fine. I'm not
willing to take such a chance without hearing from a MS expert.

What do you all recommend in this situation? I thank you all in advance for
your help!

Troy
(e-mail address removed)
Click to expand...

As a first measure I would temporarily install the problem disk
as a slave disk in some Win2000/XP PC to check if the file
system is readable.
 
Hello All,
As a first measure I would temporarily install the problem disk
as a slave disk in some Win2000/XP PC to check if the file
system is readable.
Click to expand...

I can't as this is a server w/ 3x9.1G drives (RAID5).

Troy
 
T.D. Hilton said:
I can't as this is a server w/ 3x9.1G drives (RAID5).

Troy
Click to expand...

In that case I would boot the machine with my trusty
Bart PE boot CD (www.bootdisk.com). The tools to make
one are free but there are some prerequisites:
- A CD burner
- A WinXP Professional CD (but no licence number)
- About three hours of your time

It would give you the equivalent of a WinXP Command
Prompt, with full access to your NTFS disk (if it is in
any way readable). It would also give you access to
an external USB hard disk if you wanted to salvage
some files or folders.
 
Hello All,
In that case I would boot the machine with my trusty
Bart PE boot CD (www.bootdisk.com). The tools to make
one are free but there are some prerequisites:
- A CD burner
- A WinXP Professional CD (but no licence number)
- About three hours of your time

It would give you the equivalent of a WinXP Command
Prompt, with full access to your NTFS disk (if it is in
any way readable). It would also give you access to
an external USB hard disk if you wanted to salvage
some files or folders.
Click to expand...

In other words, the system files are hosed and hte best I can hope to do it
to try and salvage whatever files I can, right?
 
T.D. Hilton said:
In other words, the system files are hosed and hte best I can hope to do it
to try and salvage whatever files I can, right?
Click to expand...

I can't say. From your posts I note that there are some
problems that prevent your machine from booting. I cannot
tell whether you have some corrupted system files or whether
your file system is hosed. That's why I would "seek a second
opinion", in the form of an independent OS. A quick way
of achieving this would be to boot the machine with a
Win98 boot disk from www.bootdisk.com, then to run
ntfsdos.exe from www.sysinternals.com to access your
NTFS volume. If unable to access your file system then
your disk is probably beyond repair.
 
Hello All,
I can't say. From your posts I note that there are some
problems that prevent your machine from booting. I cannot
tell whether you have some corrupted system files or whether
your file system is hosed. That's why I would "seek a second
opinion", in the form of an independent OS. A quick way
of achieving this would be to boot the machine with a
Win98 boot disk from www.bootdisk.com, then to run
ntfsdos.exe from www.sysinternals.com to access your
NTFS volume. If unable to access your file system then
your disk is probably beyond repair.
Click to expand...

Well, while waiting for a response I ran a "chkdsk c: /r" and now I am able
to see the c: directory. There were several errors that were repaired. I'm
still unable to boot and get the same error referring to a missing or
corrupt SYSTEM file. There may be hope yet for this system.

Troy
 
T.D. Hilton said:
Well, while waiting for a response I ran a "chkdsk c: /r" and now I am able
to see the c: directory. There were several errors that were repaired. I'm
still unable to boot and get the same error referring to a missing or
corrupt SYSTEM file. There may be hope yet for this system.

Troy
Click to expand...

When you get access to the hard disk, try replacing SYSTEM
with SYSTEM.ALT.
 
to

When you get access to the hard disk, try replacing SYSTEM
with SYSTEM.ALT.
Click to expand...

Hey Pegasus,

I replaced the SYSTEM file with one from my ERD. Now when I boot I get to
the colored Windows 2000 Server screen, then I get a blue screen:
Inaccessible Boot Device. Should I still try using the SYSTEM.ALT file or
should I try the a mdrfix commend? I'm trying to do whatever I can to save
my data.

Troy
 
T.D. Hilton said:
Hey Pegasus,

I replaced the SYSTEM file with one from my ERD. Now when I boot I get to
the colored Windows 2000 Server screen, then I get a blue screen:
Inaccessible Boot Device. Should I still try using the SYSTEM.ALT file or
should I try the a mdrfix commend? I'm trying to do whatever I can to save
my data.

Troy
Click to expand...

Using system.alt is a safe and often successful method.
To save your data, use one of the methods I described
earlier:
- Slave disk
- Bart PE boot CD
 
As a first measure I would temporarily install the problem
Using system.alt is a safe and often successful method.
To save your data, use one of the methods I described
earlier:
- Slave disk
- Bart PE boot CD
Click to expand...

Pegasus,

Well, I've learned a few things through all of this. While I was not able to
resolve my bluse screen error I was able to recover my data from my drive
array by pulling the RAID drives and installing a single hard drive, to
which I install Windows 2000 Server. I then shutdown and added the origional
RAID drives. Upon reboot I was able to view my drives and copy off all my
data.

Thanks for all your help!

Troy
 
Back
Top