[[fester:hvalid_hdd]]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
fester:hvalid_hdd [2017/06/24 15:39] – [Stopping A Badblocks Test In tmux] add content danfester:hvalid_hdd [2017/06/24 15:47] – [Getting Your Test Results] add content dan
Line 436: Line 436:
  
 ==== Resuming A Session In tmux ==== ==== Resuming A Session In tmux ====
 +
 +Badblocks tests can take a long time (when the tests completed Fester was far from where he had started due to Continental Drift and Plate Tectonics).
 +
 +You do not need to keep the terminal open or the client computer switched on in order to keep the tmux session running.
 +
 +If you need to pack up for the night then just close the window that the sessions are running in (just don’t shut down the server). Then get your ferrets to shut down your client computer and your pigeons to knock up a suitable night cap (I find a Multiple Orgasm very agreeable before bed).
 +
 +{{:fester:159bf7d2a0b8a2cb328b5e8322a0a72e.png}}
 +
 +When you need to re-establish the connection with the tmux session/s simply start an SSH session and log in.
 +
 +Type the following command in the command prompt.
 +
 +''tmux attach''
 +
 +or simply
 +
 +''tmux a''
 +
 +{{:fester:29505b0dbee390dd1dddeb6dd009e50f.png}}
 +
 +This should return you to the tmux session(s).
 +
 +{{:fester:17d1b1f52baacdfbdc94391348c2f86f.png}}
 +
 +When the tests are complete navigate to an open session, note the results if you need to and then type the following into the command prompt.
 +
 +''exit''
 +
 +This will close that particular session in tmux.
 +
 +Do this for each session in turn until you have exited all the sessions in tmux.
 +
 +You will find that on exiting the last open session in tmux you will be returned to the standard SSH console (in Fester’s case PuTTY).
 +
 +Now reboot the server to reset the kernel geometry debug flags to their standard setting.
 +
 +That’s the Badblocks tests complete.
 +
 +In order to complete all the HDD validation tests we must now repeat the SMART long tests. As this has already been documented I won’t repeat it here. Just go back to the relevant section and repeat again.
 +
 +Once the SMART long tests have completed then it is time to collect the results.
 +
  
 ===== Getting Your Test Results ===== ===== Getting Your Test Results =====
 +
 +Getting your test results is always a tense moment.
 +
 +(I remember such an instance in the doctor’s examination room after an unforgettable trip to Bognor Regis, often referred to as “The Riviera of the South West”. Unfortunately the doctor confirmed Fester had come back with more than just fond memories, but with the liberal application of a strong antibiotic cream Fester was as good as new in a couple of weeks.)
 +
 +Here is how to get your results.
 +
 +(Do not start this section until all HDD tests have been completed.)
 +
 +Open an SSH console and log in.
 +
 +We are going to issue a command to each HDD/SDD in succession that will interrogate and retrieve the results of the tests stored in each drives memory using SMART commands.
 +
 +At the command prompt type in the following command using the name of the first drive you want to interrogate (in Fester’s case this is ada0).
 +
 +''smartctl –a /dev/ada0''
 +
 +{{:fester:34575799200aec7f192df26e22dfbfbf.png}}
 +
 +This should produce the following screen with the test results. The window displaying the information has been maximised (1) so it is easier to read.
 +
 +{{:fester:748fe2ad03dbdf87fbd109dc8ee80c58.png}}
 +
 +At this point Fester copies the information and pastes it into a text editor for ease of use.
 +
 +If you want to do this then select the text in the SSH console by clicking with the left mouse button where you want to begin, hold it down and then highlight the text you want to include.
 +
 +When you have done this press the “Ctrl” button and the “v” button together. This keystroke will copy the highlighted text into the clip board.
 +
 +Open the text editor you wish to use (Fester uses Notepad in Windows) and paste it into the text into the editor.
 +
 +You now need to repeat this process for the next drive in your system.
 +
 +At the command prompt type in the following command using the name of the next drive you want to interrogate (in Fester’s case this is da0).
 +
 +''smartctl –a /dev/da0''
 +
 +This will produce the next set of results in the SSH console. Copy and paste as before (if you want to).
 +
 +Now repeat the process for the next drive and the next until all the drives have been interrogated and their data copied and pasted.
 +
 +(In this way you will build up a list of each drives test results in a single text file that can be saved for examination later.)
 +
 +In Festers case this would mean issuing the following commands in the SSH console.
 +
 +''smartctl –a /dev/da1''
 +
 +''smartctl –a /dev/da2''
 +
 +''smartctl –a /dev/da3''
 +
 +''smartctl –a /dev/da4''
 +
 +''smartctl –a /dev/da5''
 +
 +''smartctl –a /dev/da6''
 +
 +''smartctl –a /dev/da7''
 +
 +These commands produce copious amounts of information about the drives. If you want something a little less gregarious then use this command instead (don’t forget to change the drive name each time, and note the capital -A rather than the lowercase -a).
 +
 +''smartctl –A /dev/ada0''
 +
 +This should produce a screen that looks something like this (much more compact).
 +
 +{{:fester:7a146af501c56cb6375b83159bf9b42c.png}}
 +
 +So you have now gathered your results, but they make about as much sense as a bacon butty at a bar mitzvah.
 +
 +What now?
 +
  
 ==== Making Sense of SMART Data ==== ==== Making Sense of SMART Data ====
  
  
  • fester/hvalid_hdd.txt
  • Last modified: 2017/06/24 17:46
  • by dan