[Bug 1615185] [NEW] ubuntu does not remove folders for mounted drives in /media on reboot

Rocko rockorequin at hotmail.com
Sat Aug 20 04:33:24 UTC 2016


Public bug reported:

Whenever I reboot, if there are drivers mounted with corresponding
folders in /media (whether internal or external, btfrs, ntfs, or ext4),
after the reboot the original folder is still present and the drives re-
mount in a new folder. (Note that I mount drives in /media instead of
/media/<username> so that all users can access them, in case this is
relevant.)

eg if there was a file mounted in /media/drive, after reboot there is an
empty folder /media/drive and a new one /media/drive1 with the drive
mounted in it. A subsequent reboot means there will be /media/drive,
/media/drive1, and /media/drive2, and so on until I manually remove the
old folders.

I'm guessing that the issue is that systemd is not unmounting the drives
properly on reboot since is a problem in Ubuntu 16.04 as well as
yakkety. It's unlikely to be a lack-of-time issue since sometimes on
reboot systemd will wait for 90 seconds or more for the cryptfs swap to
unmount before giving up.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-4
ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
Uname: Linux 4.4.0-9134-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 20 12:27:37 2016
InstallationDate: Installed on 2016-07-04 (46 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
MachineType: Dell Inc. XPS 15 9550
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-9134-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  ubuntu does not remove folders for mounted drives in /media on reboot

Status in systemd package in Ubuntu:
  New

Bug description:
  Whenever I reboot, if there are drivers mounted with corresponding
  folders in /media (whether internal or external, btfrs, ntfs, or
  ext4), after the reboot the original folder is still present and the
  drives re-mount in a new folder. (Note that I mount drives in /media
  instead of /media/<username> so that all users can access them, in
  case this is relevant.)

  eg if there was a file mounted in /media/drive, after reboot there is
  an empty folder /media/drive and a new one /media/drive1 with the
  drive mounted in it. A subsequent reboot means there will be
  /media/drive, /media/drive1, and /media/drive2, and so on until I
  manually remove the old folders.

  I'm guessing that the issue is that systemd is not unmounting the
  drives properly on reboot since is a problem in Ubuntu 16.04 as well
  as yakkety. It's unlikely to be a lack-of-time issue since sometimes
  on reboot systemd will wait for 90 seconds or more for the cryptfs
  swap to unmount before giving up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-4
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
  Uname: Linux 4.4.0-9134-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 20 12:27:37 2016
  InstallationDate: Installed on 2016-07-04 (46 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
         Users in the 'systemd-journal' group can see all messages. Pass -q to
         turn off this notice.
   No journal files were opened due to insufficient permissions.
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-9134-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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



More information about the foundations-bugs mailing list