|
Related Topics:
| How to recover better from the NEXT Firewire HDD repeating.. - Hi, "How to recover better from the NEXT Firewire HDD repeating NTFS Lazy Write The subject is my best guess as to how the messing up of my MAXTOR Firewire 200 Gig drive occurred. I do not have proof that it was the cause, but I have seen too..
How to recover a crashed laptop hard disk (windows NTFS) - Does anyone know of freeware which can diagnose & recognize an already crashed hard disk on an IBM laptop? My kid's IBM laptop hard disk (it had been making noise, he said). - The IBM laptop would not boot no matter what I tried - I put..
Recover from a format - Anything available to recover from an error - drive was formatted by mistake. HB
Recover almost overwritten files - I started to on a cd that I wanted to preserve. Realizing I had the wrong cd in the drive I cancelled the Now when the cd is placed in the drive, all that is seen is the two files I..
Need to recover jpg files from disc - My HD (FAT32, 30GB) crashed, and I lost access to many jpg files. The folders which contained pictures are present, but instead of jpg's there's only a junk in them, So I think, that directory structure is and files are I can..
|
|
|
Next: PC Storage: Maxtor ext hd error--corrupted or unreadable
|
| Author |
Message |
External

Since: Dec 06, 2007 Posts: 9
|
(Msg. 1) Posted: Mon Jan 21, 2008 11:31 am
Post subject: Can't recover from bad NTFS unmount (post crash) Archived from groups: comp>sys>ibm>pc>hardware>storage, others (more info?)
|
|
|
I have a PC I'm working on that crashed in Windows XP Pro, and since,
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 >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Dec 06, 2007 Posts: 9
|
(Msg. 2) Posted: Mon Jan 21, 2008 12:05 pm
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Jan 21, 1:52 pm, "Rod Speed" <rod.speed.....TakeThisOut@gmail.com> wrote:
> mechphi....TakeThisOut@gmail.com wrote:
> > I have a PC I'm working on that crashed in Windows XP Pro, and since,
> > 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?
>
> 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.
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. >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Feb 01, 2006 Posts: 1570
|
(Msg. 3) Posted: Tue Jan 22, 2008 6:52 am
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: comp>sys>ibm>pc>hardware>storage, others (more info?)
|
|
|
mechphisto.TakeThisOut@gmail.com wrote:
> I have a PC I'm working on that crashed in Windows XP Pro, and since,
> 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?
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. >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Dec 06, 2007 Posts: 9
|
(Msg. 4) Posted: Tue Jan 22, 2008 8:34 am
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: comp>sys>ibm>pc>hardware>storage, others (more info?)
|
|
|
On Jan 22, 6:50 am, "Michael Hawes"
<michael.hawes1rem....RemoveThis@tiscali.co.uk> wrote:
> "Rod Speed" <rod.speed.....RemoveThis@gmail.com> wrote in message
>
> news:5vku4tF1ls4uiU1@mid.individual.net...
>
> > mechphi....RemoveThis@gmail.com wrote
> >> Rod Speed <rod.speed.....RemoveThis@gmail.com> wrote
> >>> mechphi....RemoveThis@gmail.com wrote
>
> >>>> I have a PC I'm working on that crashed in Windows XP Pro, and
> >>>> since, 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?
>
> >>> 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.
>
> >> I no stupid enough: *g* I do have a backup of all the info.
>
> > 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
>
> Boot XP CD and get to Recovery console. Type CHKDSK /? and pick
> suitable option to repair file system.
>
> Mike.
Yep, like I said in my original post, I did that.
Several times in fact.
Thanks,
Liam >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Feb 01, 2006 Posts: 1570
|
(Msg. 5) Posted: Tue Jan 22, 2008 12:05 pm
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: comp>sys>ibm>pc>hardware>storage, others (more info?)
|
|
|
mechphisto.RemoveThis@gmail.com wrote
> Rod Speed <rod.speed.....RemoveThis@gmail.com> wrote
>> mechphi....RemoveThis@gmail.com wrote
>>> I have a PC I'm working on that crashed in Windows XP Pro, and
>>> since, 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?
>> 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.
> I no stupid enough: *g* I do have a backup of all the info.
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 >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Nov 19, 2003 Posts: 210
|
(Msg. 6) Posted: Tue Jan 22, 2008 12:50 pm
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Rod Speed" <rod.speed.aaa RemoveThis @gmail.com> wrote in message
news:5vku4tF1ls4uiU1@mid.individual.net...
> mechphisto RemoveThis @gmail.com wrote
>> Rod Speed <rod.speed.... RemoveThis @gmail.com> wrote
>>> mechphi... RemoveThis @gmail.com wrote
>
>>>> I have a PC I'm working on that crashed in Windows XP Pro, and
>>>> since, 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?
>
>>> 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.
>
>> I no stupid enough: *g* I do have a backup of all the info.
>
> 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
Boot XP CD and get to Recovery console. Type CHKDSK /? and pick
suitable option to repair file system.
Mike. >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Jan 02, 2007 Posts: 37
|
(Msg. 7) Posted: Tue Jan 22, 2008 1:25 pm
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
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.
<mechphisto.TakeThisOut@gmail.com> wrote in message
news:13e5bbc6-97bb-4e39-a66e-9a6afc6a3889@v4g2000hsf.googlegroups.com...
>I have a PC I'm working on that crashed in Windows XP Pro, and since,
> 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. >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Dec 06, 2007 Posts: 9
|
(Msg. 8) Posted: Tue Jan 22, 2008 2:34 pm
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: comp>sys>ibm>pc>hardware>storage, others (more info?)
|
|
|
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. =)
On Jan 22, 3:25 pm, "Eric Gisin" <gi....DeleteThis@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....DeleteThis@gmail.com> wrote in message
>
> news:13e5bbc6-97bb-4e39-a66e-9a6afc6a3889@v4g2000hsf.googlegroups.com...
>
> >I have a PC I'm working on that crashed in Windows XP Pro, and since,
> > 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. >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Jan 16, 2007 Posts: 4
|
(Msg. 9) Posted: Tue Jan 22, 2008 5:08 pm
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: comp>sys>ibm>pc>hardware>storage (more info?)
|
|
|
On Tue, 22 Jan 2008 14:34:50 -0800 (PST), mechphisto DeleteThis @gmail.com wrote:
>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 >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
External

Since: Feb 01, 2006 Posts: 1570
|
(Msg. 10) Posted: Wed Jan 23, 2008 5:50 am
Post subject: Re: Can't recover from bad NTFS unmount (post crash) [Login to view extended thread Info.] Archived from groups: comp>sys>ibm>pc>hardware>storage, others (more info?)
|
|
|
Michael Hawes <michael.hawes1remove DeleteThis @tiscali.co.uk> wrote
> Rod Speed <rod.speed.aaa DeleteThis @gmail.com> wrote
>> mechphisto DeleteThis @gmail.com wrote
>>> Rod Speed <rod.speed.... DeleteThis @gmail.com> wrote
>>>> mechphi... DeleteThis @gmail.com wrote
>>>>> I have a PC I'm working on that crashed in Windows XP Pro, and
>>>>> since, 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?
>>>> 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.
>>> I no stupid enough: *g* I do have a backup of all the info.
>> 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
> Boot XP CD and get to Recovery console. Type CHKDSK /? and pick suitable option to repair file system.
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. >> Stay informed about: Can't recover from bad NTFS unmount (post crash) |
|
| Back to top |
|
 |  |
|