Page 3 of 3 FirstFirst 123
Results 21 to 29 of 29
  1. #21
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,514

    Default

    The script in question will only work for Samsung. The WD drives are good, but they report differently and I'd need to put one in an Untangle to modify the script.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  2. #22
    Master Untangler
    Join Date
    Jul 2018
    Posts
    145

    Default

    The output of the raw command is pretty similar.. Only thing not working is the data written part.
    Last edited by manilx; 02-21-2019 at 11:56 AM.

  3. #23
    Untangler
    Join Date
    Jan 2019
    Posts
    91

    Default

    You have to figure out how WD uses the field. A quick search didn't provide any data.

    I did find that Intel SSDs use another convention:

    "The raw value of this attribute reports the total number of sectors written
    by the host system. The raw value is increased by 1 for every 65,536
    sectors (32MB) written by the host."

  4. #24
    Master Untangler
    Join Date
    Jul 2018
    Posts
    145

    Default

    OK.

    Using only run time and health now in the script. Perhaps someone can help sometime

  5. #25
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,514

    Default

    Actually, given the output of smartctl you posted above, it looks like all you need to do is edit the script, near the top change

    Code:
    WEAR_COUNT_TAG="Wear_Leveling_Count"
    to

    Code:
    WEAR_COUNT_TAG="Media_Wearout_Indicator"
    That's the only tag that looks different given the output I get from sysctl on a Samsung equipped system vs your WD.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  6. #26
    Master Untangler
    Join Date
    Jul 2018
    Posts
    145

    Default

    Quote Originally Posted by sky-knight View Post
    Actually, given the output of smartctl you posted above, it looks like all you need to do is edit the script, near the top change

    Code:
    WEAR_COUNT_TAG="Wear_Leveling_Count"
    to

    Code:
    WEAR_COUNT_TAG="Media_Wearout_Indicator"
    That's the only tag that looks different given the output I get from sysctl on a Samsung equipped system vs your WD.
    That's what I figured and did, but alas:

    ------------------------------
    SSD Status: /dev/sda
    ------------------------------
    On time: 5,069 hr
    ------------------------------
    Data written:
    MB: .606
    GB: 0
    TB: 0
    ------------------------------
    Mean write rate:
    MB/hr: 0
    ------------------------------
    Drive health: 100 %
    ------------------------------

  7. #27
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,514

    Default

    Quote Originally Posted by manilx View Post
    That's what I figured and did, but alas:

    ------------------------------
    SSD Status: /dev/sda
    ------------------------------
    On time: 5,069 hr
    ------------------------------
    Data written:
    MB: .606
    GB: 0
    TB: 0
    ------------------------------
    Mean write rate:
    MB/hr: 0
    ------------------------------
    Drive health: 100 %
    ------------------------------
    Well it did fix the drive health line. The data written seems to be working too.

    But, if you look at the output you posted

    Code:
    === START OF READ SMART DATA SECTION ===
    SMART Attributes Data Structure revision number: 4
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    5 Reallocated_Sector_Ct 0x0032 100 100 --- Old_age Always - 0
    9 Power_On_Hours 0x0032 100 100 --- Old_age Always - 5067
    12 Power_Cycle_Count 0x0032 100 100 --- Old_age Always - 5
    165 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 13172882
    166 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
    167 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 39
    168 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 2
    169 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 400
    170 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
    171 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
    172 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
    173 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 0
    174 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 2
    184 End-to-End_Error 0x0032 100 100 --- Old_age Always - 0
    187 Reported_Uncorrect 0x0032 100 100 --- Old_age Always - 0
    188 Command_Timeout 0x0032 100 100 --- Old_age Always - 75
    194 Temperature_Celsius 0x0022 051 068 --- Old_age Always - 49 (Min/Max 34/68)
    199 UDMA_CRC_Error_Count 0x0032 100 100 --- Old_age Always - 102
    230 Unknown_SSD_Attribute 0x0032 100 100 --- Old_age Always - 124554051613
    232 Available_Reservd_Space 0x0033 100 100 004 Pre-fail Always - 100
    233 Media_Wearout_Indicator 0x0032 100 100 --- Old_age Always - 476
    234 Unknown_Attribute 0x0032 100 100 --- Old_age Always - 1784
    241 Total_LBAs_Written 0x0030 253 253 --- Old_age Offline - 1241
    242 Total_LBAs_Read 0x0030 253 253 --- Old_age Offline - 34
    244 Unknown_Attribute 0x0032 000 100 --- Old_age Always - 0
    The information you're being presented is all correct. The drive is reporting 5,067 hours of powered on time, which is obviously not true but it's reporting it. Fortunately the Media_Wearout_Indicator I know from other testing is a percentage field that decrements as the drive ages, I've been able to match that statistic against WD SSD Dashboard.

    And, well Total_LBAs_Written is coming back as 1241, each one is 512bytes, so that's 1241 * 512 = 635,392 bytes written. Which we both know is also wrong. 635,392 bytes / 1024 = 620.5Kb / 1024 = .606Mb Considering Untangle's ISO image is almost 700Mb... well that's not possible either.

    There's nothing to be done when hardware doesn't report good data, garbage in, garbage out. But you should be able to at least rely on the percentage.

    *edit*

    Actually on second thought I wonder if that LBA written field isn't returning bytes, but megabytes... a bit more than 1 gb written would be about right for a new drive on a fresh install.

    Sadly, without WD confirming anything there's not much to do but guess.
    Last edited by sky-knight; 02-21-2019 at 02:13 PM.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  8. #28
    Master Untangler
    Join Date
    Jul 2018
    Posts
    145

    Default

    Guess, the health is the most important part anyway...

  9. #29
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,514

    Default

    Quote Originally Posted by manilx View Post
    Guess, the health is the most important part anyway...
    Yes, and watching it at regular intervals over time will help you estimate the lifespan. Though honestly, that SSD is likely to outlive the platform it's installed in.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

Page 3 of 3 FirstFirst 123

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2