Brian Tao wrote:
Why am I seeing problems with a disk that isn't even active? Doesthe Netapp do periodic media checks on the spare drives? I had just added this drive in a couple hours earlier that day, and I've only seen this one occurrence so far.
Fri Aug 8 13:00:00 EDT [isp_main]: Disk 9a.3(0x004e6290): READ sector 0 unit attention (6 29, 0) Fri Aug 8 13:00:00 EDT [isp_main]: Disk 9a.3(0x004e6290): request succeeded after retry #1
The system does an hourly spare check. This coresponds with the time on your error message, 13:00.
Disk 9a.3 can only mean trouble in the future. I recommend getting disk 9a.3 out of your system, but before you pull a drive, call technical support.
Ken.
RAID Disk DISK_ID# HA.SCSI# Used (MB/blks) Phys (MB/blks)
parity 5 9a.1 4000/8192000 4095/8388312 data 1 4 9a.2 4000/8192000 4095/8388312 data 2 0 9b.0 4000/8192000 4095/8388312 data 3 1 9b.1 4000/8192000 4095/8388312 data 4 2 9b.2 4000/8192000 4095/8388312 data 5 3 9b.3 4000/8192000 4095/8388312 data 6 8 9a.4 4000/8192000 4095/8388312 data 7 9 9a.0 4000/8192000 4095/8388312 data 8 6 9b.5 4000/8192000 4095/8388312 data 9 7 9b.4 4000/8192000 4095/8388312 spare 10 9a.3 0 4095/8388312 spare 11 9a.5 0 4095/8388312
-- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"