6 posts in this topic Last Reply

Recommended Posts

Posted (edited)

I replaced a 4 TB disk this weekend with a new 10 TB disk.

 

I performed a clean shutdown

Popped the 4 TB disk out and replaced it with a new 10 TB DIsk

Started the system up in GUI mode

Issues started here.  I could not log in via the GUI console.  I keep getting "Failed to Execute Command" on the screen.

I ran to my desktop and was able to login via the web GUI and start the array rebuilding process.

Everything seemed fine.  Dockers are working, VM's are up and running.

 

I logged in via ssh and I get the following error:

 

Quote

Last login: Mon Jul  9 10:13:44 2018 from 192.168.1.11
Linux 4.14.49-unRAID.
Could not chdir to home directory Console and webGui login account: No such file or directory
-bash: [: too many arguments
root@STORAGE2:/# 

 

I rebooted after the array has synced into console mode. When i login via root, I get the following error: No directory, logging in with HOME=/


image.png.a7139d17cc59f2ecdce8c0a8aa91ad62.png

 

When I try to run MC via ssh I get the following error:

 

Quote

root@STORAGE2:/# mc
Failed to run:
Home directory path is not absolute: Console and webGui login account

root@STORAGE2:/# 

 

 

Has anyone seen this before?  Any advise?

 

As always thanks in advanced to all to any help

 

 

 

Chris

------------------------------------------------------------------------------------------------------------------------------------------------------------------

unRAID6 PRO

Case: ANTEC-1200 • 4 Icy Dock FatCage MB155SP-B • Corsair RM1000x PSU

System: Asus X99/USB 3.1 • Intel i7 5960x • 64 GB DDR4 ECC RAM • Intel QUAD Port GB Nic ET2 • ATI Radion X300

Storage: 2x Areca 1882i • 1 Samsung » 1000 GB [cache] • 2 10TB SG (Parity) 8x 6TB SG (Data) • 7x 4TB WD • 1 10TB SG » 86 TB [data]

unRAID: 6.5.3

 

 

Edited by chris0583
System Info

Share this post


Link to post

Try typing diagnostics and see if it will generate the file.  It will be in the logs folder/directory on your flash drive.  Upload it if you get it.  

 

You could also try    pwd     (that will list the present working directory)

 

and

 

 try typing     ls  -al     (That provides list of the files and directories on the current directory.  

Share this post


Link to post

Frank1940

 

Thanks for the replay.

 

Output from the pwd and ls commands

 

I also attached my diagnostics file.


 

Quote

root@STORAGE2:/# ls -la
total 40
drwxr-xr-x  21 root root   480 Jul  9 11:02 ./
drwxr-xr-x  21 root root   480 Jul  9 11:02 ../
-rw-------   1 root root     5 Jul  9 10:58 .bash_history
drwx------   3 root root    60 Jul  9 11:02 .cache/
drwx------   3 root root    60 Jul  9 11:02 .config/
drwx------   3 root root    60 Jul  9 11:02 .local/
-rw-rw-rw-   1 root root   165 Jul  9 08:34 .wget-hsts
drwxr-xr-x   2 root root  3760 Jul  9 08:34 bin/
drwxrwxrwx  12 root root 32768 Jul  9 08:44 boot/
drwxr-xr-x  15 root root  4860 Jul  9 08:34 dev/
drwxr-xr-x  56 root root  3140 Jul  9 10:13 etc/
drwxr-xr-x   2 root root    40 Jun 12 13:25 home/
lrwxrwxrwx   1 root root    10 Jun 12 13:25 init -> /sbin/init*
drwxr-xr-x   7 root root   140 Jun 12 13:25 lib/
drwxr-xr-x   3 root root  3280 Jun 12 13:25 lib64/
drwxr-xr-x  23 root root   460 Jul  9 10:13 mnt/
dr-xr-xr-x 627 root root     0 Jul  9 08:32 proc/
drwx--x---   2 root root    80 Jun 12 13:25 root/
drwxr-xr-x  10 root root   280 Jul  9 08:34 run/
drwxr-xr-x   2 root root  4920 Jul  9 08:34 sbin/
dr-xr-xr-x  13 root root     0 Jul  9 08:33 sys/
drwxrwxrwt  14 root root   300 Jul  9 13:16 tmp/
drwxr-xr-x  15 root root   360 Jul 30  2013 usr/
drwxr-xr-x  15 root root   340 Jul  9 08:34 var/
root@STORAGE2:/# pwd
/

storage2-diagnostics-20180709-1316.zip

 

Share this post


Link to post

What happens if you reboot into safe mode?

Share this post


Link to post

Same issue when I reboot into same mode. 

 

I managed to fix the issue tho.  

 

for some reason my /etc/password file was corrupted.  Cant figure out why the root entry would get corrupted and how but it was.  The entry was missing the home directory attribute.   I should of known this right out of the box due to the errors that were being presented.  (above)

 

Corrupted Entry

root:x:0:0::Console and webGui login account:/bin/bash

                    |

(Look at two colons)

 

Correct Entry

root:x:0:0:Console and webGui login account:/root:/bin/bash

                    |                                                                             |

       (one colon)                                                  (Home directory path)

 

Hope this help anyone who experience this in the future.

 

Thanks everyone for you help.

 

 

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


Copyright © 2005-2018 Lime Technology, Inc.
unRAID® is a registered trademark of Lime Technology, Inc.