Table of Contents
Advertisement
synchronization of the replacement disk, write and read performance are both degraded. A RAID 5
can survive a single disk failure at a time. A RAID 4 can survive a single disk failure at a time if the
disk is not the parity disk.
Disks can fail for many reasons such as the following:
Disk crash
Disk pulled from the system
Drive cable removed or loose
I/O errors
When a disk fails, the RAID removes the failed disk from membership in the RAID, and operates in
a degraded mode until the failed disk is replaced by a spare. Degraded mode is resolved for a single
disk failure in one of the following ways:
Spare Exists: If the RAID has been assigned a spare disk, the MD driver automatically
activates the spare disk as a member of the RAID, then the RAID begins synchronizing (RAID
1) or reconstructing (RAID 4 or 5) the missing data.
No Spare Exists: If the RAID does not have a spare disk, the RAID operates in degraded mode
until you configure and add a spare. When you add the spare, the MD driver detects the RAID's
degraded mode, automatically activates the spare as a member of the RAID, then begins
synchronizing (RAID 1) or reconstructing (RAID 4 or 5) the missing data.
6.5.2 Identifying the Failed Drive
On failure,
determine which device is a problem, use
"removed".
1 Enter the following a a terminal console prompt
mdadm -D /dev/md1
Replace
For example, an
look like this:
blue6:~ # mdadm -D /dev/md1
/dev/md1:
Version : 00.90.03
Creation Time : Sun Jul
Raid Level : raid1
Array Size : 180201024 (171.85 GiB 184.53 GB)
Device Size : 180201024 (171.85 GiB 184.53 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 1
88
SLES 10 SP2: Storage Administration Guide
automatically removes the failed drive as a component device in the RAID array. To
md
with the actual path for your RAID.
/dev/md1
report for a RAID 1 device consisting of
mdadm
2 01:14:07 2006
and look for the device that has been reported as
mdadm
/dev/sda2
and
might
/dev/sdb2
Advertisement
Table of Contents
Troubleshooting
