Trying To Determine If I Have A Hardware Issue

General questions.
Post Reply
nickhammen
Posts: 5
Joined: January 17th, 2015, 5:50 am

Trying To Determine If I Have A Hardware Issue

Post by nickhammen » August 13th, 2018, 3:10 am

Running Core Update 122

Fire Info profile for system information: https://fireinfo.ipfire.org/profile/277 ... 92459085a2

This is an issue that has been occurring since the third week in July. I have a scheduler setting set to reboot every Sunday at 3am (for housekeeping). Lately, when it goes to reboot, it never comes back on its own, so DHCP isn't renewed for resources. If I manually reboot, it comes back fine. I'm seeing entries in the logs that may suggest a hardware issue, but not sure if I'm interpreting it correctly.

DHCP entries from today since rebooting:
Unknown Entries:
reuse_lease: lease age 102 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 103 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 105 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 11 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 2 Time(s)
reuse_lease: lease age 115 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 12 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 131 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 137 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 138 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.58: 1 Time(s)
reuse_lease: lease age 139 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.58: 1 Time(s)
reuse_lease: lease age 1401 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 1409 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 15 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 2 Time(s)
reuse_lease: lease age 1564 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 1580 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 1588 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 159 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 1613 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 1619 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 1659 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 167 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.58: 2 Time(s)
reuse_lease: lease age 171 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 177 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 1777 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 186 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 196 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 21 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 211 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 22 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 221 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 26 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 271 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.51: 1 Time(s)
reuse_lease: lease age 28 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 30 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 37 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 385 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.57: 1 Time(s)
reuse_lease: lease age 386 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.57: 1 Time(s)
reuse_lease: lease age 40 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 46 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 47 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 52 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 54 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 60 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 62 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 67 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 68 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 72 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 74 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 79 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 854 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.62: 1 Time(s)
reuse_lease: lease age 855 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.62: 1 Time(s)
reuse_lease: lease age 86 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 91 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 94 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 966 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)
reuse_lease: lease age 97 (secs) under 25% threshold, reply with unaltered, existing lease for 172.20.20.48: 1 Time(s)

Kernel and Firewall:

WARNING: Kernel Errors Present
res 51/01:01:00:00:00/00:00:00:00:00/a0 Emask 0x9 (media error) ...: 3 Time(s)
ata1.00: error: { AMNF } ...: 3 Time(s)
print_req_error: I/O error, dev ...: 3 Time(s)
sd 0:0:0:0: [sda] tag#1 Sense Key : Medium Error [current] ...: 1 Time(s)
sd 0:0:0:0: [sda] tag#13 Sense Key : Medium Error [current] ...: 1 Time(s)
sd 0:0:0:0: [sda] tag#25 Sense Key : Medium Error [current] ...: 1 Time(s)


lm_sensors output:

soc_dts1-virtual-0
Adapter: Virtual device
temp1: +34.0 C

coretemp-isa-0000
Adapter: ISA adapter
Core 0: +35.0 C (high = +105.0 C, crit = +105.0 C)
Core 1: +35.0 C (high = +105.0 C, crit = +105.0 C)
Core 2: +37.0 C (high = +105.0 C, crit = +105.0 C)
Core 3: +37.0 C (high = +105.0 C, crit = +105.0 C)

it8772-isa-0a40
Adapter: ISA adapter
in0: +2.23 V (min = +0.66 V, max = +2.92 V)
in1: +2.23 V (min = +0.90 V, max = +2.89 V)
in2: +2.20 V (min = +3.02 V, max = +2.88 V) ALARM
+3.3V: +3.34 V (min = +4.20 V, max = +4.58 V) ALARM
in4: +2.02 V (min = +2.66 V, max = +2.56 V) ALARM
in5: +2.02 V (min = +2.00 V, max = +2.36 V)
in6: +2.23 V (min = +1.24 V, max = +1.80 V) ALARM
3VSB: +3.31 V (min = +3.31 V, max = +4.92 V) ALARM
Vbat: +3.26 V
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
temp1: -8.0 C (low = -128.0 C, high = +127.0 C) sensor = thermistor
temp2: -8.0 C (low = -128.0 C, high = +127.0 C) sensor = thermistor
temp3: -8.0 C (low = +48.0 C, high = +127.0 C) sensor = thermistor
intrusion0: ALARM

soc_dts0-virtual-0
Adapter: Virtual device
temp1: +34.0 C

SMART SDA:
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.14.50-ipfire] (IPFire 2.19)
Copyright (C) 2002-16 Bruce Allen Christian Franke www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: HYPERDISK SSD
Serial Number: 140900000302
Firmware Version: 20131001
User Capacity: 63 350 767 616 bytes [63.3 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6 1.5 Gb/s (current: 1.5 Gb/s)
Local Time is: Sun Aug 12 22:08:38 2018 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x0000 100 100 050 Old_age Offline - 0
5 Reallocated_Sector_Ct 0x0002 100 100 050 Old_age Always - 0
12 Power_Cycle_Count 0x0000 100 100 050 Old_age Offline - 19
160 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 0
161 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 169
162 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 129
163 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 15
164 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 1959416
165 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 979
166 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 912
167 Unknown_Attribute 0x0000 100 100 050 Old_age Offline - 947
192 Power-Off_Retract_Count 0x0000 100 100 050 Old_age Offline - 0
194 Temperature_Celsius 0x0000 100 100 000 Old_age Offline - 40 (Min/Max 40/40)
195 Hardware_ECC_Recovered 0x0000 100 100 050 Old_age Offline - 75
196 Reallocated_Event_Count 0x0000 100 100 050 Old_age Offline - 0
198 Offline_Uncorrectable 0x0000 000 000 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0000 100 100 050 Old_age Offline - 0
241 Total_LBAs_Written 0x0032 100 100 050 Old_age Always - 109124
242 Total_LBAs_Read 0x0032 100 100 050 Old_age Always - 2182


I'm in the process of checking on /var/log files, but haven't got those yet. Let me know if you need me to post anything specific.

silverknight
Posts: 15
Joined: June 27th, 2010, 2:01 pm

Re: Trying To Determine If I Have A Hardware Issue

Post by silverknight » August 13th, 2018, 11:32 pm

nickhammen wrote:
August 13th, 2018, 3:10 am

Kernel and Firewall:

WARNING: Kernel Errors Present
res 51/01:01:00:00:00/00:00:00:00:00/a0 Emask 0x9 (media error) ...: 3 Time(s)
ata1.00: error: { AMNF } ...: 3 Time(s)
print_req_error: I/O error, dev ...: 3 Time(s)
sd 0:0:0:0: [sda] tag#1 Sense Key : Medium Error [current] ...: 1 Time(s)
sd 0:0:0:0: [sda] tag#13 Sense Key : Medium Error [current] ...: 1 Time(s)
sd 0:0:0:0: [sda] tag#25 Sense Key : Medium Error [current] ...: 1 Time(s)

Thus far it looks like some trouble with the solid state drive. If the SMART test you posted wasn't run recently give it a fresh test and shoot us the results.

nickhammen
Posts: 5
Joined: January 17th, 2015, 5:50 am

Re: Trying To Determine If I Have A Hardware Issue

Post by nickhammen » September 13th, 2018, 2:00 pm

Roger that. I'll run a manual SMART test to see what I can find out. My gut is telling me the same thing since it's throwing several new errors to my syslog server, so I believe that the SSD is malfunctioning. I'll make a full backup and run a SMART test, but I'm also going to get a new drive en route just in case.

silverknight
Posts: 15
Joined: June 27th, 2010, 2:01 pm

Re: Trying To Determine If I Have A Hardware Issue

Post by silverknight » September 16th, 2018, 12:51 am

Try replacing your SATA cable too, they don't fail often but it happens.

Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests