Can't mount on booting-what's going on ? (Karmic)

Discussion in 'all things UNIX' started by Ocky, Jan 29, 2010.

Thread Status:
Not open for further replies.
  1. Ocky

    Ocky Registered Member

    Joined:
    May 6, 2006
    Posts:
    2,677
    Location:
    George, S.Africa
    Call for help from my wife just received. Something new that hasn't occured before.
    On initially booting up the laptop she gets this message:-

    'One or more of the mounts listed in etc/fstab cannot yet be mounted'

    and:-

    init:ureadahead-other main process (1106)terminated with status 4
    Ditto for process (1112)

    and:-

    /home waiting for UUID=df220301xxxxxxxxxx

    Press Control + D to try again.
    Press ESC to enter a recovery shell. (It's root BTW)

    I reinstalled grub2 from live CD but to no avail.

    Saw this and wonder whether it's OK:-

    http://creativeinstantia.blogspot.com/2009/11/upgrade-to-karmic-koala-kubuntu-910.html
    Others:-
    http://ubuntu-ky.ubuntuforums.org/showthread.php?t=1318593

    I will try some more but a fast-track solution would be nice. :)
     
  2. dan_maran

    dan_maran Registered Member

    Joined:
    Aug 30, 2004
    Posts:
    1,053
    Location:
    Stamford, CT
    This just showed up now? This should have been an issue if/when you upgraded from 9.04/9.10 if at all. (This is according to those links)

    I have seen some issues with this during normal updates though, I can't remember exactly what it was that fixed it.
    I _think_ it was that fstab somehow got the wrong UUIDs and needed to have them corrected in my case. And this was on an 8.04 install.
    Try running $blkid and compare it to the /etc/fstab and see if the UUIDs match.
     
  3. Ocky

    Ocky Registered Member

    Joined:
    May 6, 2006
    Posts:
    2,677
    Location:
    George, S.Africa
    Yes, showed up for the first time now since I did a clean install for her in November.
    Gparted in Live CD shows all partitions as mounted (unmounted greyed out).
    blkid doesn't even show sda6 the /home partition.
    See below:-

    ubuntu@ubuntu:~$ sudo blkid
    /dev/loop0: TYPE="squashfs"
    /dev/sda1: UUID="2c5f817e-48d6-4a46-b88e-26a328990a1c" TYPE="ext4"
    /dev/sda5: UUID="e851961c-c920-4e4a-b2ed-e9d6bf953bf7" TYPE="swap"
    /dev/sda7: UUID="d164403e-c050-41ac-8cb0-647812d0db64" TYPE="ext4"
    /dev/sdb1: SEC_TYPE="msdos" UUID="1804-5C08" TYPE="vfat"
    ubuntu@ubuntu:~$

    ..and fstab

    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc defaults 0 0
    # / was on /dev/sda1 during installation
    UUID=2c5f817e-48d6-4a46-b88e-26a328990a1c / ext4 errors=remount-ro 0 1
    # /backups was on /dev/sda7 during installation
    UUID=d164403e-c050-41ac-8cb0-647812d0db64 /backups ext4 defaults 0 2
    # /home was on /dev/sda6 during installation
    UUID=df220301-7dbb-42f2-a77c-9833f0c23fc1 /home
    ext4 defaults 0 2
    # swap was on /dev/sda5 during installation
    UUID=e851961c-c920-4e4a-b2ed-e9d6bf953bf7 none swap sw 0 0
    /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

    Edit: this is what I have - will try UUID's to labels and see what happens.
    https://bugs.launchpad.net/ubuntu/ bug/511963
     
    Last edited: Jan 29, 2010
  4. dan_maran

    dan_maran Registered Member

    Joined:
    Aug 30, 2004
    Posts:
    1,053
    Location:
    Stamford, CT
    Interesting how your "fix" worked. I hope someone on the bug tracker can get to looking into it. No custom kernel or anything right?
     
  5. Ocky

    Ocky Registered Member

    Joined:
    May 6, 2006
    Posts:
    2,677
    Location:
    George, S.Africa
    Ok fixed. Replaced UUID's with dev labels. Her fstab now looks like this:-

    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc defaults 0 0
    # / was on /dev/sda1 during installation
    /dev/sda1 / ext4 errors=remount-ro 0 1
    # /backups was on /dev/sda7 during installation
    /dev/sda7 /backups ext4 defaults 0 2
    # /home was on /dev/sda6 during installation
    /dev/sda6 /home ext4 defaults 0 2
    # swap was on /dev/sda5 during installation
    /dev/sda5 none swap sw 0 0
    /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

    Mystery as to what went wrong in the first place.o_O
     
Loading...
Thread Status:
Not open for further replies.