Hi,
I hae a 2000 Server with a 3 disk array running off a Mylex 170 RAID card -
I have come to this system recently so dont have much prior knowledge but
the Mylex card was replaced a few months back due to some failure or other.
The view in Disk Management shows 'Healthy (At Risk)' on the RAID volume.
Not sure what the issue is here. I have updated firmware and driver as a
matter of course but no effect.
The system seems fine in day to day use but I'd rather not have this
message(!) No errors are logged in Event Viewer.
Any help appreciated.
Healthy
The Healthy status is the normal volume status on both basic and
dynamic
volumes when the volume is accessible and has no known problems. No
user
action is required.
Volumes with the Healthy status often display an associated substatus
(in
parentheses). A volume may only display one substatus at a time. The
substatus is displayed according to the order in which it appears in
the
table below. For example, if you have only one volume which serves as
the
boot volume, system volume, active volume, page file, and crash dump,
its
status is displayed as Healthy (System). However, if an error occurs
on a
dynamic volume, the (At Risk) substatus takes precedence.
Healthy (substatuses)Description
SystemIndicates that the volume is the system volume.
BootIndicates that the volume is the boot volume.
Page FileIndicates that the volume holds the paging file. For more
information about the paging file, see System Properties overview.
ActiveIndicates that the volume is an active volume on a basic disk.
For
more information about making a volume the active volume, see Mark a
partition as active.
Crash DumpIndicates that the volume holds the crash dump, also known
as a
memory dump. The memory dump is used to record the contents of the
system
memory when Windows XP or Windows stops unexpectedly. For more
information
about the different types of memory dumps available, see Specify what
happens when the system stops unexpectedly.
Hibernation PartitionIndicates that the volume is an original
equipment
manufacturer (OEM) hibernation partition, which is used on some
laptops to
save the current state of the system during hibernation. For more
information about hibernation, see Managing power on a portable
computer.
GPT Protective PartitionOn x86-based computers, indicates that the
volume is
a GUID partition table (GPT) disk. The GPT Protective Partition
contains the
Protective MBR to prevent disk utilities on x86-based computers from
accidentally destroying GPT partitions.
EFI System PartitionIndicates that the volume is the Extensible
Firmware
Interface (EFI) system partition on a GPT disk.
EISA ConfigurationIndicates that the volume is an original equipment
manufacturer (OEM) partition.
Unknown PartitionIndicates that the partition is not recognized.
Partitions on master boot record (MBR) or GUID partition table (GPT)
disks
with Healthy (Unknown Partition) status might be an unrecognized
original
equipment manufacturer (OEM) partition, OEM partition, or non-Windows
operating system partition. You cannot format, assign drive letters or
mount
points to, or access data on partitions with Healthy (Unknown
Partition)
status. You can, however, delete these partitions using Disk
Management or
the DiskPart command. For instructions describing how to delete
partitions,
see To delete a partition or logical drive.
At RiskIndicates that the dynamic volume is currently accessible, but
I/O
errors have been detected on the underlying dynamic disk. If an I/O
error is
detected on any part of a dynamic disk, all volumes on the disk
display the
Healthy (At Risk) status and a warning icon appears on the volume.
When the volume status is Healthy (At Risk), an underlying disk's
status is
usually Online (Errors). You should reactivate the underlying disk to
return
it to Online status, and then the volume should return to the Healthy
status. If the Healthy (At Risk) status persists, the disk might be
failing.
Back up the data and replace the disk as soon as possible.
For instructions describing how to fix volumes with Healthy (At Risk)
status, see Troubleshooting
