I was just messing with my array, adding a new disk (which is pre-clearing now) and when I rebooted I was met with two notifications signifying issues. I'm not sure how concerned I should be with these issues.

 

1. "unRAID Cache disk SMART health [235] Warning: unknown attribute is 4 Samsung_SSD_840_EVO_250GB_S1DBNSBF492450T (sdg)" this is my cache... I guess the weird thing is this is an unknown attribute, so something seems wrong here.

 

2. "unRAID Disk 3 SMART health [188] Warning: command timeout is 4295032833 ST3000VN000-1HJ166_W7300KT7 (sde)" This is more concerning as a data disk... but what's confusing to me is that the disk seems responsive and is accessible just fine.

 

How concerned should I be, and any ideas what might be up with the first notice?

 

Also a few more notes, this is my only Seagate, and none of my other drives even have Attribute 188 listed... is that unusual?

 

 

Attribute #235 isn't actually monitored.  There's been a new release of the monitor program to fix that issue until a new version of the GUI is released.  You can find it here: http://lime-technology.com/forum/index.php?topic=37817.msg349980#msg349980

 

Command timeout (188) - The raw value that is being reported is pretty much useless to diagnose anything, as its a vendor specific value.  Whenever unRaid reboots, it emails the current value of 5 different attributes, and then only emails again if those attributes increase.

 

On that attribute, you want to make sure that the "Worst" reported value is not close to the "Threshold" value.

Attribute #235 isn't actually monitored.  There's been a new release of the monitor program to fix that issue until a new version of the GUI is released.  You can find it here: http://lime-technology.com/forum/index.php?topic=37817.msg349980#msg349980

 

Command timeout (188) - The raw value that is being reported is pretty much useless to diagnose anything, as its a vendor specific value.  Whenever unRaid reboots, it emails the current value of 5 different attributes, and then only emails again if those attributes increase.

 

On that attribute, you want to make sure that the "Worst" reported value is not close to the "Threshold" value.

 

Thanks for the info. On Command timeout (188) the "Worst" matches the "Value" (100,100) but neither match the Threshold of 000, so I guess I don't really need to be concerned.

 

Attribute #235 isn't actually monitored.  There's been a new release of the monitor program to fix that issue until a new version of the GUI is released.  You can find it here: http://lime-technology.com/forum/index.php?topic=37817.msg349980#msg349980

 

Command timeout (188) - The raw value that is being reported is pretty much useless to diagnose anything, as its a vendor specific value.  Whenever unRaid reboots, it emails the current value of 5 different attributes, and then only emails again if those attributes increase.

 

On that attribute, you want to make sure that the "Worst" reported value is not close to the "Threshold" value.

 

Thanks for the info. On Command timeout (188) the "Worst" matches the "Value" (100,100) but neither match the Threshold of 000, so I guess I don't really need to be concerned.

 

Yeah.  Just ignore the initial emails after a reboot and then see if any more show up.  Thats when to start getting worried.