Hello, first post here. Forgive me as I am using 7.0.0beta4 but did not see an OS 7 channel.

I'm a home user moving from QNAP and just setting up my TVS-871 to run unraid.  I have everything set up to start adding some data, so far so good, except when running the Fix Common Problems plugin I get a hardware error.  My SMART checks all show "completed without error" so I'm hoping it's not a hardware issue with the device as I purchased it used.  The error message suggests I share my logs here. See the attached screenshot of the error, screenshot of my installed plugins, and the attached logs.

I haven't updated my signature with the hardware but its a stock QNAP TVS-871 8 bay NAS with a Core i7-4790S processor and 16GB of RAM

 

Any guidance you have is appreciated.  As mentioned, there is no data on this machine yet, I purchased it used recently to be a backup device and unraid sandbox.

tvs-871-diagnostics-20241107-1508.zip

Edited November 8, 20241 yr by HutchG

The errors that Fix Common Problems reports are also visible in the log, so the plugin reports them, but you don't need the plugin for it.

 

As to the errors, Machine check events are events that are reported by the processor. It puts them in a file which you can view by using the terminal or use ssh (if enabled) to the server and type something like

cat /var/log/mcelog

I'm not sure what would show up though, since my machines don't report any errors, and so the file is empty.

If the file doesn't tell you what you need, you can use mcelog to decode it. Again, no idea what it will show. If you do want us to see it, you can dump it in the system log with

mcelog --syslog

and then re-run diagnostics and upload those.

 

Also, the bug-report-forum for pre-releases is here but your issue is a hardware-issue, so unlikely to be related to the unraid version,

Edited November 8, 20241 yr by Wody

Here is a screenshot of the output in terminal and I went ahead and did the mcelog command and re-ran the diagnostics.  

tvs-871-diagnostics-20241108-1238.zip

I have since done a shutdown and restart, and now the error is gone.  Could it have been a random one off?

4 hours ago, HutchG said:

I have since done a shutdown and restart, and now the error is gone.  Could it have been a random one off?

When I posted about this type of issue, I was told to just monitor if more occurred. So far I've only had one on my system.

Thank you