[Bug 1067836] Re: Disk drive for /tmp error displayed briefly after Lubuntu PP -> QQ dist-upgrade

Erick Brunzell lbsolost at yahoo.com
Thu Oct 18 17:15:05 UTC 2012


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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1067836

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

Status in “mountall” package in Ubuntu:
  Incomplete

Bug description:
  This error appears very briefly (10 to 15 seconds) when booting the OS
  after upgrading from Lubuntu i386 Precise to Lubuntu i386 Quantal.
  Please see the attached picture - sorry it's a bit blurry.

  It only appears during the first boot after upgrade, thereafter
  Lubuntu boots fine, so I don't think it's serious but I wanted to
  create a bug report so Phill and Julien could decide if it should be
  mentioned in the release notes.

  Should they choose to add a note to the release notes I can absolutely
  say that if the user just waits rather than pressing any keys the
  initial boot is successful and, as I previously said, it does not
  appear thereafter.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: update-manager 1:0.174.3
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  ApportVersion: 2.6.1-0ubuntu3
  Aptdaemon:
   
  Architecture: i386
  CurrentDmesg.txt:
   [   14.308090] r8169 0000:02:00.0: >eth0: link up
   [   14.308644] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   43.638772] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
  Date: Wed Oct 17 12:48:57 2012
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'launch-time' b'1350473407'
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'500'
   b'com.ubuntu.update-manager' b'window-width' b'600'
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: update-manager
  UpgradeStatus: Upgraded to quantal on 2012-10-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1067836/+subscriptions




More information about the foundations-bugs mailing list