I had 2 read / 2 write errors occur on a disk. The statistics for that drive do not update but writes to that drive are still allowed to proceed via a samba share on a user share.
Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready
Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current]
Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2
Jul 6 23:26:13 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 04 00 40 00 00 08 00
Jul 6 23:26:13 Tower2 kernel: end_request: I/O error, dev sdc, sector 262208
Jul 6 23:26:13 Tower2 kernel: md: disk2 read error
Jul 6 23:26:13 Tower2 kernel: handle_stripe read error: 262144/2, count: 1
Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready
Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current]
Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2
Jul 6 23:26:14 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 04 00 40 00 00 08 00
Jul 6 23:26:14 Tower2 kernel: end_request: I/O error, dev sdc, sector 262208
Jul 6 23:26:14 Tower2 kernel: md: disk2 write error
Jul 6 23:26:14 Tower2 kernel: handle_stripe write error: 262144/2, count: 1
Jul 6 23:26:14 Tower2 kernel: md: recovery thread woken up ...
Jul 6 23:26:14 Tower2 kernel: md: recovery thread has nothing to resync
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current]
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x28: 28 00 00 00 00 c0 00 00 08 00
Jul 6 23:26:15 Tower2 kernel: end_request: I/O error, dev sdc, sector 192
Jul 6 23:26:15 Tower2 kernel: md: disk2 read error
Jul 6 23:26:15 Tower2 kernel: handle_stripe read error: 128/2, count: 1
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Device not ready
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] Sense Key : 0x2 [current]
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] ASC=0x4 ASCQ=0x2
Jul 6 23:26:15 Tower2 kernel: sd 1:0:2:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 00 00 c0 00 00 08 00
Jul 6 23:26:15 Tower2 kernel: end_request: I/O error, dev sdc, sector 192
Jul 6 23:26:15 Tower2 kernel: md: disk2 write error
Jul 6 23:26:15 Tower2 kernel: handle_stripe write error: 128/2, count: 1
Jul 6 23:37:01 Tower2 crond[1148]: ignoring /var/spool/cron/crontabs/root- (non-existent user)
I've read the system should be in a read only mode. This feels like a bug.
Also given this is a test array, what is the best way to "clear" the error without replacing the drive?
EDIT -- and the parity check buttons are gone