Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 37

Thread: Do I need to enable TRIM?

  1. #21
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,821
    Blog Entries
    15

    Default Re: Do I need to enable TRIM?

    Quote Originally Posted by suse_rasputin View Post
    Hi and thanks for having a look. But read-only is irreversible for this kind of storage, or?

    Will have a look at the Intel service...
    Hi
    Honestly I think the Intel folks is your best course of action, after all it's their product

    They should have some low level tools to sort it out I imagine...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  2. #22

    Default Re: Do I need to enable TRIM?

    This Intel page is a profound nightmare. I entered the ISN and it said I have Warranty until something-2021. Then I made an Intel account (the next script and XSS nightmare) and logged in. Entered the SAME ISN again and now the webpage tells me

    Code:
    Product not found. Check the information you provided and try again, or  create a support request  for help identifying this product.
    I'm so so sick and tired of these "get away" "customer support" systems...
    Kind regards

    raspu

  3. #23

    Default Re: Do I need to enable TRIM?

    Quote Originally Posted by karlmistelberger View Post
    Yes, it is enabled. However you may want to check what
    fstrim.service actually does:
    ...
    I have here on TW:

    Code:
    ournalctl -b -u fstrim.service
    -- Logs begin at Mon 2019-09-02 17:59:34 CEST, end at Tue 2019-09-03 09:01:36 CEST. --
    -- No entries --
    Any way to go back in history?
    Kind regards

    raspu

  4. #24
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,688

    Default Re: Do I need to enable TRIM?

    -b limits search to current boot.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  5. #25

    Default Re: Do I need to enable TRIM?

    Hmm:

    Code:
    sudo journalctl -u fstrim.service
    [sudo] password for root: 
    -- Logs begin at Tue 2019-09-03 12:34:58 CEST, end at Tue 2019-09-03 12:59:15 CEST. --
    -- No entries --
    ..but I must confess, Intel provided me with an unofficial FW-update for the read-only SSD. However, the boot SSD wit TW in this machine (I applied the FW update on...) has an SSD of the exact same type and series. So the FW update was applied to BOTH the read-only and the boot SSD (a CLI tool which did NOT ask for which SSD it should apply the update to). Sigh...
    Kind regards

    raspu

  6. #26
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    975

    Default Re: Do I need to enable TRIM?

    Quote Originally Posted by suse_rasputin View Post
    Hmm:

    Code:
    sudo journalctl -u fstrim.service
    [sudo] password for root: 
    -- Logs begin at Tue 2019-09-03 12:34:58 CEST, end at Tue 2019-09-03 12:59:15 CEST. --
    -- No entries --
    ..but I must confess, Intel provided me with an unofficial FW-update for the read-only SSD. However, the boot SSD wit TW in this machine (I applied the FW update on...) has an SSD of the exact same type and series. So the FW update was applied to BOTH the read-only and the boot SSD (a CLI tool which did NOT ask for which SSD it should apply the update to). Sigh...
    The log is very short. You may check for /var/log/journal Create it if nonexistent.

    "The journal service stores log data either persistently below /var/log/journal or in a volatile way below /run/log/journal/ (in the latter case it is lost at reboot). By default, log data is stored persistently if /var/log/journal/ exists during boot, with an implicit fallback to volatile storage otherwise. Use Storage= in journald.conf(5) to configure where log data is placed, independently of the existence of /var/log/journal/."

    https://www.freedesktop.org/software...d.service.html
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  7. #27

    Default Re: Do I need to enable TRIM?

    Hey, thanks!

    In /var/log there was no "journal" directory. Should be effective after next reboot. I will have a look.

    Intel SSD is apparently back to life now, no idea if I can really trust this little monster any longer (have identical SSDs in router/firewall :-/ ).
    Kind regards

    raspu

  8. #28

    Default Re: Do I need to enable TRIM?

    TWIMC:

    Problem with the Intel 530/535 SSDs is high HAND write:

    Code:
    241 Host_Writes_32MiB       0x0032   100   100   000    Old_age   Always       -       47642
    242 Host_Reads_32MiB        0x0032   100   100   000    Old_age   Always       -       31544
    249 NAND_Writes_1GiB        0x0032   100   100   000    Old_age   Always       -       32467
    Therefore you have to apply a special FW update. Not available without accessing Support, afaik.

    But that won't take away the high NAND writes made in the past...

    And has nothing to do with TRIM, or?

    Sigh. I stay with HDDs where ever it's really critial.
    Kind regards

    raspu

  9. #29

    Default Re: Do I need to enable TRIM?

    Just to be clear what the numbers from the SMART status (Linux) posted above mean, here the numbers from the Intel SSD tool:

    Code:
    F1     Total LBAs Written     1604.56 GB
    F2     Total LBAs Read     985.84 GB
    F9     Total NAND Writes     32494.00 GB
    Kind regards

    raspu

  10. #30
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,821
    Blog Entries
    15

    Default Re: Do I need to enable TRIM?

    Hi
    Why not just email their support and ask for the firmware?

    I'm finding it hard to kill off this OCZ 60GB disk (btrfs).... the laptop it's in will likely be replaced....

    Code:
    5 Retired_Block_Count     0x0033   100   100   003    Pre-fail  Always       -       1
    9 Power_On_Hours_and_Msec 0x0032   039   039   000    Old_age   Always       -       54035h+08m+58.750s
    231 SSD_Life_Left           0x0013   097   097   010    Pre-fail  Always       -       0
    241 Lifetime_Writes_GiB     0x0032   000   000   000    Old_age   Always       -       25745
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

Page 3 of 4 FirstFirst 1234 LastLast

Posting Permissions

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