Thank you all for your valuable suggestions. I changed my /etc/fstab file, like this. But the problem is not solved. Waiting for your comments.....

#
# /etc/fstab
# Created by anaconda on Fri Jul 24 12:08:27 2015
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=a7b150bf-f04a-4af0-917f-b9e8a6a45f35 / xfs defaults 1 1
UUID=d92c7e03-d559-48be-aaef-eb58b1608e6a /boot xfs defaults 1 2
#/dev/sdb1 /home xfs defaults,usrquota,grpquota 1 2
UUID=bc6779ef-36cb-41ed-8f5d-21d2e7248b6b swap swap defaults 0 0
/dev/disk/by-uuid/831da725-3de4-46de-b6d4-30d15fd92d25 /mnt/831da725-3de4-46de-b6d4-30d15fd92d25 auto nosuid,nodev,nofail,x-gvfs-show 1 2

When you changed /etc/fstab /home is now on the / drive (sdb2) which may or may not be empty but now whatever was in your users home directories does not show up under /home/ anymore. What is currently on sda1 (/mnt/831da725-3de4-46de-b6d4-30d15fd92d25) and what is its purpose?

Thanks a lot. This is my hard disk(16 TB) and all my data and tools in this disk. I want to mount /sda1 as /home.

Please reboot the system, log in as root, and post the contents of /boot and /home.

Also, when you're logged in as root, what happens if you open a terminal and run "su - user", where user is the username you are trying to log in as and failing.

I can go to any user using su user. but there is nothing without a user "act" this user was created at the very beginning.

[root@workstation01 ~]# cd /boot
[root@workstation01 boot]# ls
config-3.10.0-229.11.1.el7.x86_64
config-3.10.0-229.14.1.el7.x86_64
config-3.10.0-229.7.2.el7.x86_64
config-3.10.0-229.el7.x86_64
extlinux
grub
grub2
initramfs-0-rescue-0f1e31e901a7431887b53be42b60a009.img
initramfs-3.10.0-229.11.1.el7.x86_64.img
initramfs-3.10.0-229.11.1.el7.x86_64kdump.img
initramfs-3.10.0-229.14.1.el7.x86_64.img
initramfs-3.10.0-229.14.1.el7.x86_64.img.backup
initramfs-3.10.0-229.14.1.el7.x86_64kdump.img
initramfs-3.10.0-229.7.2.el7.x86_64.img
initramfs-3.10.0-229.7.2.el7.x86_64kdump.img
initramfs-3.10.0-229.7.2.el7.x86_64-nouveau.img
initramfs-3.10.0-229.el7.x86_64.img
initramfs-3.10.0-229.el7.x86_64kdump.img
initrd-plymouth.img
nvidia.tx
shulav
symvers-3.10.0-229.11.1.el7.x86_64.gz
symvers-3.10.0-229.14.1.el7.x86_64.gz
symvers-3.10.0-229.7.2.el7.x86_64.gz
symvers-3.10.0-229.el7.x86_64.gz
System.map-3.10.0-229.11.1.el7.x86_64
System.map-3.10.0-229.14.1.el7.x86_64
System.map-3.10.0-229.7.2.el7.x86_64
System.map-3.10.0-229.el7.x86_64
vmlinuz-0-rescue-0f1e31e901a7431887b53be42b60a009
vmlinuz-3.10.0-229.11.1.el7.x86_64
vmlinuz-3.10.0-229.14.1.el7.x86_64
vmlinuz-3.10.0-229.7.2.el7.x86_64
vmlinuz-3.10.0-229.el7.x86_64
[root@workstation01 boot]# cd /home/
[root@workstation01 home]# ls
act
[root@workstation01 home]# su zillur
bash-4.2$ ls
act
bash-4.2$ su shulav
Password:
bash-4.2$ ls
act
bash-4.2$

Looks like you have a weird combination of home directories in both locations.

act has a directory in /home, and shulav has a directory in /boot, but those are the only ones I see. How was the user "zillur" created? How many users do you have? What happens if you try to su to act? Also, you should be using "su - user" as I provided in my example, not "su user".

To start with you should move shulav from /boot to /home. I don't see anything else in /boot that doesn't belong.

Which user are you trying to log in as on the GUI when it hangs?

Thank you very much.I can login as "act" and "root". After login as "act" now how can I fix all these problems?

First move shulav from /boot to /home. We also need to figure out what happened to zillur's home directory since it's not in either location, as well as any other users you've created on the system.

Once everything that needs to be in /home has been moved to /home, you need to log out as all regular users and log in as root (either on the GUI or a TTY, I prefer the TTY since I don't like logging in as root on the GUI). Use "w" to verify no other users are logged in, and also make sure sda1 is mounted at /mnt/831da725-3de4-46de-b6d4-30d15fd92d25. Then then run the following:
Then log out as root and log in as your regular user again, verify everything works and looks as expected. Once you're sure it looks right, add the new mount to /etc/fstab:
and remove the old line that was mounting it in /mnt, and reboot.

Once you're sure everything is correct, you can remove /home.backup

By mounting sda1 on /home the OP will still have still have a messy combination of data and tools in the /home directory. IMHO it would be best to separate them...

I agree, but that's where he said he wanted it mounted, so that's what I went with. It would also be possible to mount sda1 elsewhere and create a directory inside of it for all of the users' home directories, then bind mount that to /home, or change the default home directory for all users from /home to this new location. Lots of options.

Yep. lots of options.

Thank you all for your valuable suggestions. Now I can login as any user. I have another question. I installed some tools in "/home/zillur/Desktop/zillur/Tools" this folder. like:
bcftools-1.2
bcftools-1.2.tar.bz2
bowtie2-2.2.5
bowtie2-2.2.5-linux-x86_64.zip
epel-release-latest-7.noarch.rpm
fastqc
GenomeAnalysisTK-3.4-46.tar.bz2
etc.
I can run them as user "zillur"
I want to allow my other users to run this tools. How can I do this?

Best Regards
Zillur

You need to place them somewhere neutral, where all users have access. A common location is /usr/local/

1 members found this post helpful.

Thank you very much. I have moved this folder to /usr/local. Then what I need to do? after moving this: /usr/local/Tools, my tools are not working. Like:
[zillur@workstation01 Tools]$ bowtie2
bash: bowtie2: command not found...
Maybe I am missing something.
Best Regards
Zillur

You'll need to add /usr/local/Tools to your PATH. To make it permanent make this change in one of your startup scripts, like .bashrc or .bash_profile, or the startup script for whatever shell you use, eg:

Then either source .bashrc, or log out and back in, or open a new terminal, etc.

1 members found this post helpful.