December 30, 20196 yr Unraid device sdh SMART health [9]Warning [CUBE] - power on hours is 50375 I hate to ask, as i'm sure it's obvious, but I can't find the setting to tweak that'll tell unRAID to stop telling me about high power on hours? Also I'm not sure if it's related, but SMART attributes aren't showing correctly at this point for this disk. Note it's an Unassigned device also. It's on the same controller as all the other disks in the system, and they're all showing up with attributes just fine. Thanks! cube-diagnostics-20191230-2333.zip
December 31, 20196 yr If its sdh, then the problem looks to be more that unRaid can't read the attributes and needs to smart controller type to be hp cciss. Since it appears to be an unassigned device, I'd try setting that globally in Disk settings, and then set all the normal disks to be ATA
December 31, 20196 yr Author Did that on day one. unRAID is clearly able to read the attributes, as I've gotten 13 more warnings overnight for the same issue, each time the hour number has incremented by 1.
December 31, 20196 yr Remove attribute ‘9’ in the list of default smart notifications. This causes a notification to send when power on hours change value (each hour)
December 31, 20196 yr Author @bonienl Done. Curious that it all of the sudden started doing it though, as I've had '9' listed there since I put the H240 controller in the machine, and I only started getting warnings last night.
December 31, 20196 yr Author @johnnie.black neither short or extended will run; clicking the button(s) does nothing.
December 31, 20196 yr Community Expert 1 minute ago, sota said: neither short or extended will run; clicking the button(s) does nothing. You can get a smart report on the console with smartctl, but Bonienl already told you what the problem is, no point in monitoring the power on hours attribute.
December 31, 20196 yr Author understood, but i'm still curious as to why now all of the sudden it's decided to "warn" me, and why there isn't a threshold someplace I can alter. also why the Attributes box isn't populating like all the other drives. to be fair I don't know for a fact it was before.
December 31, 20196 yr Community Expert 3 minutes ago, sota said: and why there isn't a threshold someplace I can alter. There might be a threshold on the disk's SMART attribute, hence why I wanted to see the report.
December 31, 20196 yr Author and to add another conundrum to the pile... that drive is now showing a temperature in the dashboard, and ONLY that drive, and ONLY in the dashboard! Main doesn't show any drive temps at all. did someone slip my unRAID box some kind of roofie or something? @johnnie.black Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 167 152 021 Pre-fail Always - 6616 4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 6470 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 051 Old_age Always - 0 9 Power_On_Hours 0x0032 031 031 000 Old_age Always - 50393 10 Spin_Retry_Count 0x0032 100 100 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 57 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 6424 194 Temperature_Celsius 0x0022 123 086 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age Offline - 0
December 31, 20196 yr Community Expert Attribute 9 value is 31, threshold is 00, so no SMART alarm, you were only getting warning because the attribute was changing with each additional hour, no idea why you only start getting notified recently, possibly because Unraid was not reading the attributes correctly before.
Archived
This topic is now archived and is closed to further replies.