CHKDSK runnes in read only mode

  • Thread starter Thread starter Mike T
  • Start date Start date
M

Mike T

Guest
When running CHKDSK I get a message stating that it will run in read only

mode because the F parameter is not specified. so how do I specify the F

parameter and what specification should I set in order to get out of read

only.



Being a bit of a novice am I playing with fire?
 
Mike T wrote:

> When running CHKDSK I get a message stating that it will run in read only

> mode because the F parameter is not specified. so how do I specify the F

> parameter and what specification should I set in order to get out of read

> only.

>

> Being a bit of a novice am I playing with fire?





http://support.microsoft.com/kb/315265

How to perform disk error checking in Windows XP



John
 
On Feb 19, 10:22 am, Mike T

wrote:

> When running CHKDSK I get a message stating that it will run in read only

> mode because the F parameter is not specified.  so how do I specify theF

> parameter and what specification should I set in order to get out of read

> only.

>

> Being a bit of a novice am I playing with fire?



Hopefully, if you choose to run chkdsk the next time Windows reboots

(which is fine), you will also be interested in knowing what happened.



When chkdsk runs automatically on a reboot, the results are shown in

the Event Viewer Application log.



To see the Event Viewer logs, click Start, Settings, Control Panel,

Administrative Tools, Event Viewer.



A shortcut to Event Viewer is to click Start, Run and in the box

enter:



%SystemRoot%\system32\eventvwr.msc



Click OK to launch the Event Viewer.



Look in the Application log for an event sourced by Winlogon,

something like:



Event Type: Information

Event Source: Winlogon

Event Category: None

Event ID: 1001

Description:

Checking file system on C:

The type of the file system is NTFS.





A disk check has been scheduled.

Windows will now check the disk.



CHKDSK is verifying Usn Journal...

Usn Journal verification completed.



39070048 KB total disk space.

25151976 KB in 78653 files.

48256 KB in 10264 indexes.

0 KB in bad sectors.

237080 KB in use by the system.

65536 KB occupied by the log file.

13632736 KB available on disk.



4096 bytes in each allocation unit.

9767512 total allocation units on disk.

3408184 allocation units available on disk.



Windows has finished checking your disk.

Please wait while your computer restarts.
 
In news:CD67678F-7018-4200-BF7E-1B772784750F@microsoft.com,

Mike T typed:

> When running CHKDSK I get a message stating that it will run in read

> only mode because the F parameter is not specified. so how do I

> specify the F parameter and what specification should I set in order

> to get out of read only.

>

> Being a bit of a novice am I playing with fire?



After the chkdsk, simply add a space and slash-F e.g.

chkcsk /f

The /f tells it to fix problems it finds.



If you go to a command promtpt and enter

chkdsk /?

it'll show you all the switches available for the command.



If you want to start chkdsk from the Run line, simply enter

chkdsk /F

and click Run. No need to add the path; it's already in the default path.



If you try to run chkdsk on the boot disk C:, it'll tell you it can't and

ask if you want to do it on the next boot. Clidk YES and Restart the

computer. Chkdsk will run when it boots up, before windows gets loaded.



HTH,



Twayne











--

--

Life is the only real counselor; wisdom unfiltered

through personal experience does not become a

part of the moral tissue.
 
Mike T wrote:



> When running CHKDSK I get a message stating that it will run in read only

> mode because the F parameter is not specified. so how do I specify the F

> parameter and what specification should I set in order to get out of read

> only.

>

> Being a bit of a novice am I playing with fire?



Ever use the Start -> Help and Support menu in Windows?
 
On Fri, 19 Feb 2010 08:03:48 -0800 (PST), Jose

wrote:



>

>A shortcut to Event Viewer is to click Start, Run and in the box

>enter:

>

>%SystemRoot%\system32\eventvwr.msc



If it's in the system32 folder, isn't all you have to do enter

eventvwr.msc ?

>

>Click OK to launch the Event Viewer.
 
On Feb 19, 3:20 pm, mm wrote:

> On Fri, 19 Feb 2010 08:03:48 -0800 (PST), Jose

> wrote:

>

>

>

> >A shortcut to Event Viewer is to click Start, Run and in the box

> >enter:

>

> >%SystemRoot%\system32\eventvwr.msc

>

> If it's in the system32 folder, isn't all you have to do enter  

>    eventvwr.msc  ?

>

>

>

>

>

> >Click OK to launch the Event Viewer.



That will work - most of the time, but if you encounter a situation

where it doesn't and you have to figure out why it doesn't, that is

just more messages back and forth and more time.



I generally try not to work with "ifs" (or maybe, might be, could be,

probably or try).



I find it best to go with the operations that have the greatest

probability of working the first time in most environments.
 
On Feb 19, 4:12 pm, Jose wrote:

> On Feb 19, 3:20 pm, mm wrote:

>

>

>

>

>

> > On Fri, 19 Feb 2010 08:03:48 -0800 (PST), Jose

> > wrote:

>

> > >A shortcut to Event Viewer is to click Start, Run and in the box

> > >enter:

>

> > >%SystemRoot%\system32\eventvwr.msc

>

> > If it's in the system32 folder, isn't all you have to do enter  

> >    eventvwr.msc  ?

>

> > >Click OK to launch the Event Viewer.

>

> That will work - most of the time, but if you encounter a situation

> where it doesn't and you have to figure out why it doesn't, that is

> just more messages back and forth and more time.

>

> I generally try not to work with "ifs" (or maybe, might be, could be,

> probably or try).

>

> I find it best to go with the operations that have the greatest

> probability of working the first time in most environments.



....forgot: "should work" and "might work".
 
mm wrote:

> On Fri, 19 Feb 2010 08:03:48 -0800 (PST), Jose

> wrote:

>

>> A shortcut to Event Viewer is to click Start, Run and in the box

>> enter:

>>

>> %SystemRoot%\system32\eventvwr.msc

>

> If it's in the system32 folder, isn't all you have to do enter

> eventvwr.msc ?



Yes. If it doesn't work with the simple eventvwr.msc command it means

that the eventvwr.msc file is not in its proper location or that the

Path variable is missing entries. If the path variable is missing

entries it needs to be repaired as many other things might not work

properly.



John
 
You must log in or register to reply here.
Back
Top