- Jun 30, 2004
- 16,317
- 1,880
- 126
I always thought I was a real techno-hot-dawg. I knew the ins and outs of MS-DOS from 1983, following with Win 3.0, 3.1, 95, 98, NT 4, 2000-Pro and Server . . then XP-pro, VISTA, WHS v.1 and 2011 with Win 7. Now, here I am.
If my computers worked "properly" in this household network, I might focus on "red-bang" errors and "yellow-bang" warnings in event logs, but they were often elusive, many times "benign," and if I didn't get them solved in some window of time (pun) -- I'd "save it for later" as long as everything was working fine.
Beginning January, though, I had an elusive problem which would leave a trace of itself as "Event ID 41" maybe once every ten days. Since it "went away" over a month's time when I wasn't using Media Center, I had enough clues and eventually solved it. No -- it wasn't OC settings. And it was most likely misconfigured network drivers. Linked to this was a "Distributed COM" error that would pop up in the Event logs after every reboot -- related to misconfigured security settings.
Other misconfigured security settings traced to a problem with VSS or the volume shadow copy service. My WHS server backs up this system daily. Turns out that WHS is a "requestor" of VSS, and I had literally foregone the use of volume shadow copy on my system. This was "old school" prejudice -- "I don' need no darn shadow copies or images." You know -- keep it simple stupid. And I was -- both simple and stupid.
Getting rid of the security problem "red-bangs" pertaining to the daily WHS backup revealed "new stuff." Suddenly, I start getting "NTFS" Event ID 51 errors related to shadow-copy files. Panic!
And -- Panic! Is my HDD corrupted?! How is this linked to my ISRT setup?!
Ya see, the whole point after January was to clean up this system so that it was so perfectly configured, running so well, that I'd feel confident replacing ISRT with a brand-new 840-Pro SSD -- WITHOUT -- without . . reinstalling the OS and all my software, running an "upgrade-repair" on the current setup, etc. etc. yada-yada-yada.
Now -- I think I'm "there."
But the NTFS errors really had me going, running CHKDSK at least a few times while it scrutinized the disk for bad sectors as well as file problems. But "Nada."
So I suddenly find that my WHS backups were configured improperly; that there were as many as 12 shadow copy files on my system -- which relate to "restore points." You can clean up that stuff with "cleanmgr" run from "Run."
Other advice suggested turning off disk write-caching. So I began to ask: "Why do I need write-caching when the ISRT config writes to the cache and HDD simultaneously in "Enhanced mode?" And when HDDs now typically have fairly large buffers of their own?
But that's the question. When do you need write-caching, with either simple SSD as boot-disk, or with ISRT? Now that I've done other things that got rid of the NTFS Ev ID 51 errors, maybe I should re-enable it? I haven't noticed a drop in performance . .
Well, that's enough from blabber-mouth for now. Comments and observations welcome here.
If my computers worked "properly" in this household network, I might focus on "red-bang" errors and "yellow-bang" warnings in event logs, but they were often elusive, many times "benign," and if I didn't get them solved in some window of time (pun) -- I'd "save it for later" as long as everything was working fine.
Beginning January, though, I had an elusive problem which would leave a trace of itself as "Event ID 41" maybe once every ten days. Since it "went away" over a month's time when I wasn't using Media Center, I had enough clues and eventually solved it. No -- it wasn't OC settings. And it was most likely misconfigured network drivers. Linked to this was a "Distributed COM" error that would pop up in the Event logs after every reboot -- related to misconfigured security settings.
Other misconfigured security settings traced to a problem with VSS or the volume shadow copy service. My WHS server backs up this system daily. Turns out that WHS is a "requestor" of VSS, and I had literally foregone the use of volume shadow copy on my system. This was "old school" prejudice -- "I don' need no darn shadow copies or images." You know -- keep it simple stupid. And I was -- both simple and stupid.
Getting rid of the security problem "red-bangs" pertaining to the daily WHS backup revealed "new stuff." Suddenly, I start getting "NTFS" Event ID 51 errors related to shadow-copy files. Panic!
And -- Panic! Is my HDD corrupted?! How is this linked to my ISRT setup?!
Ya see, the whole point after January was to clean up this system so that it was so perfectly configured, running so well, that I'd feel confident replacing ISRT with a brand-new 840-Pro SSD -- WITHOUT -- without . . reinstalling the OS and all my software, running an "upgrade-repair" on the current setup, etc. etc. yada-yada-yada.
Now -- I think I'm "there."
But the NTFS errors really had me going, running CHKDSK at least a few times while it scrutinized the disk for bad sectors as well as file problems. But "Nada."
So I suddenly find that my WHS backups were configured improperly; that there were as many as 12 shadow copy files on my system -- which relate to "restore points." You can clean up that stuff with "cleanmgr" run from "Run."
Other advice suggested turning off disk write-caching. So I began to ask: "Why do I need write-caching when the ISRT config writes to the cache and HDD simultaneously in "Enhanced mode?" And when HDDs now typically have fairly large buffers of their own?
But that's the question. When do you need write-caching, with either simple SSD as boot-disk, or with ISRT? Now that I've done other things that got rid of the NTFS Ev ID 51 errors, maybe I should re-enable it? I haven't noticed a drop in performance . .
Well, that's enough from blabber-mouth for now. Comments and observations welcome here.
Facebook
Twitter