touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

This seems to be the interesting excerpt from the log, for /home (which
is on partition UUID=bb22..). The home.mount unit is bound to the
corresponding .device unit for the partition, but this somehow goes
wrong:

$ egrep 'bb22.*device|home.mount' /tmp/systemd-nomounts.log
Feb 09 17:23:59 duhast systemd[1]: home.mount changed dead -> mounted
Feb 09 17:23:59 duhast systemd[1]: Unit home.mount is bound to inactive service. Stopping, too.
Feb 09 17:23:59 duhast systemd[1]: Trying to enqueue job home.mount/stop/fail
Feb 09 17:23:59 duhast systemd[1]: Installed new job home.mount/stop as 9
Feb 09 17:23:59 duhast systemd[1]: Enqueued job home.mount/stop as 9
Feb 09 17:23:59 duhast systemd[1]: Job home.mount/stop finished, result=canceled
Feb 09 17:23:59 duhast systemd[1]: Installed new job home.mount/start as 59
Feb 09 17:23:59 duhast systemd[1]: Installed new job dev-disk-by\x2duuid-bb228002\x2dfcfc\x2d49ba\x2dbe13\x2d8d62ea7d940e.device/start as 60
Feb 09 17:23:59 duhast systemd[1]: Expecting device dev-disk-by\x2duuid-bb228002\x2dfcfc\x2d49ba\x2dbe13\x2d8d62ea7d940e.device...
Feb 09 17:24:01 duhast systemd[1]: dev-disk-by\x2duuid-bb228002\x2dfcfc\x2d49ba\x2dbe13\x2d8d62ea7d940e.device changed dead -> plugged
Feb 09 17:24:01 duhast systemd[1]: Job dev-disk-by\x2duuid-bb228002\x2dfcfc\x2d49ba\x2dbe13\x2d8d62ea7d940e.device/start finished, result=done
Feb 09 17:24:04 duhast systemd[1]: Job home.mount/start finished, result=done
Feb 09 17:24:09 duhast systemd[1]: home.mount changed mounted -> dead
Feb 09 17:24:13 duhast systemd[3556]: dev-disk-by\x2duuid-bb228002\x2dfcfc\x2d49ba\x2dbe13\x2d8d62ea7d940e.device changed dead -> plugged
Feb 09 17:25:42 duhast systemd[6834]: dev-disk-by\x2duuid-bb228002\x2dfcfc\x2d49ba\x2dbe13\x2d8d62ea7d940e.device changed dead -> plugged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1419623

Title:
  systemd init is no mounting drives from fstab

Status in systemd package in Ubuntu:
  New

Bug description:
  This seems to have been triggered by the glib update on ubuntu-desktop
  ppa. No partitions from fstab (apart from root of course) are getting
  mounted at boot. This is just a little problematic when /home is on a
  different partition!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-7ubuntu1 [modified: lib/systemd/system/ifup@.service]
  ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4
  Uname: Linux 3.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  9 17:30:12 2015
  InstallationDate: Installed on 2012-09-23 (869 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922)
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-12-generic root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash init=/lib/systemd/systemd systemd.log_level=debug
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P67A-UD3R-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P67A-UD3R-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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