Recently got a "new" used Seagate exos x14 to upgrade an ancient disk I was using. SMART extended test shows it is perfectly fine and I'm sort of at a loss on how to proceed with getting this drive into my array. I saw there was an issue with seagate drives and LSI controllers that started in 6.9 but the fixes there didnt fix this issue along with trying my onboard sata ports as well as externally over USB so I ruled that issue out. 

 

Quote

Jan  5 19:52:04 SERVER kernel: sd 9:0:3:0: [sdi] tag#156 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jan  5 19:52:04 SERVER kernel: sd 9:0:3:0: [sdi] tag#156 Sense Key : 0xb [current] 
Jan  5 19:52:04 SERVER kernel: sd 9:0:3:0: [sdi] tag#156 ASC=0x0 ASCQ=0x0 
Jan  5 19:52:04 SERVER kernel: sd 9:0:3:0: [sdi] tag#156 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 0c 40 00 00 04 00 00 00
Jan  5 19:52:04 SERVER kernel: I/O error, dev sdi, sector 3136 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 0
Jan  5 19:52:04 SERVER kernel: md: disk5 write error, sector=3072

 

server-diagnostics-20230105-1936.zip

Looks more like a power/connection problem, try replacing/swapping cables/slot.

Sorry for not mentioning the multiple things I’ve tried already it’s been like a week of just trying anything I can thing of and my brain is no longer functioning. Cable swapping is something I’ve already tried along with even swapping power supplies. Same result. The only way I’ve been able to get data on and off the drive is by formatting it in Windows to NTFS and mounting as an unassigned device. No errors when it comes to that.

4 minutes ago, Kashikura said:

things I’ve tried already

nevertheless

 

4 hours ago, JorgeB said:

Looks more like a power/connection problem, try replacing/swapping cables/slot.

 

Not currently near my server to try. Will do it again just to go through troubleshooting steps as suggested. 
 

I still must inquire. But per my last message. With the drive formatted as NTFS it is perfectly functioning. Without touching anything physically and only clearing the drive and assigning it into the array to be formatted as XFS it throws a fit using the same cables/bay.

You can also try connecting that disk to an onboard SATA port, swap with another, it might not like the LSI.

Different sata cables, different slots, onboard or LSI. All resulting in same errors.

I setup a new unraid install on a different flash drive and the drive in its own array seems to be working perfectly fine in that. Could it be something to do with my current install? 

Seems unlikely, but you can try starting over to rule that out.

So steps ive taken since.

Removed the small amount of data off the emulated drive so i can shrink my array and get that headache of a missing disk out of the way.

Made a new config to rebuild parity without the missing drive.

Added the new drive to that new config; same error ive been getting.

Added this valid array to the new clean unraid usb 

Added new drive to that array; no error at all.

 

Currently waiting for the drive to clear inside the array but so far so good.

Zeroed fine but looks like right after it finished/at the end it threw up a different error this time.

Quote

Jan  9 04:39:20 Tower kernel: ata3.00: exception Emask 0x1 SAct 0x7f00000 SErr 0x0 action 0x6 frozen
Jan  9 04:39:20 Tower kernel: ata3.00: irq_stat 0x40000008
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:a0:00:cf:fb/05:00:74:05:00/40 tag 20 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY }
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:a8:40:d4:fb/05:00:74:05:00/40 tag 21 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY }
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:b0:80:d9:fb/05:00:74:05:00/40 tag 22 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY }
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/80:b8:c0:de:fb/00:00:74:05:00/40 tag 23 ncq dma 65536 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY }
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:c0:40:df:fb/05:00:74:05:00/40 tag 24 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY }
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:c8:80:e4:fb/05:00:74:05:00/40 tag 25 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY }
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:d0:c0:e9:fb/05:00:74:05:00/40 tag 26 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY }
Jan  9 04:39:20 Tower kernel: ata3: hard resetting link
Jan  9 04:39:20 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: configured for UDMA/133
Jan  9 04:39:20 Tower kernel: ata3: EH complete
Jan  9 04:39:20 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x8080001e SErr 0x0 action 0x0
Jan  9 04:39:20 Tower kernel: ata3.00: irq_stat 0x40000008
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:10:80:d9:fb/05:00:74:05:00/40 tag 2 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY SENSE ERR }
Jan  9 04:39:20 Tower kernel: ata3.00: error: { ABRT }
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: configured for UDMA/133
Jan  9 04:39:20 Tower kernel: ata3: EH complete
Jan  9 04:39:20 Tower kernel: ata3.00: exception Emask 0x0 SAct 0xfc000 SErr 0x0 action 0x0
Jan  9 04:39:20 Tower kernel: ata3.00: irq_stat 0x40000008
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:90:80:d9:fb/05:00:74:05:00/40 tag 18 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY SENSE ERR }
Jan  9 04:39:20 Tower kernel: ata3.00: error: { ABRT }
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: configured for UDMA/133
Jan  9 04:39:20 Tower kernel: ata3: EH complete
Jan  9 04:39:20 Tower kernel: ata3.00: NCQ disabled due to excessive errors
Jan  9 04:39:20 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x8400000f SErr 0x0 action 0x0
Jan  9 04:39:20 Tower kernel: ata3.00: irq_stat 0x40000008
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 61/40:d0:80:d9:fb/05:00:74:05:00/40 tag 26 ncq dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY SENSE ERR }
Jan  9 04:39:20 Tower kernel: ata3.00: error: { ABRT }
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: configured for UDMA/133
Jan  9 04:39:20 Tower kernel: ata3: EH complete
Jan  9 04:39:20 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  9 04:39:20 Tower kernel: ata3.00: irq_stat 0x40000001
Jan  9 04:39:20 Tower kernel: ata3.00: failed command: WRITE DMA EXT
Jan  9 04:39:20 Tower kernel: ata3.00: cmd 35/00:40:80:d9:fb/00:05:74:05:00/e0 tag 13 dma 688128 out
Jan  9 04:39:20 Tower kernel: ata3.00: status: { DRDY SENSE ERR }
Jan  9 04:39:20 Tower kernel: ata3.00: error: { ABRT }
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:20 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:21 Tower kernel: ata3.00: configured for UDMA/133
Jan  9 04:39:21 Tower kernel: ata3: EH complete
Jan  9 04:39:21 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan  9 04:39:21 Tower kernel: ata3.00: irq_stat 0x40000001
Jan  9 04:39:21 Tower kernel: ata3.00: failed command: WRITE DMA EXT
Jan  9 04:39:21 Tower kernel: ata3.00: cmd 35/00:40:80:d9:fb/00:05:74:05:00/e0 tag 7 dma 688128 out
Jan  9 04:39:21 Tower kernel: ata3.00: status: { DRDY SENSE ERR }
Jan  9 04:39:21 Tower kernel: ata3.00: error: { ABRT }
Jan  9 04:39:21 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:21 Tower kernel: ata3.00: supports DRM functions and may not be fully accessible
Jan  9 04:39:21 Tower kernel: ata3.00: configured for UDMA/133
Jan  9 04:39:21 Tower kernel: sd 3:0:0:0: [sde] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=31s
Jan  9 04:39:21 Tower kernel: sd 3:0:0:0: [sde] tag#7 Sense Key : 0x5 [current] 
Jan  9 04:39:21 Tower kernel: sd 3:0:0:0: [sde] tag#7 ASC=0x21 ASCQ=0x4 
Jan  9 04:39:21 Tower kernel: sd 3:0:0:0: [sde] tag#7 CDB: opcode=0x8a 8a 00 00 00 00 05 74 fb d9 80 00 00 05 40 00 00
Jan  9 04:39:21 Tower kernel: I/O error, dev sde, sector 23437498752 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0
Jan  9 04:39:21 Tower kernel: ata3: EH complete

 

tower-diagnostics-20230109-1640.zip

If cables/controller don't help looks to me like a disk problem.