Hi all i am new to unraid & still learning. I have a problem i hope someone can help with, Fix common problems has detected an error which reads

Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged.

i have installed mcelog but do not know how to get the log to post on the forum.

any help would be appreciated.

Edited April 27, 20206 yr by Zedd

Tools - Diagnostics.  Post entire zip file here

tower-diagnostics-20200425-1358.zip

 

zip file above thanks

Apr 25 11:57:57 Tower root: Hardware event. This is not a software error.
Apr 25 11:57:57 Tower root: MCE 0
Apr 25 11:57:57 Tower root: CPU 3 BANK 0 TSC 7fce9dfb56 
Apr 25 11:57:57 Tower root: TIME 1587811657 Sat Apr 25 11:47:37 2020
Apr 25 11:57:57 Tower root: MCG status:
Apr 25 11:57:57 Tower root: MCi status:
Apr 25 11:57:57 Tower root: Corrected error
Apr 25 11:57:57 Tower root: Error enabled
Apr 25 11:57:57 Tower root: MCA: Internal parity error
Apr 25 11:57:57 Tower root: STATUS 9000004000010005 MCGSTATUS 0
Apr 25 11:57:57 Tower root: MCGCAP c09 APICID 6 SOCKETID 0 
Apr 25 11:57:57 Tower root: MICROCODE 21

Quick googling suggests that it's either because of an overclock, or is a known issue with your CPU (ie: ignore)

 

You should also power down and reseat the cabling to your Corsair SSD

Apr 25 13:16:58 Tower kernel: ata3.00: failed command: WRITE FPDMA QUEUED
Apr 25 13:16:58 Tower kernel: ata3.00: cmd 61/00:90:b0:9e:66/06:00:01:00:00/40 tag 18 ncq dma 786432 out
Apr 25 13:16:58 Tower kernel:         res 40/00:88:b0:94:66/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
Apr 25 13:16:58 Tower kernel: ata3.00: status: { DRDY }
Apr 25 13:16:58 Tower kernel: ata3: hard resetting link
Apr 25 13:16:58 Tower kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

 

Thanks Squid, I have the setting in unraid set to performance but will check my bios to make sure overclocking is turned off, i think i am having issues with my parity drive and errors but am thinking that is a cable as well going to invest in some new better quality cables.

 

you mentioned my cable to cache drive, I am getting errors on a parity check but when I redo the check the error count is different, do you think this is a cable issue as well? I would have thought a faulty sector would stay faulty.

tower-diagnostics-20200427-1025

I thought you might ask, I think file is attached.

Tried again

tower-diagnostics-20200427-1025.zip

Apparent connections issues with cache2, replace cables.

Errors on parity also look like a power/connection issue, it dropped offline.

ok thanks, have some new cables ordered after Squid mentioned cache & cable.