Here's my current setup:

 

Asus Z87-A ATX Motherboard - LGA1150

Intel Core i5-4570 Processor - Quad Core, 6MB L3 Cache, 3.2GHz

Kingston HyperX 16GB Kit 2 x 8GB 1600MHz DDR3

(5) Seagate 3TB Desktop HDD SATA 6Gb/s 64MB Cache 3.5-Inch Internal Bare Drive (ST3000DM001)

Toshiba 3.5-Inch 3TB 7200 RPM SATA3/SATA 6.0 GB/s 64MB Hard Drive DT01ACA300 (Parity) 

unRaid Pro 6.7.0

 

I have had the server up and running in it's current config for about 4 years. The only changes made were software updates and I replaced one bad drive about 2-3 years ago. Over the last few months, I've been running into a lot of issues. It started with the system just generally slowing down. While watching stuff on Plex, the files would freeze or stop altogether and I would have to restart Plex. The same thing with my HDHomerun DVR. When I would try to reboot the server, it would get stuck on stopping the services and I would have to hard reboot. Then I started getting overheating errors on startup, but all the fans are working properly. Now when the system starts, I'm getting SMART errors on the screen and one of my disks says "Device is disabled, contents emulated". I removed it from the array and then added it back to do a rebuild. That took 11 days and ended up with the same result. 

 

I'm at a bit of a loss as I'm not sure what to check first. I assume the one disk will need to be replaced, but I don't want to do that until I've fixed whatever else is wrong. I've attached the diagnostics file, any help provided would be greatly appreciated. 

server-pc-diagnostics-20190609-1417.zip

Your syslog is flooded with errors relating to the disk with serial number ending in 4MMQ.  There is no SMART information available so it looks like it has dropped offline.   Disk ending with serial ending DK6A also appears to be offline.   It might be worth rebooting to see if these drives come back online so a SMART report can be obtained for them and then providing new diagnostics.

 

Not directly related but you seem to have a User Share called 'disk1'.   Unraid would not let you create a share with this name via the GUI so you probably did it inadvertently by creating a folder with that name on one of your drives (all top level folders are automatically considered to be User Shares) while doing a copy.

 

 

As disks already 3 or 4 years old, it may be main cause.