Auto Mounting USB sticks

So, I've looked around a lot, but I can't find much at all about mounting my usb sticks whenever they're plugged in. It'd be nice to not have to # mount /dev/sde1 /home/droid/usb
I've set it up as the wiki says to do so with Thunar, but it's still not working. Any help?

As jasonwryan mentioned the wiki is your friend. If you are trying to automount volumes with thunar make sure to install thunar-volman:
pacman -S thunar thunar-volman
Then you must configure thunar to automount your thumbdrive(s):
From the wiki https://wiki.archlinux.org/index.php/Th … tomounting
Configuration
It can also be configured to execute certain actions when cameras and audio players are connected. After installing the plugin:
1. Launch Thunar and go to Edit -> Preferences
2. Under the 'Advanced' tab, check 'Enable Volume Management'
3. Click configure and check the following items:
Mount removable drives when hot-plugged.
Mount removable media when inserted.
also add dbus-launch to your .xinitrc making sure it comes before your windows manager/desktop environment
for example my .xinitrc contains:
exec dbus-launch openbox-session
Granted there are numerous different ways to automount usb drives, but based on your post I assume that this is the method you are trying to use.
Last edited by Gr0t92 (2013-05-16 05:20:36)

Similar Messages

Problem mounting usb stick with ISO installed on it [SOLVED]

I'm experiencing a weird problem regarding mounting usb sticks. Archlinux stopped auto-mounting usb sticks on my machine, but only those that contains an operating system. Empty or data usb sticks mount without problem.
A few weeks or month ago, I don't remember exactly, still everything was all right, but due to updates(?) usb sticks won't auto mount any more.
I have two arch partitions none of them mount usb sticks anymore with operating systems on them.
Today, I wanted to test a new operating system and write it on my usb stick, and of course I couldn't because arch didn't mount it. Luckily, on my other partitions a few old distos are still installed – I don't use them anymore for years- I booted them up and they mounted the usb stick without problem; it seems only the up-to-date system have problem handling the usb sticks. I have two Arch system installed on two different partitions, Gnome 3 and Enlightenment, both system are up to date.
Here are some info:
[mak@myhost ~]$ dmesg | grep -E "sd[a-z]"
[ 1.369732] sd 2:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
[ 1.369819] sd 2:0:0:0: [sda] Write Protect is off
[ 1.369821] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.369872] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.369924] sd 3:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[ 1.369982] sd 3:0:0:0: [sdb] Write Protect is off
[ 1.369985] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.370070] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.371642] sda: sda1 sda2 sda3 sda4 sda5 sda6
[ 1.372298] sd 2:0:0:0: [sda] Attached SCSI disk
[ 1.429438] sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8 sdb9
[ 1.430159] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 2.244580] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[ 2.348031] systemd[1]: Expecting device dev-sdb8.device...
[ 2.362842] EXT4-fs (sda5): re-mounted. Opts: discard,data=ordered
[ 3.358252] Adding 2097148k swap on /dev/sdb8. Priority:-1 extents:1 across:2097148k FS
[ 5.458907] EXT4-fs (sda5): re-mounted. Opts: discard,data=ordered,commit=0
[ 52.120360] sd 6:0:0:0: [sdc] 15679488 512-byte logical blocks: (8.02 GB/7.47 GiB)
[ 52.121310] sd 6:0:0:0: [sdc] Write Protect is off
[ 52.121319] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 52.122191] sd 6:0:0:0: [sdc] No Caching mode page present
[ 52.122199] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 52.125825] sd 6:0:0:0: [sdc] No Caching mode page present
[ 52.125838] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 52.126999] sdc: sdc1 sdc2
[ 52.131071] sd 6:0:0:0: [sdc] No Caching mode page present
[ 52.131084] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[ 52.131093] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[mak@myhost ~]$
[root@myhost mak]# fdisk -l
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
# Start End Size Type Name
1 2048 18431 8M BIOS boot parti BIOS boot
2 18432 56641478 27G Linux filesyste sda2
3 56641536 113264582 27G Linux filesyste sda3
4 113264640 169887686 27G Linux filesyste sda4
5 169887744 226510790 27G Linux filesyste sda5
6 226510848 234441614 3.8G Linux filesyste Spare
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
Disk /dev/sdb: 320.1 GB, 320072933376 bytes, 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
# Start End Size Type Name
1 2048 18431 8M BIOS boot parti Bios boot
2 18432 54544383 26G Microsoft basic Partition 2
3 54544384 109070335 26G Linux filesyste Partition 3
4 109070336 163596287 26G Microsoft basic
5 163596288 218122239 26G EFI System Partition 5
6 218122240 272647630 26G Microsoft basic Partition 6
7 272648192 327174143 26G Linux filesyste Partition 7
8 327174144 331368447 2G Linux swap Swap
9 331368448 625142414 140.1G Linux filesyste Storage
Disk /dev/sdc: 8027 MB, 8027897856 bytes, 15679488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x5fadc669
Device Boot Start End Blocks Id System
/dev/sdc1 * 0 4040703 2020352 0 Empty
/dev/sdc2 4036 38595 17280 ef EFI (FAT-12/16/32)
Disk /dev/sdc1: 2068 MB, 2068840448 bytes, 4040704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x5fadc669
Device Boot Start End Blocks Id System
/dev/sdc1p1 * 0 4040703 2020352 0 Empty
/dev/sdc1p2 4036 38595 17280 ef EFI (FAT-12/16/32)
[root@myhost mak]#
[root@myhost mak]# blkid -o list -c /dev/null
device fs_type label mount point UUID
/dev/sda1 (not mounted)
/dev/sda2 ext4 (not mounted) 0a76a275-1798-495b-aa27-732626029de2
/dev/sda3 ext4 (not mounted) 0e9363ef-3791-409c-8db9-393385007689
/dev/sda4 ext4 (not mounted) 8f043c02-8b56-4689-a0ee-ed34ccc6f21f
/dev/sda5 ext4 / 82699b0e-8fe9-41e2-be13-65c798ed8a73
/dev/sda6 ext4 (not mounted) 3eaab6bf-2d05-4a7b-a6f7-8675e5f18723
/dev/sdb1 (not mounted)
/dev/sdb2 ext4 (not mounted) 17069311-9f14-4430-8298-be48194eb874
/dev/sdb3 ext4 (not mounted) 2e3b383d-3fa7-40df-b52d-c5d07caf252e
/dev/sdb4 ext4 (not mounted) 9d9b0656-d4ca-4efa-b6f8-1797bd4ead1f
/dev/sdb5 ext4 (not mounted) 05abf58a-ae6e-4377-9b3d-d6bacd92226d
/dev/sdb6 ext4 (not mounted) 8d7c6d55-dc47-471f-84f6-aae8864dfdd7
/dev/sdb7 ext4 (not mounted) b2155741-8f88-4063-bd1b-39b210004b17
/dev/sdb8 swap <swap> 97cf7cdf-299c-4e0d-a438-c8b79766699c
/dev/sdb9 ext4 (not mounted) 426648fd-98f5-4fb0-9114-bdbdfea9047c
/dev/sdc1 udf Sabayon GNOME (not mounted) 2013-07-29-13-08-13-27
/dev/sdc2 vfat (not mounted) CF68-C2B6
[root@myhost mak]#
Thanks for the help.
jmak
Last edited by jmak (2013-08-14 00:12:54)

cfr wrote:
What is sdc1p? Is that another USB stick? It seems to have an equally weird partition map.
By the way, you can't create an Arch USB bootable in EFI mode with dd. Obviously don't know about sabayon.
EDIT: Did you dd to the disk or to a partition? What command exactly did you use? Because it almost looks as if you did something like dd once and create one thing and then dd over the top of one of the partition so you've got a partition which itself has a partition map. Not sure that's possible but it sure looks weird.
I would wipe the key and start over.
I don't know what is that. It is a partition on the same usb stick, it was the “dd” that made that partition automatically, I guess. When I burn images into usb, I always use this command:
# dd bs=4M if=/path/to/archlinux.iso of=/dev/sdx && sync
I used this when burned Sabayon and it works perfectly.
The problem is that Arch can't auto-mount its own installation usb either. I put the arch install usb in and I get the following output:
[root@myhost mak]# blkid -o list -c /dev/null
device fs_type label mount point UUID
/dev/sda1 (not mounted)
/dev/sda2 ext4 (not mounted) 0a76a275-1798-495b-aa27-732626029de2
/dev/sda3 ext4 (not mounted) 0e9363ef-3791-409c-8db9-393385007689
/dev/sda4 ext4 (not mounted) 8f043c02-8b56-4689-a0ee-ed34ccc6f21f
/dev/sda5 ext4 / 82699b0e-8fe9-41e2-be13-65c798ed8a73
/dev/sda6 ext4 (not mounted) 3eaab6bf-2d05-4a7b-a6f7-8675e5f18723
/dev/sdb1 (not mounted)
/dev/sdb2 ext4 (not mounted) 17069311-9f14-4430-8298-be48194eb874
/dev/sdb3 ext4 (not mounted) 2e3b383d-3fa7-40df-b52d-c5d07caf252e
/dev/sdb4 ext4 (not mounted) 9d9b0656-d4ca-4efa-b6f8-1797bd4ead1f
/dev/sdb5 ext4 (not mounted) 05abf58a-ae6e-4377-9b3d-d6bacd92226d
/dev/sdb6 ext4 (not mounted) 8d7c6d55-dc47-471f-84f6-aae8864dfdd7
/dev/sdb7 ext4 (not mounted) b2155741-8f88-4063-bd1b-39b210004b17
/dev/sdb8 swap <swap> 97cf7cdf-299c-4e0d-a438-c8b79766699c
/dev/sdb9 ext4 /run/media/mak/426648fd-98f5-4fb0-9114-bdbdfea9047c 426648fd-98f5-4fb0-9114-bdbdfea9047c
/dev/sdc1 iso9660 ARCH_201305 (not mounted) 2013-05-01-07-12-33-00
[root@myhost mak]#
It doesn't appear in nautilus side panel.
Last edited by jmak (2013-08-13 02:44:45)

Help me, why i canot auto mount Usb harddisk?

hi all,
i have install a new archlinux, but i found i cant auto mount Usb harddisk
Canot mount volume
Canot get volume.fstype.alternative
i have install hal,dbus , ntfs-3g, and add hal,dbus to rc.conf, why it still donnot work?

yes, i add to storage group:
[root@myhost figo]# groups figo
wheel network video audio optical storage power users dbus hal stb-admin figo
[root@myhost figo]#
i have confuse, i use dolpin which is kde4 program, i cant mount my usb harddisk, but
i have nautilus ,it canot mount.
[root@myhost figo]# hal-device /dev/sdb1
libhal.c 522 : invalid udi: /dev/sdb1 doesn't startwith '/org/freedesktop/Hal/devices/'.
(null): (null)
[root@myhost figo]#
what is the problem?

Auto-mounting USB storage devices doesn't work

Hi all,
I have some problems with the auto-mounting of USB storage devices. I already installed udisks and ntfs-3g.
When I connect the external device (it's an external hard disk WD My Passport 500GB, but I have the same problem with a SanDisk USB stick 8GB) the auto-mount doesn't work. I see a shorcut in the left panel of Thunar but if I try to use it Thunar crash without any message error.
I try with the manual mount and it works, but the left panel of Thunar continue to have the same problem.
In the italian Arch forum a friend suggest me to open Thunar from bash and close it. If I do it I receive this error log:
$ thunar
thunar: symbol lookup error: /usr/lib/libstdc++.so.6: undefined symbol: _ZNSt14error_categoryD2Ev, version GLIBCXX_3.4.15
and this is the reply of dmesg command:
[ 340.826768] usb 1-1: new high speed USB device number 2 using ehci_hcd
[ 341.591397] Initializing USB Mass Storage driver...
[ 341.592166] scsi6 : usb-storage 1-1:1.0
[ 341.592345] usbcore: registered new interface driver usb-storage
[ 341.592349] USB Mass Storage support registered.
[ 341.599805] usbcore: registered new interface driver uas
[ 342.591094] scsi 6:0:0:0: Direct-Access WD My Passport 070A 1032 PQ: 0 ANSI: 4
[ 342.591474] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 342.592845] scsi 6:0:0:1: CD-ROM WD Virtual CD 070A 1032 PQ: 0 ANSI: 4
[ 342.593048] scsi 6:0:0:1: Attached scsi generic sg2 type 5
[ 342.594050] sd 6:0:0:0: [sdb] 975400960 512-byte logical blocks: (499 GB/465 GiB)
[ 342.594814] scsi 6:0:0:2: Enclosure WD SES Device 1032 PQ: 0 ANSI: 4
[ 342.595141] scsi 6:0:0:2: Attached scsi generic sg3 type 13
[ 342.596546] sd 6:0:0:0: [sdb] Write Protect is off
[ 342.596553] sd 6:0:0:0: [sdb] Mode Sense: 23 00 10 00
[ 342.596557] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 342.599163] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 342.618228] sdb: sdb1
[ 342.621039] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 342.621046] sd 6:0:0:0: [sdb] Attached SCSI disk
[ 342.665174] sr0: scsi3-mmc drive: 51x/51x caddy
[ 342.665180] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 342.665447] sr 6:0:0:1: Attached scsi CD-ROM sr0
[ 342.665654] ses 6:0:0:2: Attached Enclosure device
[ 349.105348] [b]Thunar[996]: segfault at 0 ip b6de1660 sp bfe586f4 error 4 in libglib-2.0.so.0.2800.8[b6d6f000+ed000][/b]
Do you have any suggestion?
Thank you very much,
Gianluca

Are you using [testing]? Partially updated system?
The error looks like you have a different version of gcc-libs / glibc than the app was built against.
Last edited by Mr.Elendig (2011-06-20 19:16:33)

Cant mount usb sticks with fat32 ISO-8859-1 2.6.31-ARCH

when trying to mount my usb sticks from xfce4 desktop(halmount).
Following error occurs (as told by dmesg).
FAT: IO charset ISO-8859-1 not found
First i suspected hal being the culprit but now im not so sure anymore.
im using stock 2.6.31-ARCH.
when i checked the .config for the stock kernel CONFIG_NLS_ISO8859_1=y is enabled in the kernelconfig, and also everything below to support fat32.
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
but when i list the modules nls_iso8859-1.ko is missing.
#~ls -a /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso*
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-13.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-14.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-15.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-2.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-3.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-4.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-5.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-6.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-7.ko
/lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-9.ko
So i suspect the newest kernel broke mounting with hal.
Last edited by nichlas.johansson (2009-10-17 14:25:56)

Based on the information given in http://bbs.archlinux.org/viewtopic.php?id=82176, I changed in /etc/rc.conf from LOCALE=en_GB.iso88591 to LOCALE=en_GB.utf8, uncommented en_GB.UTF-8 UTF-8 in /etc/locale.gen, issued # locale-gen and after a reboot, I was able to mount my usb sticks again.
However, now I get "FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!" in dmesg. Is this something, I need to worry about...?
Last edited by smurf (2009-10-19 08:29:15)

Mount USB stick on an ASA 5505?

Hello,
I have an ASA 5505 and the built in flash is pretty small and I need to put 3 .pkg on it for Anyconnect 4.
I formated an USB Stick (4GB) to FAT32 and put in the USB Port 2 on the back and rebooted the firewall.
But in the filemanager I see disk0 and disk1, but disk1 does not work, doesn't list anything and I can't create folders on it.
Can I mount the USB stick manually or something?
Kind Regards.

The USB port on the 5505 is not a supported file storage location.
On the newer 5500-X series (including the 5506-X) you can do that.

[SOLVED] Thunar (XFCE4) Does not Auto-mount USB Drive

After reading some posts related to USB auto-mounting in Thunar and yet still having the problem, I decided to post this. Thunar used to detect the USB drives and auto-mount them. These days (I GUESS after moving to systemd), It cannot do so. Still, there is the icon of USB drive on the left side panel, but when I click on it to browse it, I get this error:
Failed to mount "USB_LABLE".
Error when getting information for file
'/media/usbhd-sdc1': Transport endpoint is not connected.
I am still able to use "sudo mount..." and get the job done, but I would prefer the convenient way it used to work. Here are some information about my system:
command> cat ~/.xinitrc
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec startxfce4
command> loginctl show-session $XDG_SESSION_ID
Id=1
Timestamp=Sat, 2012-11-10 20:35:51 CET
TimestampMonotonic=34276379
DefaultControlGroup=name=systemd:/user/username/1
VTNr=7
Display=:0.0
Remote=no
RemoteUser=root
Service=slim
Leader=297
Audit=1
Type=x11
Class=user
Active=yes
State=active
KillProcesses=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
command> systemctl status polkit
polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
Active: active (running) since ...
Docs: man:polkit(8)
Main PID: 305 (polkitd)
CGroup: name=systemd:/system/polkit.service
305 /usr/lib/polkit-1/polkitd --no-debug
command> dmesg
Attached scsi generic sg1 type 0
[sdc] 15470592 512-byte logical blocks: (7.92 GB/7.37 GiB)
[sdc] Write Protect is off
[sdc] Mode Sense: 23 00 00 00
[sdc] No Caching mode page present
[sdc] Assuming drive cache: write through
[sdc] No Caching mode page present
[sdc] Assuming drive cache: write through sdc: sdc1
[sdc] No Caching mode page present
[sdc] Assuming drive cache: write through
[sdc] Attached SCSI removable disk
I'd rather not edit the /etc/fstab; the way Thunar used to behave, was working with every new USB. I wonder if anybody can shed some lights.
Last edited by Shahab (2012-11-10 21:56:24)

The error looks suspiciously like one I had not so long ago and it turned out I still had an 11-media-by-label-auto-mount.rule in /etc/udev/rules.d. Once I removed that and rebooted everything was fine again.

[SOLVED] Mounted USB stick immediately unmounts itself - why?

Hi all,
I thought I was unable to mount a USB stick, however it does actually mount but then it gets immediately unmounted by something:
# mount /dev/sdd1 /mnt
# ls /mnt
<empty folder>
# umount /mnt
umount: /mnt: not mounted
# mount /dev/sdd1 /mnt && ls /mnt
<contents of USB stick>
# ls /mnt
<empty folder>
Somehow the USB stick is getting automatically *unmounted* almost immediately after I mount it!
I don't have any automounts enabled, so I'm not sure why this would happen. If I make a different folder (e.g. /root/test) and mount it there then it sticks, it is only the /mnt folder that gets automatically unmounted.
Any idea what's going on? I've never seen this happen before, and last time I tried this (a week or two ago) it worked fine.
Last edited by Malvineous (2015-03-15 01:15:16)

brebs wrote:Use "mount -v" (i.e. "verbose") to get some feedback - it's most likely not being mounted.
Like I said in my first post, if you run "ls" immediately after the mount then you can see the contents of the USB stick, so it's definitely getting mounted, but waiting only a few hundred milliseconds after the mount reveals it has been unmounted again. What is causing the unmount is unknown.
brebs wrote:
Immediately after running that mount command, run:
echo $?
To see the return code. It should be 0.
Yes it is zero, because the mount command succeeds. "ls" wouldn't be able to list the files on the USB stick if the mount failed. It is something else that is unmounting the folder mere milliseconds after it is successfully mounted, but I don't know where else to look to find out what it could be.
brebs wrote:Also, mounting to /mnt is very weird - you should be mounting a directory *inside* /mnt.
I am mounting inside /mnt, I just used /mnt as an example to keep things simple.
Vain wrote:
I made the same “mistake”. Try running “systemctl status mnt.mount” and see which device the output refers to. For me, it still listed the old device name. Hence, when you mount it, systemd tries to find the (old) device—which it can’t—and thus unmounts your device immediately.
I was too lazy/annoyed to find out how to solve this properly. I rebooted my system.
Interesting idea! Unfortunately I have nothing listed for this particular mount point. The only *.mount services on my system are the ones that are mounted at boot (e.g. srv.mount for /srv). I have the "noauto" option against this mount point in fstab (as USB sticks aren't normally attached to my system when I boot) so sensibly enough I don't seem to have a mount service running for this particular mount point.

Mount USB Stick (Solved), SSHD (Solved), Root Logon (Still open)

Sorry this is about 3 problems:
1. Already for longer time I can not login as root on one computer on the console. This machine has no X as it is a server. Access via SSH and console logon as other user works. One logged on I can use SU or sudo for root actions. There was a similar thread over here, which didn't help.
/etc/securetty:
# /etc/securetty
console
tty/1
tty/2
tty/3
tty/4
tty/5
tty/6
# End of file
Recent update related problems:
Updated files:
[2009-10-29 08:51] upgraded kernel-headers (2.6.30.5-1 -> 2.6.31.4-1)
[2009-10-29 08:51] Generating locales...
[2009-10-29 08:51] de_DE.UTF-8... done
[2009-10-29 08:51] de_DE.ISO-8859-1... done
[2009-10-29 08:51] de_DE.ISO-8859-15@euro... done
[2009-10-29 08:51] en_US.UTF-8... done
[2009-10-29 08:51] en_US.ISO-8859-1... done
[2009-10-29 08:51] zh_CN.UTF-8... done
[2009-10-29 08:51] zh_CN.GB2312... done
[2009-10-29 08:51] Generation complete.
[2009-10-29 08:51] upgraded glibc (2.10.1-4 -> 2.10.1-5)
[2009-10-29 08:51] upgraded binutils (2.19.1-5 -> 2.20-1)
[2009-10-29 08:51] upgraded gcc-libs (4.4.1-1 -> 4.4.2-2)
[2009-10-29 08:51] upgraded xulrunner (1.9.1.3-2 -> 1.9.1.4-1)
[2009-10-29 08:51] upgraded firefox (3.5.3-1 -> 3.5.4-1)
[2009-10-29 08:51] upgraded gcc (4.4.1-1 -> 4.4.2-2)
[2009-10-29 08:51] upgraded libatasmart (0.16-1 -> 0.17-1)
[2009-10-29 08:51] upgraded openntpd (3.9p1-7 -> 3.9p1-8)
[2009-10-29 08:52] Updating font cache... done.
[2009-10-29 08:52] installed ttf-freefont (20090104-2)
[2009-10-29 08:52] upgraded vlc (1.0.2-3 -> 1.0.2-4)
2. SSH logon does not work anymore. Another thread solved the proble by creating a /var/empty directory and restart sshd. This works, so the solution is confirmed.
3. Mount of USB media does not work as user although the user is in the storage group. In fact it worked before.
Mount as root by hand works, but in case of VFAT media without acl there is no way to access the media by user other than root.
Umount of course also need root rights in this case.
I'm using HAL and the message mentions "permission denied by policy"
Last edited by jcci (2009-10-31 04:23:33)

I've got some kind of problems with removable media too. My solution was to edit /etc/PolicyKit/PolicyKit.conf
I don't remember what i've changed there, so this is my file, maybe this will help:
<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.eject-removable">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.mount-fixed">
<return result="yes"/>
</match>
<match action="hal-storage-mount-fixed-extra-options">
<return result="yes"/>
</match>
<match action="hal-storage-mount-removable-extra-options">
<return result="yes"/>
</match>
</config>

Mount USB stick manually

Hi there!
I'm new to Darwin and I'm wondering how to mount a USB flash drive manually. Actually I got the problem that my USB MP3 Player (Fat32 formatted) is being mounted read-only. So I'm looking for the device which has to be mounted. Something like this:
mount -t vfat /dev/DEVICE /mnt/usbdevice -o uid=1000 (how do I get the UID in darwin?)
I tried to get the 'DEVICE' info from /etc/fstab.hd (which should be the same as /etc/fstab in linux ?) when it's mounted automaticly but no success here (it says: 'IGNORE THIS FILE').
That brings me to my second question: Where can I find all mounted devices listed like it's in fstab in other UNIX systems?
I hope that's not to much asking
greetings
z00k

That brings me to my second question: Where can I find all mounted devices listed like it's in fstab in other UNIX systems?
Open Disk utility located in Applications/Utilities. Disk Utility can mount/unmount and eject external media, (and do a lot more).

Systemd (auto)mount USB fails due to fsck

Hi,
I am trying to get 'hotplugging' functionality working for usb storage devices with systemd with the ultimate goal of running a backup service via systemd which will require certain devices and mounts to be active.
After a few searchers, I decided the approach of adding the external storage device to fstab with a couple systemd options
Here's the relevant line in my fstab
# USB for data where CoW not desired
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 2
That worked nicely. The device is mounted anytime the mountpoint is requested (e.g. by cd'ing into that directory) provided that the device has not been unmounted.
If the device has been unmounted (with systemctl stop media-storage_nocow.mount) or removed, and then plugged back in, the mount unit fails with very vague error message. I looked around but didn't find anything definitive on how to address the issue
systemctl status media-storage_nocow.mount | tail -n 2
#May 28 11:40:57 archLenFlex systemd[1]: Dependency failed for /media/storage_nocow.
#May 28 11:40:57 archLenFlex systemd[1]: Job media-storage_nocow.mount/start failed with result 'dependency'.
I checked that the device is active
systemctl status --full dev-disk-by\\x2dlabel-CORSAIR64.device
● dev-disk-by\x2dlabel-CORSAIR64.device - Voyager_VEGA CORSAIR64
Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d1-3\x2d1:1.0-host4-target4:0:0-4:0:0:0-block-sdb-sdb1.device
Loaded: loaded
Active: active (plugged) since Thu 2015-05-28 15:43:36 EDT; 2h 2min ago
Device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
The messages from journalctl were of little help. I dug around into the unit files which are generated from fstab and found that the mount requires a couple services
RequiresOverridable=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
After=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
[Mount]
What=/dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Where=/media/storage_nocow
Type=ext4
Options=nofail,rw,noauto,x-systemd.automount
the requires/after units failed
systemctl status --full systemd-fsck@dev-disk-by\\x2duuid-964cc231\\x2daf3f\\x2d49ef\\x2d94f3\\x2df73ffd551fda.service
● systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service - File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
Active: inactive (dead) since Thu 2015-05-28 15:43:26 EDT; 30min ago
Docs: man:[email protected](8)
Process: 797 ExecStart=/usr/lib/systemd/systemd-fsck %f (code=exited, status=0/SUCCESS)
Main PID: 797 (code=exited, status=0/SUCCESS)
May 28 15:31:27 archLenFlex systemd[1]: Starting File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:31:27 archLenFlex systemd-fsck[797]: CORSAIR64: clean, 12/3784704 files, 283568/15123984 blocks
May 28 15:31:27 archLenFlex systemd[1]: Started File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopped File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopping File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:45:22 archLenFlex systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:45:22 archLenFlex systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service/start failed with result 'dependency'.
Looking further into those units - the fsck service has a couple dependencies:
After=%i.device systemd-fsck-root.service local-fs-pre.target
Before=shutdown.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/lib/systemd/systemd-fsck %f
StandardOutput=journal+console
TimeoutSec=0
The only one that failed was the sytemd-fsck-root.service - the other two were active/successful.
● systemd-fsck-root.service - File System Check on Root Device
Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-fsck-root.service(8)
So, I figured I can skip the fsck in fstab and it should work. This is the case, with the following fstab line for the device,
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 0
From there, requesting the mountpoint activates the mount via the automount, provided the mount unit was stopped but the device wasn't unplugged. If the device is unplugged, it is necessary stop the mount unit and reload the systemctl daemon.
I think it is preferable to have the device fsck'd.
So can anyone advise why the fsck is failing and how to get the mount to work while keeping the fsck option in fstab? Why does the usb device mount even require the root fsck? I would think it should only require its own fsck.
Thanks in advance.
Last edited by akpol (2015-05-28 22:16:44)

Hi,
I am trying to get 'hotplugging' functionality working for usb storage devices with systemd with the ultimate goal of running a backup service via systemd which will require certain devices and mounts to be active.
After a few searchers, I decided the approach of adding the external storage device to fstab with a couple systemd options
Here's the relevant line in my fstab
# USB for data where CoW not desired
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 2
That worked nicely. The device is mounted anytime the mountpoint is requested (e.g. by cd'ing into that directory) provided that the device has not been unmounted.
If the device has been unmounted (with systemctl stop media-storage_nocow.mount) or removed, and then plugged back in, the mount unit fails with very vague error message. I looked around but didn't find anything definitive on how to address the issue
systemctl status media-storage_nocow.mount | tail -n 2
#May 28 11:40:57 archLenFlex systemd[1]: Dependency failed for /media/storage_nocow.
#May 28 11:40:57 archLenFlex systemd[1]: Job media-storage_nocow.mount/start failed with result 'dependency'.
I checked that the device is active
systemctl status --full dev-disk-by\\x2dlabel-CORSAIR64.device
● dev-disk-by\x2dlabel-CORSAIR64.device - Voyager_VEGA CORSAIR64
Follow: unit currently follows state of sys-devices-pci0000:00-0000:00:14.0-usb3-3\x2d1-3\x2d1:1.0-host4-target4:0:0-4:0:0:0-block-sdb-sdb1.device
Loaded: loaded
Active: active (plugged) since Thu 2015-05-28 15:43:36 EDT; 2h 2min ago
Device: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1
The messages from journalctl were of little help. I dug around into the unit files which are generated from fstab and found that the mount requires a couple services
RequiresOverridable=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
After=systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service
[Mount]
What=/dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Where=/media/storage_nocow
Type=ext4
Options=nofail,rw,noauto,x-systemd.automount
the requires/after units failed
systemctl status --full systemd-fsck@dev-disk-by\\x2duuid-964cc231\\x2daf3f\\x2d49ef\\x2d94f3\\x2df73ffd551fda.service
● systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service - File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
Active: inactive (dead) since Thu 2015-05-28 15:43:26 EDT; 30min ago
Docs: man:[email protected](8)
Process: 797 ExecStart=/usr/lib/systemd/systemd-fsck %f (code=exited, status=0/SUCCESS)
Main PID: 797 (code=exited, status=0/SUCCESS)
May 28 15:31:27 archLenFlex systemd[1]: Starting File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:31:27 archLenFlex systemd-fsck[797]: CORSAIR64: clean, 12/3784704 files, 283568/15123984 blocks
May 28 15:31:27 archLenFlex systemd[1]: Started File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopped File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:43:26 archLenFlex systemd[1]: Stopping File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda...
May 28 15:45:22 archLenFlex systemd[1]: Dependency failed for File System Check on /dev/disk/by-uuid/964cc231-af3f-49ef-94f3-f73ffd551fda.
May 28 15:45:22 archLenFlex systemd[1]: Job systemd-fsck@dev-disk-by\x2duuid-964cc231\x2daf3f\x2d49ef\x2d94f3\x2df73ffd551fda.service/start failed with result 'dependency'.
Looking further into those units - the fsck service has a couple dependencies:
After=%i.device systemd-fsck-root.service local-fs-pre.target
Before=shutdown.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/lib/systemd/systemd-fsck %f
StandardOutput=journal+console
TimeoutSec=0
The only one that failed was the sytemd-fsck-root.service - the other two were active/successful.
● systemd-fsck-root.service - File System Check on Root Device
Loaded: loaded (/usr/lib/systemd/system/systemd-fsck-root.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-fsck-root.service(8)
So, I figured I can skip the fsck in fstab and it should work. This is the case, with the following fstab line for the device,
UUID=964cc231-af3f-49ef-94f3-f73ffd551fda /media/storage_nocow ext4 noauto,x-systemd.automount 0 0
From there, requesting the mountpoint activates the mount via the automount, provided the mount unit was stopped but the device wasn't unplugged. If the device is unplugged, it is necessary stop the mount unit and reload the systemctl daemon.
I think it is preferable to have the device fsck'd.
So can anyone advise why the fsck is failing and how to get the mount to work while keeping the fsck option in fstab? Why does the usb device mount even require the root fsck? I would think it should only require its own fsck.
Thanks in advance.
Last edited by akpol (2015-05-28 22:16:44)

Auto mount of USB sticks and hard drives?

Hello.
I'd like ArchLinux to auto-mount USB sticks, hard drives, etc... when plugging them in. How do I manage to do this?
These are my daemons: DAEMONS=(syslog-ng network netfs crond dbus hal ntpd alsa gdm)
Thank you in advance.
EDIT: Somehow, autofs does not work.
And btw, I use Thunar as file manager.
Last edited by rik (2011-04-24 13:24:40)

You need to have gvfs and thunar-volman installed. Make sure you are a member of the storage group. https://wiki.archlinux.org/index.php/Xf … le_Devices
Last edited by yugrotavele (2011-04-24 14:55:59)

USB Auto-mounting Woes [SOLVED]

Hi,
I've been trying to get my USB sticks to auto-mount and grant all users permission to mount/unmount them.
To achieve that I initially added the following to my sudoers using visudo:
%wheel ALL=NOPASSWD: /bin/mount
%wheel ALL=NOPASSWD: /bin/umount
That however didn't solve my inability to (un)mount drives in PCMan FM.. so I headed towards the wiki. The wiki stated the following:
You can easily automount and eject removable devices with the combination of pmount, udisks2 and spacefm. Note you have to run spacefm in daemon mode with spacefm -d & in your startup scripts, ~/.xinitrc or ~/.xsession, to get automounting.
I wasn't too fussed about having to use spacefm and everything seemed to work just fine.. until I tried format a USB stick using gparted. Gparted fails because because seemingly half way through the formatting procedure the drive is mounted (my suspicion is that it's spacefm).
mkdosfs: /dev/sdb1 contains a mounted file system.
If i unmount and format manually using the CLI it works just fine.. but I quite like gparted
I tried removing
spacefm -d
from my .xinitrc and that actually stops openbox from starting up. Uninstalling (and later re-installing when it didn't help) pmount didn't help either, spacefm just auto-mounts in a strange 'run' way..
So now I'm stuck, anyone experienced similar issues with gparted and spacefm?
Last edited by omgitsaheadcrab (2012-06-22 13:27:07)

ck-list-sessions shows an active consokekit session, so that should be fine?
Session1:
unix-user = '1000'
seat = 'Seat1'
session-type = 'x11'
active = TRUE
x11-display = ':0.0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2012-06-22T12:24:47.734505Z'
login-session-id = '3'
The gparted error log is as follows:
GParted 0.12.1
Libparted 3.1
Delete /dev/sdb1 (fat32, 7.37 GiB) from /dev/sdb 00:00:01 ( SUCCESS )
calibrate /dev/sdb1 00:00:00 ( SUCCESS )
path: /dev/sdb1
start: 2048
end: 15466495
size: 15464448 (7.37 GiB)
delete partition 00:00:01 ( SUCCESS )
========================================
Create Primary Partition #1 (fat32, 7.37 GiB) on /dev/sdb 00:00:01 ( ERROR )
create empty partition 00:00:00 ( SUCCESS )
path: /dev/sdb1
start: 2048
end: 15466495
size: 15464448 (7.37 GiB)
set partition type on /dev/sdb1 00:00:01 ( SUCCESS )
new partition type: fat32
create new fat32 file system 00:00:00 ( ERROR )
mkdosfs -F32 -v -n "PATRIOT" /dev/sdb1
mkdosfs 3.0.12 (29 Oct 2011)
mkdosfs: /dev/sdb1 contains a mounted file system.
========================================
I still can't help but feel it's spacefm doing something funny (automounting when it shouldn't)
Last edited by omgitsaheadcrab (2012-06-22 12:31:36)

Usb stick not mounting as user

I cannot mount the usb stick as user. When I plug the stick in the kde window comes up indicating it is in and goes to a new window and has an error. Following is an error from xsession:
kded: ERROR: mount failed for /org/freedesktop/Hal/devices/volume_uuid_709E_ED39: org.freedesktop.DBus.Error.AccessDenied - A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
kded: ERROR: mounting /org/freedesktop/Hal/devices/volume_uuid_709E_ED39 returned A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
fifo_audio_out: audio buffer underflow!
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x3400387
konqueror: WARNING: Pixmap not found for mimetype inode/socket
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x3a00006
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x3a00006
But when I switch to root everything works fine, I can read and write to the stick. I tried from the wiki :
dev/sdb1 /mnt/usbstick vfat noauto,user 0 0 and this did nothing.

Users worked and now everything is good thank. Solved

Usb stick doesn't mount on Mac, but does on Win

Hello all,
I've been looking for a solution for my issue allover, but it seems to be persistently difficult to find.
I got an unbranded 4gb pen drive formated as FAT32. The device works perfectly on Windows, but my Mac OS 10.8.4 doesn't recognize it.
I've tried to:
a) Look at the "Utilities Disk" and "Finder". Doesn't show up.
b) Format at any possible format with Windows (FAT32, exFAT, NTFS, even HFS+ using a software).
c) Use another usb stick in the same port. It works with any other pen drive.
d) Use the usb stick in another computer. Still, work only on Windows, not on Mac.
e) Use it with Windows. Works.
P.S.: I'm attaching a image of the mounted items. The two HFS are partitions of my external hard drive (disk1s2 and disk1s3) and the other is the Bootcamp partition (disk0s4).
Does anyone know what I could do to make the usb stick work on my Mac?
I'd appreciate any help on this matter.
Cheers!

OK, a SD/compact memory card type of thing used with cameras. The same solution/diagnosis still applies. Failing mounting the memory card directly in the MacBook, you could do it indirectly, via a cable that connects the camera or whatever it is used with, with the card in it, and the cable connected to your MacBook's USB port. It's a bit of a pain, but it's usually possible to do it that way.

Auto Mounting USB sticks

Similar Messages

Maybe you are looking for