Re: Advice needed, hard drive 0 is failing on a RAID1 SBS2003 server, any tips welcome because I've not had to replace a HDD like this before.

On Oct 23, 2:44 pm, "Les Connor" <les.con...@xxxxxxxxxxxx> wrote:
You should be able to run diagnostics on the physical drive from the raid
bios.

It's probably quite legit, and needs your attention.

--
Les Connor [SBS-MVP]

____________________________"Derek" <123123123...@xxxxxxxxxxxxxxxx> wrote in message

news:eZRBY2TNJHA.2044@xxxxxxxxxxxxxxxxxxxxxxx



Dear Group,

Please can you guys help me again?

Summary:
RAID1 mirror with 2 hard drives, 1 is giving error messages in the System
Event Logs.  The server has also restarted unexpectedly, and these hard
drive errors are only showing up a single time after the restart.  It has
restarted unexpectedly twice.  I'm just wondering does this mean something
else is failing, or is it the hard drive?

I've looked in the the other Event Logs and I can't see anything else that
looks like a clue to where the problem is.  The only problem I can see is
the Disk Error.

My thoughts on a solution:
1 - CHKDSK - run this, see if it throws up any corrupted files, this might
provide more weight to the "hard drive failing" case.  If it comes back
clean then I might leave the server running for another week and see if I
get any more Disk Errors in Event Logs.

2 - Replace the failing hard drive.  Use the motherboard BIOS RAID rebuild
utility to rebuild the RAID1 array and see if the server is ok.  If I have
any problems with this then I'm prepared to do the MS restore method of
partial clean installation and restore from backup method.

3 - Do you guys have a solution?

I will include extra info below that might help, inc log files.

Other Info:
Windows updates are all up to date.

Best Practice Analyzer comes back good.

Anti Virus has not reported any problems on any of the 5 work stations.

Health Monitor - Everythig is green ticks, looks good.

**********     Log:   **********

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 52
Date:  22/10/2008
Time:  22:26:23
User:  N/A
Computer: SBS2003BG
Description:
The driver has detected that device \Device\Harddisk0\DR0 has predicted
that it will fail.  Immediately back up your data and replace your hard
disk drive. A failure  may be imminent.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0e 00 03 00 01 00 5e 00   ......^.
0008: 00 00 00 00 34 00 04 80   ....4..?
0010: 02 00 00 00 00 00 00 00   .......
0018: 00 00 00 00 00 11 2d 00   ......-.
0020: 00 00 00 00 00 00 00 00   ........
0028: 00 00 00                  ..

------------------
Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 52
Date:  21/10/2008
Time:  23:08:58
User:  N/A
Computer: SBS2003BG
Description:
The driver has detected that device \Device\Harddisk0\DR0 has predicted
that it will fail.  Immediately back up your data and replace your hard
disk drive. A failure  may be imminent.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0e 00 03 00 01 00 5e 00   ......^.
0008: 00 00 00 00 34 00 04 80   ....4..?
0010: 02 00 00 00 00 00 00 00   .......
0018: 00 00 00 00 00 11 2d 00   ......-.
0020: 00 00 00 00 00 00 00 00   ........
0028: 00 00 00                  ..

**********     End of Log:   **********

Do you think this means that hard drive 0 is about to fail?  Seems like a
dumb question, but maybe the log file event is being triggered by whatever
caused the restart?

Maybe the disk error can cause the restart?

It's a server I look after for a friend, and it's the only I have
experience of apart from my own SBS2003 home server I use for learning.
The friend's server does a backup onto a tape drive every night, this
includes enough that I believe a restore could be done successfully,
although I have not tried this.

Hardware info:
ASUS K8N-DL motherboard, onboard raid.
Pair of Maxtor PATA hard drives in RAID1.
Dual core cpu.
USB External HP DAT24 tape drive, with OBDR (One Button Disaster Recovery
feature).

If you need any more info from me I will be delighted to provide it.

Thanks again group.- Hide quoted text -

- Show quoted text -

Another possibility is your power supply or power source. Are you on
a UPS? Server restart could be cause by faulty power and as a result
allowing the HD to become corrupt. If the HD was failing enough to
cause the server to restart I would think there would be something
more specific about it in the log. Bad power however would just take
out the server without any entries to that affect.

Just a thought.

Roveer
.