Microsoft
Software
Hardware
Network
Question : predictive drive failure - 2003 server - standard edition
We have a singe windows 2003 standard server, and are getting predictive drive failure events in our log from time to time. The server also starts to run really very slowly, so much so that people cannot even log on.
We have 2 caviar drives connected in a RAID 1 config (mirror), using the on board SATA RAID controller.
Do you think we should repace the drive now,?
If so, it is probable that the existing drives are no longer available, and if this is the case, can we use a larger capacity SATA drive? Do we need to stipulate any specifications for the raplacement. or will any SATA drive do.
If we can use a larger drive, will the RAID automatically build a partition the same size as the one currently in use? Could we then use the remaining capacity of the drive for additional storage. ie create a new partition?
If we can. could we replace the faulty drive first, and then when it has rebuilt the mirror, replace the sound drive, with the same physical drive, so that they matched, and could we then mirror the new partitions?
A lot of questions I know, but I am sure this is pretty straight forward for those that know.
Any help and advice would be very much appreciated.
Thanks.
Answer : predictive drive failure - 2003 server - standard edition
I solved by
.WindowState = crptMaximized
before
.Action = 1
Thanks for your suguestion..
Random Solutions
Filtering the SSRS report based on multivalue multiple parameters passed to stored procedure
Shadowing/Overriding in C#
C# sharing variables or data between different classes
Access VBA to stop all macros
Php 500 internal server error received on website but not using xampp at home
Gmail Like File Upload
New install of SBS 2008 continuously downloads 2.5GB per day (WSUS disabled)
Delivery not authorized, message refused. 550-5.7.1 Message targeted to organization's federated delivery mailbox.
Itunes could not connect to the Itunes Store. The network connection timed out.
mySQL complicated unions and subqueries