8 hours ago, JorgeB said:

Is this disk1 or disk10? No disk10 is assigned and there are no disk related errors on the syslog.

 

Disk11 is failing and needs to be replaced.

I say disk 1(10) because it was disk 10 but now in spot of 1.

I keep getting this error 

Nov  5 14:09:26 bracservultra kernel: ata2.00: status: { DRDY }
Nov  5 14:09:26 bracservultra kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov  5 14:09:26 bracservultra kernel: ata2.00: cmd 60/40:f8:20:70:6b/01:00:05:00:00/40 tag 31 ncq dma 163840 in
Nov  5 14:09:26 bracservultra kernel:         res 40/00:f8:20:70:6b/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
Nov  5 14:09:26 bracservultra kernel: ata2.00: status: { DRDY }
Nov  5 14:09:26 bracservultra kernel: ata2: hard resetting link

 

On me trying to do parity check Disk 1 is disabled What should I do? I swapped the sata cables and y spliter to the hard drive is not hurting another drive?

 

Did some tests it has to be PSU or power splitters.

 

 

New disk in spot with cables of old disk 1 cables

 

Nov  5 15:25:54 bracservultra kernel: Buffer I/O error on dev md10, logical block 0, async page read
Nov  5 15:25:54 bracservultra kernel: Buffer I/O error on dev md10, logical block 0, async page read
Nov  5 15:25:54 bracservultra kernel: ldm_validate_partition_table(): Disk read failed.
Nov  5 15:25:54 bracservultra kernel: Buffer I/O error on dev md10, logical block 0, async page read
Nov  5 15:25:54 bracservultra kernel: md10: unable to read partition table

Nov  5 15:25:54 bracservultra kernel: Buffer I/O error on dev md10, logical block 0, async page read
Nov  5 15:25:54 bracservultra kernel: Buffer I/O error on dev md10, logical block 0, async page read
Nov  5 15:25:54 bracservultra kernel: ldm_validate_partition_table(): Disk read failed.
Nov  5 15:25:54 bracservultra kernel: Buffer I/O error on dev md10, logical block 0, async page read
Nov  5 15:25:54 bracservultra kernel: md10: unable to read partition table

 

 

Kinda clear that that spot of cables ruins the disk right?

Edited November 5, 20223 yr by MrBrac

After long time of pain and suffering I realized it was my IBM sas card , I got another SAS card a LSI and now all errors have ceased on my disks except disk11 which had bad sectors.