Re: CHKDSK: Usn Journal Corruption
From: Bob (spam_at_uce.gov)
Date: 10/16/05
- Next message: Doug Fox: "Why these ports are running on a Windows Server 2003?"
- Previous message: G. Vaught: "Interactivity Logon not permitted"
- In reply to: Steven L Umbach: "Re: CHKDSK: Usn Journal Corruption"
- Next in thread: Steven L Umbach: "Re: CHKDSK: Usn Journal Corruption"
- Reply: Steven L Umbach: "Re: CHKDSK: Usn Journal Corruption"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 16 Oct 2005 20:02:48 GMT
On Sun, 16 Oct 2005 12:59:16 -0500, "Steven L Umbach"
<n9rou@nospam-comcast.net> wrote:
>If it is not enabled yet try enabling auditing of system events in Local
>Security Policy. If nothing is reported in the logs then it will be
>difficult to track down and again may be a hardware problem. Try to boot
>into Safe Mode and then reboot to see if the problem persists. There are
>some commands that you could also try running in Recovery Console such as
>fixboot and chkdsk which may do a better job in RC mode. See the link below
>for more info on Recovery Console. Beyond that f it was my computer I would
>try doing an in place upgrade of the operating system and if that did not
>work a pristine install of the operating system which you could also do as a
>dual boot configuration to see if the new install had the problem or not.
>Try disconnecting the other drives from the motherboard [from the cable or
>via cmos] if possible [assuming RAID striping is not used] and only boot
>from the system drive and maybe try new hard drive data cables. You might
>also want to post in a hardware newsgroup or a general operating system
>newsgroup for Windows 2000. --- Steve
>
>http://support.microsoft.com/kb/q229716/
Thatks for the detailed comments, but I am looking for a simple way to
find the culprit. I am using ATA-133 80-wire ribbon cables. Before I
was using round IDE cables and replaced them because I thought they
were the culprit. I have two removable bays with two drives operative.
I see no evidence of corruption on the second drive so I tend to rule
out the hardware, especially since I have three separate identical
disks I use as boot disks. They all exhibit this problem.
If could it be my Computer Associates anti-virus program, which is the
only new background application I have installed in a long while.
Unfortunately there is no easy way to remove it from background
without uninstalling it. IOW, there is no Exit or Close option. I
suppose I could use msconfig to prevent it from loading, but first I
want to find a way to understand what the problem is all about.
What uses the Usn Journal? Why would it become corrupted and force
CHKDSK to run at startup?
- Next message: Doug Fox: "Why these ports are running on a Windows Server 2003?"
- Previous message: G. Vaught: "Interactivity Logon not permitted"
- In reply to: Steven L Umbach: "Re: CHKDSK: Usn Journal Corruption"
- Next in thread: Steven L Umbach: "Re: CHKDSK: Usn Journal Corruption"
- Reply: Steven L Umbach: "Re: CHKDSK: Usn Journal Corruption"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|