drawde Posted May 12, 2019 Share Posted May 12, 2019 (edited) how concerned should i be? just upgraded to 6.7 a few hours ago, not sure if related but saw these errors in my syslog after CA updated my dockers (usual on sunday AM). May 12 00:19:32 Tower rc.diskinfo[4610]: SIGHUP received, forcing refresh of disks info. May 12 00:19:32 Tower kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. May 12 00:19:32 Tower kernel: Either enable ECC checking or force module loading by setting 'ecc_enable_override'. May 12 00:19:32 Tower kernel: (Note that use of the override may cause unknown side effects.) May 12 00:19:37 Tower kernel: sd 13:0:0:0: [sdb] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 May 12 00:19:37 Tower kernel: sd 13:0:0:0: [sdb] tag#4 CDB: opcode=0x28 28 00 e8 e0 88 00 00 00 08 00 May 12 00:19:37 Tower kernel: print_req_error: I/O error, dev sdb, sector 3907028992 May 12 00:19:37 Tower kernel: sd 13:0:3:0: [sde] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 May 12 00:19:37 Tower kernel: sd 13:0:3:0: [sde] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00 May 12 00:19:37 Tower kernel: print_req_error: I/O error, dev sde, sector 7814036992 May 12 00:19:41 Tower kernel: sd 13:0:1:0: [sdc] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 May 12 00:19:41 Tower kernel: sd 13:0:1:0: [sdc] tag#2 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 be 00 00 00 00 08 00 00 May 12 00:19:41 Tower kernel: print_req_error: I/O error, dev sdc, sector 7814036992 May 12 00:19:46 Tower kernel: sd 13:0:11:0: [sdm] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x00 May 12 00:19:46 Tower kernel: sd 13:0:11:0: [sdm] tag#23 CDB: opcode=0x28 28 00 e8 e0 88 00 00 00 08 00 May 12 00:19:46 Tower kernel: print_req_error: I/O error, dev sdm, sector 3907028992 May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP received, forcing refresh of disks info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:46 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP received, forcing refresh of disks info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:47 Tower rc.diskinfo[4610]: SIGHUP ignored - already refreshing disk info. May 12 00:19:48 Tower rc.diskinfo[4610]: SIGHUP received, forcing refresh of disks info. the webUI does not show any errors though next to any of the disks and all disks are green. the rc.diskinfo and the ECC disabled i've seen before. I don't have ECC ram so i dont think that's something i should care about, and the rc.diskinfo i believe is just the preclear plugin, which i'm not running so i'm not too worried about. mostly the print_req_error I/O error i'm concerned about. it's the same 2 sectors across 4 different drives? May 12 00:19:37 Tower kernel: print_req_error: I/O error, dev sdb, sector 3907028992 May 12 00:19:46 Tower kernel: print_req_error: I/O error, dev sdm, sector 3907028992 May 12 00:19:37 Tower kernel: print_req_error: I/O error, dev sde, sector 7814036992 May 12 00:19:41 Tower kernel: print_req_error: I/O error, dev sdc, sector 7814036992 tower-diagnostics-20190512-0508.zip Edited May 12, 2019 by drawde Quote Link to comment
drawde Posted May 14, 2019 Author Share Posted May 14, 2019 bump for visibility Quote Link to comment
Fiservedpi Posted June 4, 2019 Share Posted June 4, 2019 (edited) All info i have read on that i/o error and bad sectors is pointing to a bad drive/ cable or Try different SATA sockets. It could be a bad SATA controller. Also try checking SATA settings in BIOS. Turn off any legacy, IDE modes. I would advise trying a new SATA cable after BACKING UP!! Edited June 4, 2019 by Fiservedpi 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.