Array problems

[kysdaddy]

Hello all,

My system has been working pretty well for a while, thanks to this group. However I have noticed that my array does not seem to be filling up in the manner that I thought it was supposed to. the first Five 4tb drives filled up to 50% one after another. The next two 2tb drives filled to 500gb each and the next drive a 6tb drive has filled 4.46 tb so far.... this does not seem logical to me. Simple question is am I over thinking it?

 

I also have drive 12 that showed up with 78 errors this AM, I am not real familiar with Smart errors, Do I need to pull that drive or is there anything I can do to correct the errors.

I am attaching the diagnostic.

 

Thank you in advance for your help

Chas

tower-diagnostics-20200412-0821.zip

[JorgeB]

Unlikely to be a disk problem since just before the read errors there where issues with multiple disks:
 

Apr 11 13:15:45 Tower kernel: sd 4:0:1:0: [sdi] tag#93 Sense Key : 0x1 [current]
Apr 11 13:15:45 Tower kernel: sd 4:0:1:0: [sdi] tag#93 ASC=0x18 ASCQ=0x7
Apr 11 14:24:19 Tower kernel: sd 4:0:1:0: [sdi] tag#28 Sense Key : 0x1 [current]
Apr 11 14:24:19 Tower kernel: sd 4:0:1:0: [sdi] tag#28 ASC=0x18 ASCQ=0x7
Apr 11 15:19:49 Tower kernel: sd 4:0:1:0: [sdi] tag#27 Sense Key : 0x1 [current]
Apr 11 15:19:49 Tower kernel: sd 4:0:1:0: [sdi] tag#27 ASC=0x18 ASCQ=0x7
Apr 11 15:34:50 Tower kernel: sd 4:0:1:0: [sdi] tag#20 Sense Key : 0x1 [current]
Apr 11 15:34:50 Tower kernel: sd 4:0:1:0: [sdi] tag#20 ASC=0x18 ASCQ=0x7
Apr 11 15:34:51 Tower kernel: sd 4:0:1:0: [sdi] tag#18 Sense Key : 0x1 [current]
Apr 11 15:34:51 Tower kernel: sd 4:0:1:0: [sdi] tag#18 ASC=0x18 ASCQ=0x2
Apr 11 15:41:34 Tower kernel: sd 4:0:1:0: [sdi] tag#66 Sense Key : 0x1 [current]
Apr 11 15:41:34 Tower kernel: sd 4:0:1:0: [sdi] tag#66 ASC=0x18 ASCQ=0x7
Apr 11 15:41:50 Tower kernel: sd 4:0:1:0: [sdi] tag#104 Sense Key : 0x1 [current]
Apr 11 15:41:50 Tower kernel: sd 4:0:1:0: [sdi] tag#104 ASC=0x18 ASCQ=0x7
Apr 11 15:42:02 Tower kernel: sd 4:0:1:0: [sdi] tag#96 Sense Key : 0x1 [current]
Apr 11 15:42:02 Tower kernel: sd 4:0:1:0: [sdi] tag#96 ASC=0x18 ASCQ=0x7
Apr 11 15:54:02 Tower kernel: sd 4:0:11:0: [sds] tag#28 Sense Key : 0x1 [current]
Apr 11 15:54:02 Tower kernel: sd 4:0:11:0: [sds] tag#28 ASC=0x18 ASCQ=0x7
Apr 11 15:54:02 Tower kernel: sd 4:0:11:0: [sds] tag#120 Sense Key : 0x1 [current]
Apr 11 15:54:02 Tower kernel: sd 4:0:11:0: [sds] tag#120 ASC=0x18 ASCQ=0x7
Apr 11 15:54:02 Tower kernel: sd 4:0:7:0: [sdo] tag#46 Sense Key : 0x1 [current]
Apr 11 15:54:02 Tower kernel: sd 4:0:7:0: [sdo] tag#46 ASC=0x18 ASCQ=0x7
Apr 11 15:54:02 Tower kernel: sd 4:0:7:0: [sdo] tag#57 Sense Key : 0x1 [current]
Apr 11 15:54:02 Tower kernel: sd 4:0:7:0: [sdo] tag#57 ASC=0x18 ASCQ=0x7
Apr 11 15:54:03 Tower kernel: sd 4:0:3:0: [sdk] tag#30 Sense Key : 0x1 [current]
Apr 11 15:54:03 Tower kernel: sd 4:0:3:0: [sdk] tag#30 ASC=0x18 ASCQ=0x7
Apr 11 15:54:51 Tower kernel: sd 4:0:7:0: [sdo] tag#118 Sense Key : 0x1 [current]
Apr 11 15:54:51 Tower kernel: sd 4:0:7:0: [sdo] tag#118 ASC=0x18 ASCQ=0x7
Apr 11 16:25:03 Tower kernel: sd 4:0:13:0: [sdu] tag#57 Sense Key : 0x1 [current]
Apr 11 16:25:03 Tower kernel: sd 4:0:13:0: [sdu] tag#57 ASC=0x18 ASCQ=0x7
Apr 11 16:25:18 Tower kernel: sd 4:0:7:0: [sdo] tag#5 Sense Key : 0x1 [current]
Apr 11 16:25:18 Tower kernel: sd 4:0:7:0: [sdo] tag#5 ASC=0x18 ASCQ=0x7
Apr 11 16:25:19 Tower kernel: sd 4:0:11:0: [sds] tag#8 Sense Key : 0x1 [current]
Apr 11 16:25:19 Tower kernel: sd 4:0:11:0: [sds] tag#8 ASC=0x18 ASCQ=0x7
Apr 11 16:33:04 Tower kernel: sd 4:0:1:0: [sdi] tag#96 Sense Key : 0x1 [current]
Apr 11 16:33:04 Tower kernel: sd 4:0:1:0: [sdi] tag#96 ASC=0x18 ASCQ=0x7
Apr 11 16:42:48 Tower kernel: sd 4:0:1:0: [sdi] tag#62 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
Apr 11 16:42:48 Tower kernel: sd 4:0:1:0: [sdi] tag#62 Sense Key : 0x3 [current]
Apr 11 16:42:48 Tower kernel: sd 4:0:1:0: [sdi] tag#62 ASC=0x11 ASCQ=0x0
Apr 11 16:42:48 Tower kernel: sd 4:0:1:0: [sdi] tag#62 CDB: opcode=0x28 28 00 00 4f 89 e8 00 04 00 00
Apr 11 16:42:48 Tower kernel: print_req_error: critical medium error, dev sdi, sector 5213055
Apr 11 16:42:48 Tower kernel: md: disk12 read error, sector=5212984

Check if these disks share anything in common besides the controller, since not all disks there were affected.

[JorgeB]

Ohh, and for the other question see:

https://wiki.unraid.net/Un-Official_UnRAID_Manual#High_Water

 

[kysdaddy]

Nothing in common that I see other than the controller, different manufacturers and different sizes the drives are not consecutively mounted . 

Thank you for the link to High_water, that clears up my misunderstanding.

 

Chas