Disk marked "dirty" after scan

Norton Security | Norton Internet Security
1

I am running windows 7 64 bit. I noticed that after NIS runs a full scan the boot disk is marked "dirty." This is shown by "chkntfs c:." So, I set it to run chkdsk on reboot ("chkntfs c: /c") and it does so. [It would anyway, even without setting it to do so]. But, it never finds any corruption with chkdsk. After reboot, the "dirty" bit is reset, and the disk is marked clean. Fortunately, this doesn't take long as I have an SSD.

 

This is important because ShadowProtect will not run automatically on a disk with a "dirty" bit.

 

I am pretty sure this is the cause after reviewing the error messages on my Event Log and comparing it to the times of the Norton Full Scan. Also, nothing else was running at the time. Also, the computer was on for days without rebooting, and I kept checking it for a "dirty" bit, and it did not have one until after the scan.

2

Hi, welcome to Norton Community!

Please post your NIS version number (example: NIS 2011 -> 18.6). You can see it on main screen of NIS -> Support -> About.

Also, please post some info about your HDD and if possible the error message on windows event log so we can help you better.

3

NIS: 19.1.1

 

Drive: Intel SSDSC2MH250A2

 

Event Log:

Log Name: Application

Source: ShadowProtectSvc

Event ID: 1121

Level: Error

User; System

Op Code: (blank)

Logged: 9/23/2011 09:00:26 PM

Task Category: None

Keywords: Classic

Computer: Cliff-Win7-Desk

 

Backup status: failed

Image file: F:\ShadowProtect\C_VOL

Log file: C:\Program Files (x86)\StorageCraft\ShadowProtect\Logs\{3577B28F-BF9F-4073-A650-030B35CF92A3}.txt

Start time: 9/23/2011 9:00:00 PM

Module: service

Code: 504

Message: The source volume is corrupt.  Schedule-triggered (but not manually-triggered) backups will fail until the volume is repaired with CHKDSK.

4

Strange.  I ran full scan and my drive is NOT marked as dirty.  I have a traditional non SSD hard drive. Perhaps its because its a SSD and it "looks" dirty but it really is not?  Just a thought.

5

I assumed it had something to do with the SSD, or the SATA 3 interface, because they are relatively new tech and probably not tested as much by Symantec.

6

or maybe the fact that the scan was triggered b the timer, not manually, or a combination of all these things.

7

The dirty flag gets set whenever there are directory information data in memory that haven't been written to the disk, yet. Performing a full disk scan will certainly queue writing a bunch of data to the disk. However, these data should automatically get written to the drive automatically after some time or immediately during shutdown and the flag automatically cleared. If you wait a few minutes before shutting down does the chkntfs status or the reboot behavior change? Do ever you observe any sorts of problems during shutdown?

8

The "dirty" flag does not change until I reboot. I get the same error message every time a scheduled back-up follows, until I reboot. It can go on for days. There are never any errors found by chkdsk. I never see any errors at shut-down, and none are logged.

 

Also, this only occurs on the SSD, not on the mechanical disk drive. This SSD replaced a smaller one, and the same errors were occuring on the smaller one.

 

 

9

Thanks for the additional information. I've filed an incident report internally for further research.

10

@reese

 

Could it be related to the issue I'm encountering: see this thread:

http://community.norton.com/t5/Norton-Internet-Security-Norton/broken-again-within-hours/m-p/546784#M175279

(message nr.9)

 

I'm running a Lenovo R500 notebook with W7Prof.  32bit. Here's what I did in the mean time:

1. again put the hard disk drive (not a SSD) through its paces with the help of the Lenovos supplied test program; this is not the installed PCDr but a version to be used outside of Windows from a CD while booting the machine. Nothing wrong with the drive.

2. Uninstalled NAV2012 and used NRT: didn't help much, still ntfs errors.

3. Next day (today that is) I restored an image from just before installing NAV on this machine. Previous to this restoration NAV2011 was on it which I completely removed at the time I made the image whilst also having used the NRT. Tested it afterwards and no more problems with ntfs errors popping up out of the blue.

4. At the moment I'm using a rival AV solution just to see whether those pesky ntfs errors come back or not. Until now I haven't encountered a single one.

 

When did the ntfs errors happen to surface?

Right after having had a quick scan by NAV2012 on the machine, also in combination with the moment the machine got into screensaver mode (just a still photo, nothing of those screensavers W7 is supplied with) and during or at the same time a quick scan was busy.

 

However, after a while I also happened to encounter them out of the blue with no activity from NAV2012 nor any activity from the machine at all, that is nothing I saw but it is possible something has been running without me seeing it of course.

 

What I do suspect however is some Lenovo program interfering with NAV, but I'm not sure.

 

I do plan however to uninstall most of those Lenovo applications because I know of one which is likely to add to the problem of those ntfs errors. (the TVT stuff that is in scheduled tasks, disabled them and after a while those ntfs errors came up. While searching for the culprit and re-enabling them, the ntfs errors did not go away however.)

 

Anyway, at the moment - I just looked in event viewer- I haven't had any ntfs errors yet since restoring the image; this is as much information I can offer for now.

 

11

artee, I've been following your thread and I don't think that the two are related. I've added a comment to your thread though.

12

Ok Thanks reese, I'll answer in the other thread then.

13

Thank you. I will look forward to a solution!

14

Apparently it has to be a full scan that deletes cookies (at least) to leave the disk dirty. It happened again at 1:30 am this morning.

15

Any progress? The issue is repeatable.

16

There has been progress but not much. The issue has been looked at by a couple of groups already and is still being researched.