This can be reproduced on my system every time simply from console:
1. Poweroff system
2. Poweron WITHOUT any CD device inserted (if it's inserted while booting it will be properly detected and mounted)
3. Insert CD
4. Run "udisksctl mount -b /dev/sr0", I get:
$ udisksctl mount -b /dev/sr0
Object /org/freedesktop/UDisks2/block_devices/sr0 is not a mountable filesystem.
5. Log in as root and manually run:
# mount /dev/sr0 /mnt/backups/
mount: warning: /mnt/backups/ seems to be mounted read-only.
6. Umount it
7. Now udisksctl works ok:
udisksctl mount -b /dev/sr0
Mounted /dev/sr0 at /run/media/pacho/Gentoo Linux amd64 20120223.
On the other hand, old udisks command always work ok:
$ udisks --mount /dev/sr0
Mounted /org/freedesktop/UDisks/devices/sr0 at /media/disk
I can even use old "udisks" command to mount it first time (instead of "mount") and udisksctl will work properly after that. Then, the problem looks to be in recognizing my device properly first time, while udisks1 looks to detect it ok
With udevil I get it failing on first run and ok on second:
$ udevil mount /dev/sr0
udevil: error: no media in device /dev/sr0 (or specify type with -t)
$ udevil mount /dev/sr0
Mounted /dev/sr0 at /media/Gentoo Linux amd64 2
But, anyway, even running it only first time (and, then, getting the failure), if I run udisksctl just after that, it's properly mounted :O
I don't think it's a problem with udisks - please attach the output of
udevadm info --export-db
(run both commands as root)
My guess is that your OS boot-up scripts simply does not initialize the udev database correctly. The output of those two commands will tell for sure. What OS are you using?
(In the future please read http://www.freedesktop.org/wiki/Software/udisks for what information to attach.)
Created attachment 64503 [details]
Created attachment 64504 [details]
I am running Gentoo Linux, thanks
(In reply to comment #4)
> Created attachment 64504 [details]
> udevadm output
Yeah, your udev initialization script seems busted since there is no ID_FS* properties for sr0. Not an udisks bug.
(In reply to comment #6)
> (In reply to comment #4)
> > Created attachment 64504 [details]
> > udevadm output
> Yeah, your udev initialization script seems busted since there is no ID_FS*
> properties for sr0. Not an udisks bug.
Do you have any idea about what could be wrong when starting udev?
(In reply to comment #7)
> (In reply to comment #6)
> > (In reply to comment #4)
> > > Created attachment 64504 [details]
> > > udevadm output
> > Yeah, your udev initialization script seems busted since there is no ID_FS*
> > properties for sr0. Not an udisks bug.
> Do you have any idea about what could be wrong when starting udev?
Could that properties being missing because I don't have kernel polling enabled? (due udev-171 being used)
I am running in the same problem and I am also using Gentoo (and systemd).
Could you point me to the stuff I have to add to udev (rule, start script)?
Ah ok, I think I have to look at the source code of udev. Thanks
on May 27, 2016 at 06:28:18.
(provided by the Example extension).