SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Current64 - with and without multilib - up to date.
When I mount a UDF ISO like: # mount -oloop /E/Lindoc/Rescue/rescue-4.7.3f.iso /cdrom
I get an error popup reading: > Unable to mount Rescue-4.7.3f
> Device /dev/loop0 is already mounted at '/cdrom'
The ISO however is mounted. There is nothing interesting in the /var/log/messages file other than the usual UDF blurp.
When I then unmount the ISO: # umount /cdrom
I get an error popup reading: > Unable to mount Volume
> Operation was cancelled
Strangely enough the messages file now has two squashfs errors ...
When I mount a plain iso9660 ISO I do not get an error popup, nor is there anything in the messages.
Unmounting however gives the same error popup: > Unable to mount Volume
> Operation was cancelled
In the messages there is now an iso9660 error message.
One or two times I noticed that the ISO was also mounted in /run/media !???!
I see these symptoms with current64 with and without multilib, but not with current32.
I do not know when these symptoms started. It must have been at least a week and possibly even more that I mounted an ISO with my current64's.
Did I pick up something "bad" recently, or are there other users with the same symptoms?
Can you break this down some more? I am curious. I know that /mnt/cdrom is the auto mount location for cdroms in slackware. But I am not a slackware expert.
Try doing an
Code:
losetup /dev/loop0
It should give you some info as to what loop0 is doing.
Can you break this down some more? I am curious. I know that /mnt/cdrom is the auto mount location for cdroms in slackware. But I am not a slackware expert.
It has nothing distribution specific. When no fstype is specified, mount tries to guess it (man mount and search for auto type).
The guess may well miss, and one or more failure records will be left in dmesg.
Things get even weirder: The popup on the mount occurs less consistently than it did yesterday. But the popup on the umount remains as was.
The remarks on type auto are correct, however stating "-tudf" or "-tiso9660" makes no difference at all.
By pure chance I noticed that the "-oloop" is no longer necessary -- I am sure it was necessary in the past.
"Losetup /dev/loop0" or "mount" (without arguments) do not show anything out of the ordinary.
I cannot help feeling that something is interfering with the mount. But I do not have an automounter running -- actually I do not even have autofs installed.
Based on the fact that I do not remember the symptoms from say a week (or two) I would say that something in the recent updates is causing things. Udisk (updated Mar 27) and udisk2 (updated Mar 23) seem good candidates.
Before diving deeper however it might be interesting to know whether or not there are other users seeing the symptoms. Any ISO will do, even the slackware-14.0-install-dvd.iso one.
...
I cannot help feeling that something is interfering with the mount. But I do not have an automounter running -- actually I do not even have autofs installed.
...
Are you using any GUI desktop environment or something alike?
Yes: Xfce 4.10 from Slackware with the "missing" packages added from Salix and Mint. I use Thunar to manage the desktop, Caja ("nautilus") as file manager and Pluma ("gedit") as editor. Both Thunar's and Caja's media handling are disabled.
Downgrading udisks 1.0.4/2 -> 1.0.4/1 and udisks2 2.1.0/1 -> 1.98.0/1 had no other effect than that the umount message now reads: > Unable to mount Volume
> The given volume was not found
However, when unmounting the Slackware64 DVD I once got the much more detailed error popup as attached. It (re-)highlights two points:
1) The message when unmounting is about a failed mount;
2) There is the "/run/media" again, and I have idea where it comes from.
The syslog message referred to reads: Mar 30 17:27:28 riposo kernel: isofs_fill_super: bread failed, dev=loop0, iso_blknum=16, block=32
Actually I noticed that the /var/log/run -> /run symlink that I expected to be there was no longer. Recreating that symlink had no effect on the problem at hand.
Yes: Xfce 4.10 from Slackware with the "missing" packages added from Salix and Mint. I use Thunar to manage the desktop, Caja ("nautilus") as file manager and Pluma ("gedit") as editor. Both Thunar's and Caja's media handling are disabled.
I bet it takes forever for you to find anyone who happens to mix the same packages from the same distributions :-D
I revived my Slackware32 installation from a backup of Mar 23 early in the morning and verified that the "mount -oloop / umount" problem was not present.
I then ran "slackpkg update ; slackpkg upgrade-all" (Sat Mar 23 22:49:52 UTC 2013 through Fri Mar 29 00:27:36 UTC 2013 : 80 upgrades, 5 additions) and found that the "mount -oloop / umount" problem *is* present now.
So the likelyhood that other current users have the same symptoms is rather high. Remains the question why I am the only one reporting them - or is no one mounting ISOs?
I revived my Slackware32 installation from a backup of Mar 23 early in the morning and verified that the "mount -oloop / umount" problem was not present.
I then ran "slackpkg update ; slackpkg upgrade-all" (Sat Mar 23 22:49:52 UTC 2013 through Fri Mar 29 00:27:36 UTC 2013 : 80 upgrades, 5 additions) and found that the "mount -oloop / umount" problem *is* present now.
So the likelyhood that other current users have the same symptoms is rather high. Remains the question why I am the only one reporting them - or is no one mounting ISOs?
So what's meaning of "with the \"missing\" packages added from Salix and Mint"?
So the likelyhood that other current users have the same symptoms is rather high. Remains the question why I am the only one reporting them - or is no one mounting ISOs?
I am running -current (32 bit) and have mounted/umounted ISOs several times today with no problem. I am using Fluxbox.
But like guanx, I am curious what you meant by "missing packages".
I boot to the console (runlevel 3). From there "startx" brings me to twm, and "xfce" (alias for "xinit /etc/X11/xinit/xinitrc.xfce") to xfce.
The fluxbox tip made me test things on the console and under twm. And lo and behold! the problem did not occur there. I then tested under xfce and the problem was back.
About the missing packages: I found the xfce implementation as provided by the xap disk set rather incomplete - e.g. no editor, no archive manager, no xfburn. Following are the packages and their dependencies from salix (-?gv builds) and mint (-1mint build extracted from a mint live CD):
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.