[solved] Mounting /media as tmpfs causes breakage on bootup

Hi,
I have a little problem when updating to systemd 208-3 and /media as tmpfs: My system won't boot anymore and I end up in an emergency-shell. Everything was and is fine with systemd 208-2 (a Downgrade fixes everything as well as commenting the line in my fstab).
Related journalentries:
Dez 21 15:15:33 mymachine systemd[1]: Job tmpfs.device/start timed out.
Dez 21 15:15:33 mymachine systemd[1]: Timed out waiting for device tmpfs.device.
Dez 21 15:15:33 mymachine systemd[1]: Dependency failed for File System Check on /tmpfs.
Dez 21 15:15:33 mymachine systemd[1]: Dependency failed for /media.
Dez 21 15:15:33 mymachine systemd[1]: Dependency failed for Local File Systems.
I specify the /media-tmpfs in my fstab as followed:
#media
tmpfs /media tmpfs rw,nodev,noexec,nosuid 0 2
Any ideas why I end up in an emergency shell and how to solve that? I would preferrably keep /media as a tmpfs.
Thanks in advance!
Last edited by Ovion (2013-12-22 22:18:28)

Ovion wrote:#media
tmpfs /media tmpfs rw,nodev,noexec,nosuid 0 2
It's about that "2". You can't fsck a tmpfs.
See also: https://bugs.archlinux.org/task/38210

Similar Messages

[SOLVED] Mounting /tmp as tmpfs does not work?

Hi,
running arch since a few days now, and began a bit of tweaking.
I read, mounting the /tmp dir as a tmpfs adding the following line to my /etc/fstab should slightly increase performance. (plus removing the old /tmp mount rule)
none /tmp tmpfs nodev,nosuid,noatime,size=1000M,mode=1777 0 0
I have conky running showing my ram usage. Shouldn't the numbers increase if I copy something to the /tmp directory? I copied a large file to the dir. but nothing happened to the ram usage.
Thank you in advance, Peter
Last edited by phoenigs (2010-09-05 19:08:20)

Hi again,
Here the outputs of the two commands:
[peter@phlap|~]$ mount
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=493581,mode=755)
/dev/disk/by-uuid/4afd9796-b899-47a8-a4e0-04d70209a635 on / type ext4 (rw,relatime,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw)
shm on /dev/shm type tmpfs (rw,nosuid,nodev)
/dev/sda4 on /home type ext4 (rw)
/dev/sda1 on /boot type ext2 (rw)
none on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=1000M,mode=1777)
[peter@phlap|~]$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 208K 9.8M 3% /dev
/dev/disk/by-uuid/4afd9796-b899-47a8-a4e0-04d70209a635
39G 3.4G 34G 10% /
shm 1.9G 2.1M 1.9G 1% /dev/shm
/dev/sda4 104G 1.1G 98G 2% /home
/dev/sda1 99M 16M 79M 17% /boot
none 1000M 661M 340M 67% /tmp
(I know the / partition is chosen a bit too large)
But here is another output:
[peter@phlap|tmp]$ free -m
total used free shared buffers cached
Mem: 3858 1965 1892 0 28 1605
-/+ buffers/cache: 330 3527
Swap: 4502 0 4502
As you can see, the mounting works properly. I have copied a 600mb file to /tmp, and it still says 330mb free ram. Or does the tmpfs count as "cached"?
I just want the "proof" that my /tmp directory is in the ram now
Last edited by phoenigs (2010-09-04 22:54:13)

[Solved] Mount LUKS encrypted hard drive at boot

Hi,
This is driving me nuts. I'm getting angry to be honest.
I encrypted my brand new WD portable hard drive with LUKS + dm-crypt and I can now normally map and mount it with the following commands:
sudo cryptsetup luksOpen /dev/sdc1 WesternDigital
[Enter Passphrase]
sudo mount /dev/mapper/WesternDigital /media/WesternDigital
I would like to map and mount it at boot time (where I should be prompted for the passphrase), so I edited:
/etc/crypttab
WesternDigital /dev/sdc1 none luks
and:
/etc/fstab
/dev/mapper/WesternDigital /media/WesternDigital ext4 defaults,noauto,noatime 0 0
During boot I get some errors regarding the decrypting or mapping of WesternDigital that fails but it's too fast to note down something (and, as you probably know, there's no known way to log boot messages on Arch...)
After boot if I try to manually mount /media/WesternDigital I get a message saying /dev/mapper/WesternDigital does not exist.
So I guess the problem is in the mapping phase and thus in the /etc/crypttab file.
I can't find anything in the internet but maybe I'm missing something very basic (a daemon, a module?).
Any help is indeed very appreciated, thank you.
Last edited by rent0n (2010-09-24 15:27:16)

Ok, it's solved. I tried many different configurations of /etc/crypttab, /etc/fstab, /etc/mkinitcpio.conf /etc/rc.conf /boot/grub/menu.lst and I finally found the right setup.
I'm not sure of what was wrong in the first place so I'll just post my current working configs for future reference.
/boot/grub/menu.lst
Doesn't need to be edited at all (ignore the above post).
/etc/rc.conf
You don't need to add any module here because the dm-crypt and dm-mod modules are loaded thanks to the encrypt hook.
/etc/mkinitcpio.conf
The HOOKS line should include usb, usbinput (probably) and encrypt. usb must precede encrypt that must precede filesystems:
HOOKS="base udev autodetect pata scsi sata usb usbinput keymap encrypt filesystems resume"
/etc/crypttab
WesternDigital /dev/sdX ASK
Do not insert 'luks', 'retry=X' or other kind of options (you can find this kind of options in many tutorials and howtos). That was one of my problems I guess.
/etc/fstab
/dev/mapper/WesternDigital /media/WesternDigital auto defaults,noatime 0 0
Note
I'm not sure if this has been helpful or not... however I was able to get it to work after following the advice found here.
Cheers,

Bootchart2-git: bootchart-renderer fails to mount /lib/bootchart/tmpfs

I recently bought a new laptop and made a fresh Arch installation. After a few initial annoyances I got everything working more or less as intended, except bootchart. Since the wiki said "Note: An alternative to Bootchart is bootchart2, which at least has more recent activity than 2005. It can be found on the AUR as bootchart2-git. It uses python for generating the final chart instead of a JVM. ", I used the git version from AUR, if that matters.
[r-a@vinter ~]$ /sbin/bootchartd start; sleep 1; /sbin/bootchartd stop
10834 109
bootchart-collector tmpfs mount to /lib/bootchart/tmpfs failed
Can't extract boot chart from collector
[r-a@vinter ~]$
A peek at the source code(collector/collector.c:625-630):
if (mount ("none", TMPFS_PATH, "tmpfs", MS_NOEXEC|MS_NOSUID, NULL) < 0) {
if (errno != EBUSY) {
fprintf (stderr, "bootchart-collector tmpfs mount to " TMPFS_PATH " failed\n");
return 1;
strace output:
15146 mount("none", "/lib/bootchart/tmpfs", "tmpfs", MS_NOSUID|MS_NOEXEC, NULL) = -1 EPERM (Operation not permitted)
man 2 mount says this:
EPERM The caller does not have the required privileges.
I haven't tried changing the default path to mount to for example something like /tmp/, perhaps it'd solve the privilege issue... What bugs me is that the default config indeed uses /lib/bootchart/ as it's base path... So I can only assume that it somehow should have permission to mount tmpfs to that directory? Whatever, I am a bit clueless here. What next?

Setting the SUID bit of bootchart-collector with chmod +s didn't do the trick; though I am not entirely sure if it was because of failed mount - I can't check it right now.
...anyone...?

[solved] Boot issues after update caused by LVM

Hi,
I know that there are some threads regarding boot issues but I haven't been able to find a solution for my problem.
I have the following partitions:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 74.5G 0 disk
├─sda1 8:1 0 128M 0 part /boot
├─sda2 8:2 0 2G 0 part [SWAP]
└─sda3 8:3 0 72.4G 0 part
├─vg_trinity-root (dm-0) 254:0 0 10G 0 lvm /
└─vg_trinity-home (dm-1) 254:1 0 25G 0 lvm /home
I have
USELVM="yes"
in my rc.conf and the following im mkinitcpio.conf:
HOOKS="base udev autodetect pata scsi sata lvm2 filesystems"
Still, when booting the volume group does not get activated. The following message appears:
:: running hook [lvm2]
Activating logical volumes...
No volume groups found
Waiting 10 seconds for device /dev/mapper/vg_trinity-root ...
ERROR: Unable to find root device '/dev/mapper/vg_trinity-root'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
At that point I just run
lvm vgchange -ay
exit the shell and booting continues. So somehow activation of the volume group does not occur early enough. I reinstalled udev, mkinitcpio, linux and generated a new boot image as proposed in https://bbs.archlinux.org/viewtopic.php … 4#p1059124 but to no avail. Is there anything else that might be wrong with my configuration?
Thanks for any help.
mK
Last edited by musiKk (2012-09-09 16:23:17)

My apologies. Usually I'm quite good at searching but this one slipped right past me. Marking as solved (even though the root cause is still WIP).

[Solved]Permission issues with mounted media

hello everyone. i have a issue that is more of a annoyance than a problem. when i attach my usb hard drive i get this error
Rejected send message, 1 matched rules; type="method_call", sender=":1.15" (uid=1000 pid=8611 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3138 comm="/usr/sbin/hald)).
and am forced to open up the file manager as root to do anything with the device or its contents after transfer. if anyone has a suggestion or fix please enlighten me. im using openbox and thunar. i used the ck-launch-session in my ~/.xinitrc. thank you ahead of time for your help.
Last edited by trishtren18 (2009-12-20 16:37:17)

DeSian wrote:
jasonwryan wrote:Have you tried the fixes suggested in the HAL entry? It sounds like a policy kit fix...
I've tried every way before and this also:
Try adding /usr/sbin/console-kit-daemon to /etc/rc.local that has fixed it for me, for some reason it mustn't of been getting started
still have the same error message by trying to mount USB device.
Error:
Rejected send message, 1 matched rules; type="method_call", sender=":1.10" (uid=1000 pid=1756 comm="pcmanfm) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1598 comm="/usr/sbin/hald))
and i can't Shutdown and Reboot from LXDE
http://wiki.archlinux.org/index.php/LXD … _from_LXDE
best regards
This thread is marked solved - you may want to open a new one & include details about your DE/WM, any errors, what happens when you try to mount manually etc...

[SOLVED] mount.nfs4: access denied by server

Hi folks. I seem to be having a bit of a problem getting nfs4 to work. I am trying to mount a share from alpha (my fileserver) onto charlie (my workstation). Both of these are new Arch systems and I haven't had any nfs working yet, although I have with other distros on the same hardware.
Fileserver (alpha) config:
# /etc/exports
/files 192.164.1.0/24(rw,sync,fsid=0,no_subtree_check)
# /etc/hosts.allow
sshd: 192.168.1.0/255.255.255.0
nfsd: 192.168.1.0/255.255.255.0
rpcbind: 192.168.1.0/255.255.255.0
mountd: 192.168.1.0/255.255.255.0
idmapd: 192.168.1.0/255.255.255.0
statd: 192.168.1.0/255.255.255.0
[General]
Verbosity = 3
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = localdomain
[Mapping]
Nobody-User = nobody
Nobody-Group = nobody
[Translation]
Method = nsswitch
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 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 /boot ext3 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda5 / ext3 defaults 0 1
/dev/sda6 /var ext3 defaults 0 1
/dev/sda7 /home ext3 defaults 0 1
/dev/sda8 /files ext3 defaults 0 1
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs defaults 0 0
nfsd /proc/fs/nfsd nfsd rw,nodev,noexec,nosuid 0 0
DAEMONS=(syslog-ng network netfs rpcbind nfs-common nfs-server hal @alsa @crond @openntpd @sshd)
[root@alpha ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 19228276 879492 17372036 5% /
none 507792 140 507652 1% /dev
none 507792 0 507792 0% /dev/shm
/dev/sda1 93307 15887 72603 18% /boot
/dev/sda6 19228276 372632 17878896 3% /var
/dev/sda7 19228276 176224 18075304 1% /home
/dev/sda8 902688436 204872 856629640 1% /files
[root@alpha ~]#
Workstation (charlie) config:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 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
UUID=437982b2-5c84-4f53-954d-cf43f8b4e707 / ext3 defaults 0 1
UUID=97d79d76-357a-4f4e-8513-f181bff6af62 /boot ext3 defaults 0 1
UUID=d8525095-9b97-4439-932f-8f4e0236cce1 /home ext3 defaults 0 1
UUID=ffba933b-af93-407c-b1b8-69d1cc5be146 swap swap defaults 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs defaults 0 0
alpha:/ /files nfs4 defaults 0 0
[General]
Verbosity = 3
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = localdomain
[Mapping]
Nobody-User = nobody
Nobody-Group = nobody
[Translation]
Method = nsswitch
DAEMONS=(syslog-ng network crond alsa hal fam rpcbind nfs-common netfs)
[root@charlie ~]# mount -a
mount.nfs4: access denied by server while mounting alpha:/
[root@charlie ~]#
This happens even after both systems are rebooted. Can anyone spot what I am missing?
Thanks for looking.
Last edited by dgregory46 (2009-10-21 01:04:09)

Now I really feel stupid. A little proofreading would have saved me a big headache. In /etc/exports I was exporting to 192.164.1.0/24 while my network is the more standard 192.168.1.0/24.
It works fine now, although I did take phaul's suggestion and added my main share "inside" the nfs4 root.

[solved] Mount/unmount extremely slow (relatively)

When I first installed my system, mounting and unmounting took a relatively unnoticeable amount of time. Now, mounting a single volume takes about a minute or more per volume, even for tmpfs volumes. I don't seem to see any other performance problems with my system other than this.
The change happened rather suddenly after I shredded a partition on my drive with one run of bytes (the overall size was about 100 GiB, but I've written several times that onto my drive). If it makes any difference, the partition was the one that's right to the left of my root partition, but I doubt that anything flowed over. The disk seems to be operating fine, and when I mount from live CDs, it takes the normal time.
Has anyone ever experienced this kind of problem before? Do you know what I can do to fix it without reinstalling my system? I tried reinstalling both the linux and util-linux packages, but that didn't seem to help.
EDIT: Problem's been solved. To fix:
- Downgrade to util-linux 2.20-2.
- Save everything that you're working on.
- Run the following:
# echo 1 > /proc/sys/kernel/sysrq
# rm -rf /etc/mtab*
- Hold Alt + SysRq and then type out REISUB to reboot.
Last edited by RetroX (2011-10-08 19:09:26)

I'm not sure I'm knowledgeable enough to help too much, but you might like to have a look at the strace command to debug this. It lets you see what calls a program makes to the kernel. You can compare its output on your arch system to what your live CD gives you.
Mounting an ext2 disk on my machine produces this summary (the -c option). I got fairly varied output each time I ran the command, but hopefully yours is more consistent.
$ strace -c mount /dev/sdb2 /mnt/Backup/
% time seconds usecs/call calls errors syscall
100.00 0.000018 1 18 mmap2
0.00 0.000000 0 101 read
0.00 0.000000 0 4 write
0.00 0.000000 0 20 6 open
0.00 0.000000 0 14 close
0.00 0.000000 0 1 execve
0.00 0.000000 0 3 time
0.00 0.000000 0 1 1 mount
0.00 0.000000 0 1 1 access
0.00 0.000000 0 3 brk
0.00 0.000000 0 2 1 ioctl
0.00 0.000000 0 1 umask
0.00 0.000000 0 11 10 readlink
0.00 0.000000 0 5 munmap
0.00 0.000000 0 1 uname
0.00 0.000000 0 7 mprotect
0.00 0.000000 0 91 _llseek
0.00 0.000000 0 2 prctl
0.00 0.000000 0 2 rt_sigprocmask
0.00 0.000000 0 5 3 stat64
0.00 0.000000 0 2 lstat64
0.00 0.000000 0 11 fstat64
0.00 0.000000 0 3 getuid32
0.00 0.000000 0 2 getgid32
0.00 0.000000 0 3 geteuid32
0.00 0.000000 0 2 getegid32
0.00 0.000000 0 1 set_thread_area
0.00 0.000000 0 1 fadvise64_64
0.00 0.000000 0 1 fstatat64
100.00 0.000018 319 22 total
The summary is probably more interesting initially, but the full dump may be useful later (replace -c with -C for the the full dump combined with the summary).
Edit:
Another similar program you might like to look at is ltrace, which shows library calls (this article put me onto it).
$ ltrace -c mount /dev/sdb2 /mnt/Backup
% time seconds usecs/call calls function
48.11 0.046996 46996 1 blkid_do_safeprobe
22.59 0.022073 49 445 strlen
15.04 0.014694 28 507 strncmp
3.45 0.003375 3375 1 mount
2.37 0.002319 2319 1 blkid_probe_set_device
2.10 0.002048 2048 1 mnt_update_table
1.21 0.001181 1181 1 blkid_free_probe
1.01 0.000989 26 37 __strdup
0.39 0.000383 383 1 mnt_update_set_fs
0.39 0.000382 76 5 __xstat64
0.37 0.000358 358 1 setlocale
0.29 0.000287 26 11 free
0.28 0.000278 139 2 open64
0.25 0.000247 123 2 close
0.20 0.000198 49 4 readlink
0.19 0.000181 25 7 __errno_location
0.14 0.000136 136 1 blkid_evaluate_spec
0.11 0.000109 27 4 strchr
0.11 0.000108 27 4 strtok
0.11 0.000104 26 4 sigdelset
0.10 0.000097 48 2 sigprocmask
0.09 0.000085 28 3 __snprintf_chk
0.08 0.000080 26 3 strrchr
0.07 0.000065 65 1 access
0.06 0.000060 30 2 sigfillset
0.06 0.000054 54 1 __lxstat64
0.05 0.000051 51 1 getuid
0.05 0.000050 50 1 mnt_fs_set_options
0.05 0.000049 49 1 umask
0.05 0.000047 47 1 geteuid
0.05 0.000047 47 1 blkid_new_probe
0.04 0.000040 40 1 blkid_probe_lookup_value
0.04 0.000039 39 1 blkid_probe_set_superblocks_flags
0.04 0.000037 37 1 blkid_probe_enable_superblocks
0.04 0.000036 36 1 mnt_new_fs
0.04 0.000035 35 1 getopt_long
0.03 0.000034 34 1 mnt_init_debug
0.03 0.000034 34 1 mnt_fs_set_source
0.03 0.000033 33 1 bindtextdomain
0.03 0.000032 32 1 mnt_fs_set_fstype
0.03 0.000032 32 1 mnt_free_update
0.03 0.000031 31 1 mnt_new_update
0.03 0.000031 31 1 textdomain
0.03 0.000030 30 1 malloc
0.03 0.000030 30 1 __cxa_atexit
0.03 0.000029 29 1 mnt_free_fs
0.03 0.000028 28 1 mnt_fs_set_target
0.03 0.000028 28 1 mnt_update_get_mflags
100.00 0.097690 1074 total
Last edited by splondike (2011-10-06 12:21:07)

[solved] mount CD/DVD

This is my problem
the DVD only shows up in "system:/media/sr0
not in
or in
My DVD Player, and also MP3 Player can't find the DVD. The Error,
no media found in "/media"
I have two DVD one DVDRom and one DVD +-RW DL Burner
so far there is no problem with K3B to burn a DVD or CD.
This Error is related to Amarok, Kaffeine, XMMS, Gxine and another players. They don't find the DVD or CD.
vi /etc/rc.conf
DAEMONS=(syslog-ng hwd network netfs kdm dbus hal crond)
What do I missing?
Last edited by JaDa (2007-06-28 23:53:07)

ndlarsen wrote:
Misfit138 wrote:I have my dvd/cdrom entries commented out in my fstab, and I let hal handle it completely. Works great.
It does look like the icon text states "blank something".
oops, it is blank & jones my test audio CD!
My problem is solved! Thanks for all your ideas!
The most important what I missed was "autofs"! Hal and dbus are not enough!
Install autofs
pacman -S autofs
then follow this wiki
http://wiki.archlinux.org/index.php/AutoFS_HowTo
very important
Edit the file /etc/autofs/auto.master. Delete the existing contents and add the following line:
/media /etc/autofs/auto.media
and take a closer look if you using VI or VIM command on "/media /" it's not "/media/"
If Autofs doesn't automatically unmount your devices (after you finish this wiki), replace last line by :
/media /etc/autofs/auto.media --timeout 3
you need to add "--timeout 3"
also add the daemon "aufofs" in the "/etc/rc.conf" if you like it at the startup.
The USB devises for digital camera and USB Stick or just changing Musik/Movie CD/DVD just work fine now.
There is no error anymore in Kaffeine or another players
no media found in "/media"
all is works perfect. The Icon's for mounted devises show now up on my desktop (KDE) too!

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

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

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

[SOLVED]Mounting usb drives "not authorized" with thunar-volman (XFCE)

Hi,
I'm new to Arch (even though I must be approximately at my 15th try at installing it properly) and I have a problem with thunar-volman.
Whenever I log in as user, and try to mount a usb drive with thunar, let's say I want to plug a drive labeled Ext3_8Go, I get the same message in a pop-up window : "Failed to mount Ext3_8Go (or anything close, not in English in the text), not authorized (that part is in English)"
My install is :
- net install
- partitions : 9Go for /, no swap, no separate /home
- packages : base and base-devel. The only modifications in the package list is that I remove ppp, pcmciautils, and xfsprogs.
- config : at the install stage I only modify rc.conf to change LOCALE and HOSTNAME, and pacman's mirrorlist to allow all French mirrors in addition to the one at the top.
When the usb installation is over, I run this script :
"installation_xfce.sh" (there may be some errors left, I modify this script as I learn) :
#!/bin/bash
# expected environment : freshly installed archlinux, login : root.
echo "Are you connected to internet ? If not, please Ctrl+C and reload this script when connected"
echo "Otherwise, press ENTER to continue installation"
read var_dummy
echo "Creation of the user : please type in your user name :"
read var_username
useradd -u 1000 -g users -G audio,lp,storage,optical,video,wheel,games,power,network -d /home/$var_username/ -s /bin/bash -m $var_username
echo "You will now be asked to create the password for this user:"
passwd $var_username
# Add servers for pacman to find packages
cat >> /etc/pacman.conf << EOF
[multilib]
Include = /etc/pacman.d/mirrorlist
[archlinuxfr]
Server = http://repo.archlinux.fr/\$arch
[catalyst]
Server = http://catalyst.apocalypsus.net/repo/catalyst/\$arch
EOF
# Install packages
pacman -Syyu
pacman -S acpi acpid alsa-oss alsa-plugins alsa-utils catalyst catalyst-utils cpufrequtils cups dbus gstreamer0.10-base-plugins iptables laptop-mode-tools mesa net-tools netcfg ntp pm-utils rfkill rsync sudo ttf-dejavu vim wireless_tools xf86-input-evdev xorg-server xorg-utils xorg-xinit xorg-xinput yaourt conky gamin gnome-icon-theme gnome-keyring gvfs-afc network-manager-applet networkmanager slim slim-themes archlinux-themes-slim hicolor-icon-theme xfce4 xfce4-goodies
# If pacman failed, better stop the script here, and wait for a network connection
if [[ $?!=0 ]]
then
echo : failed to install packages - check your network connection, or review script
exit 1
fi
# Fix sound issue
cat > /home/$var_username/.asoundrc << EOF
pcm.!default{
type hw
card 1
device 0
ctl.!default{
type hw
card 1
device 0
EOF
chown $var_username:users /home/$var_username/.asoundrc
# Configure video settings for X to use Catalyst
if [[ ! -e /etc/X11/xorg.conf.d ]]
then
mkdir /etc/X11/xorg.conf.d
fi
cat > /etc/X11/xorg.conf.d/20-fglrx.conf << EOF
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
EndSection
EOF
sed -e 's/top_left/bottom_right/' -e '/alignment/i\double_buffer yes' -e '/CPU Usage/a\${color lightgrey}Temperatures:' -e '/CPU Usage/a\ CPU:$color ${hwmon 0 temp 1}°C' </etc/conky/conky.conf >/home/$var_username/.conkyrc
chown $var_username:users /home/$var_username/.conkyrc
# Install clickpad support
yaourt -S xf86-input-synaptics-clickpad
# Add french keyboard to X
sed '/MatchIsKeyboard/a\\tOption "XkbLayout" "fr"' </etc/X11/xorg.conf.d/10-evdev.conf >/etc/X11/xorg.conf.d/10-evdev.conf.new
mv -f /etc/X11/xorg.conf.d/10-evdev.conf.new /etc/X11/xorg.conf.d/10-evdev.conf
# Add new daemons, remove old ones, disable hwclock and remove netfs since I don't use it. add it if you need it
sed '/DAEMONS=/c\DAEMONS=(!hwclock dbus syslog-ng networkmanager laptop-mode acpid @alsa @cupsd @cpufrequtils ntpd crond)' </etc/rc.conf >/etc/rc.conf.new
mv -f /etc/rc.conf.new /etc/rc.conf
# Slim login manager ; change theme
mv /usr/share/slim/themes/archlinux-darch-grey /tmp/
mv /usr/share/slim/themes/default /tmp/
rm -r /usr/share/slim/themes/*
mv /tmp/archlinux-darch-grey /usr/share/slim/themes
mv /tmp/default /usr/share/slim/themes
sed '/^current_theme/c\current_theme archlinux-darch-grey' </etc/slim.conf >/etc/slim.conf
# XFCE login, and thunar launched as a daemon
sed '/^# exec/c\' </etc/skel/.xinitrc >/tmp/.xinitrc
sed '/^# .../c\' </tmp/.xinitrc >/home/$var_username/.xinitrc
cat >> /home/$var_username/.xinitrc << EOF
exec ck-launch-session startxfce4
thunar --daemon &
EOF
chown $var_username:users /home/$var_username/.xinitrc
# Boot to runlevel 5 now, and run slim then
sed -e 's/id:3/#id:3/' -e 's/#id:5/id:5/' -e 's|x:5:respawn:/usr/bin/xdm|#x:5:respawn:/usr/bin/xdm|' -e 's|#x:5:respawn:/usr/bin/slim|x:5:respawn:/usr/bin/slim|' </etc/inittab >/etc/inittab.new
mv -f /etc/inittab.new /etc/inittab
# Add colored prompt to user and root
sed '/^PS1/c\' </etc/skel/.bashrc >/root/.bashrc
cat >> /root/.bashrc << EOF
PS1='\[\e[0;32m\]\u@\h\[\e[m\] \[\e[0;35m\]\w\[\e[m\] \[\e[m\] \[\e[0;32m\]\t -\[\e[m\] \[\e[1;31m\]\$ \[\e[m\] '
EOF
cp /root/.bashrc /home/$var_username/.bashrc
chown $var_username:users /home/$var_username/.bashrc
# How does one do that automatically ?
# Manually add user to sudoers
EDITOR="vim" visudo
# Reboot, because it's quick and I'm too lazy to learn how to start all the daemons and others.
reboot
I can mount as a user, no password asked, with :
udisks --mount /dev/sdb2
but the GUI method tells me "not authorized".
"groups user" outputs :
lp wheel games network video audio optical storage power users
the command "ck-list-sessions" outputs :
Session2:
unix-user = '1000'
realname = ''
seat = 'Seat1'
session-type = ''
active = TRUE
x11-display = ':0.0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2011-08-15T08:56:03.716103Z'
login-session-id = '1'
Session1:
unix-user = '1000'
realname = ''
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':0.0'
x11-display-device = ''
display-device = ''
remote-host-name = ''
is-local = TRUE
on-since = '2011-08-15T08:56:03.573029Z'
login-session-id = '1'
For those who don't have time to read the installation script, DBUS is in the DAEMONS list of rc.conf, and .xinitrc launches : exec ck-launch-session startxfce4
Any idea ?
Last edited by choubbi (2011-08-15 15:05:04)

Thanks a lot !
That worked !
I stumbled across this part of the wiki several times before, but didn't really understand so I had not tried.
If anyone's interested in the script, here's the corrected version :
#!/bin/bash
# expected environment : freshly installed archlinux, login : root.
echo "Are you connected to internet ? If not, please Ctrl+C and reload this script when connected"
echo "Otherwise, press ENTER to continue installation"
read var_dummy
echo "Creation of the user : please type in your user name :"
read var_username
useradd -u 1000 -g users -G audio,lp,storage,optical,video,wheel,games,power,network -d /home/$var_username/ -s /bin/bash -m $var_username
echo "You will now be asked to create the password for this user:"
passwd $var_username
# Add servers for pacman to find packages
cat >> /etc/pacman.conf << EOF
[multilib]
Include = /etc/pacman.d/mirrorlist
[archlinuxfr]
Server = http://repo.archlinux.fr/\$arch
[catalyst]
Server = http://catalyst.apocalypsus.net/repo/catalyst/\$arch
EOF
# Install packages
pacman -Syyu
pacman -S acpi acpid alsa-oss alsa-plugins alsa-utils catalyst catalyst-utils cpufrequtils cups dbus gstreamer0.10-base-plugins iptables laptop-mode-tools mesa net-tools netcfg ntp pm-utils rfkill rsync sudo ttf-dejavu vim wireless_tools xf86-input-evdev xorg-server xorg-utils xorg-xinit xorg-xinput yaourt conky gamin gnome-icon-theme gnome-keyring gvfs-afc network-manager-applet networkmanager slim slim-themes archlinux-themes-slim hicolor-icon-theme xfce4 xfce4-goodies
# If pacman failed, better stop the script here, and wait for a network connection
if [[ $?!=0 ]]
then
echo : failed to install packages - check your network connection, or review script
exit 1
fi
# Fix sound issue
cat > /home/$var_username/.asoundrc << EOF
pcm.!default{
type hw
card 1
device 0
ctl.!default{
type hw
card 1
device 0
EOF
chown $var_username:users /home/$var_username/.asoundrc
# Configure video settings for X to use Catalyst
if [[ ! -e /etc/X11/xorg.conf.d ]]
then
mkdir /etc/X11/xorg.conf.d
fi
cat > /etc/X11/xorg.conf.d/20-fglrx.conf << EOF
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
EndSection
EOF
sed -e 's/top_left/bottom_right/' -e '/alignment/i\double_buffer yes' -e '/CPU Usage/a\${color lightgrey}Temperatures:' -e '/CPU Usage/a\ CPU:$color ${hwmon 0 temp 1}°C' </etc/conky/conky.conf >/home/$var_username/.conkyrc
chown $var_username:users /home/$var_username/.conkyrc
# Install clickpad support
yaourt -S xf86-input-synaptics-clickpad
# Add french keyboard to X
sed '/MatchIsKeyboard/a\\tOption "XkbLayout" "fr"' </etc/X11/xorg.conf.d/10-evdev.conf >/etc/X11/xorg.conf.d/10-evdev.conf.new
mv -f /etc/X11/xorg.conf.d/10-evdev.conf.new /etc/X11/xorg.conf.d/10-evdev.conf
# Add new daemons, remove old ones, disable hwclock and remove netfs since I don't use it. add it if you need it
sed '/DAEMONS=/c\DAEMONS=(!hwclock dbus syslog-ng networkmanager laptop-mode acpid @alsa @cupsd @cpufrequtils ntpd crond)' </etc/rc.conf >/etc/rc.conf.new
mv -f /etc/rc.conf.new /etc/rc.conf
# Slim login manager ; change theme
mv /usr/share/slim/themes/archlinux-darch-grey /tmp/
mv /usr/share/slim/themes/default /tmp/
rm -r /usr/share/slim/themes/*
mv /tmp/archlinux-darch-grey /usr/share/slim/themes
mv /tmp/default /usr/share/slim/themes
sed '/^current_theme/c\current_theme archlinux-darch-grey' </etc/slim.conf >/etc/slim.conf
# XFCE login, and thunar launched as a daemon (note that the part with 'if [ -d /etc/X11/xinit/xinitrc.d ]" is not present, to avoid mounting problems when logged as regular user)
cat > /home/$var_username/.xinitrc << EOF
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
exec ck-launch-session startxfce4
thunar --daemon &
EOF
chown $var_username:users /home/$var_username/.xinitrc
# Boot to runlevel 5 now, and run slim then
sed -e 's/id:3/#id:3/' -e 's/#id:5/id:5/' -e 's|x:5:respawn:/usr/bin/xdm|#x:5:respawn:/usr/bin/xdm|' -e 's|#x:5:respawn:/usr/bin/slim|x:5:respawn:/usr/bin/slim|' </etc/inittab >/etc/inittab.new
mv -f /etc/inittab.new /etc/inittab
# Add colored prompt to user and root
sed '/^PS1/c\' </etc/skel/.bashrc >/root/.bashrc
cat >> /root/.bashrc << EOF
PS1='\[\e[0;32m\]\u@\h\[\e[m\] \[\e[0;35m\]\w\[\e[m\] \[\e[m\] \[\e[0;32m\]\t -\[\e[m\] \[\e[1;31m\]\$ \[\e[m\] '
EOF
cp /root/.bashrc /home/$var_username/.bashrc
chown $var_username:users /home/$var_username/.bashrc
# How does one do that automatically ?
# Manually add user to sudoers
EDITOR="vim" visudo
# Reboot, because it's quick and I'm too lazy to learn how to start all the daemons and others.
reboot
The important part of the script to solve the problem is :
cat > /home/$var_username/.xinitrc << EOF
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
exec ck-launch-session startxfce4
thunar --daemon &
EOF
chown $var_username:users /home/$var_username/.xinitrc

SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
1/ The major number for IDE based drives is 3.
2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
- The major number is 8.
- The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
Armed with this knowledge, I su'd to root and entered:
# mknod /dev/sdc4 b 8 36
and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
# ls -ald /dev/sd*
Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
brw-rw---- 1 root disk 8, 32 date time /dev/sdc
Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

Solved!
See the lengthy response in this post:
http://bbs.archlinux.org/viewtopic.php?id=36468
I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

[Solved] Mounting Partitions from Beginners Guide

Hi everyone. I've setup Arch before, but I see that the installer has been removed. I had a question on some of the documentation from the Beginners Guide...
From the section "Prepare the storage drive" it states to setup the partitions like so:
Name Flags Part Type FS Type [Label] Size (MB)
sda1 Boot Primary Linux 15440
sda2 Primary Linux swap / Solaris 1024
sda3 Primary Linux 133000*
In the section below it ("Mount the partitions ") it explains to "mount any other separate partition" like so:
# mkdir /mnt/home
# mount /dev/sda4 /mnt/home
# mkdir /mnt/boot
# mount /dev/sda1 /mnt/boot
However, I set my partitions up just how it was above, when I put in the syntax "mount /dev/sda4 /mnt/home" I receive an error that sda4 doesn't exist. Using my best judgement I put in "mount /dev/sda3 /mnt/home" as I set my partitions exactly the way from the storage drive section (minus some storage space for sda3). I'd just like to be sure that I set this up right and not doing anything extremely wrong. For some reason, Arch won't boot after I have the system setup in virtualbox, and I'm trying to narrow down the issue.
Thanks.
Last edited by Quill (2012-09-01 04:16:22)

Trilby wrote:
It says to do that if you have any additional partitions. You do not.
Sda3 should not be mounted as home, it should be your root partition right? You should have already done
mount /dev/sda3 /mnt
You should not remount sda3 as something else (in fact I suspect it should give an error).
That partition scheme does not have a separate home parition.
Cool, thanks for the info. Yeah, sda3 is set as my root partition. It's solved.

[SOLVED]mounting cdrom and usb devices doesn't work

Hello,
i have trouble mounting my usb devices. automount doesn't work and i can't mount them manually even as a superuser. here's the output of mount command:
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
i can mount cdrom manually but i can't do the same for my usb stick and external hard drives. it always complains about the above regardless of the filesystem. my devices are working under windows and other linuxes so i know hardware is not the problem.
i'm using lxde with pcmanfm.
if you need any other files just ask.
thanks
Last edited by the gray (2009-03-16 20:15:18)

above was the error when i tried to mount any usb device with "mount -t <type> /dev/sdc /media/mountpoint". and i couldn't mount any usb device as root from console. when i tried to mount devices using pcmanfm it just popped some empty dialogs and i couldn't find any mention of "IsCallerPriviliged failed" error so i (wrongly) presumed it wasn't that. i did try some of the other fixes mentioned in the forum with no success. but adding exec ck-launch-session startkde to my .xinitrc fixed the issue
thanks again
Last edited by the gray (2009-03-16 20:17:53)

Lacie external hard drive won't mount, seems dead. Caused by 10.5.6 update?

Hi all, a couple days after I updated Leopard to 10.5.6, my Lacie external drive no longer worked with TimeMachine. So I repaired permissions and ran Repair Disk from my original 10.3 Panther disk. Not sure if that was the cause, but afterward when the drive is connected by FireWire, it makes exciting new loud buzzing and grinding noises, and then I get an alert that reads "The disk you inserted was not readable by this computer." Apple Disk Utility shows it as a Maxtor Calypso drive now with a capacity of 2TB, even though it's a 160GB (a FireWire only, Porsche model). I don't want to erase the disk and reformat it because I want the data.
Lacie customer support says the drive has suffered a "controller failure." Says Lacie, "The controller on the hard drive mechanism can not obtain the volume information on the hard drive and can not gain access. It is reading the control board information. You should be able to install a new hard drive mechanism in the enclosure and be ready to go again." Lacie CS continued to say DiskWarrior etc will not help.
Now I know that theoretically software updates shouldn't damage hardware, but I believe installing Leopard in the first place caused my lower RAM slot to fail. (That happened immediately after the upgrade.)
-So, does anyone think the 10.5.6 update could have caused this problem? Any fix ideas?
-If not, should I open the drive up and attempt to repair/replace this controller mechanism? If so, can anyone direct me to tutorials or instructions on how I could do that?
-Or, should I try putting it in the freezer overnight, as some online forums recommend as a last resort fix attempt for dead HDs?
I want the data, but not enough to pay for an expensive data recovery service.
Thank you very, very much.
scott

First off, software can not cause hardware to fail.
Lower RAM slot failure is a common issue not because of software issues, but rather because memory is unaware of bus slewing issues with energy saver power requirements. Secondly, the lower RAM slot of these machines was extremely hard to properly align the RAM right in the slot, making it easy to misplace the RAM during the installation process, thus short or damage teh slot. See my FAQ on bad RAM*:
http://www.macmaps.com/badram.html
You should be able to open the drive, and insert it inside another inexpensive hard drive case that is known to be compatible such as those by http://www.macsales.com/
Unfortunately, recently LaCie has had some hard drive interface converters which have not caught up with spec changes in the operating system, meaning their external drives sometimes need a firmware update. The only company that has been able to consistently avoid firmware updates is http://www.macsales.com/ This problem has plagued Firewire hard drives since the release of 10.3, and possibly earlier at as mentioned on my FAQ*:
http://www.macmaps.com/firewirebug2.html
If inserting the drive in another case does not solve issues, Prosoft Data Rescue, Subrosasoft Filesalvage, or Boomerang's Boomerang and a second drive at least as large as the one to be recovered can sometimes extract information from a flakey hard drive. In event that doesn't work, then data recovery specialist is the only option.
In the future always backup your data and never let there be less than two copies of your data at anytime*:
http://www.macmaps.com/backup.html
- * Links to my pages may give me compensation.

[solved] Mounting /media as tmpfs causes breakage on bootup

Similar Messages

Maybe you are looking for