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)

Similar Messages

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?

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

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)

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)

[SOLVED] can't mount USB external drive since udev upgrade to systemd

At somepoint in time around the June 1 change from udev to systemd or the change from udisks to udisks2 something has changed the way my external USB drives auto-mount.
I have always just plugged them in and they show up in PacmanFM just fine. Now, they do show up but the NTFS drive is showing as read-only and another empty drive that I have reformatted using GParted to xfs, then ext2, and finally again using ext4 gives "Permission Denied" errors when I try to put a file on the drive. Happens no matter how I format it.
Did something change that I need to manually configure? Up to this point I relied on udev just kind of doing its thing - I never had to configure anything to get these drives to work properly.
Last edited by AyeCapn (2012-06-26 15:15:59)

Perhaps the cause of my issue might be relevant:
While the now deleted udev automount script from the Arch Wiki had worked for months without issue, approximately since the udev/systemd merger it became broken for NTFS partitions on USB devices.
It still worked with the classic initscripts, but with systemd it only resulted in "Transport endpoint is not connected" for the supposed mount point and ls reported lots of "?" for it.

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)

Auto-mount failing with segfault on FAT drives

I've been running Arch on ThinkPads for years, just got an x240 and installed Arch on it. Everything seems to work fine except for external drives of any sort.
I'm running Gnome 3.
With my USB stick, every time I insert it, Nautilus detects it and when I attempt to view the drive it fails. Here's the dmesg output:
[32426.659595] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[32426.675126] usb-storage 2-1:1.0: USB Mass Storage device detected
[32426.675173] scsi5 : usb-storage 2-1:1.0
[32427.676716] scsi 5:0:0:0: Direct-Access Patriot Memory PMAP PQ: 0 ANSI: 6
[32427.677167] sd 5:0:0:0: [sdb] 60566016 512-byte logical blocks: (31.0 GB/28.8 GiB)
[32427.677442] sd 5:0:0:0: [sdb] Write Protect is off
[32427.677458] sd 5:0:0:0: [sdb] Mode Sense: 45 00 00 00
[32427.677775] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[32427.831483] sdb: sdb1
[32427.832493] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[32439.190500] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[32439.328724] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[32444.339799] usb 2-1: device descriptor read/8, error -110
[32444.443060] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[32449.454646] usb 2-1: device descriptor read/8, error -110
[32449.611683] sd 5:0:0:0: [sdb] Unhandled error code
[32449.611686] sd 5:0:0:0: [sdb]
[32449.611687] Result: hostbyte=0x07 driverbyte=0x00
[32449.611688] sd 5:0:0:0: [sdb] CDB:
[32449.611690] usb 2-1: USB disconnect, device number 4
[32449.611689] cdb[0]=0x28: 28 00 00 00 0d 9b 00 00 0f 00
[32449.611695] end_request: I/O error, dev sdb, sector 3483
[32449.617844] sd 5:0:0:0: [sdb] Unhandled error code
[32449.617846] sd 5:0:0:0: [sdb]
[32449.617847] Result: hostbyte=0x01 driverbyte=0x00
[32449.617848] sd 5:0:0:0: [sdb] CDB:
[32449.617849] cdb[0]=0x28: 28 00 00 00 0d 9c 00 00 0e 00
[32449.617852] end_request: I/O error, dev sdb, sector 3484
[32449.617876] sd 5:0:0:0: [sdb] Unhandled error code
[32449.617877] sd 5:0:0:0: [sdb]
[32449.617878] Result: hostbyte=0x01 driverbyte=0x00
[32449.617878] sd 5:0:0:0: [sdb] CDB:
[32449.617879] cdb[0]=0x28: 28 00 00 00 0c ab 00 00 f0 00
[32449.617882] end_request: I/O error, dev sdb, sector 3243
[32449.617952] FAT-fs (sdb1): FAT read failed (blocknr 3211)
[32449.618677] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801574ef380
[32449.618680] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8801574ef3c0
[32449.621107] FAT-fs (sdb1): Directory bread(block 32768) failed
[32449.621111] FAT-fs (sdb1): Directory bread(block 32769) failed
[32449.621113] FAT-fs (sdb1): Directory bread(block 32770) failed
[32449.621115] FAT-fs (sdb1): Directory bread(block 32771) failed
[32449.621117] FAT-fs (sdb1): Directory bread(block 32772) failed
[32449.621119] FAT-fs (sdb1): Directory bread(block 32773) failed
[32449.621120] FAT-fs (sdb1): Directory bread(block 32774) failed
[32449.621122] FAT-fs (sdb1): Directory bread(block 32775) failed
[32449.621124] FAT-fs (sdb1): Directory bread(block 32776) failed
[32449.621126] FAT-fs (sdb1): Directory bread(block 32777) failed
[31813.104727] ------------[ cut here ]------------
[31813.104734] WARNING: CPU: 3 PID: 7798 at fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
[31813.104736] sysfs group ffffffff81895c40 not found for kobject 'target3:0:0'
[31813.104737] Modules linked in: nls_cp437 vfat fat twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common serpent_avx2 serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic xts loop usb_storage usbhid hid fuse ctr ccm snd_hda_codec_hdmi joydev mousedev arc4 snd_hda_codec_realtek intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm iTCO_wdt iTCO_vendor_support cdc_mbim microcode evdev cdc_ncm psmouse uvcvideo pcspkr serio_raw iwlmvm usbnet videobuf2_vmalloc mii videobuf2_memops mac80211 cdc_acm videobuf2_core cdc_wdm videodev media btusb iwlwifi bluetooth cfg80211 rtsx_pci_ms memstick wmi tpm_tis thinkpad_acpi i915 snd_hda_intel nvram tpm rfkill ac battery snd_hda_codec video intel_agp intel_gtt drm_kms_helper drm e1000e snd_hwdep snd_pcm snd_page_alloc thermal
[31813.104776] snd_timer mei_me lpc_ich mei i2c_algo_bit snd button shpchp i2c_i801 ptp soundcore pps_core i2c_core processor ext4 crc16 mbcache jbd2 dm_crypt dm_mod sd_mod rtsx_pci_sdmmc mmc_core atkbd libps2 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci ehci_pci libahci ehci_hcd libata scsi_mod rtsx_pci xhci_hcd usbcore usb_common i8042 serio
[31813.104801] CPU: 3 PID: 7798 Comm: umount Not tainted 3.13.6-1-ARCH #1
[31813.104802] Hardware name: LENOVO 20AL009NMC/20AL009NMC, BIOS GIET66WW (2.16 ) 12/02/2013
[31813.104804] 0000000000000009 ffff88013ecb5b40 ffffffff81513274 ffff88013ecb5b88
[31813.104806] ffff88013ecb5b78 ffffffff81061a3d 0000000000000000 ffffffff81895c40
[31813.104809] ffff8800c72a5c38 ffff8802114d4190 ffff8801728fb000 ffff88013ecb5bd8
[31813.104812] Call Trace:
[31813.104818] [<ffffffff81513274>] dump_stack+0x4d/0x6f
[31813.104824] [<ffffffff81061a3d>] warn_slowpath_common+0x7d/0xa0
[31813.104827] [<ffffffff81061aac>] warn_slowpath_fmt+0x4c/0x50
[31813.104831] [<ffffffff8151843e>] ? mutex_unlock+0xe/0x10
[31813.104834] [<ffffffff8121925e>] ? sysfs_get_dirent_ns+0x4e/0x70
[31813.104837] [<ffffffff8121a3e6>] sysfs_remove_group+0xc6/0xd0
[31813.104843] [<ffffffff813b7033>] dpm_sysfs_remove+0x43/0x50
[31813.104846] [<ffffffff813aceb5>] device_del+0x45/0x1c0
[31813.104857] [<ffffffffa00a52b7>] scsi_target_reap_usercontext+0x27/0x40 [scsi_mod]
[31813.104862] [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[31813.104870] [<ffffffffa00a65d4>] scsi_target_reap+0xc4/0xf0 [scsi_mod]
[31813.104879] [<ffffffffa00a8558>] scsi_device_dev_release_usercontext+0x188/0x1c0 [scsi_mod]
[31813.104882] [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[31813.104890] [<ffffffffa00a83cc>] scsi_device_dev_release+0x1c/0x20 [scsi_mod]
[31813.104894] [<ffffffff813ac3f2>] device_release+0x32/0xa0
[31813.104899] [<ffffffff812b6b47>] kobject_cleanup+0x77/0x1b0
[31813.104902] [<ffffffff812b69c8>] kobject_put+0x28/0x60
[31813.104906] [<ffffffff813ac7f7>] put_device+0x17/0x20
[31813.104913] [<ffffffffa009c5eb>] scsi_device_put+0x3b/0x50 [scsi_mod]
[31813.104920] [<ffffffffa025e7e0>] scsi_disk_put+0x30/0x50 [sd_mod]
[31813.104926] [<ffffffffa025f6a1>] sd_release+0x31/0x70 [sd_mod]
[31813.104931] [<ffffffff811dc75c>] __blkdev_put+0x17c/0x1b0
[31813.104936] [<ffffffff811dc6f7>] __blkdev_put+0x117/0x1b0
[31813.104940] [<ffffffff811dd0be>] blkdev_put+0x4e/0x140
[31813.104944] [<ffffffff811a5f64>] kill_block_super+0x44/0x70
[31813.104947] [<ffffffff811a622d>] deactivate_locked_super+0x3d/0x60
[31813.104950] [<ffffffff811a67e6>] deactivate_super+0x46/0x60
[31813.104954] [<ffffffff811c24d5>] mntput_no_expire+0xe5/0x170
[31813.104958] [<ffffffff811c3730>] SyS_umount+0x90/0x3c0
[31813.104962] [<ffffffff8151d8be>] ? do_page_fault+0xe/0x10
[31813.104966] [<ffffffff815216ad>] system_call_fastpath+0x1a/0x1f
[31813.104968] ---[ end trace 9c2068df074620da ]---
I never had any trouble this this before on my previous laptop (Lenovo ThinkPad E330).
Likewise, when I use TrueCrypt to mount a volume, although I don't get the stack trace, It does never shows up in Nautilus, and dmesg has the following to say about it:
[31234.534922] loop: module loaded
[31234.610930] FAT-fs (dm-5): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I can view the drive, however, so it's not as bad as the USB stick, but still not the correct behavior. There is no automount and Nautilus does not show it in the device list.
I've tried formatting the USB stick a few different times (it needs to be FAT for compatibility) and always Arch ends up corrupting the drive and making it useless.
Anyone have any idea as to what's going on here?
Thanks
-Nick
Last edited by silverbucket (2014-03-16 23:59:56)

Trying again, to manually mount the USB stick, when I insert it, dmesg shows:
[22021.214586] usb-storage 2-1:1.0: USB Mass Storage device detected
[22021.214633] scsi5 : usb-storage 2-1:1.0
[22022.215965] scsi 5:0:0:0: Direct-Access Patriot Memory PMAP PQ: 0 ANSI: 6
[22022.216251] sd 5:0:0:0: Attached scsi generic sg1 type 0
[22022.216440] sd 5:0:0:0: [sdb] 60566016 512-byte logical blocks: (31.0 GB/28.8 GiB)
[22022.216733] sd 5:0:0:0: [sdb] Write Protect is off
[22022.216736] sd 5:0:0:0: [sdb] Mode Sense: 45 00 00 00
[22022.217088] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[22022.373041] sdb: sdb1
[22022.374051] sd 5:0:0:0: [sdb] Attached SCSI removable disk
I then try to mount it with:
# mount /dev/sdb1 /mnt/usbstick
And although the command appears to be successful, I get the following in dmesg:
[22182.804311] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[22186.212884] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[22191.224027] usb 2-1: device descriptor read/8, error -110
[22191.327268] usb 2-1: reset SuperSpeed USB device number 4 using xhci_hcd
[22196.338854] usb 2-1: device descriptor read/8, error -110
[22196.495462] sd 5:0:0:0: [sdb] Unhandled error code
[22196.495465] sd 5:0:0:0: [sdb]
[22196.495466] Result: hostbyte=0x07 driverbyte=0x00
[22196.495468] sd 5:0:0:0: [sdb] CDB:
[22196.495470] usb 2-1: USB disconnect, device number 4
[22196.495468] cdb[0]=0x28: 28 00 00 00 0c ad 00 00 f0 00
[22196.495477] end_request: I/O error, dev sdb, sector 3245
[22196.502037] sd 5:0:0:0: [sdb] Unhandled error code
[22196.502041] sd 5:0:0:0: [sdb]
[22196.502043] Result: hostbyte=0x01 driverbyte=0x00
[22196.502045] sd 5:0:0:0: [sdb] CDB:
[22196.502046] cdb[0]=0x28: 28 00 00 00 0c ae 00 00 ef 00
[22196.502056] end_request: I/O error, dev sdb, sector 3246
[22196.502138] FAT-fs (sdb1): FAT read failed (blocknr 3213)
[22196.502139] sd 5:0:0:0: [sdb] Unhandled error code
[22196.502141] sd 5:0:0:0: [sdb]
[22196.502142] Result: hostbyte=0x01 driverbyte=0x00
[22196.502143] sd 5:0:0:0: [sdb] CDB:
[22196.502144] cdb[0]=0x28: 28 00 00 00 0d 9d 00 00 0d 00
[22196.502152] end_request: I/O error, dev sdb, sector 3485
[22196.504146] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800785c7980
[22196.504149] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8800785c79c0
A `df` does not show the mounted location, neither does Nautilus, however `mount` does.
/dev/sdb1 on /mnt/ZELENACEK type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
When I attempt to unmount it:
# umount /dev/sdb1
I get the following dmesg output:
[22410.233289] FAT-fs (sdb1): FAT read failed (blocknr 3210)
[22415.819947] FAT-fs (sdb1): Directory bread(block 32768) failed
[22415.819951] FAT-fs (sdb1): Directory bread(block 32769) failed
[22415.819953] FAT-fs (sdb1): Directory bread(block 32770) failed
[22415.819955] FAT-fs (sdb1): Directory bread(block 32771) failed
[22415.819956] FAT-fs (sdb1): Directory bread(block 32772) failed
[22415.819958] FAT-fs (sdb1): Directory bread(block 32773) failed
[22415.819960] FAT-fs (sdb1): Directory bread(block 32774) failed
[22415.819961] FAT-fs (sdb1): Directory bread(block 32775) failed
[22415.819963] FAT-fs (sdb1): Directory bread(block 32776) failed
[22415.819964] FAT-fs (sdb1): Directory bread(block 32777) failed
[22556.688959] ------------[ cut here ]------------
[22556.688967] WARNING: CPU: 2 PID: 27239 at fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
[22556.688968] sysfs group ffffffff81895c40 not found for kobject 'target5:0:0'
[22556.688970] Modules linked in: sg nls_cp437 vfat fat usb_storage fuse ctr ccm snd_hda_codec_hdmi joydev mousedev arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm iTCO_wdt iTCO_vendor_support microcode iwlmvm evdev cdc_mbim pcspkr uvcvideo psmouse serio_raw mac80211 videobuf2_vmalloc videobuf2_memops btusb videobuf2_core videodev cdc_ncm usbnet bluetooth mii cdc_acm cdc_wdm media iwlwifi rtsx_pci_ms cfg80211 memstick thermal snd_hda_codec_realtek wmi e1000e i915 ac thinkpad_acpi nvram rfkill battery tpm_tis snd_hda_intel tpm snd_hda_codec intel_agp intel_gtt snd_hwdep drm_kms_helper mei_me snd_pcm i2c_i801 ptp drm snd_page_alloc video snd_timer mei i2c_algo_bit snd button shpchp soundcore pps_core i2c_core lpc_ich processor ext4 crc16 mbcache jbd2 dm_crypt dm_mod sd_mod rtsx_pci_sdmmc
[22556.689016] mmc_core atkbd libps2 crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci libata ehci_pci ehci_hcd xhci_hcd rtsx_pci scsi_mod usbcore usb_common i8042 serio
[22556.689032] CPU: 2 PID: 27239 Comm: umount Tainted: G W 3.13.6-1-ARCH #1
[22556.689034] Hardware name: LENOVO 20AL009NMC/20AL009NMC, BIOS GIET66WW (2.16 ) 12/02/2013
[22556.689035] 0000000000000009 ffff880066217b40 ffffffff81513274 ffff880066217b88
[22556.689038] ffff880066217b78 ffffffff81061a3d 0000000000000000 ffffffff81895c40
[22556.689040] ffff88020af40438 ffff880089e30190 ffff880211ce7800 ffff880066217bd8
[22556.689043] Call Trace:
[22556.689048] [<ffffffff81513274>] dump_stack+0x4d/0x6f
[22556.689052] [<ffffffff81061a3d>] warn_slowpath_common+0x7d/0xa0
[22556.689055] [<ffffffff81061aac>] warn_slowpath_fmt+0x4c/0x50
[22556.689058] [<ffffffff8151843e>] ? mutex_unlock+0xe/0x10
[22556.689060] [<ffffffff8121925e>] ? sysfs_get_dirent_ns+0x4e/0x70
[22556.689063] [<ffffffff8121a3e6>] sysfs_remove_group+0xc6/0xd0
[22556.689067] [<ffffffff813b7033>] dpm_sysfs_remove+0x43/0x50
[22556.689070] [<ffffffff813aceb5>] device_del+0x45/0x1c0
[22556.689079] [<ffffffffa00c02b7>] scsi_target_reap_usercontext+0x27/0x40 [scsi_mod]
[22556.689082] [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[22556.689089] [<ffffffffa00c15d4>] scsi_target_reap+0xc4/0xf0 [scsi_mod]
[22556.689096] [<ffffffffa00c3558>] scsi_device_dev_release_usercontext+0x188/0x1c0 [scsi_mod]
[22556.689098] [<ffffffff8107b887>] execute_in_process_context+0x67/0x70
[22556.689105] [<ffffffffa00c33cc>] scsi_device_dev_release+0x1c/0x20 [scsi_mod]
[22556.689107] [<ffffffff813ac3f2>] device_release+0x32/0xa0
[22556.689111] [<ffffffff812b6b47>] kobject_cleanup+0x77/0x1b0
[22556.689114] [<ffffffff812b69c8>] kobject_put+0x28/0x60
[22556.689117] [<ffffffff813ac7f7>] put_device+0x17/0x20
[22556.689123] [<ffffffffa00b75eb>] scsi_device_put+0x3b/0x50 [scsi_mod]
[22556.689128] [<ffffffffa029a7e0>] scsi_disk_put+0x30/0x50 [sd_mod]
[22556.689133] [<ffffffffa029b6a1>] sd_release+0x31/0x70 [sd_mod]
[22556.689136] [<ffffffff811dc75c>] __blkdev_put+0x17c/0x1b0
[22556.689140] [<ffffffff811dc6f7>] __blkdev_put+0x117/0x1b0
[22556.689143] [<ffffffff811dd0be>] blkdev_put+0x4e/0x140
[22556.689145] [<ffffffff811a5f64>] kill_block_super+0x44/0x70
[22556.689148] [<ffffffff811a622d>] deactivate_locked_super+0x3d/0x60
[22556.689150] [<ffffffff811a67e6>] deactivate_super+0x46/0x60
[22556.689153] [<ffffffff811c24d5>] mntput_no_expire+0xe5/0x170
[22556.689156] [<ffffffff811c3730>] SyS_umount+0x90/0x3c0
[22556.689158] [<ffffffff815216ad>] system_call_fastpath+0x1a/0x1f
[22556.689160] ---[ end trace 615f2c14f65f6abb ]---
If I take the USB stick out and plug it in to my other Arch Linux laptop, the drive mounts fine (and complains about fsck only because of the problems incurred on my main laptop). I know the USB stick is good, it's new and I've used it many times between my other machines. I'm assuming the hardware is good as it's a new laptop, I installed Arch Linux from this same USB stick without an issue. I've also used other types of USB devices, like wireless headphones, without issues.
It must be some system configuration error. Perhaps something with the kernel or system libraries that are / are not installed? lib32 issues? (it's an x86_64 install)? I don't know, I'm grasping at straws. I have read through the USB_Storage_Devices and Udisks Arch Wiki pages without any luck.
Any help is greatly appreciated as I currently can't get any large amounts data on or off this laptop easily.
Last edited by silverbucket (2014-03-16 23:42:56)

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

KDE mount USB device fails

Hi,
I am running KDE and having problems mounting USB devices via the KDE Device Notifier in the task bar. When I insert the USB stick there is the normal little popup giving me the option to open the flash drive in dolphin. When I click it, I get the following error:
"Could not mount the following device"
Mounting the device via terminal works fine. I also put my user into the "storage" group like the wiki tells me. Still no change.
Any ideas?

willtriv wrote:
Note: slim is ConsoleKit capable since version 1.3.3. Unless you happen to run an old version, you must no longer include ck-launch-session in your .xinitrc or slim.conf login_cmd.
These kind of changes without notifications to users cause headaches. Someone was kind enough to update the wiki!
You are my personal hero for today, I was suffering the same problem. Manifests itself as 2 CK sessions listed by ck-launch-session, with the wrong session being marked as active.
Last edited by crobe2 (2012-06-11 14:28:12)

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

Systemd-remount-fs.service fails [SOLVED]

After a fresh install on a brandnew laptop, my root partition is being mounted read only, and I see that systemd-remount-fs.service fails:
[root@anton ~]# systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
Active: failed (Result: exit-code) since Sat, 2012-12-01 21:00:05 MST; 18min ago
Docs: man:systemd-remount-fs.service(8)
Process: 186 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-remount-fs.service
Dec 01 21:00:05 anton systemd-remount-fs[186]: mount: / not mounted or bad option
Dec 01 21:00:05 anton systemd-remount-fs[186]: In some cases useful info is found in syslog - try
Dec 01 21:00:05 anton systemd-remount-fs[186]: dmesg | tail or so
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I have no idea why this is happening, or what to do to try and fix it - any help/advice would be greatly appreciated. Following is the information I think is necessary for assistance:
Note that I have /usr on a separate partition, which I suspect is possibly involved in the issue somehow.
Here's my fstab:
[root@anton ~]# cat /etc/fstab
# /dev/sda5
#UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 defaults,rw,noatime,discard,data=writeback 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,noatime,discard,data=writeback 0 0
# /dev/sda7
UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
# /dev/sda8
UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
Here's the relevant output from mount (note that my root (sda5) partition is not being mount with the options I specified in fstab):
[root@anton ~]# mount | grep sda
/dev/sda5 on / type ext4 (ro,relatime,data=ordered)
/dev/sda6 on /usr type ext4 (rw,noatime,discard,data=writeback)
/dev/sda7 on /var type ext4 (rw,noatime,discard,data=ordered)
/dev/sda8 on /home type ext4 (rw,relatime,discard,data=ordered)
Relavant snippet from /boot/grub/grub.cfg:
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-a09ff37e-ce60-4173-b95a-4b71a53c01d3' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 a09ff37e-ce60-4173-b95a-4b71a53c01d3
else
search --no-floppy --fs-uuid --set=root a09ff37e-ce60-4173-b95a-4b71a53c01d3
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 ro init=/usr/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
Finally, here's my mkinitcpio.cfg:
[root@anton ~]# cat /etc/mkinitcpio.conf
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect sata filesystems usbinput usr fsck shutdown"
Last edited by corey_s (2012-12-02 08:57:35)

Thanks for the quick response, WonderWoofy ( by the way, great username! )!
When I removed or modified the the mount options in the bootloader kernel command line, there was no change to the status of the fs after boot-up. I had changed it at one point from 'ro', to 'rw'; but doing so had no affect on the output of the mount command.
However, I did finally identify the cause: turns out if I specify 'data=writeback', in fstab for the root partition, then systemd-remount-fs.service fails, as per my OP - leaving me with a 'ro'-mounted root filesystem. Simply removing that, or changing it to 'data=ordered', solved the issue: when I rebooted, the root partition was mounted as per my fstab config.
So, my fstab now looks like this:
# /dev/sda5
UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 rw,noatime,discard 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,ro,noatime,discard,data=writeback 0 0
# /dev/sda7
UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
# /dev/sda8
UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
... and all is now well.
I'll mark this as solved, but I'll also ask: why does specifying 'data=writeback' on my root partition cause the systemd-remount-fs.service to fail? Any experts out there know?
Last edited by corey_s (2012-12-02 06:46:32)

Systemd (auto)mount USB fails due to fsck

Similar Messages

Maybe you are looking for