Udev 057-1 - /dev/hdc permissions wrong

I upgraded to udev-057-1 and found that my DVD burners group permissions have been set to `disk' instead of `optical'
[root@64-3200 father]# pacman -Ss udev
current/udev 057-1
The userspace dev tools (udev)
extra/hwd 4.7-1
Hardware detect for Arch Linux (devfs and udev).
[root@64-3200 father]# pacman -Qs udev
local/udev 057-1
The userspace dev tools (udev)
[root@64-3200 father]# ls -l /dev/hdc
brw-rw---- 1 root disk 22, 0 2005-05-23 22:31 /dev/hdc
in my /etc/udev/rules.d/00.rules file has the following
KERNEL="hdc", NAME="hdc", GROUP="optical", SYMLINK="dvd"
KERNEL="nvidia*", GROUP="video", MODE="0666"
# For VMWare
# tty devices
KERNEL="tty[0-9]*", NAME="vc/%n", SYMLINK="%k"
# floppy devices
KERNEL="fd[0-9]*", NAME="floppy/%n" , SYMLINK="fd%n"
which i would've thought would override the group permissions, but doesnt
can someone provide the correct 00.rules file format for that entry.. or correct the udev permissions in the package
thanks

see flyspray, http://bugs.archlinux.org/?do=details&id=2691

Similar Messages

/dev/video0 and wrong permissions

Hi.
I have a usb webcam (/dev/video0, uvcvideo module)
After latest updates, /dev/video0 permissions are wrong (group root, access None instead of group Video, access RW)
Reloading uvcvideo module fixes the permissions.
This happens randomly, some times the permissions are right, other wrong, and i need to reload the module or do:
chgrp video /dev/video0
chmod 660 /dev/video0
I am in the 'video' group.
Never had this problem before.
Is this a udev problem? Kernel module problem?
Thanks.
Last edited by tritonas00 (2013-10-05 16:43:12)

I've read some forum posts that suggest that being in the video group (or audio etc.) can actually cause problems for you now. Try removing yourself from the group, log out then back in again, and see if the problem goes away.
Last edited by skottish (2013-10-05 17:44:51)

[Solved-sortof] Mounting dvd drive /dev/hdc

My dvd drive is not mounting for some reason, I thought maybe I just needed to restart and that it would mount again but no luck, this is what I get:
mount /dev/hdc /test
mount: no medium found
I put the same DvD in my cdrom/dvd drive and it mounts so i know it's not the dvd. I thought well, this is a dell shipped dvd drive so maybe it died, I'll give it a test. I slap the dvd in the drive, since it's the master cd drive it shoudl load a cd at bootup and it does, loads Fedora dvd image easily. I did upgrade something this morning, mostly gnome stuff, so I am thinking it's one of the packages assuming I don't have /dev/hdc on my computer. Is there a way to see what's going on?
Quick Edit
I did a quick edit to see what exactly was going on, I am far from a linux pro, but I do have some common sense. I took gdm / hal off my daemons list and rebooted. Now from command linue I logged into root and tried to mount the drive /dev/hdc and it worked perfectly flawless, no errors. So I am guessing this has to do with a hal problems that was caused during an update. Any further help would be much appreciated though because I don't know where to go from here.
Edit again
I solved my little "issue" apparently it was just the dvd I was trying, for some odd reason my dvd drive was refusing to auto-load the dvd movie. Yes I burned a dvd movie, I do own the original copy, I just burn a backup incase of dmg / loss. The original dvd loads fine with no mounting issues. The dvd I burned works in a dvd player, and on my secondary dvd/rw drive, I don't like watching movies on the dvd/rw drive though because of the fact that it's read capabilities is much slower. I am still puzzled on why my dvd drive doesn't like to mount / read it correctly.

mzneverdies wrote:
not sure, but in order to mount cds/dvds, I think you must use the -o loop flag
sudo mount -t iso9660 -o loop /dev/cdrom /media/cdrom
The loop flag is for mounting ISOs.

Can't mount /dev/hdc during install?

Hi,
I've inherited a Dell Precision 410 computer (PIII, perhaps 6 years old?). It currently has
an older version of RedHat installed and I'm attempting to install Arch. The Arch CD boots
and loads vmlinuz and goes through screenfulls of initialization info. It gets down
to loading the add-on modules and pauses; then it comes back and says
"Can't mount /dev/hdc -- (Empty media?)" and drops me at the "#" prompt with the
message to enter "loaddisk /dev/hdc" if I need extra modules. I attempt that and I
get the same "Can't mount hdc" message. I can enter "/arch/setup" and get the
initial menu, but since no modules are loaded my network card is not working, etc.
How can the bootup and menus work, but yet /dev/hdc (which is the CDROM itself)
not be mountable? If I boot the old Redhat, I see the link "/dev/cdrom --> /dev/hdc".
If I start Gnome and insert the Arch CD, it automounts (under /dev/hdc) and
I can browse the CD contents (including the add-ons folder) and see all the files.
I have used the same CD to install Arch on another non-Dell computer so I believe
the media is OK.
Clues as to how/why /dev/hdc is causing a problem during vmlinuz startup?
Thanks in advance,
Roggie Boone

Problem solved ... looks like it was either a defective CDROM drive or just one
that the kernel did not recognize. I salvaged a Lite-On drive from another
computer and Arch was able to mount it as /dev/hdc during the install.
Roggie

EXFAT formatted USB stick - sharing permissions wrong - Read Only - Cannot Reformat - Help please!

EXFAT formatted USB stick - sharing permissions wrong - Read Only - Cannot Reformat - Help please!
Hi.
Having various problems with a USB stick that is formatted in EX-FAT.
It was working fine for a long period.
Yesterday I lent it to a friend to put some things on it.
Now when I try and work on it, I get messages like this.
Mac OS X can’t repair the disk “Disk Name"
You can still open or copy files on the disk, but you can’t save changes to files on the disk. Back up the disk and reformat it as soon as you can.
It will also randomly eject the drive.
I have tried to reformat it multiple times, in mac and windows.
[I have never used it in windows previous to this occasion of needing to reformat].
In windows, it crashes the disk when I attempt to format with disk manager [I attempted this due to advice in an internet article].
In Mac , I cannot even try to reformat it, because for some reason the permissions on the USB stick have been set to "read only" and I cannot find any way to change them to read-write, or full permissions, or whatever is appropriate.
I have tried "erase" disk in disk utility. I know how to do a full reformat, but it simply will not allow me to do so.
All the options are greyed out.
Does anybody have any information or links they can point me to?
I've been searching around.
Thanks very much in advance for any advice received.
Running latest mountain lion , 10.8.4, and windows 7 through VMware fusion.

Start over:
select the drive > select the Partition tab > select 1 Partition
select Option > select GUID Partition Table > select OK
name it > click the Apply button > then lastly click Partition

UDev not setting correct group / permissions

Hello, I am a new user of Arch, switched from Gentoo.
I can't figure out why my devices aren't being set up properly. Here is my udev config . . .
# audio devices
dsp*:root:audio:0660
audio*:root:audio:0660
midi*:root:audio:0660
mixer*:root:audio:0660
sequencer*:root:audio:0660
sound/*:root:audio:0660
snd/*:root:audio:0660
beep:root:audio:0660
admm*:root:audio:0660
adsp*:root:audio:0660
aload*:root:audio:0660
amidi*:root:audio:0660
dmfm*:root:audio:0660
dmmidi*:root:audio:0660
sndstat:root:audio:0660
# optical devices
cdrom*:root:optical:0660
dvd:root:optical:0660
cdroms/*:root:optical:0660
cdrw:root:burning:0660
A listing of the actual devices yields this though.
[root@dogma ~]# ls /dev/dsp /dev/sound/ /dev/dvd /dev/cdrw /dev/cdroms/ -l
lrwxrwxrwx 1 root root 3 2004-12-14 22:03 /dev/cdrw -> hdd
lrwxrwxrwx 1 root root 9 2004-12-14 22:03 /dev/dsp -> sound/dsp
lrwxrwxrwx 1 root root 3 2004-12-14 22:03 /dev/dvd -> hdc
/dev/cdroms/:
total 0
lrwxrwxrwx 1 root root 6 2004-12-14 22:03 cdrom -> ../hdd
/dev/sound/:
total 0
crw-rw---- 1 root audio 14, 4 2004-12-14 22:03 audio
crw-rw---- 1 root audio 14, 9 2004-12-14 22:03 dmmidi
crw-rw---- 1 root audio 14, 3 2004-12-14 22:03 dsp
crw-rw---- 1 root audio 14, 2 2004-12-14 22:03 midi
crw-rw---- 1 root audio 14, 0 2004-12-14 22:03 mixer

rmbalfa wrote:title Arch Linux 2.6.5
root (hd0,0)
kernel /bzImage-2.6.5-udev root=/dev/discs/disc0/part3 devfs=nodevfs ro
it should be devfs=nomount - i'll assume you just typoed it... maybe... check "ps aux | grep udev" to see if udev is running....
rmbalfa wrote:I want the real file to belong to the audio group as well.
the real file does belong to the group - it's the symlink that doesn't... and as was said earlier, symlink permissions don't mean jack, because it will follow the link before checking permissions...
I think symlinks have permissions according to who created them... so if you really want the symlinks in a diff group, make a "udevd" user and add him to group audio... and run udev as that user and not root....

/dev/null permissions spontaneously become crw-------

Every so often, once in a couple of weeks or so, /dev/null spontaneously becomes unreadable and unwriteable for group and others. This happens on my laptop, on VMs and on servers. Only on Archlinux installs. It doesn't happen often enough for me to track down the cause.
Has anyone else encountered this?
Could it be a udev issue?

Yep, encountered it myself. Right now you can either symlink /bin/sh to /bin/zsh (NOT recommended), or use emacs-git from the AUR (fixed in 25.0.50).
http://lists.gnu.org/archive/html/bug-g … 00980.html
Last edited by Alad (2015-04-10 15:27:38)

Mail won't open, reports permissions wrong

Mail suddenly would not open. The operating system warning screen that comes up states that the mail folder does not have read and write permissions for user (user on this computer is only one person). File info on the mail folder in the library for this user reports that this user has read/write permissions and the disk utility repair permissions program was also run; it reported no problem and no repairs necessary.
So effectively we have lost the entire mailbox and now can't open the program at all. Any suggestions?

I had the same issue (I keep my Mail folder on a secondary HD in my MacBook since my SSD is small), and found that it requires a symlink rather than an alias to work in 10.8. A symlink is very similar to an alias but is created using the 'ln' command in the Terminal, rather than by the Finder. The command below should do what you need:
ln -s '/Users/cutterd/Dropbox/Mail/' '/Users/cutterd/Library/Mail'
And yes, it appears to be a bug (at least in the sense that the error message makes no sense), but it is one that is easily worked around for now.

[Solved] Can't boot; udev not creating /dev/disk/

After doing a system upgrade I can no longer boot. I get the message that /dev/disk/by-uuid/{device id} cannot be found. (There is no /dev/disk/ path at all). I tried changing the grub boot path to dev/sdaX, but /dev/sda?? are also not created.
I have a Fedora rescue CD lying around, and if I boot from that I can see and mount the boot device (/dev/disk/by-uuid/ is created), so I don't think it's a hardware issue.
Last edited by rhodie (2012-03-20 18:26:53)

Booting from a NetInstaller CD worked.
A couple of notes in case others have the same issue.
I had to turn on networking before I could run pacman. I turned on networking by issuing these commands (not sure of the proper order for them or if they're all necessary, but it worked):
/etc/rc.d/networking start
ip link set eth0 up
dhcpd
I then ran through the steps listed at https://wiki.archlinux.org/index.php/Pa … nger_boot. , but I got errors on "mkinitcpio -p linux" so I added "pacman -S linux," which seemed to include mkinitcpio, but I ran mkinitcpio again afterwards just to be sure and got no errors.
Last edited by rhodie (2012-03-20 16:09:20)

Udev rules and group / permission errors [solved] [outdated]

Latest udev is a miracle to me. It ignores every group ore permission settings. Anyone else having same experiences?
Last edited by Moo-Crumpus (2008-09-29 05:17:40)

Let's assume that you have two files with udev rules. The basic udev.rules and 00.udev.rules (with custom rules).
Udev first reads all rules from 00 file and then rules from the basic file.
This means that if you have a custom rule for a given device you should copy all rules that apply to it from the basic file to the 00 file (not only lines with GROUP). This is because with OPTIONS="last_rule" udev will stop processing rules for this device.
All rules are read and then applied in the order from the top to bottom except SUBSYTEM which is applied as the last rule (kind of held in a buffer). This is the reason why my cd burner /dev/hdc had permissions for disk group and not optical.
This is my 00.udev.rules (it still needs some cosmetic changes but it works and of course I don't have all the devices):
SUBSYSTEM="video4linux", GROUP="users"
SUBSYSTEM="sound", GROUP="users"
SUBSYSTEM="printer", GROUP="users"
SUBSYSTEM="block", GROUP="disk"
BUS="ide", KERNEL="hd[a-z]", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2} %c{3} %c{4} %c{5} %c{6}"
BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-devfs.sh %k %b %n", SYMLINK="%c{1} %c{2}"
BUS="ide", KERNEL="hdc", SYSFS{removable}="1", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom*", NAME="%k", GROUP="users", SYMLINK="nagrywarka dvd cdrw", OPTIONS="last_rule"
BUS="ide", KERNEL="hd[a-z]", SYSFS{removable}="1", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT="cdrom*", NAME="%k", GROUP="users", OPTIONS="last_rule"
BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-floppy.sh %k", RESULT="floppy", NAME{all_partitions}="%k", GROUP="users", OPTIONS="last_rule"
BUS="scsi", KERNEL="sr[0-9]*", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2} %c{3} %c{4} %c{5} %c{6}"
BUS="scsi", KERNEL="scd[0-9]*", PROGRAM="/etc/udev/cdsymlinks.sh %k", SYMLINK="%c{1} %c{2} %c{3} %c{4} %c{5} %c{6}"
BUS="scsi", KERNEL="sr[0-9]*", SYSFS{type}="5", NAME="scd%n", GROUP="users", OPTIONS="last_rule"
BUS="scsi", KERNEL="sg[0-9]*", SYSFS{type}="5", NAME="%k", GROUP="users", OPTIONS="last_rule"
KERNEL="fd[0-9]*", NAME="fd%n", GROUP="users", SYMLINK="floppy/%n fd%nu1440 fd%nu720 fd%nh1200 fd%nu360", OPTIONS="last_rule"
BUS="usb", SYSFS{serial}="CN16J1Q3HWSX", KERNEL="lp[0-9]*", NAME="usb/%k", GROUP="users", SYMLINK="drukarka_hp_845c drukarka", OPTIONS="last_rule"
BUS="usb", KERNEL="sd*", PROGRAM="/etc/udev/usb-storage.sh %k", RESULT="1", NAME="%k", GROUP="users", OPTIONS="last_rule"
KERNEL="rtc", NAME="misc/%k", SYMLINK="%k", GROUP="users", MODE="0664", OPTIONS="last_rule"
KERNEL="agpgart", NAME="misc/%k", SYMLINK="%k" GROUP="users", OPTIONS="last_rule"
KERNEL="nvidia*", GROUP="users", OPTIONS="last_rule"
KERNEL="fb[0-9]*", NAME="fb/%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="card[0-9]*", NAME="dri/%k", GROUP="users", OPTIONS="last_rule"
KERNEL="3dfx*", NAME="%k", GROUP="users", OPTIONS="last_rule"
KERNEL="dvb*", PROGRAM="/etc/udev/dvb.sh %k", NAME="%c", GROUP="users", OPTIONS="last_rule"
KERNEL="video[0-9]*", NAME="v4l/video%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="radio[0-9]*", NAME="v4l/radio%n", GROUP="users", SYMLINK="radio%e", OPTIONS="last_rule"
KERNEL="vbi[0-9]*", NAME="v4l/vbi%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="vtx[0-9]*", NAME="v4l/vtx%n", GROUP="users", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="controlC[0-9]*", NAME="snd/%k", OPTIONS="last_rule"
KERNEL="hw[CD0-9]*", NAME="snd/%k", OPTIONS="last_rule"
KERNEL="pcm[CD0-9cp]*", NAME="snd/%k", OPTIONS="last_rule"
KERNEL="midi[CD0-9]*", NAME="snd/%k", OPTIONS="last_rule"
KERNEL="timer", NAME="snd/%k", OPTIONS="last_rule"
KERNEL="seq", NAME="snd/%k", OPTIONS="last_rule"
KERNEL="audio*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="dmmidi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="admmidi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="dsp*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="adsp*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="midi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="amidi*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="mixer*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="sequencer*", NAME="sound/%k", SYMLINK="%k", OPTIONS="last_rule"
KERNEL="pktcdvd", NAME="pktcdvd/control", GROUP="users", MODE="0660", OPTIONS="last_rule"
KERNEL="pktcdvd[0-9]*", NAME="pktcdvd/pktcdvd%n", GROUP="users", MODE="0660", OPTIONS="last_rule"
The problem with /dev/hdc was that first udev (version 057) was reading a rule from my 00 file (BUS="ide", KERNEL="hdc"...) with GROUP=users. Then it was reading SUBSYSTEM="block", GROUP="disk" rule from the basic file (but it wasn't executed at that time). And then it was reading BUS="ide", KERNEL="hd[a-z]", SYSFS{removable}="1"... with GROUP=optical. Then it was executing SUBSYTEM rule (hdc is a block device). That's why only disk group had an access to /dev/hdc (with OPTIONS="last_rule" in the basic file in the GROUP="optical" line it would ignore SUBSYSTEM rule).
There are also other rules that you should add (IMO) to your custom rules if you are changing something. In my case it's for example BUS="ide", KERNEL="hd[a-z]", PROGRAM="/etc/udev/cdsymlinks.sh %k"... which creates symlinks for cd drives. This rule must be above other rules (the number of the symlinks is now unlimited - previously it was 5 IIRC).
So now the rules are mixed together in the lexical order (except SUBSYTEM rules which are executed at the end) unless OPTIONS="last_rule" is used or second (and other) rule has a NAME filed (only one rule for a given device can have NAME filed. Every other rule for the same device with NAME field is ignored IIRC). It also means you can now split rules for a device into several rules - only one of them can have NAME filed and the last should have OPTIONS="last_rule".
Since in your case you have custom rules only for a well defined usb devices (not /dev/sd*) IMO it should work as you think (only add OPTIONS="last_rule").
I hope it's now perfectly clear 8)

Mounting drives on a udev+hal+gnome-volume-manager setup

Hi,
I set up Arch Linux on a friends computer. The setup seems to work, for example gnome-cd is started when one inserts an Audio CD. However, everything that involves mounting does not work. The error message given by gnome-volume-manager is
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
or too many mounted file systems
* /bin/mount has sid set, 755, owner and file group are root
* udev is set up correctly, so /dev/hdc for example does have write rights for the group disk, and the user is member of that group.
What could be wrong?

The problem was mainly about mounting, and not about /dev/sda or /dev/hdc. We found the solution:
The "mount" binary in Arch's current is confused by the entry "managed" that hal puts in /etc/fstab. You can correct this by
a) Adding a policy file in /usr/share/hal/fdi/95userpolicy named, for example, local.fdi that hinders hal from doing so:
<?xml version="1.0" encoding="ISO-8859-1"?> 
<deviceinfo version="0.2">

<device>
<match key="info.udi" string="/org/freedesktop/Hal/devices/computer">
<merge key="storage.policy.default.managed_keyword.primary" type="string">user</merge>
</match>
</device>
</deviceinfo>
Then restart hal by typing
/etc/rc.d/hal restart
as root
b) Patching "mount" as described in Arch Linux bug #1930.[/code]

[SOLVED]udev doesn't execute my custom rule

Here is my device info:
XSign rules.d # udevadm info -a -n /dev/sdb1
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1':
KERNEL=="sdb1"
SUBSYSTEM=="block"
DRIVER==""
ATTR{ro}=="0"
ATTR{size}=="15685569"
ATTR{stat}==" 240 1120 1906 320 0 0 0 0 0 320 320"
ATTR{partition}=="1"
ATTR{start}=="63"
ATTR{discard_alignment}=="0"
ATTR{alignment_offset}=="0"
ATTR{inflight}==" 0 0"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb':
KERNELS=="sdb"
SUBSYSTEMS=="block"
DRIVERS==""
ATTRS{ro}=="0"
ATTRS{size}=="15685632"
ATTRS{stat}==" 255 1123 2050 330 0 0 0 0 0 330 330"
ATTRS{range}=="16"
ATTRS{discard_alignment}=="0"
ATTRS{events}=="media_change"
ATTRS{ext_range}=="256"
ATTRS{events_poll_msecs}=="-1"
ATTRS{alignment_offset}=="0"
ATTRS{inflight}==" 0 0"
ATTRS{removable}=="1"
ATTRS{capability}=="51"
ATTRS{events_async}==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0':
KERNELS=="8:0:0:0"
SUBSYSTEMS=="scsi"
DRIVERS=="sd"
ATTRS{rev}=="1.00"
ATTRS{type}=="0"
ATTRS{scsi_level}=="0"
ATTRS{model}=="USB SD Reader "
ATTRS{state}=="running"
ATTRS{queue_type}=="none"
ATTRS{iodone_cnt}=="0x1dd"
ATTRS{iorequest_cnt}=="0x1dd"
ATTRS{timeout}=="30"
ATTRS{evt_media_change}=="0"
ATTRS{max_sectors}=="240"
ATTRS{ioerr_cnt}=="0x2"
ATTRS{queue_depth}=="1"
ATTRS{vendor}=="Generic "
ATTRS{device_blocked}=="0"
ATTRS{iocounterbits}=="32"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0':
KERNELS=="target8:0:0"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8':
KERNELS=="host8"
SUBSYSTEMS=="scsi"
DRIVERS==""
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0':
KERNELS=="1-1.1:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="usb-storage"
ATTRS{bInterfaceClass}=="08"
ATTRS{bInterfaceSubClass}=="06"
ATTRS{bInterfaceProtocol}=="50"
ATTRS{bNumEndpoints}=="02"
ATTRS{supports_autosuspend}=="1"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1':
KERNELS=="1-1.1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="1.1"
ATTRS{idVendor}=="090c"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="8"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="500mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="12345678901234567890"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="1264"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Silicon Motion, Inc."
ATTRS{removable}=="removable"
ATTRS{idProduct}=="6200"
ATTRS{bDeviceClass}=="00"
ATTRS{product}=="Generic USB2.0 card "
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="1"
ATTRS{idVendor}=="8087"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="6"
ATTRS{bcdDevice}=="0000"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="130"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="fixed"
ATTRS{idProduct}=="0020"
ATTRS{bDeviceClass}=="09"
looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}==" 0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="3"
ATTRS{bcdDevice}=="0308"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:1a.0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="26"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.8.3-2-ARCH ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:1a.0':
KERNELS=="0000:00:1a.0"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="23"
ATTRS{subsystem_vendor}=="0x17aa"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="ff"
ATTRS{device}=="0x3b3c"
ATTRS{uframe_periodic_max}=="100"
ATTRS{enable}=="1"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-7"
ATTRS{vendor}=="0x8086"
ATTRS{subsystem_device}=="0x2163"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
and rule:
XSign rules.d # cat 100-usb.rules
KERNEL=="sd*", SUBSYSTEMS=="scsi", ATTRS{model}=="USB SD Reader", SYMLINK+="test_%n", OPTIONS+="all_partitions"
and the test:
XSign rules.d # udevadm test /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1
calling: test
version 198
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
=== trie on-disk ===
tool version: 198
file size: 5544030 bytes
header size 80 bytes
strings 1242254 bytes
nodes 4301696 bytes
load module index
Skipping overridden file: /usr/lib/udev/rules.d/80-net-name-slot.rules.
read rules file: /etc/udev/rules.d/01-razer-udev.rules
read rules file: /usr/lib/udev/rules.d/10-dm.rules
read rules file: /usr/lib/udev/rules.d/10-vboxdrv.rules
read rules file: /etc/udev/rules.d/100-usb.rules
read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
read rules file: /usr/lib/udev/rules.d/60-fprint-autosuspend.rules
read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
read rules file: /usr/lib/udev/rules.d/60-rfkill.rules
read rules file: /usr/lib/udev/rules.d/60-vboxguest.rules
read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
IMPORT found builtin 'usb_id --export %p', replacing /usr/lib/udev/rules.d/69-cd-sensors.rules:85
read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
read rules file: /usr/lib/udev/rules.d/70-infrared.rules
read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
read rules file: /usr/lib/udev/rules.d/71-seat.rules
read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
read rules file: /usr/lib/udev/rules.d/75-net-description.rules
read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
read rules file: /usr/lib/udev/rules.d/80-drivers.rules
read rules file: /etc/udev/rules.d/80-net-name-slot.rules
read rules file: /usr/lib/udev/rules.d/80-udisks.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
read rules file: /etc/udev/rules.d/91-fingerprint-gui-upek.rules
read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
read rules file: /usr/lib/udev/rules.d/95-keyboard-force-release.rules
read rules file: /usr/lib/udev/rules.d/95-keymap.rules
read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
read rules file: /usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules
read rules file: /usr/lib/udev/rules.d/99-laptop-mode.rules
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
rules contain 49152 bytes tokens (4096 * 12 bytes), 20074 bytes strings
3343 strings (40625 bytes), 2291 de-duplicated (21604 bytes), 1053 trie nodes used
GROUP 6 /usr/lib/udev/rules.d/50-udev-default.rules:40
LINK 'disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' /usr/lib/udev/rules.d/60-persistent-storage.rules:43
LINK 'disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' /usr/lib/udev/rules.d/60-persistent-storage.rules:57
IMPORT builtin 'blkid' /usr/lib/udev/rules.d/60-persistent-storage.rules:70
probe /dev/sdb1 raid offset=0
LINK 'disk/by-uuid/1DFC8855338F968C' /usr/lib/udev/rules.d/60-persistent-storage.rules:76
LINK 'disk/by-label/Hacksign\x27s\x20Documents\x20Disk' /usr/lib/udev/rules.d/60-persistent-storage.rules:77
IMPORT 'udisks-part-id /dev/sdb1' /usr/lib/udev/rules.d/80-udisks.rules:84
starting 'udisks-part-id /dev/sdb1'
'udisks-part-id /dev/sdb1' [2444] exit with return code 0
handling device node '/dev/sdb1', devnum=b8:17, mode=0660, uid=0, gid=6
preserve permissions /dev/sdb1, 060660, uid=0, gid=6
preserve already existing symlink '/dev/block/8:17' to '../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-id\x2fusb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1'
creating link '/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-label\x2fHacksign\x5cx27s\x5cx20Documents\x5cx20Disk'
creating link '/dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-path\x2fpci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1'
creating link '/dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1' to '../../sdb1'
found 'b8:17' claiming '/run/udev/links/\x2fdisk\x2fby-uuid\x2f1DFC8855338F968C'
creating link '/dev/disk/by-uuid/1DFC8855338F968C' to '/dev/sdb1'
preserve already existing symlink '/dev/disk/by-uuid/1DFC8855338F968C' to '../../sdb1'
ACTION=add
DEVLINKS=/dev/disk/by-id/usb-Generic_USB_SD_Reader_12345678901234567890-0:0-part1 /dev/disk/by-label/Hacksign\x27s\x20Documents\x20Disk /dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/1DFC8855338F968C
DEVNAME=/dev/sdb1
DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb/sdb1
DEVTYPE=partition
ID_BUS=usb
ID_DRIVE_FLASH_SD=1
ID_FS_LABEL=Hacksign_s_Documents_Disk
ID_FS_LABEL_ENC=Hacksign\x27s\x20Documents\x20Disk
ID_FS_TYPE=ntfs
ID_FS_USAGE=filesystem
ID_FS_UUID=1DFC8855338F968C
ID_FS_UUID_ENC=1DFC8855338F968C
ID_INSTANCE=0:0
ID_MODEL=USB_SD_Reader
ID_MODEL_ENC=USB\x20\x20SD\x20Reader\x20\x20
ID_MODEL_ID=6200
ID_PART_ENTRY_DISK=8:16
ID_PART_ENTRY_NUMBER=1
ID_PART_ENTRY_OFFSET=63
ID_PART_ENTRY_SCHEME=dos
ID_PART_ENTRY_SIZE=15685569
ID_PART_ENTRY_TYPE=0x87
ID_PART_TABLE_TYPE=dos
ID_PATH=pci-0000:00:1a.0-usb-0:1.1:1.0-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_1a_0-usb-0_1_1_1_0-scsi-0_0_0_0
ID_REVISION=1.00
ID_SERIAL=Generic_USB_SD_Reader_12345678901234567890-0:0
ID_SERIAL_SHORT=12345678901234567890
ID_TYPE=disk
ID_USB_DRIVER=usb-storage
ID_USB_INTERFACES=:080650:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=Generic
ID_VENDOR_ENC=Generic\x20
ID_VENDOR_ID=090c
MAJOR=8
MINOR=17
SUBSYSTEM=block
TAGS=:systemd:
UDISKS_PARTITION=1
UDISKS_PARTITION_ALIGNMENT_OFFSET=0
UDISKS_PARTITION_NUMBER=1
UDISKS_PARTITION_OFFSET=32256
UDISKS_PARTITION_SCHEME=mbr
UDISKS_PARTITION_SIZE=8031011328
UDISKS_PARTITION_SLAVE=/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/host8/target8:0:0/8:0:0:0/block/sdb
UDISKS_PARTITION_TYPE=0x87
UDISKS_PRESENTATION_NOPOLICY=0
USEC_INITIALIZED=7735553
It seems that 100-usb.rules doesn't be executed~
Am I anywhere wrong ?
Last edited by Hacksign (2013-04-09 02:15:13)

Pasted another example of my usb sd card reader.
there is no test_X symbol link in /dev/ directory after i un-pluged sd card reader and re-pluged it in on my computer
oh, I use systemd of course:
XSign rules.d # cat /boot/grub/menu.lst
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/root resume=/dev/sda7 ro vga=0x361 init=/usr/lib/systemd/systemd quiet
initrd /boot/kernel26.img
Hacksign wrote:
brebs wrote:You're mixing the hierarchy levels (i.e. subsystems) - can't do that. See working example.
no, I dont think I mixed te hierarchy level.
SUBSYSTEM=="input" matched '/devices/platform/i8042/serio1/serio2/input/input24/mouse2'
and
SUBSYSTEMS=="usb", ATTR{idVendor}=="1532",
matched its parent
and I'm so sorry that I pasted a wrong device tree...
sorry

[SOLVED] udev rule no longer working

I have a udev rule set up to automatically mount an ext4 filesystem when I plug a certain thumb drive in. It was working fine until yesterday (probably due to updates). Here is the rule, in file /etc/udev/rules.d/99-gfk.rules:
KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", SYMLINK+="gfshare"
ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mkdir /media/gfshare"
ACTION=="add", KERNEL=="sd?2", SUBSYSTEM=="block", ATTRS{idVendor}=="0930", ATTRS{idProduct}=="6545", ATTRS{serial}=="1C6F654E4041ED601910053F", RUN+="/bin/mount -t ext4 -o ro,nosuid,nodev,noexec,noatime /dev/gfshare /media/gfshare"
The symlink and the mkdir command are both working fine, but the mount command is not being run for some reason. If I manually run the mount command it works fine. Some possibly helpful output:
# pacman -Qo $(which udevadm)
/usr/bin/udevadm is owned by systemd 212-1
# dmesg |tail -16
[26458.120628] usb 7-1.3: new high-speed USB device number 7 using ehci-pci
[26458.223059] usb-storage 7-1.3:1.0: USB Mass Storage device detected
[26458.223825] scsi10 : usb-storage 7-1.3:1.0
[26459.311607] scsi 10:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 4
[26460.834081] sd 10:0:0:0: [sdd] 15240576 512-byte logical blocks: (7.80 GB/7.26 GiB)
[26460.834931] sd 10:0:0:0: [sdd] Write Protect is off
[26460.834935] sd 10:0:0:0: [sdd] Mode Sense: 23 00 00 00
[26460.835617] sd 10:0:0:0: [sdd] No Caching mode page found
[26460.835621] sd 10:0:0:0: [sdd] Assuming drive cache: write through
[26460.839455] sd 10:0:0:0: [sdd] No Caching mode page found
[26460.839460] sd 10:0:0:0: [sdd] Assuming drive cache: write through
[26460.860579] sdd: sdd1 sdd2
[26460.867111] sd 10:0:0:0: [sdd] No Caching mode page found
[26460.867115] sd 10:0:0:0: [sdd] Assuming drive cache: write through
[26460.867118] sd 10:0:0:0: [sdd] Attached SCSI removable disk
[26461.041982] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: (null)
# udevadm test /sys/bus/usb/devices/7-1.3
calling: test
version 212
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
load module index
timestamp of '/etc/systemd/network' changed
timestamp of '/usr/lib/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context
timestamp of '/etc/udev/rules.d' changed
Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
read rules file: /usr/lib/udev/rules.d/10-dm.rules
read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
read rules file: /etc/udev/rules.d/12-android.rules
read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
read rules file: /usr/lib/udev/rules.d/50-firmware.rules
read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
read rules file: /usr/lib/udev/rules.d/51-android.rules
read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
read rules file: /usr/lib/udev/rules.d/60-drm.rules
read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules
read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
read rules file: /usr/lib/udev/rules.d/70-infrared.rules
read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
read rules file: /usr/lib/udev/rules.d/71-seat.rules
read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
read rules file: /usr/lib/udev/rules.d/75-net-description.rules
read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
read rules file: /usr/lib/udev/rules.d/80-drivers.rules
read rules file: /etc/udev/rules.d/80-net-setup-link.rules
read rules file: /usr/lib/udev/rules.d/80-udisks.rules
read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
read rules file: /etc/udev/rules.d/99-gfk.rules
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
read rules file: /usr/lib/udev/rules.d/kino.rules
rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
IMPORT builtin 'usb_id' /usr/lib/udev/rules.d/50-udev-default.rules:9
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:9
MODE 0664 /usr/lib/udev/rules.d/50-udev-default.rules:37
GROUP 1002 /usr/lib/udev/rules.d/51-android.rules:387
MODE 0660 /usr/lib/udev/rules.d/51-android.rules:387
RUN '/usr/share/virtualbox/VBoxCreateUSBNode.sh $major $minor $attr{bDeviceClass} vboxusers' /usr/lib/udev/rules.d/60-vboxdrv.rules:6
PROGRAM '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' /usr/lib/udev/rules.d/69-libmtp.rules:1204
starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'
'/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7'(out) '0'
'/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3 7 7' [24644] exit with return code 0
IMPORT builtin 'path_id' /usr/lib/udev/rules.d/71-seat.rules:43
RUN 'uaccess' /usr/lib/udev/rules.d/73-seat-late.rules:15
handling device node '/dev/bus/usb/007/007', devnum=c189:774, mode=0660, uid=0, gid=1002
preserve permissions /dev/bus/usb/007/007, 020660, uid=0, gid=1002
preserve already existing symlink '/dev/char/189:774' to '../bus/usb/007/007'
ACTION=add
BUSNUM=007
DEVNAME=/dev/bus/usb/007/007
DEVNUM=007
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3
DEVTYPE=usb_device
DRIVER=usb
ID_BUS=usb
ID_DRIVE_THUMB=1
ID_FOR_SEAT=usb-pci-0000_00_1a_7-usb-0_1_3
ID_MODEL=DataTraveler_2.0
ID_MODEL_ENC=DataTraveler\x202.0
ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
ID_MODEL_ID=6545
ID_PATH=pci-0000:00:1a.7-usb-0:1.3
ID_PATH_TAG=pci-0000_00_1a_7-usb-0_1_3
ID_REVISION=0100
ID_SERIAL=Kingston_DataTraveler_2.0_1C6F654E4041ED601910053F
ID_SERIAL_SHORT=1C6F654E4041ED601910053F
ID_USB_INTERFACES=:080650:
ID_VENDOR=Kingston
ID_VENDOR_ENC=Kingston
ID_VENDOR_FROM_DATABASE=Toshiba Corp.
ID_VENDOR_ID=0930
MAJOR=189
MINOR=774
PRODUCT=930/6545/100
SUBSYSTEM=usb
TAGS=:seat:uaccess:
TYPE=0/0/0
USEC_INITIALIZED=26452326568
adb_user=yes
run: '/usr/share/virtualbox/VBoxCreateUSBNode.sh 189 774 00 vboxusers'
run: 'uaccess'
unload module index
Unloaded link configuration context
# udevadm test /sys/bus/usb/devices/7-1.3:1.0
calling: test
version 212
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
load module index
timestamp of '/etc/systemd/network' changed
timestamp of '/usr/lib/systemd/network' changed
Parsed configuration file /usr/lib/systemd/network/99-default.link
Created link configuration context
timestamp of '/etc/udev/rules.d' changed
Skipping overridden file: /usr/lib/udev/rules.d/80-net-setup-link.rules.
read rules file: /usr/lib/udev/rules.d/10-dm.rules
read rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
read rules file: /etc/udev/rules.d/12-android.rules
read rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
read rules file: /usr/lib/udev/rules.d/40-hpet-permissions.rules
read rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
read rules file: /usr/lib/udev/rules.d/42-usb-hid-pm.rules
read rules file: /usr/lib/udev/rules.d/50-firmware.rules
read rules file: /usr/lib/udev/rules.d/50-udev-default.rules
read rules file: /usr/lib/udev/rules.d/51-android.rules
read rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
read rules file: /usr/lib/udev/rules.d/60-drm.rules
read rules file: /usr/lib/udev/rules.d/60-keyboard.rules
read rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-serial.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
read rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
read rules file: /usr/lib/udev/rules.d/60-vboxdrv.rules
read rules file: /usr/lib/udev/rules.d/61-accelerometer.rules
read rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
read rules file: /usr/lib/udev/rules.d/64-btrfs.rules
read rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
read rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
read rules file: /usr/lib/udev/rules.d/69-dm-lvm-metad.rules
read rules file: /usr/lib/udev/rules.d/69-libmtp.rules
read rules file: /usr/lib/udev/rules.d/70-infrared.rules
read rules file: /usr/lib/udev/rules.d/70-power-switch.rules
read rules file: /usr/lib/udev/rules.d/70-uaccess.rules
read rules file: /usr/lib/udev/rules.d/71-seat.rules
read rules file: /usr/lib/udev/rules.d/73-seat-late.rules
read rules file: /usr/lib/udev/rules.d/75-net-description.rules
read rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
read rules file: /usr/lib/udev/rules.d/75-tty-description.rules
read rules file: /usr/lib/udev/rules.d/78-sound-card.rules
read rules file: /usr/lib/udev/rules.d/80-drivers.rules
read rules file: /etc/udev/rules.d/80-net-setup-link.rules
read rules file: /usr/lib/udev/rules.d/80-udisks.rules
read rules file: /usr/lib/udev/rules.d/80-udisks2.rules
read rules file: /usr/lib/udev/rules.d/85-usbmuxd.rules
read rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
read rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
read rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
read rules file: /usr/lib/udev/rules.d/95-udev-late.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules
read rules file: /usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules
read rules file: /usr/lib/udev/rules.d/95-upower-csr.rules
read rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
read rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
read rules file: /etc/udev/rules.d/99-gfk.rules
read rules file: /usr/lib/udev/rules.d/99-systemd.rules
read rules file: /usr/lib/udev/rules.d/kino.rules
rules contain 98304 bytes tokens (8192 * 12 bytes), 22360 bytes strings
10092 strings (88570 bytes), 8317 de-duplicated (67986 bytes), 1776 trie nodes used
IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/50-udev-default.rules:11
RUN 'kmod load $env{MODALIAS}' /usr/lib/udev/rules.d/80-drivers.rules:5
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb7/7-1/7-1.3/7-1.3:1.0
DEVTYPE=usb_interface
DRIVER=usb-storage
ID_MODEL_FROM_DATABASE=Kingston DataTraveler 102 Flash Drive / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
ID_VENDOR_FROM_DATABASE=Toshiba Corp.
INTERFACE=8/6/80
MODALIAS=usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00
PRODUCT=930/6545/100
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=452326811
run: 'kmod load usb:v0930p6545d0100dc00dsc00dp00ic08isc06ip50in00'
unload module index
Unloaded link configuration context
Last edited by bentglasstube (2014-04-03 20:51:36)

I see. That is somewhat aggravating but I will find another way to achieve what I wanted I suppose.
Thank you. Should I mark this is solved or unsolvable or something? Sorry, I'm new to posting on these forums.
Edit: I was able to achieve what I wanted with udevil as recommended by the wiki.
Last edited by bentglasstube (2014-04-03 20:55:45)

OL5.11 device null's permissions

Fresh OL5.11 installation, updated from Oracle's Public Yum. [required as as OL6 and OL7 do not support the older Mellanox Cougar HCA card in the servers]
After boot, /dev/null permissions are incorrectly set:
crw-rw---- 1 root root 1, 3 Jan 21 2015 /dev/null
udev rules file seems correct:
[root@xxxx ~]# grep null /etc/udev/rules.d/50-udev.rules
KERNEL=="null",                 MODE="0666", OPTIONS="last_rule"
KERNEL=="null",                 SYMLINK+="XOR"
And rule is executed correctly according to this test:
[root@xxxx ~]# udevtest /class/mem/null
main: looking at device '/devices/virtual/mem/null' from subsystem 'mem'
udev_rules_get_name: no node name set, will use kernel name 'null'
udev_db_get_device: no db file to read /dev/.udev/db/devices@virtual@mem@null: No such file or directory
udev_node_add: creating device node '/dev/null', major = '1', minor = '3', mode = '0666', uid = '0', gid = '0'
So it would seem that something resets the permissions afterwards. But what and where?
The only "non-standard" service that runs, that a vanilla OL5.11 will not have, is openibd (Infiniband service, renamed rdma on later kernel versions). However it should not touch /dev/null. i have a couple of OL5.7 and OL5.4 servers too with openibd enabled, but without the permissions issue around /dev/null. That said, there are a number of changes I spotted between OL5.7 and OL5.11 ito service startup with the openibd service. [btw, the Infiniband service loads fine and IPoIB works, and in bonded and connected modes too, on these OL5.11 servers]
Searching via google turned up a bunch of related but mostly useless info, some dating back to 2007. No, I do not want to hack this via rc.local. Yes, I do want to know where and why it is caused, and fixed the root problem.
RHEL5 has a support note logged for this exact issue - which contents are only visible to RHN users. Did not find a similar note on Oracle's My Support.
Any ideas, comments and suggestions on how to troubleshoot and fix this, will be much appreciated.

The following is the output of a default system installation from the OL 5.11 x64 iso image in VirtualBox.
# lsb_release -d
Description:    Enterprise Linux Enterprise Linux Server release 5.11 (Carthage)
# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jan 21 2015 /dev/null
/dev/null looks fine.
The /dev device tree is populated by udev at every system restart. The procedure that creates /dev/null is /sbin/start_udev script which reads the content of /etc/udev/makedev.d/50-udev.nodes, which contains "null".
Perhaps the following can help to determine whether the problem is caused by udev:
# rm -f /dev/null
# sh -x /sbin/start_udev
# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 Jan 21 21:45 /dev/null
The command that gets executed is:
/sbin/MAKEDEV -x /dev/null
If your /dev/null looks fine after that, than udev is most likely not the problem. If it does not, do you have any other udev.rules file that may overwrite 50-udev.rules. Can you check all udev rules?
# grep "null" /etc/udev/rules.d/*
/etc/udev/rules.d/50-udev.rules:KERNEL=="null",            MODE="0666", OPTIONS="last_rule"
/etc/udev/rules.d/50-udev.rules:KERNEL=="null",            SYMLINK+="XOR"
If it is not udev, I have no idea. But perhaps you can spot the problem by adding "set -vx" to /etc/rc, restart and watch the screen.

The switch to udev

Hi,
Will there be a new release of Arch (.8) to handle the switch to udev? Or maybe a pacman-accessible program to make all the changes? I realize that there is a wiki page about it but a lot of people won't be able to implement the change properly.
Oh yeah, how close is it to happening??
Jim

leeghoofd wrote:The program fstab-sync added a line for the dvd-burner automatic
$ pacman -Qo /usr/sbin/fstab-sync
/usr/sbin/fstab-sync is owned by hal 0.5.2-3
That's hal working for you David, not udev - very handy alright.
dibblethewrecker wrote:My old distro used /dev/hda - and cos it was old and not bleeding edge I assumed that was the devfs way but it seems not and the /dev/discs is actually the devs fs way and i now need to use all /dev/hd* stuff with udev - is that right?
Before udev, before devfs, there was static dev, although nobody called it that back then - it was (and still is) the /dev directory - here's a small excerpt from the one on my Debian server:
$ ls /dev/hd*
/dev/hda /dev/hda2 /dev/hdb11 /dev/hdb4 /dev/hdc14 /dev/hdc7 /dev/hdd17 /dev/hde /dev/hde2 /dev/hdf11 /dev/hdf4 /dev/hdg14 /dev/hdg7 /dev/hdh17
/dev/hda1 /dev/hda20 /dev/hdb12 /dev/hdb5 /dev/hdc15 /dev/hdc8 /dev/hdd18 /dev/hde1 /dev/hde20 /dev/hdf12 /dev/hdf5 /dev/hdg15 /dev/hdg8 /dev/hdh18
/dev/hda10 /dev/hda3 /dev/hdb13 /dev/hdb6 /dev/hdc16 /dev/hdc9 /dev/hdd19 /dev/hde10 /dev/hde3 /dev/hdf13 /dev/hdf6 /dev/hdg16 /dev/hdg9 /dev/hdh19
/dev/hda11 /dev/hda4 /dev/hdb14 /dev/hdb7 /dev/hdc17 /dev/hdd /dev/hdd2 /dev/hde11 /dev/hde4 /dev/hdf14 /dev/hdf7 /dev/hdg17 /dev/hdh /dev/hdh2
/dev/hda12 /dev/hda5 /dev/hdb15 /dev/hdb8 /dev/hdc18 /dev/hdd1 /dev/hdd20 /dev/hde12 /dev/hde5 /dev/hdf15 /dev/hdf8 /dev/hdg18 /dev/hdh1 /dev/hdh20
/dev/hda13 /dev/hda6 /dev/hdb16 /dev/hdb9 /dev/hdc19 /dev/hdd10 /dev/hdd3 /dev/hde13 /dev/hde6 /dev/hdf16 /dev/hdf9 /dev/hdg19 /dev/hdh10 /dev/hdh3
/dev/hda14 /dev/hda7 /dev/hdb17 /dev/hdc /dev/hdc2 /dev/hdd11 /dev/hdd4 /dev/hde14 /dev/hde7 /dev/hdf17 /dev/hdg /dev/hdg2 /dev/hdh11 /dev/hdh4
/dev/hda15 /dev/hda8 /dev/hdb18 /dev/hdc1 /dev/hdc20 /dev/hdd12 /dev/hdd5 /dev/hde15 /dev/hde8 /dev/hdf18 /dev/hdg1 /dev/hdg20 /dev/hdh12 /dev/hdh5
/dev/hda16 /dev/hda9 /dev/hdb19 /dev/hdc10 /dev/hdc3 /dev/hdd13 /dev/hdd6 /dev/hde16 /dev/hde9 /dev/hdf19 /dev/hdg10 /dev/hdg3 /dev/hdh13 /dev/hdh6
/dev/hda17 /dev/hdb /dev/hdb2 /dev/hdc11 /dev/hdc4 /dev/hdd14 /dev/hdd7 /dev/hde17 /dev/hdf /dev/hdf2 /dev/hdg11 /dev/hdg4 /dev/hdh14 /dev/hdh7
/dev/hda18 /dev/hdb1 /dev/hdb20 /dev/hdc12 /dev/hdc5 /dev/hdd15 /dev/hdd8 /dev/hde18 /dev/hdf1 /dev/hdf20 /dev/hdg12 /dev/hdg5 /dev/hdh15 /dev/hdh8
/dev/hda19 /dev/hdb10 /dev/hdb3 /dev/hdc13 /dev/hdc6 /dev/hdd16 /dev/hdd9 /dev/hde19 /dev/hdf10 /dev/hdf3 /dev/hdg13 /dev/hdg6 /dev/hdh16 /dev/hdh9
Only hda and hdb actually exist.......

Udev 057-1 - /dev/hdc permissions wrong

Similar Messages

Maybe you are looking for