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

[nomnex]

Ubuntu 9.10
2.6.31-17-generic
Fresh install (not an upgrade)

I have been using the new Karmic on my notebook a couple of days just fine (just installed). This morning I couldn't pass the first splash screen - black and white logo. 10 consecutive shut-downs did not help. message:

      One or more of the mounts listed in /etc/fstab cannot yet be mounted:
      /home/waiting for UUID=e2cca39c-70bb-46be-a5d1-2fdafe1dd2a1
      Press ESC to enter a recovery shell

Several bugs relate the same issue, but they occurred during a Karmic upgrade, and/or either with the swap or the root partition.

From the recovery shell, fstab seemed fine. Running "blkid" however returned the UUID of 2 of the 3 devices:

/dev/sda1 /
/dev/sda5 /home - this one was missing
/dev/sda2 /swap

Following bug: https://bugs.launchpad.net/ubuntu/+bug/505751, I have replaced the UUID for each device by its label and I could log-in. This time, running "blkid" returned the UUID of my 3 devices. I have modified the fstab back to its original state (labels > UUID). The system seems working again.

I don't explain why I could not log-in Karmic in the normal course of its utilisation?
Why changing /home's UUID for its label, and reverting to its UUID solved - so far - the issue?

[Russel Winder (russel)]

I have a workstation with a fresh Karmic install and am seeing that all my NFS mounts are failing at boot time with this same message:

One or more of the mounts listed in /etc/fstab cannot yet be mounted:
. . .
Press ESC to enter a recovery shell.

Is this bug effectively a duplicate of 461133 which is reported to be a duplicate of 470776

On trying to mount things manually in the "repair shell" I get:

mount.nfs: DNS resolution failed for . . .

for the server for each mount.

Seems like mount is being called before DNS look ups are set up.

[narnie (signupnarnie)]

I, too, have this bug on a fresh install of Ubuntu karmic from intrepid.

This wasn't a dist-upgrade. I wiped / (/home is on a separate partition as above). Then during install mounted /dev/sda6 (as is my system setup) to /home.

I can always log on, but I sometimes get the same error as above barring a different UUID, of course. It might wait a bit. The above error doesn't ALWAYS happen. It is sporadic. Sometimes the error goes away, but other times it stays through the entire boot sequence. I can ALWAYS log on and, hence, always find my /dev/sda6 on /home where it should be.

For me, it is just an irritant ruining the "beauty" of the boot process to have this annoying message. I would love to know the underlying cause. I may play with the way it was "fixed" above later.

Narnie

[narnie (signupnarnie)]

BWT, I have this on EVERY machine I have installed Karmic on. Including 3 brand new Acer Aspire One's that had no previous ubuntu on them. The only difference from the base install was my running gparted 1st to have more advance partitioning while shrink this "other" OS that came preinstalled and installing home to /dev/sda6 on all machines

[Scott James Remnant (Canonical) (canonical-scott)]

nomnex: thanks for the tar files - I think you had a transient problem which has been since fixed - changing to the label was enough to get the device mounted and fix the problem

[nomnex (nomnex)]

Scott: you are welcome, and sorry for posting the .tar at the wrong place. Bug 511963 relates an upgrade. Mine happened on a fresh install, all of a sudden, after a few days of use without incident, so assumption was wrong, they can't be marked as duplicate bugs.