dirty bit

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

How do you unset the dirty bit for a drive. Chkdsk runs every boot up. I
have found how to set it, but not the reverse.
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

On Tue, 7 Dec 2004 20:14:21 -0500, "Nick Burns" <thedoc@hotmail.com>

>Power went out when defrag was running and that started the glitch.
>Drive is about 2 months old..

That sounds like possible physical damage - which the HD's firmware
and NTFS code may try to hide from you.

>I use drive every day for video rendering for mega hours and never have
>problems.

>All my software including manufacture test show no errors.
>All software says drive is dirty.

I'd look for SMART detail, e.g. with AIDA32; drive vendor's tools are
likely to take "you are dying" to mean "you aren't dead yet, so
everything's fine; no, we don't need to send you a replacemet".

If ChkDsk or anything else claims to have found bad sectors (or
clusters) but it's OK because they are fixed now, suspect the worst.

>Is this bit part of the HD, the reg, or where is it. I do write assembly if
>I know where to go...?

First thing is to see which bit it is. If it's simple "interrupted
file ops" then OK, force it; it will pop back if it has to. If it's
the "hey, I can't access the drive" bit, then nature's trying to tell
you something that's quite important.

The location of these bits is documented in FATxx, but I don't know
where from memory (it's in the front of the FAT). NTFS doesn't have a
FAT, so obviously they must be somewhere else there.



>--------------- ---- --- -- - - - -
I'm baaaack!
>--------------- ---- --- -- - - - -
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

A naive reply perhaps, but I cured this on a customer's machine by booting
into "safe mode with command prompt", and running scandisk from there.
Never saw it again.

--
####################
## PH, London
####################
"Nick Burns" <thedoc@hotmail.com> wrote in message news:ug1s%>> On Mon, 6
Dec 2004 17:20:33 -0500, "Nick Burns" <thedoc@hotmail.com>
>>
>> >How do you unset the dirty bit for a drive. Chkdsk runs every boot up. I
>> >have found how to set it, but not the reverse.
>>
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

No check has detected any problem and I have used AIDA32 and drive vendors
tool.

The problem was not from a power out, it was when I started defrag and
decided to cancel. The drive light never went out so I did a restart and
chkdsk has run ever their after. I will just copy all from the e: to a
folder in c: and format e: To bad their is not a easier.



"cquirke (MVP Win9x)" <cquirkenews@nospam.mvps.org> wrote in message
news:u1tcr0h8hi39anb210f8e58uv664mrbd67@4ax.com...
> On Tue, 7 Dec 2004 20:14:21 -0500, "Nick Burns" <thedoc@hotmail.com>
>
> >Power went out when defrag was running and that started the glitch.
> >Drive is about 2 months old..
>
> That sounds like possible physical damage - which the HD's firmware
> and NTFS code may try to hide from you.
>
> >I use drive every day for video rendering for mega hours and never have
> >problems.
>
> >All my software including manufacture test show no errors.
> >All software says drive is dirty.
>
> I'd look for SMART detail, e.g. with AIDA32; drive vendor's tools are
> likely to take "you are dying" to mean "you aren't dead yet, so
> everything's fine; no, we don't need to send you a replacemet".
>
> If ChkDsk or anything else claims to have found bad sectors (or
> clusters) but it's OK because they are fixed now, suspect the worst.
>
> >Is this bit part of the HD, the reg, or where is it. I do write assembly
if
> >I know where to go...?
>
> First thing is to see which bit it is. If it's simple "interrupted
> file ops" then OK, force it; it will pop back if it has to. If it's
> the "hey, I can't access the drive" bit, then nature's trying to tell
> you something that's quite important.
>
> The location of these bits is documented in FATxx, but I don't know
> where from memory (it's in the front of the FAT). NTFS doesn't have a
> FAT, so obviously they must be somewhere else there.
>
>
>
> >--------------- ---- --- -- - - - -
> I'm baaaack!
> >--------------- ---- --- -- - - - -
 
Archived from groups: microsoft.public.windowsxp.hardware (More info?)

I have run all forms of chkdsk and other utilities from run mode safemode
and the recovery console.


"Philip Herlihy" <foof8501@herlihy.eu.veil.com> wrote in message
news:ehjDHzR3EHA.2804@TK2MSFTNGP15.phx.gbl...
> A naive reply perhaps, but I cured this on a customer's machine by booting
> into "safe mode with command prompt", and running scandisk from there.
> Never saw it again.
>
> --
> ####################
> ## PH, London
> ####################
> "Nick Burns" <thedoc@hotmail.com> wrote in message news:ug1s%>> On Mon, 6
> Dec 2004 17:20:33 -0500, "Nick Burns" <thedoc@hotmail.com>
> >>
> >> >How do you unset the dirty bit for a drive. Chkdsk runs every boot up.
I
> >> >have found how to set it, but not the reverse.
> >>
>
>