This is my 8 year old WD Red drive, so pretty sure it's just going bad, but wanted to get a second opinion.  Errors are below. As far as ejecting the disk out of the raid, what is the best way? Use unbalance or zero out the disk?

 

 
May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635848
May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635856
May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635864
May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635872
May 31 07:34:11 FS kernel: md: disk2 read error, sector=1364635880
May 31 07:34:11 FS kernel: ata5: EH complete
May 31 07:34:21 FS kernel: ata5.00: exception Emask 0x0 SAct 0x8079fd5d SErr 0x0 action 0x0
May 31 07:34:21 FS kernel: ata5.00: irq_stat 0x40000008
May 31 07:34:21 FS kernel: ata5.00: failed command: READ FPDMA QUEUED
May 31 07:34:21 FS kernel: ata5.00: cmd 60/18:80:98:c3:56/03:00:51:00:00/40 tag 16 ncq dma 405504 in
May 31 07:34:21 FS kernel:         res 41/40:00:4f:c5:56/00:00:51:00:00/40 Emask 0x409 (media error) <F>
May 31 07:34:21 FS kernel: ata5.00: status: { DRDY ERR }
May 31 07:34:21 FS kernel: ata5.00: error: { UNC }
May 31 07:34:21 FS kernel: ata5.00: configured for UDMA/133
May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=43s
May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 Sense Key : 0x3 [current]
May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 ASC=0x11 ASCQ=0x4
May 31 07:34:21 FS kernel: sd 5:0:0:0: [sde] tag#16 CDB: opcode=0x88 88 00 00 00 00 00 51 56 c3 98 00 00 03 18 00 00
May 31 07:34:21 FS kernel: I/O error, dev sde, sector 1364641103 op 0x0:(READ) flags 0x0 phys_seg 45 prio class 2
May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641032
May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641040
May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641048
May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641056
May 31 07:34:21 FS kernel: md: disk2 read error, sector=1364641064
 

 

 

 

Edited June 2, 20233 yr by Ati2

It's logged as a disk problem, you can run an extended SMART test to confirm.

Thanks - showing read failure. Working on removing it from the array.