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: SEE: Securing Linux policy (Tech Pro Research) Usage Once the package is installed, you’re ready to go. 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. Would the drives still get killed because they will still be mounted under the main root of the Proxmox OS filesystem? I've never done a lot of linux in my VM's on ESXi, it would be possible that more linux in that setup would have also killed my consumer SSD's I suppose.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. Would it be possible to use an enterprise class SSD for the OS and then use consumer SSD's (the Samsung 960 Pro NVME for example) for the equivalent of ESXi datastores (no idea yet how that would be named in Proxmox land)? The idea of course being able to use cheaper very fast SSD's for the VM's without killing the drives. After this experience I would like to move my main box to Proxmox. I am going to get a Samsung PM863a (240GB) for that, which should be up to it. This will be mainly to learn about and test DRBD and Ceph configurations, without any serious workloads on top. I want to do some testing first on the ML110 with two or three nested Proxmox instances on top of a bare metal Proxmox install. I'd like to move from ESXi to Proxmox but it would kind of suck if that forces me to spend way more on enterprise class SSD's. There never was a problem with that setup. I just install ESXi on a USB-stick and then add a couple of consumer SSD's (Samsung Pro series) as datastores. I've been using ESXi at home for a couple of years. When I read some posts on this forum I discovered that Proxmox, at least since version 4, can kill consumer SSD's in a heartbeat. After letting it run for about a day, even without any VM's running, I noticed the health status of the SSD decreased rather fast. The only drive in the box is an older Kingston 120GB consumer SSD. I would be very thankful and will provide my experiences and results here in the future if I'm able to get Proxmox working for my scenario.Ī while back I installed Proxmox on my old HP ML110 G7. I apologize if the following is too redundant but I was not able to find exact answers and I'm hoping the people here can provide some perspective. I have yet another question about Proxmox and SSD's.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |