NTOSKRNL problem + Bad NTFS Partiti
|
Original Message
|
Name: Chris
Date: October 8, 2002 at 11:57:07 Pacific
Subject: NTOSKRNL problem + Bad NTFS PartitiOS: Windows 2000CPU/Ram: 1Ghz/256mb |
Comment: The other day I went to reboot in Windows 200 and got the error message about the ntoskrnl.exe being bad and that I shoukd replace it. That didn't seem to be much of a problem because I figured I could just replace the file with another one. However my windows 2000 os is on an NTFS partition which can't be read by anything. It is showing up as an unformatted partition in partition magic and is completely inacessible. Using the demo copy of ntphoenix I can get to the files I need, but being a demo, it doesn't allow me to recover them. Anyone have any possible solutions?
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: Dan
Date: October 8, 2002 at 12:46:27 Pacific
|
Reply: (edit)It looks like you have only two other options... The first being that if you have a system with NT or 2k on it hook up the drive that has the bad ntoskrnl.exe as the slave and copy the file threw the other OS. The other Option is to create a parallel installation of 2k on your System and boot into the newer OS to copy the file over. The first option is what I have done in the past and it worked fine.
Report Offensive Follow Up For Removal
|
|
Response Number 2
|
Name: Chris
Date: October 8, 2002 at 15:13:24 Pacific
|
Reply: (edit)I tried installing another copy of Windows 2000 on a new NTFS partition and when I try to access the old partition it says the drive is unformatted. And when I try to run chckdsk /f on the drive it says the file system is RAW and it can't fix errors on that type of drive. Any ideas?
Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: Dan
Date: October 9, 2002 at 09:14:44 Pacific
|
Reply: (edit)Have you tried booting off the W2k disk and trying a repair, or booting into the recovery console? those might be next steps...That is very strange that W2k would recognize your other partition as a RAWFS. I have actually never heard of that before. If the repair does not go over well I would try installing NT over the top of the OS that is giving you problems, making sure to NOT format the drive and leave it intact. It will give you that option. Also I would install to a differnt directory than the default /WINNT, maybe to NTTEMP or something to that effect. Then you will be booting to the partition that holds the original corrupt NTOSKRNL file and you can replace it from there. Keep me posted.
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: trvlr
Date: October 9, 2002 at 11:21:59 Pacific
|
Reply: (edit)If a standard setup/repair routine doesn't resolve it for you perhaps... http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q153973 might be of help?
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: Chris
Date: October 9, 2002 at 12:47:43 Pacific
|
Reply: (edit)Okay . . . When I tried to install a new OS into the bad partition it wouldn't let me without formatting it because it sad it was bad or damaged, so I didn't do it. The recovery process didn't work either. The method posted by trvlr seems like it could work. The only problem is the only way I can get the bad partition to be assigned a drive letter is to boot into Windows 2000. I can't get a boot disk to boot into DOS and assign it a drive letter. So when I boot up and try to run diskedit I can't view the bad partition because it hasn't been assigned a drive letter. Understand, or am I too confusing? :-)
Report Offensive Follow Up For Removal
|
Use following form to reply to current message: