Ask Your Question

Fedora20 behavior is strange after a hdd mounted as /home

asked 2014-09-25 11:02:52 -0500

malmed gravatar image

updated 2014-09-28 23:48:20 -0500

mether gravatar image

Hello, I installed Fedora20 on ssd disk and then I wanted to move /home on second hard disk. I followed this manual: , but not completely because /home was created as logical volume on ssd. (I mounted in /etc/fstab original home to /home-orig and hdd as /home with copied contend of /home-orig.) Everything seems ok after reboot so I remove logical volume with home from ssd ( > lvremove ).

But some things are working differently now. Google chrome can't display any site or setting, but it seems me that is running ... you can see tabs, but not content). I tried delete chrome's .cache/google-chrome and .config/google-chrome and reinstall chrome. It helps until I logged to my google account. Or, when I try add new user (settings > user > unlock and add) it ends with: Failed to add account running '/usr/sbin/useradd' failed: Child process exited with code 12 And I am afraid of I'll find more such things.

Any suggestions what is different between old and new home? Thanks.

edit retag flag offensive close merge delete


Thank you, randomuser. It solves the problem.

malmed gravatar imagemalmed ( 2014-09-25 15:29:11 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2014-09-25 11:49:51 -0500

updated 2014-09-26 08:45:28 -0500


restorecon -R /home

Fedora uses SELinux, which labels files and processes to make sure that a given service or user is confined to only seeing the files and resources they are allowed to. For example, you don't want your web server to be reading your personal files in /home so that is disabled by default.

When you copied the files from the old home to the new, the SELinux contextx did not come with. Usually copied files will get the default context of the target directory, so I'm guessing that the new home was not mounted at /home when you copied to it.

restorecon simply restores the default contexts of a given file or path.

fixfiles onboot will trigger a relabel of the entire system when you next reboot.

ls -Z /home will show the context on the files in /home

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2014-09-25 11:02:52 -0500

Seen: 470 times

Last updated: Sep 26 '14