Re: CHKDSK errors



Thanks for the ideas.

I have tried a chkdsk /f (and from a microsoft link I found chkdsk /r /x).
They do ask for a reboot to run the test. These sometimes fix errors but
usually only the 'orphaned' file types mentioned above. Once, I seem to
recall, it did say it had found and repaired errors in the filesystem.

Agreed re Factory restore discs, I'll keep a better eye out when I get my
next PC.

I do back the complete PC up every month or so, to an external USB2 HD and
have at least 3 archives running worth of backups, so hopefully I should be
able to recover most if not all - assuming the worst happens.

I have now emailed the PCs tech support, awaiting reply.

I'll take a look at the links you sent - thanks.


Regarding the specific queries, and mainly for my interest, is there an MS
explanation as to what something like "Recovering orphaned file 'opr01h5w
(187182) into directory file '33825" means? i.e. where are the opr015h and
33825 files located, has it actually fixed/repaired something or just 'tidied
up the garbage'? I tried a search for the files and found nothing.

Also is this a usual response when running chkdsk against C: (without a
reboot)?

CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

I don't get that on D: or E:, only against C:


Once again - Thanks.



"db.·.. ><))) ·>` .. ." wrote:

you can launch a command
console from the desktop by
installing its option to launch
into the boot menu.

the problem is however,
that having only the ability
to perform a factory restore
on the pc puts the data and
files you have accumulated
at great risk because as you
can see at this time, you are
experiencing issues with the
o.s.; although i don't beleive this
particular issue is serious, since
your checkdisk reports no flaws.

but there will be a time in the
future that your o.s. may simply
become corrupted for what
ever reason and not functional
for you.

so if such an event occurs,
the only option that you have
at this time is to do a factory
restore which wipes away
everything off the disk and
returns it to ground zero - as
it was when you first got it a
few years ago.

and as you know, there has
been hundreds of updates to
the o.s. since then.

therefore you need to make
a plan of action.

in anycase, contact the tech
support for advice. they might
be friendly and concerned with
the issue you are experiencing
and offer advice for free.

also, here is the instructions
to install the command console,
eg recovery console/repair console
from the files located on your disk:

http://search.microsoft.com/results.aspx?form=MSHOME&setlang=en-us&q=install+command+console&mkt=en-us

in addition, so that you can minimize
the risk of corrupting your system,
do not install software or freeware
without thoroughly researching its
compatiability with your system.

in doing so, you may inadverdently
corrupt your system.

also, i strongly recommend to use
the below every week or so. it will also
help reduce your risks as well:

http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm

in closing, you might want to
open your pc and take a look
at the cables to your harddrive.

be sure that none are connected
loosely or the cables are bent or
frayed.

--------------

also, you might want to consider/plan
buying/adding an additional harddrive
where you can keep copies of
your personal files, in the event
you have to wipe away the main
disk.

an easy method to apply to a
secondary harddrive would be to
move your entire my documents
folder from the system drive and
into the new location via
the option provided in the
properties of "my documents"
--

db·´¯`·...¸><)))º>


.



Relevant Pages

  • /dev/ttya & output-device changing in OS Solaris 7
    ... I an boot off one disk and the console works fine using /dev/ttya, ... I reboot off a recovered OS on another disk I appear to lose the ... console after the Solaris 7 message. ...
    (comp.unix.solaris)
  • Re: /dev/ttya & output-device changing in OS Solaris 7
    ... I reboot off a recovered OS on another disk I appear to lose the ... console after the Solaris 7 message. ... that's now trying to boot it? ...
    (comp.unix.solaris)
  • Re: /dev/ttya & output-device changing in OS Solaris 7
    ... I reboot off a recovered OS on another disk I appear to lose the ... console after the Solaris 7 message. ...
    (comp.unix.solaris)
  • Re: New HDD Installation
    ... I entered the repair console and pressed F6 ... while your installation is up and running use the Disk Management ... Description of the Windows XP Recovery Console ... if it gets the new HDD in and the small out. ...
    (microsoft.public.windowsxp.general)
  • Re: New HDD Installation
    ... Incidentally I think that the reason that the disc doesn't want to boot is because it doesn't have a proper Master Boot Record, it wasn't done by the cloning operation. ... If running the commands doesn't fix the problem then you can use the F10 option to install Windows and do an In-Place Upgrade, or what is more commonly called a "Repair Install". ... The results of our earlier test in the Disk Management console were not conclusive, was the option to do so there but simply unavailable or did you not see any option to do so at all? ...
    (microsoft.public.windowsxp.general)