I want to mount the contents of an iso9600 (CD) image via a loop to access its contents. To do so I execute

mount -r -t iso9600 -o loop file.iso mountpoint/

and would expect the contents in the (existing) directory mountpoint. However, I get mount: mounting /dev/loop0 on mountpoint/ failed: No such device. What are the likely reasons for this?

2 Answers 2


There are multiple reasons I can think of. Probably the more common one is that something with the loop devices is not in order, e.g., there are too many loop device in use already. You can check if this is the case by setting up the loop device manually:

# losetup --find --show file.iso
# mount -o ro /dev/loop0 mountpoint/
# losetup --detach /dev/loop0

If the first command does not print a legal loop device (/dev/loop*) but gives an error message then the infrastructure for loop devices themselves is somehow the issue. See if losetup -a shows any devices. The maximum number might be reached. In that case you could try creating more via the module's max_loop option (and reboot) or manually with mknod as explained in this answer.

However, there is another option that is explained concisely in the mount syscall's manpage:

ENODEV     filesystemtype not configured in the kernel.

Your kernel might not support the required file system. In the example above using a CD image this would be iso9660. Try loading the respective module via

# modprobe iso9660

and retry. If you get modprobe: module iso9660 not found then you are kind of out of luck because your kernel does not support the file system at all and there is no easy way to enable it. You can verify the supported filesystems listed in /proc/filesystems. To make it work you have to recompile the kernel or at least the respective module (matching the exact kernel version of course).

PS: The module is named isofs in newer kernels but at least for modprobe and friends there exists an alias iso9660.


I got this error message by starting the Live version of Linux Mint from my bootable USB drive. It turned out that the used ISO was corrupt - redownloading the ISO fixed the problem.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .