Mounting an *.iso...

darkarcon2015 · 02-01-2005, 07:40 PM

I can't seem to mount them. I will do this:

Code:

mount -o loop -t iso9660 ISO_NAME.iso /mnt/cdrom

and then get this output:

Code:

ioctl: LOOP_SET_FD: Invalid argument

After reading a few other threads on this I did an "ls -R /dev | grep loop" and recieved this:

Code:

loop0
loop1
loop10
loop11
loop12
loop13
loop14
loop15
loop2
loop3
loop4
loop5
loop6
loop7
loop8
loop9

So I proceeded to "modprobe loop" and it said that it doesn't exist. I read that I have to make sure loopback filesystem support is compiled into my kernel but I couldn't find an option for it in the config. Where would this be or what am I doing wrong? Thanks a lot.

dowelld · 02-01-2005, 07:46 PM

Were you root when you tried to modprobe loop ?

you can use cat /proc/devices and look for an entry like

7 loop

under Block Devices :

If it is not there then either the module is not loaded, or support is not built in.

if you haven't got the module did you compile it in ?

Dave

egag · 02-02-2005, 05:59 AM

------------
mount -o loop ISO_NAME.iso /mnt/cdrom
------------

that works here......
( be sure nothing else is mounted on /mnt/cdrom... )

egag

d00msweek · 02-02-2005, 06:15 AM

or just make another directory in /mnt eg.

mkdir /mnt/iso
mount file.iso -o loop -t iso9660 /mnt/iso

jawkins · 02-02-2005, 07:00 AM

Quote:

Originally posted by egag
( be sure nothing else is mounted on /mnt/cdrom... )

You can mount over an already mounted directory.

Jim

egag · 02-02-2005, 07:14 AM

yep,

from man mount...
-----------
mount -t type device dir
This tells the kernel to attach the file system found on device (which is of type type) at the directory dir.

The previous contents (if any) and owner and mode of dir become invisible, and as long as this file system remains mounted, the pathname dir refers to the root of the file system on device.
-----------

...but you can't use what's mounted there.
but anyway good to know....

egag

roninja · 02-02-2005, 09:02 AM

In the kernel its under Block devices as Loopback device support

darkarcon2015 · 02-02-2005, 02:43 PM

Yes, I was root user when I tried that :-\ I have also tried creating a new mountpoint, in my kernel configuration it says that it's built-in, and I have "7 loop" listed under Block Devices when I run "cat /proc/devices".

egag · 02-02-2005, 02:56 PM

did you try without the " -t iso9660 " part...?

egag

darkarcon2015 · 02-02-2005, 03:09 PM

Yes, same error.

EDIT *** SOLVED *** I had to copy the *.iso from my windows partition into my linux partition.

denning · 02-25-2005, 11:46 PM

i face the same problem, except i am trying to mount initrd.img to edit the slackware installer.

I see 7 loop in /proc/devices, but keep getting either

root@fawkes:~# mount -o loop initrd.img /mnt/intrd/
ioctl: LOOP_CLR_FD: Device or resource busy
mount: you must specify the filesystem type

OR

root@fawkes:~# mount -o loop -t auto initrd.img /mnt/intrd
ioctl: LOOP_CLR_FD: Device or resource busy
mount: you must specify the filesystem type

I am using a vanilla Slackware 10.1 installation.

DaHammer · 02-26-2005, 12:37 AM

If you mean the initrd.img for the CDROM from the isolinux directory, it's gzipped. Decompress it first, then mount it.

Code:

gzip -d -S .img initrd.img
mount -o loop initrd /mnt/loop

denning · 02-26-2005, 04:10 PM

omg. Thanks so much DaHammer!! I can now mod the slackware installer to my heart's content!

IamI · 06-16-2005, 09:27 PM

Quote:

Originally posted by darkarcon2015
Yes, same error.

EDIT *** SOLVED *** I had to copy the *.iso from my windows partition into my linux partition.

Sorry to reanimate this old thread's corpse, but I had the very same problem as darkacron2015, and the same solution worked for me as well. Basically all I wanted to do was watch a dvd iso located on my NTFS partition, but I ended up having to copy all four and a half gig of it to my home directory to do so.

I am curious: I've mounted numerous isos of various descriptions from my Windows partitions before, and now I can't seem to suddenly. Can somebody tell me what the explanation might be?

jamessnell · 10-25-2005, 06:01 PM

I had the same problem..

I have loopback support built directly in to my kerenel, I even copied the iso to my local filesystem (though you shouldn't need to do this, it'll mount over nfs or smb just fine).. and yet I still couldn't get it to mount.. I specified the file system type, you normally don't really need to do this either.. It turned out it was simply a bad iso.. So, make sure you get the same results with other isos or try mounting them on other machines, just to save yourself some time. I rebuilt my kernel and wasted about 40mins on this one. Don't make the same mistake.. Though, if you're here, you probably have a 'real' problem.

Good luck,
J