Disk drive for /tmp error displayed briefly after Lubuntu PP -> QQ dist-upgrade

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1067836

I just performed an Lubuntu amd64 dist-upgrade test and did not see this so it's likely hardware related.

This latest amd64 test that did NOT display this error was performed on this hardware:

AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
nVidia MCP61 High Definition Audio (rev a2)
nVidia MCP61 Ethernet (rev a2)
2GB DDR2 RAM

All of the tests that did display this error using the i386 image were performed on this hardware:

Intel Atom CPU 230 @ 1.60GHz
Intel 82945G/GZ Integrated Graphics Controller (rev 02)
Intel N10/ICH 7 Family High Definition Audio Controller (rev 01)
Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
2GB DDR2 RAM

I hope that info is helpful.

Please attach the /etc/fstab from the affected machine.

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

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.

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?

If I did that right it returns nothing:

lance@lance-desktop:~$ mount | grep /tmp
lance@lance-desktop:~$

Later today I'm going to dist-upgrade a highly modified Ubuntu Precise to Quantal. By highly modified I mean it's using 'gnome-session-fallback' with a bunch of gconf and dconf tweaks. So I'll see if I get the same behavior with that Ubuntu.

All of the Lubuntu tests I've done began with a totally fresh and updated Lubuntu Precise, no modifications, and I was just using the command 'update-manager -d -c'.

I'm guessing that by the time I get to the next test the upgrade process will be "official" so I can just use the update-manager. I must now take care of some non-puter issues that can't wait.

Status changed to 'Confirmed' because the bug affects multiple users.

I've now upgraded 3 laptops from Kubuntu 12.04 to 12.10 and all of them have shown this message on the first boot after upgrading. I checked in each system's /etc/fstab and found nothing that might cause this.

Some reports suggest this may be the same as bug #1059471, though I don't currently understand how. You may want to check if the problem goes away using mountall 2.43 from raring, or the 2.42ubuntu0.1 which should soon be available in quantal-proposed.

I get this on every single boot, and have done since upgrading from Precise. The message starts off white and then turns blue, before eventually continuing to boot. /tmp is not mounted.

If I try to mount /tmp after boot, it fails like this:

# mount /tmp
mount: unknown filesystem type 'none'

I do not know where the filesystem type is specified. It's certainly not in fstab.

I have the same issue. Just upgraded from 12.04. Every boot it returns "Can not mount /tmp"