UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The hard drive, or partition that the data of your home is dictated by your /etc/fstab.
If you just mount a partition there, you won't see any of your existing home stuff, that's why you have to copy your data over to the new partition/drive first then mount the drive/partition in your /etc/fstab.
When you use tar, it's like a zip file, so it didn't remove your existing stuff. I personally use tar.gz for this, as it's less compression than bzip but a little more than simply tar.
I suspect you didn't use tar command properly. Maybe you should make another one, then move it over to the new drive/partition then extract the contents there.
Is it possible, that you do not have "write access" to the drive you tried to extract the contents too?
Can anybody tell me what to change?
@imageaxion:
The error message is just to long to post, I think about a thousand times my screen...
But if you think it is useful I can give you some examples
i think old_fogie will have to help you with this one or someone else...
from looking at your last post and from what i understand about mount partitions etc, it looks like when you installed the system you somehow made media/daten1 a partition and the location of your home folder
this is a bit confusing for me...
if i was in you position i would do a reinstall and make sure i had the partition table set up correctly
this is not exactly good advice i know but if you are really struggling and some one else cant help that is what i suggest - if it is possible of course
kubuntu is a pretty good distro - one of the best and my second choice after debian.
so good luck. if you come across anything that i can help with i will be glad to
Yes, /media/daten1 is a partition.
ubuntu didn't have it in /etc/fstab (just like /media/win), so I had to put it there manually. But it worked well, I could read and write, see the data I had put on it using windows, but then I just made /media/daten1 my homefolder...
I think I'll reinstall Ubuntu on Monday, if there isn't any other post until then.
Thanks, I already found the solution (changing the home folder worked with usermod -d) , so I really thank you all for allowing me to write this using kubuntu linux!
Oops ! looks like you've got the problem fixed, guess i'm too late to post this. Naah, I'll put it anywas, might help someone else
I had similar problems with my KDE when I used to have Kubuntu (I've got Xubuntu now ) and also thought that there were problems with my graphic card, but finally the problem was with file access permissions. KDE couldn't get access to the config files in my home folder.
What I did was to see if KDE works as root. In a terminal, logged in, then typed:
Code:
sudo startx
and surprise ! KDE worked, the only problem was it was working as being root, which isn't the best of ideas.
So since that worked, I went back to the terminal and did this little trick:
I also discovered that kdm also bugged if my disk was full. funny eh ?
Not surprising. No place to put the log and error files. Once on Debian 3.1 (long time ago) I found that my 32 gigabyte disk had no space left on it because of 25-gigs of errors logged from xorg and kdm. Deleted the logfiles and BAM! I had diskspace again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.