{"action":"created","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/230","labels_url":"https://api.github.com/repos/systemd/systemd/issues/230/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/230/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/230/events","html_url":"https://github.com/systemd/systemd/issues/230","id":88772345,"number":230,"title":"Cannot mount /boot after removing usb device","user":{"login":"micah","id":2832,"avatar_url":"https://avatars.githubusercontent.com/u/2832?v=3","gravatar_id":"","url":"https://api.github.com/users/micah","html_url":"https://github.com/micah","followers_url":"https://api.github.com/users/micah/followers","following_url":"https://api.github.com/users/micah/following{/other_user}","gists_url":"https://api.github.com/users/micah/gists{/gist_id}","starred_url":"https://api.github.com/users/micah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/micah/subscriptions","organizations_url":"https://api.github.com/users/micah/orgs","repos_url":"https://api.github.com/users/micah/repos","events_url":"https://api.github.com/users/micah/events{/privacy}","received_events_url":"https://api.github.com/users/micah/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-16T16:19:49Z","updated_at":"2015-06-17T14:51:35Z","closed_at":"2015-06-17T10:24:37Z","body":"Hi,\r\n\r\nI have my /boot partition on a USB stick. It is inserted to the machine to boot it, and is configured to be mounted read-only in the fstab. \r\n\r\nI used to be able to simply remove the usb from the system after it has booted, and udev would remove the mount point. Then when I wish to have it available again (for example, when I need to regenerate an initramfs), I would insert the USB, and then mount /boot as rw for the operation, then unmount it again. One could argue that I should 'umount /boot' before removing the device from the system, however this shouldn't matter.\r\n\r\nNow, if I remove the device from the system (or umount /boot and then remove the device) it is no longer mounted, as before. However, I cannot mount it again, it simply doesn't show up in mount:\r\n\r\n```\r\nroot@muck:/home/micah# umount /boot\r\n\r\n[remove device from system]\r\n\r\nroot@muck:/home/micah# df\r\nFilesystem     1K-blocks      Used Available Use% Mounted on\r\nudev               10240         0     10240   0% /dev\r\ntmpfs            3274344      1456   3272888   1% /run\r\n/dev/dm-0      113290912 103756284   3756660  97% /\r\ntmpfs            8185860    133016   8052844   2% /dev/shm\r\ntmpfs               5120         4      5116   1% /run/lock\r\ntmpfs            8185860         0   8185860   0% /sys/fs/cgroup\r\ntmpfs            1637172         4   1637168   1% /run/user/1000\r\n\r\n[insert device]\r\n\r\nroot@muck:/home/micah# mount /boot\r\nroot@muck:/home/micah# df\r\nFilesystem     1K-blocks      Used Available Use% Mounted on\r\nudev               10240         0     10240   0% /dev\r\ntmpfs            3274344      1456   3272888   1% /run\r\n/dev/dm-0      113290912 103756284   3756660  97% /\r\ntmpfs            8185860    133016   8052844   2% /dev/shm\r\ntmpfs               5120         4      5116   1% /run/lock\r\ntmpfs            8185860         0   8185860   0% /sys/fs/cgroup\r\ntmpfs            1637172         4   1637168   1% /run/user/1000\r\n```\r\nThe device is inserted in the system and available, it shows up in dmesg. This is what the journal says when I umounted:\r\n\r\n```\r\nJun 16 12:13:43 muck kernel: EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null)\r\nJun 16 12:13:43 muck systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\\x2duuid-2ddd48ad\\x2d2e02\\x2d492e\\x2db5d7\\x2df95e8e91ebac.device. Stopping, too.\r\nJun 16 12:13:43 muck systemd[1]: Unmounting /boot...\r\nJun 16 12:13:43 muck systemd[1]: Unmounted /boot.\r\n```\r\n\r\nhuh, ok, so it immediately unmounted it? Thats odd... \r\n\r\n```\r\nroot@muck:/home/micah# systemctl status dev-disk-by\\x2duuid-2ddd48ad\\x2d2e02\\x2d492e\\x2db5d7\\x2df95e8e91ebac.device\r\n● dev-disk-byx2duuid-2ddd48adx2d2e02x2d492ex2db5d7x2df95e8e91ebac.device\r\n   Loaded: loaded\r\n   Active: inactive (dead)\r\n```\r\n\r\nok its because its inactive, lets activate it:\r\n\r\n```\r\nroot@muck:/home/micah# systemctl start dev-disk-by\\x2duuid-2ddd48ad\\x2d2e02\\x2d492e\\x2db5d7\\x2df95e8e91ebac.device\r\nJun 16 12:15:32 muck polkitd(authority=local)[1549]: Registered Authentication Agent for unix-process:28960:592467 (system bus name :1.138 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)\r\nJun 16 12:17:01 muck CRON[29160]: pam_unix(cron:session): session closed for user root\r\nsystemctl status dev-disk-by\\x2duuid-2ddd48ad\\x2d2e02\\x2d492e\\x2db5d7\\x2df95e8e91ebac.deviceJun 16 12:17:02 muck systemd[1]: dev-disk-byx2duuid-2ddd48adx2d2e02x2d492ex2db5d7x2df95e8e91ebac.device: Job dev-disk-byx2duuid-2ddd48adx2d2e02x2d492ex2db5d7x2df95e8e91ebac.device/start timed out.\r\nJun 16 12:17:02 muck systemd[1]: Timed out waiting for device dev-disk-byx2duuid-2ddd48adx2d2e02x2d492ex2db5d7x2df95e8e91ebac.device.\r\nJun 16 12:17:02 muck systemd[1]: dev-disk-byx2duuid-2ddd48adx2d2e02x2d492ex2db5d7x2df95e8e91ebac.device: Job dev-disk-byx2duuid-2ddd48adx2d2e02x2d492ex2db5d7x2df95e8e91ebac.device/start failed with result 'timeout'.\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/systemd/systemd/issues/comments/112829894","html_url":"https://github.com/systemd/systemd/issues/230#issuecomment-112829894","issue_url":"https://api.github.com/repos/systemd/systemd/issues/230","id":112829894,"user":{"login":"dkg","id":66738,"avatar_url":"https://avatars.githubusercontent.com/u/66738?v=3","gravatar_id":"","url":"https://api.github.com/users/dkg","html_url":"https://github.com/dkg","followers_url":"https://api.github.com/users/dkg/followers","following_url":"https://api.github.com/users/dkg/following{/other_user}","gists_url":"https://api.github.com/users/dkg/gists{/gist_id}","starred_url":"https://api.github.com/users/dkg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dkg/subscriptions","organizations_url":"https://api.github.com/users/dkg/orgs","repos_url":"https://api.github.com/users/dkg/repos","events_url":"https://api.github.com/users/dkg/events{/privacy}","received_events_url":"https://api.github.com/users/dkg/received_events","type":"User","site_admin":false},"created_at":"2015-06-17T14:51:35Z","updated_at":"2015-06-17T14:51:35Z","body":"Is this a duplicate of some other bug report?  if so, which one?\r\n\r\nIs it fixed with a specific git commit?  if so, which one?\r\n\r\nHow is micah supposed to know which patch to urge his distro to backport, since it clearly isn't fixed for him?"}}