October 24, 20196 yr This is the error i got from one of my disks Tower kernel: print_req_error: critical medium error, dev sdc, sector 11068416312 what does it mean? I made SMART quick test and everything seems OK! Edited October 24, 20196 yr by livingonline8
October 24, 20196 yr Author I am very sorry here is the diagnostics file tower-diagnostics-20191024-1128.zip
October 24, 20196 yr Community Expert Looks like a connection problem with the SSD, suggest replacing/swapping both cables to rule them out.
October 26, 20196 yr Author But the Disk that has this error is not not an SSD it is Disk 9 not the SSD So, was that a false message ? Edited October 26, 20196 yr by livingonline8
October 26, 20196 yr Community Expert SSD is also having issues, and it was the first to have problems on the syslog, so I didn't look further down, disk9 errors appear to be a disk problem, but they can be intermittent, suggest running an extended SMART test. P.S. there are also hardware errors being detected, possibly bad RAM
October 26, 20196 yr Author 3 hours ago, johnnie.black said: SSD is also having issues, and it was the first to have problems on the syslog, so I didn't look further down, disk9 errors appear to be a disk problem, but they can be intermittent, suggest running an extended SMART test. P.S. there are also hardware errors being detected, possibly bad RAM This is bad !! I know that SSD is having issues and I have brand new one ready for deployment so I am not worried about this, already back-up and replacement process will be performed this coming weekend. But, My worries are related to what you mentioned regarding HardDisk 9 and the RAM. I am running extended SMART test now and I will post the result as soon as it is done Also, you mentioned that there are hardware errors being detected possibly bad RAM. is there a way to verify this? on this same point, could it be a RAM issue caused by a docker such as Emby and not actually a hardware error? I hear that Emby sometimes plays funny with RAM !!
October 26, 20196 yr Community Expert 4 minutes ago, livingonline8 said: could it be a RAM issue caused by a docker such as Emby and not actually a hardware error? No, it's a hardware error, but not clear to me if it's RAM, CPU cache or other thing, but maybe CPU cache. Oct 24 04:40:30 Tower root: Hardware event. This is not a software error. Oct 24 04:40:30 Tower root: MCE 0 Oct 24 04:40:30 Tower root: CPU 8 BANK 18 TSC 304eedb876f36 Oct 24 04:40:30 Tower root: MISC 304a028086 ADDR 1039060f40 Oct 24 04:40:30 Tower root: TIME 1571820660 Wed Oct 23 11:51:00 2019 Oct 24 04:40:30 Tower root: MCG status: Oct 24 04:40:30 Tower root: MCi status: Oct 24 04:40:30 Tower root: Uncorrected error Oct 24 04:40:30 Tower root: MCi_MISC register valid Oct 24 04:40:30 Tower root: MCi_ADDR register valid Oct 24 04:40:30 Tower root: MCA: corrected filtering (some unreported errors in same region) Oct 24 04:40:30 Tower root: Data CACHE Level-2 Data-Read Error Oct 24 04:40:30 Tower root: STATUS ac20000000081136 MCGSTATUS 0 Oct 24 04:40:30 Tower root: MCGCAP 1000c14 APICID 20 SOCKETID 1 Oct 24 04:40:30 Tower root: MICROCODE 718 Oct 24 04:40:30 Tower root: CPUID Vendor Intel Family 6 Model 45 Oct 24 04:40:30 Tower root: Hardware event. This is not a software error. Oct 24 04:40:30 Tower root: MCE 1 Oct 24 04:40:30 Tower root: CPU 0 BANK 18 TSC 318f16d686628 Oct 24 04:40:30 Tower root: MISC 7041034086 ADDR 816c3e380 Oct 24 04:40:30 Tower root: TIME 1571829122 Wed Oct 23 14:12:02 2019 Oct 24 04:40:30 Tower root: MCG status: Oct 24 04:40:30 Tower root: MCi status: Oct 24 04:40:30 Tower root: Uncorrected error Oct 24 04:40:30 Tower root: MCi_MISC register valid Oct 24 04:40:30 Tower root: MCi_ADDR register valid Oct 24 04:40:30 Tower root: MCA: corrected filtering (some unreported errors in same region) Oct 24 04:40:30 Tower root: Data CACHE Level-2 Data-Read Error Oct 24 04:40:30 Tower root: STATUS ac20000000081136 MCGSTATUS 0 Oct 24 04:40:30 Tower root: MCGCAP 1000c14 APICID 0 SOCKETID 0 Oct 24 04:40:30 Tower root: MICROCODE 718 Oct 24 04:40:30 Tower root: CPUID Vendor Intel Family 6 Model 45 Edited October 26, 20196 yr by johnnie.black
October 26, 20196 yr Author Just now, johnnie.black said: No, it's a hardware error: Oct 24 04:40:30 Tower root: Hardware event. This is not a software error. Oct 24 04:40:30 Tower root: MCE 0 Oct 24 04:40:30 Tower root: CPU 8 BANK 18 TSC 304eedb876f36 Oct 24 04:40:30 Tower root: MISC 304a028086 ADDR 1039060f40 Oct 24 04:40:30 Tower root: TIME 1571820660 Wed Oct 23 11:51:00 2019 Oct 24 04:40:30 Tower root: MCG status: Oct 24 04:40:30 Tower root: MCi status: Oct 24 04:40:30 Tower root: Uncorrected error Oct 24 04:40:30 Tower root: MCi_MISC register valid Oct 24 04:40:30 Tower root: MCi_ADDR register valid Oct 24 04:40:30 Tower root: MCA: corrected filtering (some unreported errors in same region) Oct 24 04:40:30 Tower root: Data CACHE Level-2 Data-Read Error Oct 24 04:40:30 Tower root: STATUS ac20000000081136 MCGSTATUS 0 Oct 24 04:40:30 Tower root: MCGCAP 1000c14 APICID 20 SOCKETID 1 Oct 24 04:40:30 Tower root: MICROCODE 718 Oct 24 04:40:30 Tower root: CPUID Vendor Intel Family 6 Model 45 Oct 24 04:40:30 Tower root: Hardware event. This is not a software error. Oct 24 04:40:30 Tower root: MCE 1 Oct 24 04:40:30 Tower root: CPU 0 BANK 18 TSC 318f16d686628 Oct 24 04:40:30 Tower root: MISC 7041034086 ADDR 816c3e380 Oct 24 04:40:30 Tower root: TIME 1571829122 Wed Oct 23 14:12:02 2019 Oct 24 04:40:30 Tower root: MCG status: Oct 24 04:40:30 Tower root: MCi status: Oct 24 04:40:30 Tower root: Uncorrected error Oct 24 04:40:30 Tower root: MCi_MISC register valid Oct 24 04:40:30 Tower root: MCi_ADDR register valid Oct 24 04:40:30 Tower root: MCA: corrected filtering (some unreported errors in same region) Oct 24 04:40:30 Tower root: Data CACHE Level-2 Data-Read Error Oct 24 04:40:30 Tower root: STATUS ac20000000081136 MCGSTATUS 0 Oct 24 04:40:30 Tower root: MCGCAP 1000c14 APICID 0 SOCKETID 0 Oct 24 04:40:30 Tower root: MICROCODE 718 Oct 24 04:40:30 Tower root: CPUID Vendor Intel Family 6 Model 45 Ok I get it, It is definitely a hardware issue but why did you suspect it is the RAM and not something else? Is there a way to verify or troubleshoot this to get to the root cause of this error? Regarding HardDisk 9, you said its errors can be intermittent and you suggested running an extended test "which I am doing right now" will this show us what's wrong with it?
October 26, 20196 yr Community Expert 1 minute ago, livingonline8 said: Is there a way to verify or troubleshoot this to get to the root cause of this error? MCE outupt can be rather cryptic, at least for me, but like mentioned above I think it might be bad CPU cache, maybe someone else can point you in the right direction. 2 minutes ago, livingonline8 said: Regarding HardDisk 9, you said its errors can be intermittent and you suggested running an extended test "which I am doing right now" will this show us what's wrong with it? If it fails the extended SMART test it should be replace now, if it passes it's mostly up to you, you can keep using it and monitor for more issues.
October 26, 20196 yr Author 1 minute ago, johnnie.black said: MCE outupt can be rather cryptic, at least for me, but like mentioned above I think it might be bad CPU cache, maybe someone else can point you in the right direction. If it fails the extended SMART test it should be replace now, if it passes it's mostly up to you, you can keep using it and monitor for more issues. Very well, I really cannot thank you enough. Much respect for you and your assistance... Thank you so much I really hope some of the guys here can point me to the right direction regarding the hardware error
Archived
This topic is now archived and is closed to further replies.