martinf Posted January 1, 2020 Share Posted January 1, 2020 (edited) Over Xmas, I built a new server. Cache is based on two ssd. SSD have given me problems since start. Smart indicated cable and or controller problem so I replaced data cable and changed sata port. Since then, it has not fallen off / disappeared, require reboot. Yet, I see errors in the log. Some info from syslog below. Thoughts, comments? Cheers Martin Jan 2 06:28:25 Tower kernel: ata8.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 12 Jan 2 06:28:25 Tower kernel: res 51/04:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error) Jan 2 06:28:25 Tower kernel: ata8.00: status: { DRDY ERR } Jan 2 06:28:25 Tower kernel: ata8.00: error: { ABRT } Jan 2 06:28:25 Tower kernel: ata8.00: configured for UDMA/133 Jan 2 06:28:25 Tower kernel: ata8.00: device reported invalid CHS sector 0 Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 Sense Key : 0x5 [current] Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 ASC=0x21 ASCQ=0x4 Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jan 2 06:28:25 Tower kernel: print_req_error: I/O error, dev sdf, sector 0 Jan 2 06:28:25 Tower kernel: ata8: EH complete Jan 2 06:53:39 Tower root: Fix Common Problems Version 2019.12.29 Jan 2 06:53:44 Tower root: Fix Common Problems Version 2019.12.29 Jan 2 06:53:47 Tower root: Fix Common Problems: Other Warning: Unassigned Devices Plus installed ** Ignored Jan 2 06:53:52 Tower root: Fix Common Problems: Other Warning: Unassigned Devices Plus installed ** Ignored Jan 2 07:32:27 Tower kernel: md: sync done. time=27146sec Jan 2 07:32:27 Tower kernel: md: recovery thread: exit status: 0 Jan 2 07:47:28 Tower kernel: mdcmd (54): spindown 0 Jan 2 07:47:29 Tower kernel: mdcmd (55): spindown 1 Jan 2 08:29:47 Tower kernel: mdcmd (56): spindown 0 Jan 2 08:29:47 Tower kernel: mdcmd (57): spindown 1 Jan 2 09:50:16 Tower kernel: usb 4-1: USB disconnect, device number 3 Jan 2 10:02:04 Tower kernel: mdcmd (58): spindown 0 Jan 2 10:10:12 Tower kernel: mdcmd (59): spindown 1 Jan 2 10:23:26 Tower kernel: btrfs_print_data_csum_error: 1071 callbacks suppressed Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7954432 csum 0xcfa10387 expected csum 0xe6b460b2 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7946240 csum 0x98cedc4c expected csum 0xcef63324 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7974912 csum 0x99ae0a4a expected csum 0xd39032bb mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7999488 csum 0x2f10fcd8 expected csum 0x269a3145 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7987200 csum 0xae91e6ab expected csum 0xcb613bf9 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7983104 csum 0x68af43b8 expected csum 0xb07935f4 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7933952 csum 0x610e459b expected csum 0x26a6cb07 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7950336 csum 0x6b4f16fc expected csum 0x60526509 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7995392 csum 0xa9138887 expected csum 0xba2194d2 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7979008 csum 0x5edf42d6 expected csum 0xcdf3b158 mirror 1 Jan 2 10:23:26 Tower kernel: repair_io_failure: 524 callbacks suppressed Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7946240 (dev /dev/mapper/sde1 sector 87499880) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7974912 (dev /dev/mapper/sde1 sector 87500040) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7999488 (dev /dev/mapper/sde1 sector 87501016) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7933952 (dev /dev/mapper/sde1 sector 87501608) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7954432 (dev /dev/mapper/sde1 sector 87501648) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7950336 (dev /dev/mapper/sde1 sector 87502064) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7995392 (dev /dev/mapper/sde1 sector 87502280) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7979008 (dev /dev/mapper/sde1 sector 87500968) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7929856 (dev /dev/mapper/sde1 sector 87502128) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7991296 (dev /dev/mapper/sde1 sector 87503968 Edited January 1, 2020 by martinf Quote Link to comment
JWMutant Posted January 1, 2020 Share Posted January 1, 2020 Faulty port on your board? Have you tried plugging it in a different port to see if you get the same read error's? Quote Link to comment
martinf Posted January 1, 2020 Author Share Posted January 1, 2020 Different port on expansion card. Will move to a motherboard port. Quote Link to comment
FreeMan Posted January 1, 2020 Share Posted January 1, 2020 Also, once you've moved the drives, post the complete diagnostics, not just a "relevant snippet". Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.