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?

Similar Messages

[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.

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)

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 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)

Mounting USB harddisk at startup

Hi, I want to mount my external USB hdd at startup, however, there is an error during the boot process: "mount: special device /dev/sdb1 does not exist"
Here is the relevant fstab-line:
/dev/sdb1 /mnt/extern ext2 defaults,users 0 0
If I mount sdb1 manually everything works. Thank you for your help!
greetings, Tom

Same here. It used to work before, but it seems that with the newer kernels these devices need more time to settle (or whatever the reason might be). I then put "mount -a" in /etc/rc.local, but even that stopped working. When I need the external USB-HD (mainly for backups) I do a quick "mount -a".

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)

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)

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)

LG USB drive won't (auto)mount

Hi guys,
This is my first post, and I'm not sure if this thread goes here, but anyways, I have a problem with my LG USB External Drive.
Ok, this is what happened. When I connected the drive the activity LED turned on but the volume didn't appear in Thunar, so I went to check if it was at least detected but neither GParted nor lsusb show the USB disk listed. I connected the drive to a netbook with Xubuntu 9.10 and it automounts correctly, also in the same netbook with Windows 7. I've been looking for information about evdev, udev, HAL and Xorg but I couldn't fix the error. The drive worked sporadically one month ago, but I reinstalled Arch and now it won't work.
Here is all the additional data.
* Desktop Environment: XFCE 4.6.1
* lsusb:
Bus 002 Device 002: ID 043d:0057 Lexmark International, Inc. Z35 Printer
Bus 002 Device 004: ID 045e:070f Microsoft Corp.
Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 18e3:9101 Fitipower Integrated Technology Inc
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
* rc.conf: http://dpaste.com/163807/
* mkinitcpio.conf: http://dpaste.com/163810/
* xorg.conf: http://dpaste.com/163811/
* /etc/udev/rules.d/11-media-by-label-auto-mount.rules: http://dpaste.com/163815/
This is all I have (or I think so).
Thanks in advance

Hi scar,
This is the output.
sd 4:0:0:3: Attached scsi generic sg5 type 0
usb-storage: device scan complete
sd 4:0:0:0: [sdb] Attached SCSI removable disk
sd 4:0:0:1: [sdc] Attached SCSI removable disk
sd 4:0:0:3: [sde] Attached SCSI removable disk
sd 4:0:0:2: [sdd] Attached SCSI removable disk
EXT4-fs (sda2): mounted filesystem with ordered data mode
Adding 1951888k swap on /dev/sda3. Priority:-1 extents:1 across:1951888k
forcedeth 0000:00:07.0: irq 27 for MSI/MSI-X
fuse init (API version 7.13)
Seems to be the disk is at least detected. Maybe I need further HAL/Udev configuration, well, what do you think?
Last edited by Penguino (2010-02-24 20:39:06)

[solved] USB drives won't auto mount

When I plug in a drive, I get this error message:
Rejected send message, 1 matched rules; type="method_call", sender=":1.24" (uid=1000 pid=4499 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3069 comm="/usr/sbin/hald)).
2nd harddrive:
Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=3537 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3058 comm="/usr/sbin/hald)).
There are fixes in other forums, but they are all radically differnet, and the one's I tried aren't working.
I have an eee pc with xfce and slim.
I know this is a perimssion problems since auto mount works fine for root. Could anyone tell me the (probably simple) fix for this? Thanks.
Last edited by Meskarune (2010-04-15 04:21:08)

HAL:
http://wiki.archlinux.org/index.php/HAL#Troubleshooting
Also check your .xinitrc and make sure your lines matches this:
exec ck-launch-session startxfce4
Lastly, you can also use udev to automount your drives:
http://wiki.archlinux.org/index.php/Ude … SB_devices

How do I stop a CCC partition auto mounting in Lion

I have an external USB drive with 2 partitions. The first partition has a CCC Clone of my drive before Lion. The second is used for Time Machine. This drive auto mounts on boot which is fine but the CCC partition causes problems with the App Store as it sees Apps that I installed in the Clone backup as installed on Lion. The easy way for me to fix this is just to eject the CCC partition but I have to do this every time I boot. Is there a way of just stopping this drive from auto mounting on boot and manually mounting if need be. Any help would be appreciated. Many Thanks in advance.

I just upgraded to the latest version of Lion--I don't know why it didn't change the info. under my Apple icon. And I know I can uncheck the box while signing off, but you have to do it each time--I'm looking for a way to uncheck it and recheck whenever I want, the way the dock options are supposed to work (although it doesn't for me anymore with Lion).
Checked the Users and Groups--the only login items listed are basically 4 apps that I had back when I had my PC and I no longer have them--I may have had Growl for awhile but I deleted it. There are yellow triangles by them. No other apps listed there.
I guess I'll have to uncheck the box each time I sign off. Tedious, but that's the way it is. Wish I had Snow Leopard back!
Thanks for your suggestions though--just wish they worked.

Mounting USB drive as regular user (with ntfs-3g)

Hello. First of all, I not asking to do the homework for me, rather is someone can help me understand why I can't get this work.
I spent the last night trying to figure how mount an USB drive as a regular user, using ntfs-3g. I read the related wiki entries and researched quite a lot in the forums. I came up with this:
fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda1 / ext3 defaults,noatime 0 1
/dev/sda2 /home ext3 defaults,noatime 0 2
/dev/sda3 swap swap defaults 0 0
/dev/sdb1 /mnt/usb ntfs-3g noauto,uid=0,gid=0,noatime,umask=000, 0 0
I created a ntfsuser group, added my user to that group and trim permissions to the ntfd-3g executable (link in this post). That allows me mount the partition as root and read/write as regular user. It works, so (i think) not big deal here.
However if I add user to the mount options the following error shows up:
Mount is denied because setuid and setgid root ntfs-3g is insecure with the
external FUSE library. Either remove the setuid/setgid bit from the binary
or rebuild NTFS-3G with integrated FUSE support and make it setuid root.
Please see more information at http://ntfs-3g.org/support.html#unprivileged
What bugs me the most is I don't understand why I can't mount as regular user when the user option is set in the fstab. Shouldn't that allow regular users to mount and unmount? Is not like that I'm mounting and dismounting USB drives every 5', but I would like to get this done because I know it can be done
Sorry for asking such trivial question, but I sense that I'm missing something really stupid and I just can't figure what it is

Beware of the double post! (+1)
Ok, I decided I'd get this to work, although the method and the implications it could have might not seem pretty to some. There are certain conditions for a user to mount any ntfs volume with ntfs-3g, I will name them here:
1. ntfs-3g with integrated fuse support. You'll get this by:
1A. Removing ntfs-3g and fuse from your system if you have them installed as separate packages, so do this as root:
pacman -Rn ntfs-3g
pacman -Rn fuse
Now you can install the new package.
1B. Getting a modified version of the PKGBUILD found in that AUR link previously mentioned by me, here's mine:
# Maintainer: Gula <gulanito.archlinux.org>
# Slightly modified by anderfs
# Don't forget to setuid-root for the ntfs-3g binary after you install this
pkgname=ntfs-3g-fuse-internal
pkgver=2010.5.16
pkgrel=1
pkgdesc="Stable read and write NTFS driver (whit internal fuse suport)"
url="http://www.tuxera.com"
arch=('i686' 'x86_64')
license=('GPL2')
depends=('glibc')
conflicts=('ntfs-3g')
makedepends=('pkgconfig')
options=('!libtool')
source=(http://www.tuxera.com/opensource/ntfs-3g-${pkgver}.tgz
http://aur.archlinux.org/packages/ntfs-3g-fuse-internal/ntfs-3g-fuse-internal/25-ntfs-config-write-policy.fdi)
sha1sums=('895da556ad974743841f743c49b734132b2a7cbc'
'200029f2999a2c284fd30ae25734abf6459c3501')
build() {
cd "${srcdir}/ntfs-3g-${pkgver}"
ac_cv_path_LDCONFIG=/bin/true ./configure --prefix=/usr \
--with-fuse=internal --disable-static || return 1
make || return 1
package() {
cd "${srcdir}/ntfs-3g-${pkgver}"
make DESTDIR="${pkgdir}" install || return 1
ln -s /bin/ntfs-3g "${pkgdir}/sbin/mount.ntfs" || return 1
install -m755 -d "${pkgdir}/usr/share/hal/fdi/policy/10osvendor"
install -m644 "${srcdir}/25-ntfs-config-write-policy.fdi" "${pkgdir}/usr/share/hal/fdi/policy/10osvendor/" || return 1
Save this as PKGBUILD, preferrably in an empty directory so it doesn't clutter things up when you build it.
1C. Now go to the directory where you saved it and do this as a regular user:
makepkg PKGBUILD
After that's done, you'll get a package called ntfs-3g-fuse-internal-2010.5.16-1-i686.pkg.tar.xz, or something similar.
1D. Install that package as root:
pacman -U ntfs-3g-fuse-internal-2010.5.16-1-i686.pkg.tar.xz
If all went well you now have ntfs-3g compiled with integrated fuse support.
2. The ntfs-3g version must be higher than 1.2506, this is already covered, the package installed from AUR matches this requirement.
3. The ntfs-3g binary must be set to setuid-root, to accomplish this you shall do the following as root:
chown root $(which ntfs-3g)
chmod 4755 $(which ntfs-3g)
I used 4750 instad of 4755, I guess that last bit can be a matter of personal taste as long as it isn't something obnoxious like "7".
4. The user must have the right access to the volume. Okay, this is the ugly part, volumes are owned by root and managed by the disk group with permissions brw-rw----, this means you have to add any users you want mounting this volume to the disk group.
4A. So, do this as root:
gpasswd -a [user] disk
Where [user] is obviously the name of whichever user you're adding to the disk group, do this for any user you want mounting this volume.
Any users currently logged in will have to log out and back in for these change to take effect, this most likely includes you.
4B. Now that you logged back in, try this:
groups
One of the groups listed should be disk, if it's not there you didn't completely log out of all open sessions.
5. The user must have the right permissions/access to the mount point. For a user to be able to mount something to a mount point, that user needs to have read permission (pretty self-explanatory), write permission (so the user can make any changes to the sub-structure of the mount point), and execute permission (so the user can change-dir to that mount point) to it. Mount points can be anywhere, so this really depends where you're mounting.
In my case, I'm mounting these volumes on certain directories under /mnt/, for example /mnt/example. If you're mounting stuff there, you might as well take advantage of the fact your "mounting user" is already in the group disk, and do the following as root:
chgrp disk /mnt/example
chmod 774 /mnt/example
Now users in the disk group will be able to manage these mount points.
6. Mount it. That's it, you should now be able to mount ntfs volumes as an "unpriveleged enough" user. Here's an example of what you'd have to put in /etc/fstab:
UUID=XXXXYYYYXXXXYYYY /mnt/example ntfs-3g noauto,noatime,user,uid=0,gid=6,fmask=137,dmask=027,rw 0 0
uid=0 means root will be the owner of this mount-point and anything in it after it's mounted. This is due to the fact that even though users might own their mountpoints and have rwx permissions on them, you might still not want them to write to the mounted ntfs volumes. Remove this if you want them to be able to write to the volume.
gid=6 means this will be managed by the disk group in my system. Perhaps the disk group has a different id in your system, run "id root" to find out, as root usually is part of this group.
fmask = 137 means the owner (root) can do anything with files in this volume except executing files. Group members (disk) can only read files here, not create or execute them. And other users can't do anything in this volume.
dmask = 027 means the owner can do anything with directories (execute here is needed to chdir), users can't write directories but they can read or execute in them (once again, needed by 'cd'), and finally other users still don't have any access.
You can use whichever fmask and dmask makes sense to you, or use an umask instead.
Last edited by anderfs (2010-07-15 11:34:48)

E17 on a fresh Arch Linux + gtk apps... auto mounting and other issues

hi all...
I have gone through the forums and found a similar but-not-quite-the-same thread about this, which is why I am posting a new thread - so, please excuse any redundancy/laziness.
As the topic says, I am making a new Arch Install, on my laptop that has/had arch+kdemod on it for quite some time now. I have now tarred that old install and put it on my desktop that has more RAM than this lappy. So I went with a minimalist approach - after googling for long, I managed to put together something that takes up about 350 MB RAM, when running the desktop, firefox, mplayer, openoffice, two or three terminals, and conky - which is all pretty good. But I am having some teething troubles in many issues, so any help in the following is most appreciated.
My set-up and the problems....
WM - e17, from the repos (I tried, but could not get the easy_e17 script to work properly)
FM - emelfm2
- I am not able to get my USBs, CDs, DVDs etc to mount automagically. I have HAL from the repos. This is my fstab.
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
This setup gave me no trouble at all when using Arch-Kdemod. Now I have to be root to mount from the command line, and can not auto mount cd/dvd/USBs.
E17 file manager enabled is also no help.
browser - firefox, dillo
terminal - mrxvt
editor - leafpad
audio - mpd + sonata
video - gmplayer
sys monitor - conky
cd/dvd burner - recorder, from the repos
Openoffice, PSPP for statistics
Pidgin
Wengophone2
at the moment I am behind a proxy and haven't yet tried it, but can anyone confirm it is still working...?
epdfview
chmsee
rtorrent
feh, exhibit
dreamchess
That is the whole setup, in case it helps someone.
Thanks for reading, and waiting for suggestions about the auto mount issue.
Last edited by jaydoc (2009-03-06 00:01:34)

hi all...
Thanks for the replies.
@fingel... That udev rules addition on the wiki gave me the jitters initially as it looked like I was hacking away at my systems innards, BUT, after trying everything else, including things mentioned here, nothing worked. So I finally did the udev thing, and now the USB is mounting fine.
However I still cannot get DVDs or CDs to mount. I am added to the optical group, and yet I have to click the mount icon in emelfm2 to be able to mount the CD or DVD - the only consolation is that I am able to mount it as normal user.
Any help there....? I haven't modified anything from the usual install, except for this udev thingy.
And, How can I make the mrxvt terminal show me more lines on scrolling up. Now it is allowing me to scroll up only by 10 lines or so, and I am having to pipe through less to be able to view anything meaningful in commands like yaourt -Ss
Last edited by jaydoc (2009-03-06 23:55:37)

[SOLVED] How to automatically mount USB drives with custom mount point

edit:
Original title was : 'Unable to mount USB disk via /etc/rc.local', but got changed since the /etc/rc.local problem isn't relevant for me anymore.
Hello,
Since I am new to this forum, I'll start off with this :
Thanks to archlinux, its founder and all its contributors, cause this is the operating system (flavour) that annoys me the least.
The root problem :
I want to automount USB storage devices to other places than /media/ and without the need for programs that depend on gnome and the like. As I tried some stuff with hald and such, I didn't really get to a nice and easy to configure solution. Any hints in that direction are always welcome.
For now, automount of known USB storages devices during boot, will do.
So the things I tried and didnt work :
1.
Provide the disk info to /etc/fstab (via the disks UUID and 'auto' filesystem)
Add 'mount /mountpoint' to /etc/rc.local
Result : the mount command in rc.local says '... specify filesystem'
However, after boot, running /etc/rc.local mounts the USB disks correctly.
2.
Provide the disk info to /etc/fstab (via the disks UUID and the correct filesystem)
Add 'mount /mountpoint' to /etc/rc.local
Result : pc doesn't get through boot process and gives me the 'ctrl-d to reboot or root passwd for maintenance'
3.
Provide no disk info in /etc/fstab
Add the full mount line to /etc/rc.local (mount -t fs /dev/disks/by-uuid/MyUUID /MyMountpoint )
Result : don't remember the output of the mount execution, but well, it didn't mount
However, after boot, running /etc/rc.local mounts the USB disks correctly.
Is there something that isn't loaded at the time of rc.local execution that I need for mounting of USB devices ? Or why else is this failing ?
Regards,
BasiK
Last edited by BasiK (2009-08-28 07:22:50)

Thanks for the hint hunterthomson, but the pc I will be using it on, is an own-built HTPC/home file server, so there is no way I want to use a graphical file manager to get the usb disks mounted.
I tried to figure out a little about udev rules, and I got to do what I wanted to do, so thx for pointing me in that direction Mr.Elendig.
Btw, I am indeed also using auto-sleep/park disks, but this udev way works perfectly.
I added two rules files to /etc/udev/rules.d/ :
The first for a known usb disk (with its volume uuid), with a named mountpoint under my media dir /symbiosis/ :
[basik@plox ~]$ cat /etc/udev/rules.d/80-usb-utopia.rules
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",SYMLINK+="usb-%n", GROUP="storage", NAME="%k"
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a",RUN+="/bin/mkdir -p /symbiosis/utopia"
ACTION=="add", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/utopia", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[b-z][0-9]", ENV{ID_FS_UUID}=="a59332c2-07ba-4c52-afb5-20e361bdf71a", RUN+="/bin/umount -l /symbiosis/utopia", OPTIONS="last_rule"
The second for unknown usb disks, to mount under the same dir. This is simply taken from the archwiki http://wiki.archlinux.org/index.php/Ude … .26_Tricks
Make sure these rules are executed after the ones for specific usb disks.
[basik@plox ~]$ cat /etc/udev/rules.d/usb-disks.rules
KERNEL=="sd[a-z]", NAME="%k", SYMLINK+="usb%m", GROUP="storage", OPTIONS="last_rule"
ACTION=="add", KERNEL=="sd[a-z][0-9]", SYMLINK+="usb%n", GROUP="storage", NAME="%k"
ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mkdir -p /symbiosis/usb%n"
ACTION=="add", KERNEL=="sd[a-z][0-9]", RUN+="/bin/mount -t auto -o rw,noauto,sync,dirsync,noexec,nodev,noatime /dev/%k /symbiosis/usb%n", OPTIONS="last_rule"
ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/umount -l /symbiosis/usb%n"
ACTION=="remove", KERNEL=="sd[a-z][0-9]", RUN+="/bin/rmdir /symbiosis/usb%n", OPTIONS="last_rule"
These may not be the nicest looking udev rules, but it works for what I wanted to do with it.

Help me, why i canot auto mount Usb harddisk?

Similar Messages

Maybe you are looking for