Linux

Linux Almost KILLED MY SSD…



If you’ve enjoyed the video leave a like, comment and a sub! If you’re using disk encryption, there’s a good chance that a default …

[ad_2]

source

Related Articles

35 Comments

  1. I'm not certain but this may have actually killed a previous SSD of mine. I'm glad I ran across this video and checked whether fstrim actually worked, before it maybe happened again! Your solution worked, thank you for the guidance!

  2. Hallo! I like a lot your videos, especially the one about the Linux App Iceberg! I need some advice about something, because I am not so experienced in Linux. I have recently switched from Windows to Fedora Kinoite (immutable KDE version of Fedora), and my main SSD with the OS is in BTRFS. I have a second internal SSD for storage and I had formatted it in NVME because I used it initially in windows. This SSD is unmount at system startup and I have to mount it (with password) every time I need to use it. Which file system would you suggest me to reformat it to, and also is there a way to do it without to transfer all my data to another external disk and put them again back? It is only by 1/3 full so I thought to format half of the disk, move my data there and after format the other half and merge them, but I am not sure if it is a good method for SSD's health. The other option is to let it be NVME. It is not so slow. My primary concern is longevity of the disk. I would like to see your opinion about this!

  3. Wow! Even though I discovered your channel yesterday, you have become my favorite Linux channel. I am amazed by how you never give up on a problem and try to solve it. You are a very good channel.I wish you continued success.

  4. Linux is really great and secure, but I noticed that many distros still to this day don't optimize for (nvme)SSD's!
    -noatime should be the default in /etc/fstab to reduce writes on your SSD
    -discard is a must in /etc/crypttab if you use encryption!
    -If you have a good amount of RAM and don't need hibernation zram should be the defaul!

    Btrfs is a great FS for SSD's. You Video Title is very catchy and I hope more ppl see this and Distro Maintainers finally update their stuf …

  5. I belive every time you trim it shows that it trims all the available free space, so the 800gb is working as intended, still definitely a good thing. I now have discard and persistant allow-discard on luks2 also using btrfs

  6. β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž β€β€β€Ž

  7. Yeah there should be some kind of warning about it, especially on major distributions, things like this might cause gnu/linux to seem unreliable to the average end user ,and cause general harm to the gnu/linux ecosystem overtime. Love the video though, continue the good work!

  8. Aren't you using Arch? Why are you expecting that you should see a "allow discards" button? Also, giving the discard flag in fstab will enable continuous discard, which will hurt your performance. It is recommended to perform periodic TRIM instead (fstrim cronjob). TRIM generally will not increase the risk of your encryption getting penetrated, it will just make it possible to guess the file system that you use, and whatnot, and Linux does not want to provide a vulnerable security feature by default, hence this "absurd" default setting. All of this information is available on the Arch Wiki page (or linked to), surprised you did not read it.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button