urgent Q ! unable to open enough prompts for badblocks tests

[VladTepes]

Urgent ! (well, important to me at any rate :) )

The instructions proposed by qwertymodo state that:

Once you've started the first test, press Ctrl+B, then " (the double-quote key, not the single quote twice). You should now see a half-white, half-green line through the screen (in PuTTY, it's q's instead of a line, but same thing) with the test continuing in the top half of the screen and a new shell prompt in the bottom. Run the badblocks command again on the next disk, then press Ctrl+B, " again to create another shell. Continue until you've started a test on each disk.

I have just 6 x 3TB disks ada1 through to ada6.

From the NAS machine itself (using attached kbd and monitor) I ran tmux and commenced a badblocks test on ada1.

I then did the ctrl-b followed by " to open another shell prompt.
Unsure if it means anything but line is all green not green/white.

I was then able to commence testing ada2

and again for ada3

When I pressed ctrl-b " this time, it gives me an error message stating:

Code:

create pane failed. pane too small

What can I do to sort this out so I can test all my drives concurrently rather than consecutively which might, literally, take all week.

Assistance much appreciated.

 

[VladTepes]

Would I do better to stop it and go in via SSH instead?

 

[Mirfster]

Would I do better to stop it and go in via SSH instead?

I usually connect over SSH (Putty).

 

[VladTepes]

Do i need to do the whole keygen rubbish each time i want to ssh with putty

 

[Mirfster]

If possible, can you post a screenshot? Sorry, coffee not fully kicked in yet.. :)

 

[VladTepes]

Of the error? No it only shows for a second before disappearing
Also not sure how to screenshot.from nas console.

 

[Mirfster]

K, I thought you were talking about some message when you used Putty? Guess if it continues, then maybe an aptly timed "Prnt Scrn" hit on your Keyboard; then Paste into MSPaint would work...

 

[Bidule0hm]

Would I do better to stop it and go in via SSH instead?

Yes.

Do i need to do the whole keygen rubbish each time i want to ssh with putty

Nop.

 

[VladTepes]

Cheers all.

Mirf i mean from the actual freenas box as opposed to the windows one with ssh etc

 

[VladTepes]

äarrgghh now using putty to ssh in.
using tmux
I can only get one running (ada1) and the ctrl b " thing doesn't work at all. I can't open any other prompts to allow other disks to be tested.....

 

[danb35]

You're always better off using SSH than using the shell from the web GUI, and almost always better off using ssh than using the console. Fortunately, since you used tmux, you can detach from that session at the console (Ctrl-B, d), log in via ssh, then run tmux a to reconnect to that session.

To give yourself room to test more drives, you have two options that I can think of: (1) create a second tmux session in which you'd test those drives ( tmux new, give it a distinct name, and then you can switch between them; or (2) split the screen vertically first (Ctrl-B %).

 

[VladTepes]

ÖK well despite my best efforts to be thick it appears I now have one tmux opened doing drive ada1 , 2 , 3 , 4 and 5 and a second tmux sessions doing ada6. Now the waiting game.

Thanks all for your help

 

[danb35]

If it helps, I usually have to look up a tmux cheat sheet when I do drive testing, as I do it rarely enough that I've usually forgotten the commands by the next time I need it. Here's one that I've used: https://gist.github.com/MohamedAlaa/2961058

 

[Mirfster]

Agree with @danb35. Even though I have a "Cheat Sheet" of my own somewhere, I haven't documented it well enough and find myself doing a quick search.

 

[VladTepes]

OK... so I wake up this morning and see that the two putty tmux sessions have ceased at around 33% and that there is a "network error, connection timed out'pop up box.

I closed the putty windows and then tried to reopen a ssh session with putty and continue to get a "network error connection timed out"pop up.

This really is getting frustrating.

Thoughts please?

 

[Mirfster]

I think the putty session just closed, not a big deal. The tmux sessions on FreeNAS are still running. All you see is the last transmission when network connectivity was loss.

Go ahead and reconnect via Putty, your tmux sessions should still be there and running.

Just run tmux ls to get a list of the active sessions and then tmux a %SessionNumber# to re-attach to it.

 

[VladTepes]

SORTED connection error
The IP had changed. Will have to sort that out later.....

 

[danb35]

Assign a static IP to your FreeNAS server. Either via a DHCP reservation in your router, or just by configuring a static IP (outside your DHCP range) on the FreeNAS box. Shouldn't have interrupted your tmux sessions, though; you should be able to reattach to them.

 

[VladTepes]

OK I did a tmux ls :

Code:

[root@Remus] ~# tmux ls
0: 1 windows (created Thu Sep  8 18:30:12 2016) [80x24] (attached)
1: 1 windows (created Thu Sep  8 22:56:25 2016) [80x23]
2: 1 windows (created Thu Sep  8 23:05:51 2016) [253x67]
4: 1 windows (created Thu Sep  8 23:27:03 2016) [80x23]

I tried to connect/attach to session 1 by typing tmux a %1#
which returned the following :

Code:

usage: attach-session [-dEr] [-c working-directory] [-t target-session]

What am I doing wrong please?

Do I need to ún-attach'from session 0 first? If so how please.

 

[Ericloewe]

As the error says, you need to use tmux attach-session -t 1.