After a reboot 2 days ago it automatically started a parity check without my realizing it.  I usually put a desk fan on the enclosure when I choose to run a parity check b/c of heat, thus things overheated & locked-up.  The next day after a reboot disk10 shows red.  And now, in Dynamix gui, it keeps reporting drives overheating even though the drives are cold, and the devices gui shows low temps - see screenshot.

 

I can access disk10's data & the shares just fine through smb.  Also, the section to run a parity check is missing.

 

I've also recently experienced other weird things like the unraid occasionally freezing when coming out of sleep.  All of this couldn't be memory going bad could it?  I haven't run a memtest yet b/c the temp and disk10 issues don't seem like memory-related problems to me.

 

Any help would be greatly appreciated.

system_log.txt

unRAID will always do an automatic parity check if it detects an unclean shutdown. You must stop the array before shutting down or rebooting.

 

You can "read" disk 10 because it is being emulated by reading parity and all of the other drives. unRAID has taken it offline because a write to it failed. You can't do a parity check with a red or missing drive.

 

You should post a complete syslog.

You can set the warning and critical disk temperature thresholds in Settings -> Display Settings

 

Adjust them to a level which is suitable for your environment.

 

To remove (acknowledge) a notification click on its X sign in top right corner.

Thanks, I just adjusted the settings, but what was weird is as you can see in my screenshot, I was getting the temp warning for drives that weren't past that threshold. 

 

Any ideas on why disk10 doesn't show temp & has a red bullet, yet I can access the data just fine?

Any ideas on why disk10 doesn't show temp & has a red bullet, yet I can access the data just fine?

That will be because unRAID has disabled the physical drive due to a write error.  It is currently being emulated using the combination of the other drives plus the parity drive.

 

This means your array is currently running in unprotected mode and if a second drive has problems you will almost certainly get data loss.  You need tom take action to correct the red-balled drive issue ASAP.

 

Thanks, I just adjusted the settings, but what was weird is as you can see in my screenshot, I was getting the temp warning for drives that weren't past that threshold. 

 

Any ideas on why disk10 doesn't show temp & has a red bullet, yet I can access the data just fine?

Disk 10 is not being used by unRAID and spun down drives don't report temperature. See my previous post about why you can access the data and also see this wiki.

 

Disk 10 has failed in some way and we can't really tell you much more without a syslog.

unRAID will always do an automatic parity check if it detects an unclean shutdown. You must stop the array before shutting down or rebooting.

 

I did not realize that, and I bet you are correct that I'd been rebooting w/o stopping the array. 

 

Attached is the syslog.  I'm hoping someone can help me figure out what's wrong with disk10 aside from 'it's dead'.  The problem started after an overheating parity check.

syslog_9-6-2014.txt

Not sure about my false drive temps, but in regard to the failed drive I rebooted the array without the drive, then rebooted again with the same old drive.  Rebuild.  All is good... so far.