eb80580794
Merge remote-tracking branch 'upstream/dev' into dev
2019-04-25 19:18:20 -07:00
896f9e4a05
Explicitly define smartctl tolerance levels
...
* Fixes issue #104
2019-04-25 18:37:17 -07:00
a0f4d74656
Merge remote-tracking branch 'upstream/dev' into dev
2019-04-20 18:57:10 -07:00
4d9ab2215b
Ensure SMART values are shown for some disks
...
* smartctl can return non-zero if there are errors in the SMART logs
2019-04-08 18:57:38 -07:00
6a7ef8ebcb
Merge remote-tracking branch 'upstream/dev' into dev
2019-04-02 16:37:09 -07:00
e089dd99a3
Avoid crash when no disks are connected
...
* It was attempting to recheck the NVMe/SMART data for the fake N/A lines
2019-04-02 16:29:09 -07:00
86f81f2720
Prevent updating OVERRIDE to CS
2019-03-16 15:11:42 -06:00
5aeeb41995
Prevent updating OVERRIDE to PASS
2019-03-16 15:09:35 -06:00
d447e694b2
Set NVMe/SMART test to FAIL if safety check fails
...
* Fixes issues #49
2019-03-14 00:22:11 -06:00
8835fb486d
Include ticket ID and name in osTicket posts
...
* Fixes issue #58
2019-03-13 23:01:32 -06:00
c73bf2521c
Include ticket ID and name in top pane
...
* Only if ticket ID and name are set
* Expands on fix for issue #58
2019-03-13 22:49:07 -06:00
4c3fe1d66f
Avoid crash if connection to osTicket fails
2019-03-13 22:26:42 -06:00
b6ecf348d4
Merge remote-tracking branch 'upstream/dev' into dev
2019-03-13 21:00:25 -06:00
34ef0bfae6
Fail test on SMART self-test timeout
2019-03-13 20:22:28 -06:00
c45c1c9225
Merge remote-tracking branch 'upstream/dev' into dev
...
* Fixes issues #54 & #55
2019-03-12 22:45:43 -06:00
122bbfb157
Added debug mode for HW Diagnostics
...
* Uses alternative major exception
* Saves State, CpuObj, and DiskObj data after traceback
* Uploads the whole LogDir folder (compressed) instead of just the main log
2019-03-12 21:24:06 -06:00
7381547b27
Added functions.json
...
* Uses safer method to get JSON data from a command
* Replaced nearly all uses of json.loads with new get_json_from_command()
* Fixes issue #100
2019-03-12 16:08:21 -06:00
480222c1f2
Adjusted variable name usage for consistency
2019-03-12 15:13:16 -06:00
1d10503b91
Support disks over 4TB in badblocks test
...
* Set read block size to 4KB if disk is 4Kn or 3TB+
* Fixes issue #99
2019-03-11 21:00:26 -06:00
e7d31c21c3
Get disk size in bytes during object creation
...
* Also moved dd calc section into docstring
2019-03-11 20:55:24 -06:00
7f6509d235
Return to HW-Diags menu from safety_check()
2019-03-11 13:26:11 -06:00
7701418e55
Recheck disk attributes after all tests
...
* Should catch errors exposed by badblocks
* Addresses issue #96
2019-03-11 13:25:12 -06:00
7078efe9e7
Adjusted SMART self-test running message
2019-03-11 13:23:56 -06:00
a3d2de92bc
Show CS/NS in quick mode if self-test is running
...
* It still shows the slightly ambiguous message "all tests disabled"
* Addresses issue #96
2019-03-11 12:37:01 -06:00
607d4b1e57
Skip SMART self-test in quick mode
...
* Addresses issue #96
2019-03-11 12:36:33 -06:00
6edfcc9766
Moved SMART self-test code to its own function
...
* Allows for a simpler run_nvme_smart_tests()
* Self-test is now done before the attribute check
* Addresses issue #96
2019-03-11 11:57:29 -06:00
40f269aabd
More cleanup for generate_attribute_report()
2019-03-11 10:52:11 -06:00
a5852d1caa
Major overhaul of NVMe/SMART reporting/testing
...
* Moved all errors/warnings to new nvme_smart_notes var
* Allows the notes to be appended to the attribute report much easier
* Allows the attribute report to be updated without losing notes
* NVMe/SMART should only contains the SMART short self-test results
* If available and requested
* Updated safety_check to fix erroneous requests
* Disable tests logic reworked
* Updated generate_disk_report() to include notes
* Addresses issue #96
2019-03-09 21:42:28 -07:00
95aa063a69
Adjusted disk safety checks
...
* check_attributes() is now always silent
* Returns a PASS/FAIL bool
* override_disabled is now at the Disk() scope
* Moved self-test checks to check_smart_self_test()
* Returns a PASS/FAIL bool
* Addressed issue #96
2019-03-09 18:07:04 -07:00
858c2e1bd5
Avoid crash on some Macs
...
* Partially addresses issue #88
* HW damage should be avoided by using the THERMAL_LIMIT setting
2019-03-09 14:15:42 -07:00
d5dc453ffa
Added maximum threshold for NVMe/SMART attributes
...
* Fixes issue #95
2019-03-05 19:36:43 -07:00
e2c83aad6e
Moves HW-Diags settings to separate file
2019-03-05 19:36:41 -07:00
bc4fa92e16
Show ticket ID and name on results screen
...
* Fixes issue #58
2019-02-26 21:49:42 -07:00
3428e9dff8
Merge remote-tracking branch 'upstream/dev' into dev
...
Fixed issue #41
2019-02-05 21:50:50 -07:00
017c0e3385
Avoid marking aborted badblocks test as failed
2019-02-05 21:49:00 -07:00
4245d13375
Stop Prime95 if CoreTemps hit 95*C
2019-02-05 21:39:28 -07:00
7132d971f6
Add temp limit to report
2019-02-05 21:26:27 -07:00
dc6de9cab0
Use consistent labels
2019-02-05 21:25:28 -07:00
a28a754be1
Added thermal limit logic to Prime95 test
2019-02-05 21:08:06 -07:00
c29e84131b
Merge remote-tracking branch 'upstream/dev' into dev
2019-01-15 18:59:11 -07:00
7c7d8e41e2
Prevent crash when testing some NVMe disks
2019-01-15 18:56:29 -07:00
2c87021301
Avoid incorrectly updating osTicket disk checkbox
...
* Only update if disk tests are enabled and disk(s) were detected
* Addresses issue #40
2019-01-15 14:27:32 -07:00
2583358963
Missed a call to stop_tmux_repair_thread()
2019-01-08 19:34:17 -07:00
a839140ff4
Merge remote-tracking branch 'upstream/dev' into dev
2019-01-08 19:25:39 -07:00
ed70d1ab18
Simplified tmux repair thread handling
...
* Just start once and let run until script is exited
* Pretty sure this fixed the 100%+ CPU usage after returning to the menu
2019-01-08 19:18:00 -07:00
1e5f72f79a
Switched to PASS/FAIL instead of CS/NS by request
2019-01-08 15:02:56 -07:00
014da1b224
Fix issue #37
2019-01-07 12:20:48 -07:00
0fcfc4b5ac
Merge remote-tracking branch 'upstream/dev' into dev
2019-01-07 12:12:28 -07:00
7a9474a6a8
Try enabling SMART before checking attributes
...
* Fixes issue #84
2019-01-06 21:51:45 -07:00
68bbee66d5
Replaced hw-diags-badblocks with threaded section
...
* Should fix issue #83
2019-01-06 21:45:01 -07:00
