Hi,
Making some test today I could debug the server side to try
understanding what's wrong. I got an output like this:
08:27:28.607 [I] osspec.c:256: SEQNUM=2647, ACTION=add,
SUBSYSTEM=bdi, DEVPATH=/sys/devices/virtual/bdi/251:1, DEVNAME=,
IFINDEX=0
08:27:28.607 [D] hotplug.c:476: checking ADD event
/sys/devices/virtual/bdi/251:1
08:27:28.607 [D] hotplug.c:397: event
/sys/devices/virtual/bdi/251:1: skip ourselves and all later events
08:27:28.607 [I] hotplug.c:145: /sys/devices/virtual/bdi/251:1 is a
device (subsystem)
08:27:28.607 [I] device.c:4997: add_dev: subsys=bdi
sysfs_path=/sys/devices/virtual/bdi/251:1 dev= parent_dev=0x00000000
08:27:28.607 [D] hotplug.c:500: events queued = 0, events in
progress = 0
08:27:28.607 [D] hotplug.c:505: Hotplug-queue empty now ... no
hotplug events in progress
08:27:28.688 [I] osspec.c:256: SEQNUM=2648, ACTION=add,
SUBSYSTEM=block, DEVPATH=/sys/devices/virtual/block/utdisk1,
DEVNAME=/dev/utdisk1, IFINDEX=0
08:27:28.688 [D] hotplug.c:476: checking ADD event
/sys/devices/virtual/block/utdisk1
08:27:28.688 [D] hotplug.c:397: event
/sys/devices/virtual/block/utdisk1: skip ourselves and all later events
08:27:28.688 [I] blockdev.c:904: block_add:
sysfs_path=/sys/devices/virtual/block/utdisk1 dev=/dev/utdisk1
is_part=0, parent=0x00000000
08:27:28.688 [I] blockdev.c:958: Looking in
/sys/devices/virtual/block/utdisk1/slaves for Device Mapper
08:27:28.688 [I] blockdev.c:969:
/sys/devices/virtual/block/utdisk1/slaves/. ->
/sys/devices/virtual/block/utdisk1/slaves
08:27:28.688 [I] blockdev.c:1003: Couldn't find slave volume in devices
08:27:28.689 [I] blockdev.c:969:
/sys/devices/virtual/block/utdisk1/slaves/.. ->
/sys/devices/virtual/block/utdisk1
08:27:28.689 [I] blockdev.c:1003: Couldn't find slave volume in devices
08:27:28.689 [I] blockdev.c:1009: Done looking in
/sys/devices/virtual/block/utdisk1/slaves
08:27:28.689 [I] blockdev.c:1016: Ignoring hotplug event - no parent
08:27:28.689 [W] blockdev.c:1587: Not adding device object
08:27:28.689 [D] hotplug.c:500: events queued = 0, events in
progress = 0
08:27:28.689 [D] hotplug.c:505: Hotplug-queue empty now ... no
hotplug events in progress
08:27:29.415 [I] osspec.c:303: /proc/mounts tells, that the mount
has tree changed
08:27:38.960 [I] osspec.c:256: SEQNUM=2649, ACTION=add,
SUBSYSTEM=block,
DEVPATH=/sys/devices/virtual/block/utdisk1/utdisk1p1,
DEVNAME=/dev/utdisk1p1, IFINDEX=0
08:27:38.960 [D] hotplug.c:476: checking ADD event
/sys/devices/virtual/block/utdisk1/utdisk1p1
08:27:38.960 [D] hotplug.c:397: event
/sys/devices/virtual/block/utdisk1/utdisk1p1: skip ourselves and all
later events
08:27:38.960 [I] blockdev.c:904: block_add:
sysfs_path=/sys/devices/virtual/block/utdisk1/utdisk1p1
dev=/dev/utdisk1p1 is_part=1, parent=0x00000000
08:27:38.960 [I] blockdev.c:1016: Ignoring hotplug event - no parent
08:27:38.960 [W] blockdev.c:1587: Not adding device object
08:27:38.960 [D] hotplug.c:500: events queued = 0, events in
progress = 0
08:27:38.960 [D] hotplug.c:505: Hotplug-queue empty now ... no
hotplug events in progress
Honestly, I don't understand where the problem is. I think it's trying
to find some info under /sys/devices/virtual/block/utdisk1/slaves/ and
as this is an empty directory, it simply won't mount it. I still wonder
why it mounts it when the device is plugged in directly to the server,
though, and trying to research a bit over this there seems not to be
quite much information (basically because HAL was discontinued a while
ago...).
I'll try to investigate a bit more, if not, I guess I'll give up this...
Regards,
Nicolás
El 10/07/2014 20:03, Edwin Marqe escribió:
Hi Nicolas,
I would say this is caused because of the HAL daemon not recognizing
your USB drive, but if you say it actually does when you plug it
directly to the server, it must be something else. Weird, though. As
far as I know on version 4.3.4 of KDE the default storage backend is
HAL and I'm not quite sure it's possible to change it (for example by
UDisks) - at least I was unable.
What you could try is to stop the haldaemon, start it as a foreground
process using --daemon=no and --verbose=yes and see whether you see
something revealing in the debug log.
Hope this helps
2014-07-09 17:49 GMT+01:00 Nicolás <[email protected]
<mailto:[email protected]>>:
Hi!
Picking this up again, being the usbdrived solution very useful, I
still can't manage to make the mounted USB drive show up in the
"Device notifier". I'm using Oracle Linux 6.3 w/ KDE 3.4.3 (yep, I
know KDE is not officially supported, but maybe someone has gone
through this and can help...).
Once plugged in, the drive is correctly mounted, I can read,
write, browse contents, etc. The only problem is that it doesn't
seem to send any notification into the "Device notifier" area.
I've tried making a simple trace with the 'udisks --monitor'
command and the result seems to be correct:
added: /org/freedesktop/UDisks/devices/utdisk1
Showing information for /org/freedesktop/UDisks/devices/utdisk1
native-path: /sys/devices/virtual/block/utdisk1
device: 251:1
device-file: /dev/utdisk1
presentation: /dev/utdisk1
detected at: mié 09 jul 2014 13:05:18 WEST
system internal: 0
removable: 1
has media: 1 (detected at mié 09 jul 2014
13:05:18 WEST)
detects change: 1
detection by polling: 1
detection inhibitable: 1
detection inhibited: 0
is read only: 0
is mounted: 0
mount paths:
mounted by uid: 0
presentation hide: 0
presentation nopolicy: 1
presentation name:
presentation icon:
size: 4284481536
block size: 512
job underway: no
usage:
type:
version:
uuid:
label:
partition table:
scheme: mbr
count: 1
drive:
vendor:
model:
revision:
serial:
WWN:
detachable: 0
can spindown: 0
rotational media: Yes, unknown rate
write-cache: unknown
ejectable: 0
adapter: Unknown
ports:
similar devices:
media:
compat:
interface: (unknown)
if speed: (unknown)
ATA SMART: not available
added: /org/freedesktop/UDisks/devices/utdisk1p1
Showing information for /org/freedesktop/UDisks/devices/utdisk1p1
native-path: /sys/devices/virtual/block/utdisk1/utdisk1p1
device: 251:2
device-file: /dev/utdisk1p1
presentation: /dev/utdisk1p1
by-id: /dev/disk/by-uuid/25E6-DE47
detected at: mié 09 jul 2014 13:05:23 WEST
system internal: 0
removable: 0
has media: 1 (detected at mié 09 jul 2014
13:05:23 WEST)
detects change: 0
detection by polling: 0
detection inhibitable: 0
detection inhibited: 0
is read only: 0
is mounted: 1
mount paths: /tmp/SUNWut/mnt/nicolas/noname
mounted by uid: 0
presentation hide: 0
presentation nopolicy: 1
presentation name:
presentation icon:
size: 4284481536
block size: 512
job underway: no
usage: filesystem
type: vfat
version: FAT32
uuid: 25E6-DE47
label: USB20FD
partition:
part of: /org/freedesktop/UDisks/devices/utdisk1
scheme: mbr
number: 1
type: 0x0c
flags:
offset: 24576
alignment offset: 0
size: 4284481536
label:
uuid:
This happens with /any/ device. On the other hand, the
'solid-hardware list' command (which seems to be the KDE's
hardware control tool) doesn't list this device, which I guess is
the problem. I also tried sticking the USB device to the server
instead of the client, and it gets mounted and notified. However,
it doesn't seem to be getting mounted by the 'utstoraged' daemon,
because the mount-point is defined this way instead of the Sun-Ray
'characteristic':
/dev/sdb1 on /media/USB20FD type vfat
(rw,nosuid,nodev,uhelper=hal,uid=500,utf8,shortname=mixed,flush)
Could the utstoraged daemon have something with the fact it's not
being notified? Any hint or test that I might try to know why is
this happening?
Thanks a lot.
Regards,
Nicolás
El 05/06/2014 18:03, Nicolás escribió:
El 05/06/2014 17:51, Darrel Hankerson escribió:
Nicolás <[email protected]> <mailto:[email protected]> writes:
Is there a way to configure automatic notifications for the
users
mounting their devices on their sessions? Is that a job for
the utmountd
daemon or is there something it's not working as intended?
We've used
# usbdrived
#
# Author: Daniel Cifuentes
# Version: v67, July 2008
Thanks Darrel! I've downloaded it and I'll give it a try tomorrow
at work.
Regards.
_______________________________________________
SunRay-Users mailing list
[email protected] <mailto:[email protected]>
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected] <mailto:[email protected]>
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
