Array locked up tonight (dockers running on a WD 500GB all froze, however the array shows good health and two new disks are clearing just fine).  I have the WD 500 mounted with Unassigned Devices.  This is what I'm getting:

 

--

 

root@ffs2:/# tail /var/log/syslog -n 50
Jul 10 04:21:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179340, flush 1, corrupt 0, gen 0
Jul 10 04:21:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:21:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179341, flush 1, corrupt 0, gen 0
Jul 10 04:21:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:21:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179342, flush 1, corrupt 0, gen 0
Jul 10 04:22:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10666560
Jul 10 04:22:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179343, flush 1, corrupt 0, gen 0
Jul 10 04:22:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:22:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179344, flush 1, corrupt 0, gen 0
Jul 10 04:22:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:22:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179345, flush 1, corrupt 0, gen 0
Jul 10 04:22:07 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10666560
Jul 10 04:22:07 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179346, flush 1, corrupt 0, gen 0
Jul 10 04:22:07 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 6821792
Jul 10 04:22:07 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179347, flush 1, corrupt 0, gen 0
Jul 10 04:22:07 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10666560
Jul 10 04:22:07 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179348, flush 1, corrupt 0, gen 0
Jul 10 04:22:07 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 6821792
Jul 10 04:22:07 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179349, flush 1, corrupt 0, gen 0
Jul 10 04:22:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10666560
Jul 10 04:22:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179350, flush 1, corrupt 0, gen 0
Jul 10 04:22:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:22:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179351, flush 1, corrupt 0, gen 0
Jul 10 04:22:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:22:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179352, flush 1, corrupt 0, gen 0
Jul 10 04:23:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10666560
Jul 10 04:23:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179353, flush 1, corrupt 0, gen 0
Jul 10 04:23:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:23:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179354, flush 1, corrupt 0, gen 0
Jul 10 04:23:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:23:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179355, flush 1, corrupt 0, gen 0
Jul 10 04:23:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10666560
Jul 10 04:23:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179356, flush 1, corrupt 0, gen 0
Jul 10 04:23:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:23:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179357, flush 1, corrupt 0, gen 0
Jul 10 04:23:33 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:23:33 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179358, flush 1, corrupt 0, gen 0
Jul 10 04:23:43 ffs2 kernel: scsi_io_completion: 2895 callbacks suppressed
Jul 10 04:23:43 ffs2 kernel: sd 1:0:0:0: [sdj] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Jul 10 04:23:43 ffs2 kernel: sd 1:0:0:0: [sdj] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Jul 10 04:23:43 ffs2 kernel: sd 1:0:0:0: [sdj] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00
Jul 10 04:23:43 ffs2 kernel: sd 1:0:0:0: [sdj] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
Jul 10 04:23:43 ffs2 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Jul 10 04:23:44 ffs2 kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
Jul 10 04:24:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10666560
Jul 10 04:24:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179359, flush 1, corrupt 0, gen 0
Jul 10 04:24:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:24:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179360, flush 1, corrupt 0, gen 0
Jul 10 04:24:03 ffs2 kernel: blk_update_request: I/O error, dev loop0, sector 10665696
Jul 10 04:24:03 ffs2 kernel: BTRFS error (device loop0): bdev /dev/loop0 errs: wr 0, rd 179361, flush 1, corrupt 0, gen 0
 

--

 

I tried to run a SMART test from the GUI and clicking "start" pressed the icon down but then it immediately turn light great again and says "start" (as though the button was pressed but didn't do anything)

 

WD500's share is unavailable, and from the command prompt, "ls" or "cd" to it returns "i/o error."  Drive shows online in the GUI, mounted.....

 

And idea?

Edited July 10, 20178 yr by tucansam

Those are read errors, power down, check cables, reboot and grab a SMART report.

Thanks, I am planning on swapping cables and moving to another SATA port.

 

Problem is I have two new disks clearing in it as we speak.  I don't mind re-starting the clearing, just want to make sure I'm not going to cause issues if I stop the clearing, stop the array, and power down.

It's not a problem to stop the clearing, but it will re-start from the beginning.

It preread is complete, there is a way to skip repeating that step when you restart the preclear.

26 minutes ago, bjp999 said:

It preread is complete, there is a way to skip repeating that step when you restart the preclear.

 

I assumed he's clearing the disks on the array since he didn't mentioned preclearing.