Re: Server 2k + Hard Disk Corruption.


<cybac@xxxxxxxxxxxxxxxxxx> wrote in message
news:1159179265.269214.227710@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Guys,

I'm having a bit of a nightmare at the moment. I have a windows server
2k + SP4 environment in which I have 2 x 200gb Sata hard disks. The
first is split into 3 partitions, C: = 18.5gb and D: =83.8gb, E: =
83.8gb. The second is in 2 partitions, F: =93.1gb , G: =93.1gb.

Drive C = System
Drive D = Users (redirected My Documents and shared home folders)
Drive E = SQL + Apache Webserver
Drive F = Backups + Logs (AD logs)
Drive G = Recordings

Clients connect using XP with SP2 installed.

My problem is that every so often there seems to be some corruption
happening on one of the disks, the problem has occured on both disks,
on drives D, E,F & G. Small mercy that drive C has not been effected.

I get an error message that says the "file system on drive xx is
corrupt and unusable, please run chkdsk". I run chkdsk, it usually
deletes orphan files and rebuilds the file structure. After that
finishes the drive is useable boot sometime the data i need is either
gone or corrupt.

I have tried moving things and reformatting to get a new file system on
the partition, however over time the problem happens again. If it's not
dealt with straight away the server usually crashes and I have a bad
time trying to clean up the mess.

These drives contain a lot of user work and there have been a couple of
occasions where files have become corrupt and work lost. There are
quite a few shared folders.

Once the problem is fixed I check all the error logs and the system
seems stable again for a while.

I really would appreciate any suggestions as to what my next port of
call should be.


While I do not know what's causing your particular problem,
you might be able to extract some useful information from a
similar problem I recently had.

This was a brand-new HP server with two SATA disks. Shortly
after installing Trend Client Server Messaging, the machine crashed.
It subsequently booted up OK but Windows kept complaining about
a corrupted system disk. Running chkdsk either during a reboot or
under a Bart PE boot fixed numerous errors. It also caused the
loss of many files installed after the crash but before the chkdsk run.

After playing the chkdsk game for a week, I deleted the file system
on the system partition and restored it from an image I had previously
made. This was four weeks ago - the machine hasn't missed a beat
since then.

I assume you have checked the event logger for error messages.
I also recommend strongly that you install an automatic logger for
each and every boot event.


.

Relevant Pages

  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... I did see an issue related to the "security id" and chkdsk if you have over 4 million, but the hotfix is a few years old and the version of the system dll's on the server are later than the ones in the hotfix, so it appears that the fix is already there. ... are there any special issues with the cluster? ... The three drives are a 500MB for the> quorum, ...
    (microsoft.public.windows.server.general)
  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... I did see an issue related to the "security id" and chkdsk if you have over 4 million, but the hotfix is a few years old and the version of the system dll's on the server are later than the ones in the hotfix, so it appears that the fix is already there. ... are there any special issues with the cluster? ... The three drives are a 500MB for the quorum,> and two ...
    (microsoft.public.windows.server.general)
  • Re: Correcting corrupt $MFT on shared clustered disk.
    ... Next I am not sure if you are aware but http://support.microsoft.com/kb/903650 Extended Maintenance mode is now available when you need to run chkdsk on a drive. ... We have a two node cluster running Windows 2003 R2 ... The three drives are a 500MB for the quorum, ... directory E:\$Mft is corrupt and unreadable. ...
    (microsoft.public.windows.server.clustering)
  • Re: Correcting a corrupted $MFT on a shared clustered disk
    ... We're limited on the number of calls we can use, so I usually save them for something major (like if chkdsk didn't fix the corrupt disk). ... I did see an issue related to the "security id" and chkdsk if you have over 4 million, but the hotfix is a few years old and the version of the system dll's on the server are later than the ones in the hotfix, so it appears that the fix is already there. ... are there any special issues with the cluster? ... The three drives are a 500MB for the> quorum, ...
    (microsoft.public.windows.server.general)
  • Re: BSOD
    ... I've had tape drives do this to me ... incident on a server so these things don't always stick in your head. ... > indeed possible that these are corrupt, ... > I think you should first try an in-place upgrade reinstall of Windows ...
    (microsoft.public.win2000.general)
Loading