Can't recover from bad NTFS unmount (post crash)
mechp...@gmail.com
will BSOD upon reboot before it gets to the Windows splash screen.
"Load last good configuration" changes nothing.
In safe mode it scrolls a page of drivers before it BSOD.
The message is:
PROCESS1_INITIALIZATION_FAILED
...
STOP: 0x0000006B ...
From everything I can find, this is a messed up unmount problem.
When I load Knoppix and try to access the drive, it tells me it has to
"force a dirty mount," but I can still access the data.
fdisk -l tells me that "partition does not end on cylinder boundary".
With the Partition Magic 8 boot disk, it tells me the partition has
several:
Error, Number 1608, File record marked used, File [file number]
then after chkdsk /r, it comes up with a 1516 error.
I used repair console to chkdsk /r a couple of times, and Partition
Magic actually no longer detects a problem!
Except...it's still BSODing when trying to boot up.
Any ideas or suggestions what to do?
Thanks!
-Liam
Rod Speed
Thats what backups are for.
If are stupid enough to not have backed up what you care about losing,
does the knoppix mount allow you to copy off what you need to recover ?
If not, try a decent recovery app. I like easy recovery pro,
but it aint cheap if you have to pay for it.
mechp...@gmail.com
I no stupid enough: *g* I do have a backup of all the info.
I spent two days last week reinstalling Windows and whatnot on this
machine and I'd really like to avoid having to repartition and format
the drive and start all over if there's some way around it.
I don't know if they would do any good in this case, but something
like FIXMBR or FIXBOOT.
If there is nothing that can make the drive boot into Windows again,
then I'll do what I have to, but I like to see if I have options.
Rod Speed
Then why did you ask the original question ?
> I spent two days last week reinstalling Windows and whatnot on this machine
If you had done the backups properly, it would only take 30 mins at most.
> and I'd really like to avoid having to repartition and format
> the drive and start all over if there's some way around it.
There is, work out where the hardware problem is, fix that, and do the backups properly,
a full physical drive image to an external hard drive with something like True Image.
> I don't know if they would do any good in this case, but something like FIXMBR or FIXBOOT.
Those only fix a very trivial subset of what gets corrupted and wont
do a damned thing about the hardware problem that system has.
> If there is nothing that can make the drive boot into Windows again,
> then I'll do what I have to, but I like to see if I have options.
Most likely the hard drive is dying. Post the Everest SMART report on the drive.
http://www.majorgeeks.com/download.php?det=4181
Michael Hawes
"Rod Speed" <rod.sp...@gmail.com> wrote in message
news:5vku4tF...@mid.individual.net...
suitable option to repair file system.
Mike.
mechp...@gmail.com
<michael.hawes1rem...@tiscali.co.uk> wrote:
> "Rod Speed" <rod.speed....@gmail.com> wrote in message
>
> news:5vku4tF...@mid.individual.net...
>
> > mechphi...@gmail.com wrote
Yep, like I said in my original post, I did that.
Several times in fact.
Thanks,
Liam
Rod Speed
> Rod Speed <rod.sp...@gmail.com> wrote
Pointless if the drive is dying and thats very likely.
Stupid to be ignoring what produced the corruption in the
first place and just closing your eyes and hoping for the best.
Eric Gisin
Try copying ntoskrnl, hal.dll, atapi.sys, from XP SP2 CD or working computer.
If that doesn't work, a repair install will fix it but takes longer.
<mechp...@gmail.com> wrote in message
news:13e5bbc6-97bb-4e39...@v4g2000hsf.googlegroups.com...
mechp...@gmail.com
I did the copy, and ntfs.sys (after copying those files you mentioned,
safe mode prompted me a new message that ntfs.sys was corrupt), but it
still BSOD at bootup.
=(
Unfortunately, repair (not repair console, but repair the installed
OS) is for some reason not an option.
Thanks for replying. =)
On Jan 22, 3:25 pm, "Eric Gisin" <gi...@uniserve.com> wrote:
> You have corruption of a kernel file (one listed during safe mode boot).
> Try copying ntoskrnl, hal.dll, atapi.sys, from XP SP2 CD or working computer.
> If that doesn't work, a repair install will fix it but takes longer.
>
> <mechphi...@gmail.com> wrote in message
Michael Cecil
>Darn it, you gave me hope. =)
>I did the copy, and ntfs.sys (after copying those files you mentioned,
>safe mode prompted me a new message that ntfs.sys was corrupt), but it
>still BSOD at bootup.
>=(
>Unfortunately, repair (not repair console, but repair the installed
>OS) is for some reason not an option.
>Thanks for replying. =)
Exactly, it's not an option. In other words, the screen doesn't offer
that. What people mean when they say to do a repair install is just to do
a regular install on top of the existing install.
I had a machine a short while ago that had a similar problem where I
didn't have access to the installation media so what I ended up trying was
doing a binary compare between the windows, system 32 and drivers folder
and the backup files in the dllcache folder. I copied over the files from
the dllcache folder to the other locations as needed. Then I booted up
the system and re-ran windowsupdate, and finally ran sfc /scannow.
--
Michael Cecil
http://macecil.googlepages.com/index.htm
http://macecil.googlepages.com/safehex.htm
http://macecil.googlepages.com/hackingvista.htm
Chuck Norris: Afraid of NOTHING, except John McCain's 95 year-old mother