Windows 2000 boot-up stops 1

[Jasonchatham]

When I power up Windows 2000 fails to boot.
On the boot up screen where you can press F8 for advanced options the bar moves about 2 inches and then the message comes up ;

"windows 200 could not start because the following file is missing or corrupt"
"\winnt\system32\config\system"

Booted from the windows 2000 install disk and selected Recover.
The automatic recover couldn't find a W2000 installation
The manual recover couldn't find a W2000 installation
The recovery console wouldnt LOGON to the install

I can see the OS and the data files using DIR but cannot access them.

Any help would be appreciated

 

[wolluf]

'I can see the OS and the data files using DIR but cannot access them' - does this mean its fat32 filestore and you can boot from 98 boot floppy?

See but can't access - so you can't for example copy file to/from the hard drive?

Have you access to another machine (preferably running 2k/XP). If so, could try installing drive as slave and running chkdsk on it. Could also try replace the
\winnt\system32\config\system with \winnt\system32\config\system.alt (after backing up original of course).

Could also try the drive manufacturer's diagnostic utility (probably on their website).

btw - some history on how/when this problem started (eg, any hardware/software changes, crashed, virus etc beforehand) would be useful.

 

[Jasonchatham]

I think its an NTFS partition.
When in recovery console mode, I can use the dir command.
But, it will not allow me to Change in to a directory.

"Access is denied"

Also, it will not allow me to copy files from the winnt directory to another location. (or other directories).
c:\ allows me to create and copy files

I have access to another PC running windows 2000.

User not sure if opened or agreed to any files being run. Although its sat on a very unprotected workgroup with broadband access through a W98 machine!

 

[wolluf]

ok - didn't understand, thought you couldn't get into recovery console. From recovery console you should have access to root of C: and C:\Winnt and all subfolders. You should also be able to run chkdsk. So, I'd try running chkdsk, then reboot & see if ok (assuming chkdsk finds anything to fix). If no good, go back to recovery console & see if it will let you do this (it should do)

copy \winnt\system32\config\system \winnt\system32\config\system.bak

copy \winnt\system32\config\system.alt \winnt\system32\config\system

Then try booting normally again.

http://support.microsoft.com/default.aspx?scid=kb;en-us;229716

 

[Jasonchatham]

Thanks for this help wolluf

When I choose the Recovery console option the machine changes to a cmd type screen at c:
I get no choice about which windows to repair.

The logon command does not work(I dont think anyway)

I cannot copy any files to or from the Winnt DIR "access is denied"

 

[wolluf]

It sounds like you have some system corruption if recovery console not loading properly (so presumably can't run chkdsk?). Try the slave in another machine approach (and as well as chkdsk, I'd run a virus checker). There may be problems with more than just the file mentioned (which is one of the registry hives). You could also check the contents of the \winnt\system32\config folder against the one on the machine you're slaving to, to see if any files missing.

 

[Jasonchatham]

Wolluf

I have successfully placed the drive into another w2000 machine.

Currently running a virus scan on the drive.
Its seeing all the data etc.

will run chkdsk next.

do I now attempt to copy the files you mentioned earlier ?

thanks

 

[wolluf]

If chkdsk finds anything to fix, I'd try it without copying anything first. Otherwise or if no good - do the copy.

PS. Have you created an ERD for this machine - and if so, did you do a regsitry backup too? (I ask, as there are potentially 2 more copies of that 'system' file - one made when 2k first installed - not usually advisable to restore - and one from last time ERD/reg backup done. This can be ok to restore if recent enough. Locations are \WINNT\repair\system (original) and \WINNT\repair\RegBack\system (reg backup).

 

[Jasonchatham]

No ERD made as far as i know - therefore no reg backup

Virus scan has found nothing - going for a second pass.

Do you run chkdsk from the command line - if so what switches should i use ??

 

[wolluf]

chkdsk /f ?

 

[Jasonchatham]

OK - CHKDSK g: /f

STAGE 1
File record segment is unreachable 28 is unreachable
ditto 29, 30, 31, 2152, .... (24 in total)

STAGE 2
Deleting index entry "drivers" in index $130 of file 26
.... (27 others)

STAGE 3
Recovering orphaned file "MYDOCU~1.MYD" into directory file 6307 ..... (13 others)

anything else here for help ?

 

[Jasonchatham]

Wolluf

Now I can access all the folders and drives which ones would you recommend replacing or should I just try a reboot on the drive now ?

I've copied all the users data from the drive as a precaution

many many thanks for today

 

[Jasonchatham]

OK

Tried reboot after chkdsk - still no good

Tried renaming the system file and got "cyclic reduncy check" error.

move it to the recycle bin

renamed system.alt to system
(it had same time and date stamp as the system)
rebooted machine - still same error

shall I copy system from winnt\repair

 

[wolluf]

As I said - version there is from original install of machine - it may or may 'work' (ie, boot machine) - but certainbly wouldn't be 'right'.


Your chkdsk didn't sound good - could the disk be damaged? (could try /r on chkdsk too to look for bad sectors). I'd be inclined to get hold of drive manufacturer's diagnostic from their website too. I'd definitely want to check out status of the drive before continuing (you've got user data off - which is good).

 

[Jasonchatham]

The system file from the winnt\repair has let the machine go further although now it cant find pci.sys from the config dir.

Its a maxtor drive I will look for their diag tool.

It does look like the disk has been damaged in some way from the chkdsk report doesnt it

 

[Jasonchatham]

wolluf

Many thanks for all your help today,
Its good to know your not alone and others are willing to help.

Maxtor diags confirmed drive is failing.
I did manage to reboot the machine by copying the entire drivers dir to the system32 folder! but its gonna fail so I will replace it under Maxtors warranty program.

Once again THANKS.

 

[wolluf]

glad you caught it without losing your data