I posted the question and additonal infomation 2.5 years ago. Still no answer. New SSD since then. Switched from the Marvell to the Intel controller, updated NIS to current version. Still the same behaviour. I just set NIS to full-scan only once a week and to turn off after the scan. Then when I turn the computer on it runs checkdisk, finds nothing wrong and clears the bit. Then my back-up program works. But, I should not have to do that.
original message link:
Hi 73fromme,
For the sake of getting a complete view of the issue, could you detail out the steps it takes to reproduce the issue? From the defect we've been tracking internally and the thread, I can see the following info:
I noticed that after NIS runs a full scan the boot disk is marked "dirty." ShadowProtect will not run automatically on a disk with a "dirty" bit. The "dirty" flag does not change 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. this only occurs on the SSD, not on the mechanical disk drive. it has to be a full scan that deletes cookies (at least) to leave the disk dirty.
It would help for us to have some steps to reproduce, list of your hardware and software installed, and possibly some screenshots of the problem. This would help us figure out what the cause might be. Any details you can provide is appreciated.
I posted the question and additonal infomation 2.5 years ago. Still no answer. New SSD since then. Switched from the Marvell to the Intel controller, updated NIS to current version. Still the same behaviour. I just set NIS to full-scan only once a week and to turn off after the scan. Then when I turn the computer on it runs checkdisk, finds nothing wrong and clears the bit. Then my back-up program works. But, I should not have to do that.
original message link:
An updated version of the same program
The disk is clean. NIS performs a scan, unattended. It finishes leaving the disk marked dirty (it always finds cookies, but whether I delete them automatically or not does not matter to this issue).
ShadowProtect will not trigger on a dirty marked disk, so I get an event error message.
I worked around this by setting SphadowProtect to back-up before the NIS scan. Then I just reboot after the NIS scan fcleaning the "dirty" disk. No errors ever returned.
I use SSDs. I just replaced my old SSD C-drive with a new one. No change in the issue. I also switched to the native Intel controller, but both are 6MB SATA 3.
I use an ASUS MB. Very fast system.
I will reproduce it agian today and email you.
Have you ever tried this without Shadow Protect installed?
I have a ASUS P8Z77-V Pro with a OCZ Vertex 4 SSD and never had the dirty bit set after a scan.
Dave
Here is the dos box showing drive not dirty befiore scan, the scan results (no threats), the dos box showing the drive is now dirty. So, it is independant of ShadowProtect. It is just that ShadowProtect will not trigger with the dirty bit set.
I see in the event viewer, an event 55 : "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Boot4-13-14." This is logged about 19 minutes, 47 seconds into the scan and relogged 5 more times within 2 seconds. It is only on drive C. Only drive C is now "dirty."
I wouldn't rule out Shadow Protect quite so fast.
After all, it does interact with volume shadow service and thats running all the time.
You'll also find that the dirty bit being set is not a widespread problem here so it's safe to assume it is not a problem with NIS but more likely a conflict or interaction with some other program.
It does after all work fine for me, you also rulled out the SSD as the cause since it also happens on the second SSD.
Only other think I could think of is something maybe causing your system to hang on shutdown not letting windows flush the hard drive cache or powering down the drive.
BTW- I benchmarked both the Marvell and Intel controllers on my MB and I get significantly better performace on the Intel.
Hope you can get your problem resolved.
Dave
Here is a report from SiSoft Sandra - hardware and software