md: disk1 write error, sector=38282240

[Dacobi]

I just added a new 4TB disk to my array and started copying over data from an older disk, but now the disk is listed as faulty?

 

in dmesg I get a lot of these errors:

 

[ 7003.883756] md: disk1 write error, sector=38282240

 

What could be causing this error?

[pwm]

Problem with the disk.

Problem with the cable.

Problem with the disk controller.

 

Can you access the disk?

Can you get SMART information for the disk?

Did you remember the first important step - capturing the diagnostics? It helps to post the diagnostics.

[Dacobi]

As far as I can tell data is still being copied onto the drive.

 

Also there are no new errors in dmesg.

 

I'm not sure what you mean, capture diagnostics? 

 

The SMART status in dashboard is green.

[pwm]

Under Tools you have a choice Diagnostics.

There you can download a full diagnostics that can be uploaded to this forum.

 

Besides the SMART status you see in the dashboard, you can click on a disk and there you can download the most recent SMART report for the drive which contains much more information than "red" or "green". There you can also start an extended self-test that will tell the drive to read through all disk surface.

[Dacobi]

The SMART report says:

 

Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

tower-diagnostics-20180626-1630.zip

 

Also, dmesg says

[10281.578855] program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO

[pwm]

Your drive did drop out.

Jun 26 13:59:09 Tower kernel: ata5.00: ATA-10: ST4000DM004-2CV104,             ZFN14998, 0001, max UDMA/133

 

Jun 26 15:54:41 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jun 26 15:54:41 Tower kernel: ata5.00: failed command: FLUSH CACHE EXT
Jun 26 15:54:41 Tower kernel: ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 3
Jun 26 15:54:41 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 26 15:54:41 Tower kernel: ata5.00: status: { DRDY }
Jun 26 15:54:41 Tower kernel: ata5: hard resetting link
Jun 26 15:54:47 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)
Jun 26 15:54:51 Tower kernel: ata5: COMRESET failed (errno=-16)
Jun 26 15:54:51 Tower kernel: ata5: hard resetting link
Jun 26 15:54:57 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)
Jun 26 15:55:01 Tower kernel: ata5: COMRESET failed (errno=-16)
Jun 26 15:55:01 Tower kernel: ata5: hard resetting link
Jun 26 15:55:07 Tower kernel: ata5: link is slow to respond, please be patient (ready=0)
Jun 26 15:55:36 Tower kernel: ata5: COMRESET failed (errno=-16)
Jun 26 15:55:36 Tower kernel: ata5: limiting SATA link speed to 3.0 Gbps
Jun 26 15:55:36 Tower kernel: ata5: hard resetting link
Jun 26 15:55:41 Tower kernel: ata5: COMRESET failed (errno=-16)
Jun 26 15:55:41 Tower kernel: ata5: reset failed, giving up
Jun 26 15:55:41 Tower kernel: ata5.00: disabled

Jun 26 13:59:24 Tower kernel: md: import disk1: (sdc) ST4000DM004-2CV104_ZFN14998 size: 3907018532 

Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269056
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269064
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269072
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269080
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269088
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269096
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269104
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269112
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269120
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269128
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269136
Jun 26 15:55:41 Tower kernel: md: disk1 write error, sector=2084269144

 

It could be an issue with the drive. Or with the cable. Or with the controller card.

 

No smart data from the drive as long as it is disabled.

 

Consider checking the cables and reboot the machine and see if you get contact with the drive.

Then post new diagnostics so we can see fresh SMART data.

[Dacobi]

I changed the SATA cable and now the disk starts again and the array says: rebuilding.

but the disk is still listed as faulty.

 

I've attached the new diagnostics 

 

 

tower-diagnostics-20180628-0236.zip

[JorgeB]

45 minutes ago, Dacobi said:

but the disk is still listed as faulty.

It's not faulty, it's invalid, and that's normal until the rebuild is complete.