Author Topic: graphic interface for smartahci  (Read 3290 times)

Rick C. Hodgin

  • Newbie
  • *
  • Thank You
  • -Given: 1
  • -Receive: 1
  • Posts: 34
    • View Profile
Re: graphic interface for smartahci
« Reply #15 on: November 01, 2019, 02:42:57 pm »
Hi Rick,

Not one of the latest ones but I did before the 8080 came out - it was a monster made up of discrete components on a bread board just to show ir could be done.

This reminds me, by the way ... Busicom, the company that originally contracted Intel to build their 4004 CPU that started the whole x86 affair, had developed the entire CPU in that same breadboard fashion.  They had the software, hardware, and everything designed, in the lab, in an impractical way, so that when the 4004-series chips came out, they would be ready.

There's a documentary about that too from the Computer Science Museum:  Intel 4004 Microprocessor 35th Anniversary

Today, in 2019, the 4004 is actually 48+ years old.  It will turn 50 in May 2021 I believe.

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1026
    • View Profile
Re: graphic interface for smartahci
« Reply #16 on: November 01, 2019, 06:16:26 pm »
Ah, those were the days.

I've seen a lot of changes in my 80 years and I'm not sure that it is all that much better.  We now have computers built to only run windows 10 and even if you buy separate items they are still designed with windows use in mind especially motherboards and graphics cards.  Still we battle on with what we can get hence my various AMD Ryzen based computers I have built.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: graphic interface for smartahci
« Reply #17 on: November 01, 2019, 11:43:31 pm »
Hi All

I have both smartahci.exe - aka smartctl version 5.37 - and smartctl.exe 6.6 2017-04-23 r4424 installed. They simply seem to be different versions of smartmontools.

I can confirm grep works with both smartahci.exe and smartctl.exe:-

[M:\SYS\BIN]smartctl -A ahci0 | grep -i "temp"
194 Temperature_Celsius     0x0022   030   100   000    Old_age   Always       -
       30 (Min/Max 16/41)
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -
       1

[M:\SYS\BIN]smartahci -A hd0 | grep -i "temp"
194 Temperature_Celsius     0x0022   030   100   000    Old_age   Always       -
       30 (Lifetime Min/Max 16/41)
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -
       1


The smartctl.exe seems to be a later build than smartahci.exe and returns less "Unknown_Attribute" entries when run against my SSD:-

Output of smartahci -A hd0 > smartahci_hd0.txt

smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 48
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   100   100   000    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       9786
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1332
100 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       912496
101 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       132352
170 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
171 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
174 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       1331
175 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
176 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
177 Unknown_Attribute       0x0032   099   099   000    Old_age   Always       -       538
178 Unknown_Attribute       0x0002   100   100   000    Old_age   Always       -       0
180 Unknown_Attribute       0x0002   100   100   000    Old_age   Always       -       654
183 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       6
187 Reported_Uncorrect      0x0033   100   100   000    Pre-fail  Always       -       0
194 Temperature_Celsius     0x0022   029   100   000    Old_age   Always       -       29 (Lifetime Min/Max 16/41)
195 Hardware_ECC_Recovered  0x0032   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0012   100   100   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x0032   100   100   000    Old_age   Always       -       0
204 Shock_Count_Write_Opern 0x0032   100   100   000    Old_age   Always       -       0
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -       1
233 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       839
234 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       653
241 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       714
242 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       791
250 Read_Error_Retry_Rate   0x0032   100   100   000    Old_age   Always       -       0


Output of smartctl -A ahci0 > smartctl_ahci0.txt

smartctl 6.6 2017-04-23 r4424 [i386-pc-os2-emx] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 48
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   100   100   000    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       9790
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       1333
100 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       912640
101 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       132368
170 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
171 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
174 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       1332
175 Program_Fail_Count_Chip 0x0032   100   100   000    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   000    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   099   099   000    Old_age   Always       -       538
178 Used_Rsvd_Blk_Cnt_Chip  0x0002   100   100   000    Old_age   Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0002   100   100   000    Old_age   Always       -       654
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       6
187 Reported_Uncorrect      0x0033   100   100   000    Pre-fail  Always       -       0
194 Temperature_Celsius     0x0022   025   100   000    Old_age   Always       -       25 (Min/Max 16/41)
195 Hardware_ECC_Recovered  0x0032   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
199 UDMA_CRC_Error_Count    0x0012   100   100   000    Old_age   Always       -       0
201 Unknown_SSD_Attribute   0x0032   100   100   000    Old_age   Always       -       0
204 Soft_ECC_Correction     0x0032   100   100   000    Old_age   Always       -       0
231 Temperature_Celsius     0x0032   099   099   000    Old_age   Always       -       1
233 Media_Wearout_Indicator 0x0032   100   100   000    Old_age   Always       -       839
234 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       653
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       714
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       792
250 Read_Error_Retry_Rate   0x0032   100   100   000    Old_age   Always       -       0


Regards

Pete


Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: graphic interface for smartahci
« Reply #18 on: November 20, 2019, 04:03:52 am »
Hi All

I have to correct my above post as it only applies when os2ahci.add V1.32 is installed.

Neither smartahci.exe or smartctl.exe can be used with os2ahci.add V2.03 on 5 systems here as attempting to use either results in a locked system requiring the use of the Reset/Power Off button.

The version of smartahci is that supplied in the package with os2ahci.add V2.03 - would have been nice if AN had checked that it worked... Or is the problem just on my systems - same problem on 2 laptops and 3 desktops all running either eCS2.2b2+ or ArcaOSV5.02+.

Is os2ahci.add V2.03 the latest release of this driver? - If there is a later version what version of smartahci/smartctl is supplied?


Regards

Pete


Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2168
    • View Profile
Re: graphic interface for smartahci
« Reply #19 on: November 20, 2019, 04:44:40 am »
Is os2ahci.add V2.03 the latest release of this driver? - If there is a later version what version of smartahci/smartctl is supplied?

The latest beta has,
Code: [Select]
O:\OS2\BOOT>bldlevel OS2AHCI.ADD
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#Arca Noae LLC:2.07#@##1## 24 Aug 2019 15:17:12     DAZAR1
::::::@@AHCI Driver (c) 2019 Arca Noae LLC
Vendor:          Arca Noae LLC
Revision:        2.07
Date/Time:       24 Aug 2019 15:17:12
Build Machine:   DAZAR1
File Version:    2.7
Description:     AHCI Driver (c) 2019 Arca Noae LLC
and
Code: [Select]
O:\sys\bin>SMARTAHCI.EXE
smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

No AHCI hardware to test though.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: graphic interface for smartahci
« Reply #20 on: November 20, 2019, 04:48:02 pm »
Hi Dave

So, os2ahci.add has been updated but smartahci is the same version.

Now all I need is someone to test whether smartahci works with the updated os2ahci... I suspect the result will be a system lockup requiring a reboot.


Regards

Pete

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 46
  • Posts: 1251
    • View Profile
Re: graphic interface for smartahci
« Reply #21 on: November 20, 2019, 06:12:35 pm »
Quote
Now all I need is someone to test whether smartahci works with the updated os2ahci... I suspect the result will be a system lockup requiring a reboot.

No, it works just as badly, and just as well, as the old version works with IDE. The data is misleading, and often completely wrong. It also changes between disk manufacturers. If you understand what it is actually saying, and exactly what to look for, it MAY tell you something useful. It has been my experience that , so called, SMART monitoring is a total waste of time, and effort. You are far better off to simply do proper, tested, backups.

Here is a sample output (the program name is actually SMARTAHCI.EXE, not SMARTCTL.EXE):
Code: [Select]
smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     ST1000DM010-2EP102
Serial Number:    Z9ANJZV0
Firmware Version: CC43
User Capacity:    1,000,204,886,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Wed Nov 20 09:23:56 2019   
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

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (   0) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   1) minutes.
Extended self-test routine
recommended polling time: ( 103) minutes.
Conveyance self-test routine
recommended polling time: (   2) minutes.
SCT capabilities:        (0x1085) SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   083   063   006    Pre-fail  Always       -       231254441
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       838
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   085   060   045    Pre-fail  Always       -       358959151
  9 Power_On_Hours          0x0032   086   086   000    Old_age   Always       -       12719
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       835
183 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   066   061   040    Old_age   Always       -       34 (Lifetime Min/Max 31/35)
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1162
194 Temperature_Celsius     0x0022   034   013   000    Old_age   Always       -       34 (0 13 0 0)
195 Hardware_ECC_Recovered  0x001a   002   001   000    Old_age   Always       -       231254441
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       21556440871248
241 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       14553047179
242 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       45958338958

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

I don't know why anybody would want a "graphical" interface, just redirect the output to a file, and look at it in an editor (that is what I did here). You could also do a simple REXX thing, to track whatever might interest you. I also suggest that you look up what the disk manufacturer means by the various numbers. They aren't always what the program says they are.

As a sample of "BAD information, this is from the second HDD in the machine:
Code: [Select]
smartctl version 5.37 [i386-pc-ibmvac365] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     ST3320613AS
Serial Number:    9SZ2YC9J
Firmware Version: CC2H
User Capacity:    320,072,933,376 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Wed Nov 20 09:44:22 2019   
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
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 625) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: (   1) minutes.
Extended self-test routine
recommended polling time: (  71) minutes.
Conveyance self-test routine
recommended polling time: (   2) minutes.
SCT capabilities:        (0x103f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   116   082   006    Pre-fail  Always       -       109681403
  3 Spin_Up_Time            0x0003   100   096   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   098   098   020    Old_age   Always       -       2111
  5 Reallocated_Sector_Ct   0x0033   020   020   036    Pre-fail  Always   FAILING_NOW 3290
  7 Seek_Error_Rate         0x000f   081   060   030    Pre-fail  Always       -       138637869
  9 Power_On_Hours          0x0032   065   065   000    Old_age   Always       -       31024
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   037   020    Old_age   Always       -       1974
184 Unknown_Attribute       0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       6293
188 Unknown_Attribute       0x0032   100   096   000    Old_age   Always       -       47245623365
189 High_Fly_Writes         0x003a   053   053   000    Old_age   Always       -       47
190 Airflow_Temperature_Cel 0x0022   065   048   045    Old_age   Always       -       35 (Lifetime Min/Max 33/37)
194 Temperature_Celsius     0x0022   035   052   000    Old_age   Always       -       35 (0 16 0 0)
195 Hardware_ECC_Recovered  0x001a   020   010   000    Old_age   Always       -       109681403
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       1
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       210796994918617
241 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       588313026
242 Unknown_Attribute       0x0000   100   253   000    Old_age   Offline      -       2780383231

SMART Error Log Version: 1
ATA Error Count: 4255 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 4255 occurred at disk power-on lifetime: 24723 hours (1030 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d4 00 82 4f c2 a0 00      00:01:30.182  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 00 00 4f c2 a0 00      00:01:29.928  SMART READ DATA
  b0 d0 00 00 4f c2 a0 00      00:01:28.424  SMART READ DATA
  b0 d0 00 00 4f c2 a0 00      00:01:16.395  SMART READ DATA
  b0 d4 00 81 4f c2 a0 00      00:01:15.870  SMART EXECUTE OFF-LINE IMMEDIATE

Error 4254 occurred at disk power-on lifetime: 24723 hours (1030 days + 3 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  b0 d4 00 81 4f c2 a0 00      00:01:15.870  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 00 00 4f c2 a0 00      00:01:15.366  SMART READ DATA
  b0 d0 00 00 4f c2 a0 00      00:01:12.805  SMART READ DATA
  b0 da 01 00 4f c2 a0 00      00:01:03.492  SMART RETURN STATUS
  b0 d0 01 00 4f c2 a0 00      00:00:46.946  SMART READ DATA

Error 4253 occurred at disk power-on lifetime: 24632 hours (1026 days + 8 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 94 e4 01 00  Error: UNC at LBA = 0x0001e494 = 124052

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 80 e4 01 40 00      00:04:12.891  READ DMA EXT
  25 03 80 00 e4 01 40 00      00:04:12.833  READ DMA EXT
  25 03 80 80 3f 60 40 00      00:04:12.830  READ DMA EXT
  25 03 80 00 3f 60 40 00      00:04:12.806  READ DMA EXT
  25 03 80 80 43 00 40 00      00:04:12.792  READ DMA EXT

Error 4252 occurred at disk power-on lifetime: 24521 hours (1021 days + 17 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ed c0 5f 00  Error: UNC at LBA = 0x005fc0ed = 6275309

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  25 03 80 f0 ac 5f e0 00      01:01:39.451  READ DMA EXT
  25 03 80 70 ac 5f e0 00      01:01:38.752  READ DMA EXT
  25 03 80 f0 ab 5f e0 00      01:01:37.594  READ DMA EXT
  25 03 80 70 ab 5f e0 00      01:01:37.036  READ DMA EXT
  25 03 80 f0 aa 5f e0 00      01:01:37.031  READ DMA EXT

Error 4251 occurred at disk power-on lifetime: 24519 hours (1021 days + 15 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 78 b1 68 00  Error: UNC at LBA = 0x0068b178 = 6861176

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 03 08 78 b1 68 e0 00      00:20:56.237  READ VERIFY SECTOR(S) EXT
  42 03 08 70 b1 68 e0 00      00:20:53.507  READ VERIFY SECTOR(S) EXT
  42 03 10 b0 b1 68 e0 00      00:20:53.430  READ VERIFY SECTOR(S) EXT
  42 03 10 a0 b1 68 e0 00      00:20:50.697  READ VERIFY SECTOR(S) EXT
  42 03 10 90 b1 68 e0 00      00:20:47.873  READ VERIFY SECTOR(S) EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended captive    Completed: unknown failure    90%     24723         -
# 2  Short captive       Completed: unknown failure    90%     24723         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Note the "fail" line. About 8 years ago, this disk was in my brother's machine. The BIOS refused to use the disk, because of those lines (with no way to ignore them). After some analysis, we replaced the disk (not because it wasn't working, but because the machine refused to use it). I put the disk into a USB enclosure (which doesn't care about this stuff), and started to copy the data. OOOPS! the new disk had the same problem. After replacing the SATA cable, and resetting the controller, it was okay. Fortunately, we got that before the disk was corrupted (I have never found a way to reset bad numbers). Anyway, my brother's problem was solved (although his new disk has some high numbers, that aren't at "fail" point, yet), and I have been using the "bad" disk, with no problems, other than I need to set the BIOS to ignore SMART data, and future bad spots may not have anywhere to go.

Bottom line is: Don't believe what SMART monitoring says.

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: graphic interface for smartahci
« Reply #22 on: November 20, 2019, 07:07:05 pm »
Hi Doug

I can see the smartctl (aka smartahci) version used but which os2ahci.add is in use?


Regards

Pete

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 46
  • Posts: 1251
    • View Profile
Re: graphic interface for smartahci
« Reply #23 on: November 20, 2019, 07:55:27 pm »
Quote
I can see the smartctl (aka smartahci) version used but which os2ahci.add is in use?

Sorry, I meant to include that, and forgot. It is:
Signature:       @#Arca Noae LLC:2.06#@##1## 26 Nov 2018 09:15:52     DAZAR1
::::::@@AHCI Driver (c) 2018 Arca Noae LLC
Vendor:          Arca Noae LLC
Revision:        2.06
Date/Time:       26 Nov 2018 09:15:52
Build Machine:   DAZAR1
File Version:    2.6
Description:     AHCI Driver (c) 2018 Arca Noae LLC

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: graphic interface for smartahci
« Reply #24 on: November 21, 2019, 12:18:12 am »
Hi Doug

Thanks. Confirms that the problem I am seeing is with the os2ahci.add v2.03 driver.

And now I am wondering if smartctl v6.6 2017-04-23 r4424 - http://hobbes.nmsu.edu/download/pub/os2/util/disk/smartmontools-6.6-r4424.zip - is less misleading/wrong. Yes, this build works with ahci, uses ahci0 instead of hd0 to specify an ahci controlled disk.


Regards

Pete

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 46
  • Posts: 1251
    • View Profile
Re: graphic interface for smartahci
« Reply #25 on: November 21, 2019, 03:12:43 am »
Quote
Confirms that the problem I am seeing is with the os2ahci.add v2.03 driver.

Not necessarily. SMARTAHCI.EXE was tweaked by Arca Noae to work with AHCI, It was sourced from the IDE version.

Quote
And now I am wondering if smartctl v6.6 2017-04-23 r4424 - http://hobbes.nmsu.edu/download/pub/os2/util/disk/smartmontools-6.6-r4424.zip - is less misleading/wrong. Yes, this build works with ahci, uses ahci0 instead of hd0 to specify an ahci controlled disk.

I don't know where that version actually came from (and I never wasted my time looking at it). I doubt if it was used by Arca Noae for their version (the only reason I tried the AN version, was because I do testing for Arca Noae, and they asked). I expect that v6.6 works, but it has no "official" standing in OS/2. The Arca Noae version does have Arca Noae behind it (and that is about as close to being "official" as you can get with OS/2 now). It should be pretty easy to extract data from a disk. Formatting it would be the hard part, and that hasn't changed. The access to the disk is the only difference from the IDE version, which probably explains the version used (probably just a port address change).

BTW, os2ahci.add v2.07 also works (not, yet released).

Pete

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 36
  • Posts: 850
    • View Profile
Re: graphic interface for smartahci
« Reply #26 on: November 21, 2019, 06:43:31 pm »
Hi Doug

Well, smartahci works with the os2ahci v1.32 driver but locks the system solid when os2ahci v2.03 is installed - it is the same smartahci that you report as working with os2ahci v2.06. the difference between smartahci working and locking up the system seems to be reliant on the os2ahci version in use.

I suggest you try the later smartctl package as it is a much later version than that used by AN for smartahci just to see if the accuracy of data is improved.


Regards

Pete

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 21
  • Posts: 451
    • View Profile
Re: graphic interface for smartahci
« Reply #27 on: November 21, 2019, 08:21:21 pm »
It's a know issue that some os2ahci versions crash the system rock solid when trying to read smart information. I think 2.04 was the version which fixed this issue.

Neil Waldhauer

  • Sr. Member
  • ****
  • Thank You
  • -Given: 8
  • -Receive: 34
  • Posts: 467
    • View Profile
    • Blonde Guy
Re: graphic interface for smartahci
« Reply #28 on: November 22, 2019, 03:23:27 pm »
For the current Arca Noae AHCI driver, smartctl from Hobbes (listed as smartmontools) works. But how do I get a nice display like smartmon and DaniS506 used to give me?

The data is there if I use smartctl -a ahci1

OK, smartctl -A ahci1 seems to give a black and white version of the smartmon display.
Expert consulting for ArcaOS, OS/2 and eComStation
http://www.blondeguy.com

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2168
    • View Profile
Re: graphic interface for smartahci
« Reply #29 on: November 22, 2019, 04:38:07 pm »
If you mean the coloured (ANSI) output, I'd guess it is a compile time option or needs to be forced on on OS/2. It's a shame that no one seems to follow the license and make the source available.