[[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 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:42] – [Resuming A Session In tmux] 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 =====
  • fester/hvalid_hdd.txt
  • Last modified: 2017/06/24 17:46
  • by dan