Comment 6 for bug 1067836

On Thu, Oct 18, 2012 at 05:15:05PM -0000, Erick Brunzell wrote:
> That fstab looks quite normal to me:

> # /etc/fstab: static file system information.
> #
> # Use 'blkid' 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 nodev,noexec,nosuid 0 0
> # / was on /dev/sda10 during installation
> UUID=a865446a-a89e-4faa-8117-1be88a7e07a3 / ext4 errors=remount-ro 0 1
> # swap was on /dev/sda9 during installation
> UUID=80627269-1ccd-4774-b4ea-a5ef8824ffaa none swap sw 0 0

Agreed, this looks normal.

> I want to stress again that the aforementioned warning only appears for
> about 10 to 15 seconds during the initial boot following the upgrade,
> all subsequent reboots thereafter work quite normally.

> I just wondered if it was worth mentioning in the Lubuntu Quantal
> release notes, just so users don't freak out.

There should be nothing specific to Lubuntu in such an issue. It is likely
an uncommon issue that can happen on any Ubuntu flavor. I just don't see at
the moment how it would happen at all if /tmp isn't listed as a mount point.

What does 'mount | grep /tmp' return after boot?