[SOLVED] partial upgrade or update /home/user not found anymore on software raid0 partition
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
partial upgrade or update /home/user not found anymore on software raid0 partition
I have Ubuntu Studio Lucid 64 (pre-empt kernel) on a software raid 0 partition (md0). My /home is supposed to be on another raid 0 partition (md1).
I believe that in my tiredness I may have ran a partial upgrade which didn't succeed in loading the latest kernel -30, so I am still on -28.
I couldn't boot into my system anymore, so I tried recovery, and chose to repair broken pkgs, (also apt-get clean since I also had a message that my /boot partition was 100% full- which is ok now).
What I can do at this point is to boot into a blank desktop with no access to programs or my files etc....
ERROR:could not update ICEauthority file /home/user.ICEauthority
nautilus could not create the following required folders
pls. create therse folders or set the permissions such that nautilus can create them.
I worked from TTY console or recovery console and attempted various recommended chown but get message that/home/usr is not found:
"/home/user" "file does not exist"
lists swap files only no / or /home ...Is this normal? If not how can I still be accessing / then? Other Ubuntu versions on same and other computers seem to have / and /home partitions in fstab. Could a partial upgrade that didn't get fully installed mess up fstab?
From terminal and cding to /home and typing:
shows 2 lines with permissions etc ending in .
but NO lines showing lost+found
here's an example of a working OS also on a md0 partition on another computer:
user@computer:/home$ ls -la
drwxr-xr-x 4 root root 4096 2008-10-25 07:13 .
drwxr-xr-x 22 root root 4096 2011-04-05 12:48 ..
drwx------ 2 root root 16384 2008-10-25 06:38 lost+found
drwxr-xr-x 69 user user 4096 2011-04-15 21:16 user
Some posts suggest to remove and re-install nautilus but I beleive I need to fix /home first...For all I know it may have been just a partial update-I was so tired. I did a couple of other things that had changed the permissions, but I didn't rm anything for certain!
Are my home contents lost?
Pls. re-installating the whole distribution is NOT an option and re-installing home will be tricky with software raid....any solutions???
Sorry, finished work today and now promised hubby to watch a movie on the computer in question, cause I have been at it for a couple of days (note: my generic non-raid Ubuntu boots fine)... ASAP afterwards, I will post it, check /proc/partitions and /proc/mounts and use DU disk utility as someone mentionned. Pls. bear with me, in case I have to reconstuct my software raid0, as I have never done anything like this, and don't want to mess things up furthur. I am worried since my multi drive/ OS set up was such a headache to get done, partly cause my MB had a quirk or 2, which I discovered only once 1/2 my OS were installed!
ok back...hope you'll get to see this, bhaslinux...
I was attempting to photograph my screen with the results, from my webcam on a long USB cable, but that was a fool's errand. Nope, I don't have a digital camera yet...
Looks like /home is missing from cat /proc/mounts! Its still listed by blkid, mdadm --detail/dev/md1, cat/proc/partitions, and cat /proc/mdstat. I'll try to list some details but that has to be it. Now the only problem is that blkid and sudo mdadm --detail/dev/md1 give different UUIDs for the raid partitions. Maybe it doesn't matter. I want to use nano and try to add the md1 device to cat /proc/mounts, but maybe I'll wait a little for a confirmation just to make sure...
/dev/md1: label "U Studio L Home" UUID:63626aef-46d0-49cc-83ei-7810029217d2 Type
I double checked and everything seems to correspond to the right /dev; for example my / is md0 and is around 45 Gigs total thus confirms that md1 is /home. BTW when if I changed permissions for a partition/directory and have a label like my /home above, without the _ between the words (U_Studio_L_Home) can this cause a problem? It seems to matter if I want it to be seen as a directory, correct?
Let me know if more info is needed!
Last edited by streams &dragonflies; 04-16-2011 at 11:42 PM.
bhaslinux, I have some good news! Before I had a chance to see these instructions to add to /proc/mount, I kept trying to add /home to fstab with nano. I had tried using the UUID, /dev/md1 /home ext4 defaults 0 0 and /dev/md1 /home ext4 relatime 0 0 and finally /dev/md1 /home ext4 defaults 0 2. And it only worked until a second reboot, which at that point, I didn't expect it to!
As soon as I was back with /home/my username and nautilus working again, the message with /boot being full 100% came up so I followed instructions and checked my linux-images in synaptic: It confirmed that last kernel had installed in /boot but failed due to dependancies:
I then I removed linux-image-2.6.32-30 & 2.6.32-21 & 2.6.32-25 pre-empt kernels (I marked the latter 2 for complete removal) and did:
Now everything works fine as before!!
I will keep note how to add lines in /proc/mounts for any future problems, because I wasen't using the right format so it gave me "invalid arguement". I will add more details if needed for anyone else who may run into a similar problem...