Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 27 replies
  • Subscribers 5 subscribers
  • Views 26261 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SG Enterprise encryption - Bad Sectors survey

jb1111

Has anyone here encountered bad sectors on encrypted machines?  I had 2 computers run for 3-4 months, get bad sectors and start crashing or going to a Windows screen with no icons <-you can only power off at this point.  Attempting to fix the bad sectors does not help.  The only thing I've gotten to work is backup the files (assuming I can even get into the system) and destroy the hard disk with Dban or killdisk.  These low level format and, "Zero out" the drive.  Once this 6 hour process is done, I reload Windows.  Chkdsk no longer shows bad sectors and life is good.

Has anyone come up with another approach to bad sectors or other hard drive issues?  I am most concerned this will be a monthly occurance.  Perhaps I could get a utility to report when drives start getting bad sectors?

Thanks.

PS - my SG policy is set to, "Proceed on bad sectors = yes"

:4085


This thread was automatically locked due to age.
Parents
  • 0

    Hi JB,

    I schedule a simple "chkdsk > c:\chklog.txt". I don't put any switches on expecially /f because you cannot do that in the background on the system drive anyway so it's pointless. In this very simple mode, it reports the state of the disk without fixing anything and is not particularly hard-hitting on the drive so the users don't really notice the task in the background (especially if we time the task correctly). We then have a job that runs on the server and checks the size of the log file on each machine it can see. If the log is larger than a specific size, we investigate further and If on further investigation we find bad sectors or other nasties, we schedule more vigorous maintenance on the machine therefore a considerably pro-active approach to disk maintenance. With SGN creating 'good' bad sectors, this becomes very difficult to establish what's good from what's bad. SGE never used to do this and we're just going with SGN now as we migrate to Win 7. My initial impressions are that SGN is not as well thought out as the competition. I have 50 seats of SGE mostly running 4.40 or 4.50 with a full SGN maitenance contract so I'm not a huge company by any means either.

    Matt

    :4441
Reply
  • 0

    Hi JB,

    I schedule a simple "chkdsk > c:\chklog.txt". I don't put any switches on expecially /f because you cannot do that in the background on the system drive anyway so it's pointless. In this very simple mode, it reports the state of the disk without fixing anything and is not particularly hard-hitting on the drive so the users don't really notice the task in the background (especially if we time the task correctly). We then have a job that runs on the server and checks the size of the log file on each machine it can see. If the log is larger than a specific size, we investigate further and If on further investigation we find bad sectors or other nasties, we schedule more vigorous maintenance on the machine therefore a considerably pro-active approach to disk maintenance. With SGN creating 'good' bad sectors, this becomes very difficult to establish what's good from what's bad. SGE never used to do this and we're just going with SGN now as we migrate to Win 7. My initial impressions are that SGN is not as well thought out as the competition. I have 50 seats of SGE mostly running 4.40 or 4.50 with a full SGN maitenance contract so I'm not a huge company by any means either.

    Matt

    :4441
Children
No Data
Unfiltered HTML