Started long smart self test, can I now exit the shell?

[BigDave]

I'm a noob who's learning the CLI.
Today I was successful in starting a SMART long self test from the shell.
The testing has begun. Please wait 410 minutes for test to complete.
Question: may I safely exit the shell while this is going on?
Thnx
BigDave

 

[cyberjock]

Yep.

 

[Ericloewe]

I'm a noob who's learning the CLI.
Today I was successful in starting a SMART long self test from the shell.
The testing has begun. Please wait 410 minutes for test to complete.
Question: may I safely exit the shell while this is going on?
Thnx
BigDave

If a program dumps you back into the command line (as opposed to waiting for input or occasionally writing to the command line), that's typically a good sign it expects nothing further from you, for now.

 

[BigDave]

Thanks to you both!
I was able to run smart long tests on both drives yesterday.
Today I discovered the command to shows the results, seems both drives are
in the pink

 

[panz]

Go to your favorite SSH shell (e.g. Putty), login as root. At command prompt

Code:

tmux

now something new appears on the terminal window: it has a green bar at the bottom.

Now you can issue your CLI commands. If you want to check the results after some hours, simply close the terminal window with the classic red "X" (Windows). Do NOT type exit at the CLI.

When you re-open your SSH session type

Code:

tmux attach

and, voilà, you're back into your command terminal.

 

[BigDave]

I have installed puTTY on my windows machine and have used it to log in to my NAS shell.
I learned to cut and paste the results of my smart long self tests (performed a couple of nights ago)
from the SSH window and save the output to a notepad doc.
Now I have to learn how to interpret the results.
Thanks for the push everyone.