tmux "device not configured"

Status
Not open for further replies.

tromba

Dabbler
Joined
Jul 13, 2014
Messages
15
Hello everyone,

I used the search box here and googled the problem with no joy.

I'm setting up FreeNAS for the first time and was running hard drive tests as described in qwertymodo's guide here. I got to the part with parallel badblocks testing and can't start tmux. It fails with this return message:

/usr/local/bin/tmux: Device not configured.

What am I doing wrong?

Cheers
M
 
Last edited:

tromba

Dabbler
Joined
Jul 13, 2014
Messages
15
Update: an ls of /usr/local/bin/ shows all services as "Device not configured"
 

tromba

Dabbler
Joined
Jul 13, 2014
Messages
15
Okay, so I might have found the cause.
My very old long lan cable, which I am only using so I can have the case sitting next to my desktop on the other end of the room so I can share the monitor, was not sitting properly during the first FreeNAS install. This apparently affected the installation process, with the entire first section with updates/inits/configs not going as planned. I only noticed this as the install came into an endless loop searching for an internet connection. After I reseated the cable the install continued normally, so I didn't think much of it.
I was able to run the s.m.a.r.t tests (short, conveyance, long) with no problems.

Reinstalling FreeNAS from a fresh stick, WITH a properly seated lan connection seems to have sorted the problem out. tmux started immediately with no problems on the fresh install. I retried the old install with no connection, and it seems my coffee run during the installation process meant I didn't see FreeNAS throwing multiple warnings of things it couldn't load (I assume because of the lack of a connection).

I'd still appreciate any explanations that are more technical than my trial and error gambit.

Cheers
M
 

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,194
tmux shouldn't depend on the LAN, but I'm just guessing here. Likewise, the installation has nothing at all to do with the LAN, so it should've been fine, after replacing the cable.
 
Status
Not open for further replies.
Top