Replace member errors
NOTE: For more information about the Replace Member features, see Conguring hot spare.
Source disk fails during replace member operation
Issue: The source disk fails during the Replace Member operation.
Corrective Action: If the source data is available from other disks in the virtual disk, the rebuild begins automatically on the target disk,
using the data from the other disks.
Target disk fails
Issue: The target disk fails.
Corrective Action: If the target disk fails, the Replace Member operation aborts.
General disk fails
Issue:
A general disk fails.
Corrective Action: If the target disk fails and the Replace Member operation aborts but the source data is still available, then the
Replace Member operation continues as Replace Member.
Linux operating system errors
Virtual disk policy is assumed as write-through error message
Error:
<Date:Time> <HostName> kernel: sdb: asking for cache data failed<Date:Time>
<HostName> kernel: sdb: assuming drive cache: write through
Corrective Action: The error message is displayed when the Linux Small Computer System Interface (SCSI) mid-layer asks for
physical disk cache settings. The controller rmware manages the virtual disk cache settings on a per controller
and a per virtual disk basis, so the rmware does not respond to this command. The Linux SCSI mid-layer assumes
that the virtual disk's cache policy is Write-Through. SDB is the device node for a virtual disk. This value changes
for each virtual disk.
For more information about Write-Through cache, see Virtual Disk Write Cache Policies.
Except for this message, there is no eect of this behavior on normal operation. The cache policy of the virtual disk
and the I/O throughput are not aected by this message. The cache policy settings for the PERC SAS RAID
system remain unchanged.
72 Troubleshooting