This rule raises an alert when there is an alarming trend in the increase of disk failures in any given disk type in the enterprise
Disk Failure
Having a reliable set of troubleshooting guidelines can increase your odds of recovering from a hard drive failure. This checklist walks you through a proven hard drive troubleshooting process.
Physical connections
Cables
Securely reconnect power cable to hard drive.
Securely reconnect IDE or SCSI Ribbon cable to hard drive.
Securely reconnect IDE or SCSI Ribbon cable to hard drive controller (motherboard or expansion card).
Install proper ribbon cable used (UltraDMA 66, UltraDMA 33, SCSI, etc.).
Match red trip on ribbon cable to Pin 1 on hard drive.
Match red trip on ribbon cable to Pin 1 on controller.
Connect LED cable to hard drive (AT/LPX system) or motherboard (ATX systems).
Jumper settings (IDE only)
Set the jumper properly when a single drive is being used.
Note: the drive is the only one on that ribbon cable and IDE subsystem.
Set the jumper properly when a primary (MS), secondary (SL), or Cable Select (SL) is being used.
Note: the drive is one of two on that ribbon, and IDE subsystem one drive should be the MS and the other SL. CS relies on the drive's position to determine its primary/secondary status (not a common setting).
SCSI Termination and ID (SCSI hard drives only)
Terminate SCSI cable with hard drive jumper setting or SCSI cable cap/plug.
Assign hard drive appropriate SCSI ID using hard drive wheel, button, or jumper setting.
BIOS Setup (IDE only)
Take BIOS attempt to detect the drive by setting its primary channel to Auto.
Enter correct hard drive specifications manually.
Viruses
Scan the hard drive with bootable, write-protected antivirus disk created with up-to-date antivirus software on working machine.
If the drive is not partitioned and formatted, the boot disk might not be able to check the drive data area, but might be able to check the boot partition. Let the antivirus scanning proceed as far as possible.
Valid partition
If the drive has a partition problem, try to retrieve the data with a data-recovery program, or give up on the data, delete the partition and re-create it using FDISK or other partition management utility.
Formatting
If OS presents an invalid media type error message, you can try to retrieve the data with a data-recovery program, or give up on the data and reformat the drive.
Physical and logical drive errors
Scan the hard drive for physical and logical errors with a disk-checking program. Allow the disk-checking program to fix any found errors.
Disk Management
Disk Management reports the hard drive is offline, or has a status other than Healthy
Right-click the drive and choose Reactivate Drive
Target | Microsoft.SystemCenter.DataWarehouse | ||
Category | EventCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.Client.Win10.SQLProvider | Default |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.Windows.Client.Win10.ComputerGroup.DiskTrendsDisk" Target="SCDW!Microsoft.SystemCenter.DataWarehouse" Enabled="true" ConfirmDelivery="true" DiscardLevel="60" Remotable="true" Priority="Normal">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Microsoft.Windows.Client.Win10.SQLProvider">
<Query>
SELECT 1, Win10.DiskData.Model
FROM Win10.vWin10DiskFailureAggregationDisk AS Result
JOIN Win10.DiskData ON (Win10.DiskData.DiskDataRowId = Result.DiskDataRowId)
WHERE (SELECT SUM(NumDrives)
FROM Win10.vWin10DiskFailureAggregationDisk AS ThisWeek
WHERE ThisWeek.DiskDataRowId = Result.DiskDataRowId
AND DATEDIFF(day, ThisWeek.DateTime, GETUTCDATE()) <= 7
GROUP BY ThisWeek.DiskDataRowId
)
>= 1.2 *
(SELECT SUM(NumDrives)
FROM Win10.vWin10DiskFailureAggregationDisk AS LastWeek
WHERE LastWeek.DiskDataRowId = Result.DiskDataRowId
AND DATEDIFF(day, LastWeek.DateTime, GETUTCDATE()) <= 14
AND DATEDIFF(day, LastWeek.DateTime, GETUTCDATE()) > 7
GROUP BY LastWeek.DiskDataRowId
)
GROUP BY Win10.DiskData.Model
</Query>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Client.Win10.ComputerGroup.DiskTrendsDisk.AlertMessage"]$</AlertMessageId>
<AlertParameters/>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>