To view the results of the test, issue the command sudo smartctl -a /dev/sdX (Where sdX is the name of the drive tested). The short test takes approximately two minutes to complete, whereas the long test will require between 20-60 minutes (depending upon your hardware). The entire disk is checked (as opposed to just a section).No time restriction and in the Read/Verify segment.
The long test runs everything included with the short test, while adding:
#SSD HEALTH CHECK TOOL HOW TO#
How to choose a database (hint: boring is good) If not, you know, right away, there’s something wrong with your SSD. One of the first things you should see is the results of the SMART overall-health self-assessment test. I recommend you run a short and a long test weekly or (monthly) on your drives. This will immediately report some bits of information ( Figure B). These tests will actually wind up giving you the most accurate data on your drive (so it’s important to make use of these included tools). The above command will print out the details associated with your drive ( Figure A).Īs you can see, the drive in question is in the smartctl database, so information should be up to date. Where sdX is the name of the drive to be tested. To use the smartctl tool, the first thing you will want to do is gather information about the drive, which is done via the command:
#SSD HEALTH CHECK TOOL PRO#
SEE: Securing Linux policy (Tech Pro Research) Usage Once the package is installed, you’re ready to go.
#SSD HEALTH CHECK TOOL INSTALL#
This can be installed with a single command:ĭo note, the above command will also install libgsasl7, libkyotocabinet16v5, libmailutils5, libntlm0, mailutils, mailutils-common, and postfix. The smartctl utility is a part of the smartmontools package. The required package is found on all the standard repositories, so adjust the installation command to fit your particular distribution of choice. I will be demonstrating with the Ubuntu platform (Ubuntu 17.10 to be exact). Even with that in mind, you can get a good estimation as to the wear and tear on your drives. Because of this, you cannot be certain the number of times your SSD chips have been written to. tools aren’t always up to date with every SSD drive. Of course, how much mileage you get from the command will depend upon what make/model of SSD you employ.
With this command, you can get a quick glimpse of your SSD health. Why? Most of the time, your Linux servers won’t include a GUI with the command line, you can easily make use it by secure shelling into your remote Linux server and run your tests from the terminal. Although a GUI solution exists (GNOME Disks), I highly recommend going with a command line tool for this task. How do you check the health of those drives? As with everything in Linux, there are options. The last thing you want to do is fall victim to that particular end of days. Why? Because, even though solid state drives will dramatically outlast rotating platter drives, they do have a finite lifespan. If your data center makes use of Linux machines, one of the administrative tasks you’ll want to undertake is regularly checking the health of the SSD drives used on those machines.
0 kommentar(er)
