Hi,

 

I'm hoping someone can help. Recently my unRAID server's CLI stopped working, when trying to login directly into the console on the server using the correct credentials I get the following error, then I'm taken back to the login prompt:

 

"No such directory or file"

 

I'm sure it's something simple, but I'm stumped. It should be noted that the webGUI works and the server is running fine otherwise.

 

I recently edited the passwd file under the config folder, not sure if that messed something up.

 

I already tried disabling all my plugins and downgrading back to 5.0-rc16c from 5.0-i386.

 

syslog attached

syslog.txt

Linux is picky with editors, especially over smb in windows.

 

Try resetting ur ROOT login password via the webgui. Might restore the passwd file.

Thanks for the suggestion Hexen, afraid no joy.

 

I use Notepad++ as my editor as I have had issues in the past. Tried reseting the password as suggested, still fails to login. It looks like it is authenticating correctly, it only terminates the Telnet session if I input the correct login details. Hmm, hoping I don't have to start over, it would be a mission to setup all those shares again.

Did you make a backup of the passwd file before editing?

LOL I wish, safe to say I learn't my lesson. Not sure if that is the problem though as it is passing other commands fine. I added in the following lines for the avahi user as I use Plex.

 

avahi:x:61:214:Avahi Daemon User:/dev/null:/bin/false

avahi-autoipd:x:62:62:Avahi AutoIP Daemon User:/dev/null:/bin/false

 

The avahi user is created fine so I would assume the file is fine as well. Must be something else went amiss

 

How does your passwd file compare to the default file included with the unRAID download?

 

You mentioned using Notepad+ as an editor and it got me to thinking about the differences between the line ending character "^M" that Windows uses versus Unix, which does not use it. Maybe Notepad+ stuck some "^M's" (what is it, LineFeed?) in the file and now it's messing you up.

 

Since you can't get to the console to look at the file in MCEdit, which shows the hidden control character, maybe there's an editor available in Windows, or even Notepad+).

 

Otherwise couldn't you temporarily substitute a "stock" passwd file in config folder, of course, just rename your existing one and see if you get ROOT login back?

 

It's probably not a bad idea to just copy the whole USB stick to your workstation and have a backup of everything. 

how many users do you have defined? if none, just copy a stock one from an unraid distribution.

Hey Guys, Thanks you rock, I fired up a VM and setup a virtual unRAID server to generate a clean passwd file, copied it over and I can log in the CLI now  ;D .

 

Strange thing was I checked for hidden chars in the file and could not find any. But it's working now so I'm happy. Same to say I made a backup of my flash drive 

 

After a second look I see Windows must have added something as the lines ended in CR LF, whereas the original file only has LF