USB drive are not mounted automatically
My USB Drive is not mounted automatically but it has detected through lsusb.
I also used dconf-Editor but it is not working. Every time I have to mount manually through Disk Utility.
usb automount
asked Dec 29 '13 at 11:58
nafrinafri
56114
add a comment |
My USB Drive is not mounted automatically but it has detected through lsusb.
I also used dconf-Editor but it is not working. Every time I have to mount manually through Disk Utility.
usb automount
asked Dec 29 '13 at 11:58
nafrinafri
56114
add a comment |
My USB Drive is not mounted automatically but it has detected through lsusb.
I also used dconf-Editor but it is not working. Every time I have to mount manually through Disk Utility.
usb automount
asked Dec 29 '13 at 11:58
nafrinafri
56114
My USB Drive is not mounted automatically but it has detected through lsusb.
I also used dconf-Editor but it is not working. Every time I have to mount manually through Disk Utility.
usb automount
usb automount
asked Dec 29 '13 at 11:58
nafrinafri
56114
asked Dec 29 '13 at 11:58
nafrinafri
56114
asked Dec 29 '13 at 11:58
nafrinafri
56114
asked Dec 29 '13 at 11:58
nafrinafri
56114
asked Dec 29 '13 at 11:58
nafrinafri
56114
56114
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
A complete description for configuring auto-mount is given here:
https://help.ubuntu.com/community/Mount/USB
If this does not help, please insert your usb-stick and post the last lines of dmesg and syslog.
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
I don't know why the automount is no longer work even with org.gnome.desktop.media-handling.automount key set to true, but manually mounting by the utility Disks to mount it works.
– Yu Shen
Dec 29 '18 at 20:04
add a comment |
Have you recently not unmounted the drive correctly, either power failure or a crash while writing to or reading from the drive? This can cause errors with the drive and while once mounted it functions normally the superblock may have errors causing it to not mount correctly.
As Requist asked, check dmesg immediately after inserting you flash drive, you may see one of the last lines as "Volume was not properly unmounted. Some data may be corrupt. Please run fsck.".
Check the device label in gparted then run
sudo fsck /dev/xxx (swapping xxx for your device)
You may get some details back about an invalid Superblock.
Fixing this is dependent on the drive filesystem, is it ext4 or Fat32 etc?
Here's a page on repairing an ext4 superblock
If your drive is fat32 or other msdos type, then testdisk may help but be careful with this tool, with great power...
sudo apt-get install testdisk
sudo testdisk
here is a post on using testdisk to repair a fat32 superblock issue. It links to this post, read both before starting.
Hope it helps.
edited Mar 20 '17 at 10:18
Community♦
1
answered May 4 '16 at 13:28
JoolsJools
114
I was trying to figure out why a FAT32-formatted thumbdrive wasn't automounting in GNOME (the kernel was recognizing it just fine). When I set the label (I didn't look at it beforehand; I'm guessing that it was empty), it was immediately seen and mounted. Can you explain this behavior? I would assume that, if there wasn't a label, GNOME would just provide a placeholder in the UI. Do you have an opinion whether this was an underlying filesystem issue that was simply corrected by setting a label?
– Dustin Oprea
Dec 31 '16 at 17:36
It should still mount the drive and give it a default 'disk1' type label if none are present. This should be in /media/[username]/disk1 etc. Check your automount config with dconf-editor, check org.gnome.desktop.media-handling for specific configurations on automounting and Nautilus actions. More here help.ubuntu.com/community/Mount/USB
– Jools
Jan 5 '17 at 11:02
For my situation, dmesg did not show any error message of mount failure, it seemed that there is no event of mounting. There is a piece of message: "sd 0:0:0:0: [sdb] Spinning up disk..." then after that there were message indicating spinning ready. The last message is "[sdb] Attached SCSI disk", then the USB drive is not automounted. But with Disk, I was able to mount it.
– Yu Shen
Jan 12 at 15:31
For my above situation, maybe, there was some error message as they were in red color in dmesg: "[ 5925.011521] sd 0:0:0:0: [sdb] No Caching mode page found [ 5925.011530] sd 0:0:0:0: [sdb] Assuming drive cache: write through" after spinning ready. Before that there were also red messages: "[ 5920.917889] ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8 [ 5920.917899] ses 0:0:0:1: Failed to get diagnostic page 0x1 [ 5920.917906] ses 0:0:0:1: Failed to bind enclosure -19" after Spinning up disk...
– Yu Shen
Jan 12 at 15:46
add a comment |
This is a bug described in Bug #1768010: usbmount does not work on Bionic. The solution, also given in Unix & Linux Stack Exchange, is the following:
Edit the systemd-udevd configutation
sudo systemctl edit systemd-udevd
insert the following two lines:
[Service]
MountFlags=shared
then run:
sudo systemctl daemon-reload
sudo service systemd-udevd --full-restart
Note also that this workaround is not perfect: a delay of 40 seconds can be observed between the time an usb key is inserted an the time the auto-mount is fully executed.
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
It did not work for my Ubuntu 18.04 to solve the problem of no automount for USB drive.
– Yu Shen
Jan 12 at 15:47
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f397190%2fusb-drive-are-not-mounted-automatically%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
A complete description for configuring auto-mount is given here:
https://help.ubuntu.com/community/Mount/USB
If this does not help, please insert your usb-stick and post the last lines of dmesg and syslog.
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
I don't know why the automount is no longer work even with org.gnome.desktop.media-handling.automount key set to true, but manually mounting by the utility Disks to mount it works.
– Yu Shen
Dec 29 '18 at 20:04
add a comment |
A complete description for configuring auto-mount is given here:
https://help.ubuntu.com/community/Mount/USB
If this does not help, please insert your usb-stick and post the last lines of dmesg and syslog.
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
I don't know why the automount is no longer work even with org.gnome.desktop.media-handling.automount key set to true, but manually mounting by the utility Disks to mount it works.
– Yu Shen
Dec 29 '18 at 20:04
add a comment |
A complete description for configuring auto-mount is given here:
https://help.ubuntu.com/community/Mount/USB
If this does not help, please insert your usb-stick and post the last lines of dmesg and syslog.
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
A complete description for configuring auto-mount is given here:
https://help.ubuntu.com/community/Mount/USB
If this does not help, please insert your usb-stick and post the last lines of dmesg and syslog.
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
answered Dec 29 '13 at 12:46
RequistRequist
1,74811127
1,74811127
I don't know why the automount is no longer work even with org.gnome.desktop.media-handling.automount key set to true, but manually mounting by the utility Disks to mount it works.
– Yu Shen
Dec 29 '18 at 20:04
add a comment |
I don't know why the automount is no longer work even with org.gnome.desktop.media-handling.automount key set to true, but manually mounting by the utility Disks to mount it works.
– Yu Shen
Dec 29 '18 at 20:04
I don't know why the automount is no longer work even with org.gnome.desktop.media-handling.automount key set to true, but manually mounting by the utility Disks to mount it works.
– Yu Shen
Dec 29 '18 at 20:04
I don't know why the automount is no longer work even with org.gnome.desktop.media-handling.automount key set to true, but manually mounting by the utility Disks to mount it works.
– Yu Shen
Dec 29 '18 at 20:04
add a comment |
Have you recently not unmounted the drive correctly, either power failure or a crash while writing to or reading from the drive? This can cause errors with the drive and while once mounted it functions normally the superblock may have errors causing it to not mount correctly.
As Requist asked, check dmesg immediately after inserting you flash drive, you may see one of the last lines as "Volume was not properly unmounted. Some data may be corrupt. Please run fsck.".
Check the device label in gparted then run
sudo fsck /dev/xxx (swapping xxx for your device)
You may get some details back about an invalid Superblock.
Fixing this is dependent on the drive filesystem, is it ext4 or Fat32 etc?
Here's a page on repairing an ext4 superblock
If your drive is fat32 or other msdos type, then testdisk may help but be careful with this tool, with great power...
sudo apt-get install testdisk
sudo testdisk
here is a post on using testdisk to repair a fat32 superblock issue. It links to this post, read both before starting.
Hope it helps.
edited Mar 20 '17 at 10:18
Community♦
1
answered May 4 '16 at 13:28
JoolsJools
114
I was trying to figure out why a FAT32-formatted thumbdrive wasn't automounting in GNOME (the kernel was recognizing it just fine). When I set the label (I didn't look at it beforehand; I'm guessing that it was empty), it was immediately seen and mounted. Can you explain this behavior? I would assume that, if there wasn't a label, GNOME would just provide a placeholder in the UI. Do you have an opinion whether this was an underlying filesystem issue that was simply corrected by setting a label?
– Dustin Oprea
Dec 31 '16 at 17:36
It should still mount the drive and give it a default 'disk1' type label if none are present. This should be in /media/[username]/disk1 etc. Check your automount config with dconf-editor, check org.gnome.desktop.media-handling for specific configurations on automounting and Nautilus actions. More here help.ubuntu.com/community/Mount/USB
– Jools
Jan 5 '17 at 11:02
For my situation, dmesg did not show any error message of mount failure, it seemed that there is no event of mounting. There is a piece of message: "sd 0:0:0:0: [sdb] Spinning up disk..." then after that there were message indicating spinning ready. The last message is "[sdb] Attached SCSI disk", then the USB drive is not automounted. But with Disk, I was able to mount it.
– Yu Shen
Jan 12 at 15:31
For my above situation, maybe, there was some error message as they were in red color in dmesg: "[ 5925.011521] sd 0:0:0:0: [sdb] No Caching mode page found [ 5925.011530] sd 0:0:0:0: [sdb] Assuming drive cache: write through" after spinning ready. Before that there were also red messages: "[ 5920.917889] ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8 [ 5920.917899] ses 0:0:0:1: Failed to get diagnostic page 0x1 [ 5920.917906] ses 0:0:0:1: Failed to bind enclosure -19" after Spinning up disk...
– Yu Shen
Jan 12 at 15:46
add a comment |
Have you recently not unmounted the drive correctly, either power failure or a crash while writing to or reading from the drive? This can cause errors with the drive and while once mounted it functions normally the superblock may have errors causing it to not mount correctly.
As Requist asked, check dmesg immediately after inserting you flash drive, you may see one of the last lines as "Volume was not properly unmounted. Some data may be corrupt. Please run fsck.".
Check the device label in gparted then run
sudo fsck /dev/xxx (swapping xxx for your device)
You may get some details back about an invalid Superblock.
Fixing this is dependent on the drive filesystem, is it ext4 or Fat32 etc?
Here's a page on repairing an ext4 superblock
If your drive is fat32 or other msdos type, then testdisk may help but be careful with this tool, with great power...
sudo apt-get install testdisk
sudo testdisk
here is a post on using testdisk to repair a fat32 superblock issue. It links to this post, read both before starting.
Hope it helps.
edited Mar 20 '17 at 10:18
Community♦
1
answered May 4 '16 at 13:28
JoolsJools
114
I was trying to figure out why a FAT32-formatted thumbdrive wasn't automounting in GNOME (the kernel was recognizing it just fine). When I set the label (I didn't look at it beforehand; I'm guessing that it was empty), it was immediately seen and mounted. Can you explain this behavior? I would assume that, if there wasn't a label, GNOME would just provide a placeholder in the UI. Do you have an opinion whether this was an underlying filesystem issue that was simply corrected by setting a label?
– Dustin Oprea
Dec 31 '16 at 17:36
It should still mount the drive and give it a default 'disk1' type label if none are present. This should be in /media/[username]/disk1 etc. Check your automount config with dconf-editor, check org.gnome.desktop.media-handling for specific configurations on automounting and Nautilus actions. More here help.ubuntu.com/community/Mount/USB
– Jools
Jan 5 '17 at 11:02
For my situation, dmesg did not show any error message of mount failure, it seemed that there is no event of mounting. There is a piece of message: "sd 0:0:0:0: [sdb] Spinning up disk..." then after that there were message indicating spinning ready. The last message is "[sdb] Attached SCSI disk", then the USB drive is not automounted. But with Disk, I was able to mount it.
– Yu Shen
Jan 12 at 15:31
For my above situation, maybe, there was some error message as they were in red color in dmesg: "[ 5925.011521] sd 0:0:0:0: [sdb] No Caching mode page found [ 5925.011530] sd 0:0:0:0: [sdb] Assuming drive cache: write through" after spinning ready. Before that there were also red messages: "[ 5920.917889] ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8 [ 5920.917899] ses 0:0:0:1: Failed to get diagnostic page 0x1 [ 5920.917906] ses 0:0:0:1: Failed to bind enclosure -19" after Spinning up disk...
– Yu Shen
Jan 12 at 15:46
add a comment |
Have you recently not unmounted the drive correctly, either power failure or a crash while writing to or reading from the drive? This can cause errors with the drive and while once mounted it functions normally the superblock may have errors causing it to not mount correctly.
As Requist asked, check dmesg immediately after inserting you flash drive, you may see one of the last lines as "Volume was not properly unmounted. Some data may be corrupt. Please run fsck.".
Check the device label in gparted then run
sudo fsck /dev/xxx (swapping xxx for your device)
You may get some details back about an invalid Superblock.
Fixing this is dependent on the drive filesystem, is it ext4 or Fat32 etc?
Here's a page on repairing an ext4 superblock
If your drive is fat32 or other msdos type, then testdisk may help but be careful with this tool, with great power...
sudo apt-get install testdisk
sudo testdisk
here is a post on using testdisk to repair a fat32 superblock issue. It links to this post, read both before starting.
Hope it helps.
edited Mar 20 '17 at 10:18
Community♦
1
answered May 4 '16 at 13:28
JoolsJools
114
Have you recently not unmounted the drive correctly, either power failure or a crash while writing to or reading from the drive? This can cause errors with the drive and while once mounted it functions normally the superblock may have errors causing it to not mount correctly.
As Requist asked, check dmesg immediately after inserting you flash drive, you may see one of the last lines as "Volume was not properly unmounted. Some data may be corrupt. Please run fsck.".
Check the device label in gparted then run
sudo fsck /dev/xxx (swapping xxx for your device)
You may get some details back about an invalid Superblock.
Fixing this is dependent on the drive filesystem, is it ext4 or Fat32 etc?
Here's a page on repairing an ext4 superblock
If your drive is fat32 or other msdos type, then testdisk may help but be careful with this tool, with great power...
sudo apt-get install testdisk
sudo testdisk
here is a post on using testdisk to repair a fat32 superblock issue. It links to this post, read both before starting.
Hope it helps.
edited Mar 20 '17 at 10:18
Community♦
1
answered May 4 '16 at 13:28
JoolsJools
114
edited Mar 20 '17 at 10:18
Community♦
1
edited Mar 20 '17 at 10:18
Community♦
1
edited Mar 20 '17 at 10:18
Community♦
1
1
answered May 4 '16 at 13:28
JoolsJools
114
answered May 4 '16 at 13:28
JoolsJools
114
answered May 4 '16 at 13:28
JoolsJools
114
114
I was trying to figure out why a FAT32-formatted thumbdrive wasn't automounting in GNOME (the kernel was recognizing it just fine). When I set the label (I didn't look at it beforehand; I'm guessing that it was empty), it was immediately seen and mounted. Can you explain this behavior? I would assume that, if there wasn't a label, GNOME would just provide a placeholder in the UI. Do you have an opinion whether this was an underlying filesystem issue that was simply corrected by setting a label?
– Dustin Oprea
Dec 31 '16 at 17:36
It should still mount the drive and give it a default 'disk1' type label if none are present. This should be in /media/[username]/disk1 etc. Check your automount config with dconf-editor, check org.gnome.desktop.media-handling for specific configurations on automounting and Nautilus actions. More here help.ubuntu.com/community/Mount/USB
– Jools
Jan 5 '17 at 11:02
For my situation, dmesg did not show any error message of mount failure, it seemed that there is no event of mounting. There is a piece of message: "sd 0:0:0:0: [sdb] Spinning up disk..." then after that there were message indicating spinning ready. The last message is "[sdb] Attached SCSI disk", then the USB drive is not automounted. But with Disk, I was able to mount it.
– Yu Shen
Jan 12 at 15:31
For my above situation, maybe, there was some error message as they were in red color in dmesg: "[ 5925.011521] sd 0:0:0:0: [sdb] No Caching mode page found [ 5925.011530] sd 0:0:0:0: [sdb] Assuming drive cache: write through" after spinning ready. Before that there were also red messages: "[ 5920.917889] ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8 [ 5920.917899] ses 0:0:0:1: Failed to get diagnostic page 0x1 [ 5920.917906] ses 0:0:0:1: Failed to bind enclosure -19" after Spinning up disk...
– Yu Shen
Jan 12 at 15:46
add a comment |
I was trying to figure out why a FAT32-formatted thumbdrive wasn't automounting in GNOME (the kernel was recognizing it just fine). When I set the label (I didn't look at it beforehand; I'm guessing that it was empty), it was immediately seen and mounted. Can you explain this behavior? I would assume that, if there wasn't a label, GNOME would just provide a placeholder in the UI. Do you have an opinion whether this was an underlying filesystem issue that was simply corrected by setting a label?
– Dustin Oprea
Dec 31 '16 at 17:36
It should still mount the drive and give it a default 'disk1' type label if none are present. This should be in /media/[username]/disk1 etc. Check your automount config with dconf-editor, check org.gnome.desktop.media-handling for specific configurations on automounting and Nautilus actions. More here help.ubuntu.com/community/Mount/USB
– Jools
Jan 5 '17 at 11:02
For my situation, dmesg did not show any error message of mount failure, it seemed that there is no event of mounting. There is a piece of message: "sd 0:0:0:0: [sdb] Spinning up disk..." then after that there were message indicating spinning ready. The last message is "[sdb] Attached SCSI disk", then the USB drive is not automounted. But with Disk, I was able to mount it.
– Yu Shen
Jan 12 at 15:31
For my above situation, maybe, there was some error message as they were in red color in dmesg: "[ 5925.011521] sd 0:0:0:0: [sdb] No Caching mode page found [ 5925.011530] sd 0:0:0:0: [sdb] Assuming drive cache: write through" after spinning ready. Before that there were also red messages: "[ 5920.917889] ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8 [ 5920.917899] ses 0:0:0:1: Failed to get diagnostic page 0x1 [ 5920.917906] ses 0:0:0:1: Failed to bind enclosure -19" after Spinning up disk...
– Yu Shen
Jan 12 at 15:46
I was trying to figure out why a FAT32-formatted thumbdrive wasn't automounting in GNOME (the kernel was recognizing it just fine). When I set the label (I didn't look at it beforehand; I'm guessing that it was empty), it was immediately seen and mounted. Can you explain this behavior? I would assume that, if there wasn't a label, GNOME would just provide a placeholder in the UI. Do you have an opinion whether this was an underlying filesystem issue that was simply corrected by setting a label?
– Dustin Oprea
Dec 31 '16 at 17:36
I was trying to figure out why a FAT32-formatted thumbdrive wasn't automounting in GNOME (the kernel was recognizing it just fine). When I set the label (I didn't look at it beforehand; I'm guessing that it was empty), it was immediately seen and mounted. Can you explain this behavior? I would assume that, if there wasn't a label, GNOME would just provide a placeholder in the UI. Do you have an opinion whether this was an underlying filesystem issue that was simply corrected by setting a label?
– Dustin Oprea
Dec 31 '16 at 17:36
It should still mount the drive and give it a default 'disk1' type label if none are present. This should be in /media/[username]/disk1 etc. Check your automount config with dconf-editor, check org.gnome.desktop.media-handling for specific configurations on automounting and Nautilus actions. More here help.ubuntu.com/community/Mount/USB
– Jools
Jan 5 '17 at 11:02
It should still mount the drive and give it a default 'disk1' type label if none are present. This should be in /media/[username]/disk1 etc. Check your automount config with dconf-editor, check org.gnome.desktop.media-handling for specific configurations on automounting and Nautilus actions. More here help.ubuntu.com/community/Mount/USB
– Jools
Jan 5 '17 at 11:02
For my situation, dmesg did not show any error message of mount failure, it seemed that there is no event of mounting. There is a piece of message: "sd 0:0:0:0: [sdb] Spinning up disk..." then after that there were message indicating spinning ready. The last message is "[sdb] Attached SCSI disk", then the USB drive is not automounted. But with Disk, I was able to mount it.
– Yu Shen
Jan 12 at 15:31
For my situation, dmesg did not show any error message of mount failure, it seemed that there is no event of mounting. There is a piece of message: "sd 0:0:0:0: [sdb] Spinning up disk..." then after that there were message indicating spinning ready. The last message is "[sdb] Attached SCSI disk", then the USB drive is not automounted. But with Disk, I was able to mount it.
– Yu Shen
Jan 12 at 15:31
For my above situation, maybe, there was some error message as they were in red color in dmesg: "[ 5925.011521] sd 0:0:0:0: [sdb] No Caching mode page found [ 5925.011530] sd 0:0:0:0: [sdb] Assuming drive cache: write through" after spinning ready. Before that there were also red messages: "[ 5920.917889] ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8 [ 5920.917899] ses 0:0:0:1: Failed to get diagnostic page 0x1 [ 5920.917906] ses 0:0:0:1: Failed to bind enclosure -19" after Spinning up disk...
– Yu Shen
Jan 12 at 15:46
For my above situation, maybe, there was some error message as they were in red color in dmesg: "[ 5925.011521] sd 0:0:0:0: [sdb] No Caching mode page found [ 5925.011530] sd 0:0:0:0: [sdb] Assuming drive cache: write through" after spinning ready. Before that there were also red messages: "[ 5920.917889] ses 0:0:0:1: Wrong diagnostic page; asked for 1 got 8 [ 5920.917899] ses 0:0:0:1: Failed to get diagnostic page 0x1 [ 5920.917906] ses 0:0:0:1: Failed to bind enclosure -19" after Spinning up disk...
– Yu Shen
Jan 12 at 15:46
add a comment |
This is a bug described in Bug #1768010: usbmount does not work on Bionic. The solution, also given in Unix & Linux Stack Exchange, is the following:
Edit the systemd-udevd configutation
sudo systemctl edit systemd-udevd
insert the following two lines:
[Service]
MountFlags=shared
then run:
sudo systemctl daemon-reload
sudo service systemd-udevd --full-restart
Note also that this workaround is not perfect: a delay of 40 seconds can be observed between the time an usb key is inserted an the time the auto-mount is fully executed.
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
It did not work for my Ubuntu 18.04 to solve the problem of no automount for USB drive.
– Yu Shen
Jan 12 at 15:47
add a comment |
This is a bug described in Bug #1768010: usbmount does not work on Bionic. The solution, also given in Unix & Linux Stack Exchange, is the following:
Edit the systemd-udevd configutation
sudo systemctl edit systemd-udevd
insert the following two lines:
[Service]
MountFlags=shared
then run:
sudo systemctl daemon-reload
sudo service systemd-udevd --full-restart
Note also that this workaround is not perfect: a delay of 40 seconds can be observed between the time an usb key is inserted an the time the auto-mount is fully executed.
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
It did not work for my Ubuntu 18.04 to solve the problem of no automount for USB drive.
– Yu Shen
Jan 12 at 15:47
add a comment |
This is a bug described in Bug #1768010: usbmount does not work on Bionic. The solution, also given in Unix & Linux Stack Exchange, is the following:
Edit the systemd-udevd configutation
sudo systemctl edit systemd-udevd
insert the following two lines:
[Service]
MountFlags=shared
then run:
sudo systemctl daemon-reload
sudo service systemd-udevd --full-restart
Note also that this workaround is not perfect: a delay of 40 seconds can be observed between the time an usb key is inserted an the time the auto-mount is fully executed.
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
This is a bug described in Bug #1768010: usbmount does not work on Bionic. The solution, also given in Unix & Linux Stack Exchange, is the following:
Edit the systemd-udevd configutation
sudo systemctl edit systemd-udevd
insert the following two lines:
[Service]
MountFlags=shared
then run:
sudo systemctl daemon-reload
sudo service systemd-udevd --full-restart
Note also that this workaround is not perfect: a delay of 40 seconds can be observed between the time an usb key is inserted an the time the auto-mount is fully executed.
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
edited Jan 5 at 21:32
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
answered Jan 5 at 19:15
Ortomala LokniOrtomala Lokni
1665
1665
It did not work for my Ubuntu 18.04 to solve the problem of no automount for USB drive.
– Yu Shen
Jan 12 at 15:47
add a comment |
It did not work for my Ubuntu 18.04 to solve the problem of no automount for USB drive.
– Yu Shen
Jan 12 at 15:47
It did not work for my Ubuntu 18.04 to solve the problem of no automount for USB drive.
– Yu Shen
Jan 12 at 15:47
It did not work for my Ubuntu 18.04 to solve the problem of no automount for USB drive.
– Yu Shen
Jan 12 at 15:47
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f397190%2fusb-drive-are-not-mounted-automatically%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
