mount a ISO file

Kabuto · 03-17-2005, 05:10 AM

I'm trying to mount a ISO image. However I get mount: Not a directory when I do mount -o loop suse/SU920.001.iso /mnt/iso1/ (by the way I am root, I am in /root and there is a suse/ in it and /mnt/iso1/ exists too).

What to do about this?

abisko00 · 03-17-2005, 05:22 AM

Have a try with: mount -o loop ./suse/SU920.001.iso /mnt/iso1

enemorales · 03-17-2005, 05:31 AM

Dont you need to put also "-t iso9660"?

abisko00 · 03-17-2005, 05:41 AM

Quote:

Originally posted by enemorales
Dont you need to put also "-t iso9660"?

just tried it, no!

EDIT: and now I also know why

excerpt from 'man mount':

Code:

              The  type  iso9660 is the default.  If no -t option
              is given, or if the auto  type  is  specified,  the
              superblock is probed for the filesystem type (adfs,
              bfs, cramfs, ext, ext2, ext3, hfs,  hpfs,  iso9660,
              jfs,  minix, ntfs, qnx4, reiserfs, romfs, udf, ufs,
              vxfs, xfs, xiafs are  supported).   If  this  probe
              fails,   mount   will   try   to   read   the  file
              /etc/filesystems,  or,  if  that  does  not  exist,
              /proc/filesystems.   All  of  the  filesystem types
              listed there will be tried, except for  those  that
              are  labeled  "nodev" (e.g., devpts, proc and nfs).
              If /etc/filesystems ends in a line with a single  *
              only, mount will read /proc/filesystems afterwards.

Kabuto · 03-17-2005, 06:25 AM

I tried what abisko00 said, and what enemorales said, and the result is the same

n0sr · 03-17-2005, 06:31 AM

Quote:

Originally posted by Kabuto
I'm trying to mount a ISO image. However I get mount: Not a directory when I do mount -o loop suse/SU920.001.iso /mnt/iso1/ (by the way I am root, I am in /root and there is a suse/ in it and /mnt/iso1/ exists too).

What to do about this?

Am I correct that suse is in the /root directory? If so try this:

Code:

#mount -o loop /root/suse/suseSU920.001.iso /mnt/iso1

I'm pretty sure you don't need -t iso9660

Kabuto · 03-17-2005, 06:45 AM

Quote:

Originally posted by n0xvb
Am I correct that suse is in the /root directory? If so try this:

Code:

#mount -o loop /root/suse/suseSU920.001.iso /mnt/iso1

I'm pretty sure you don't need -t iso9660

I tried that too

abisko00 · 03-17-2005, 06:51 AM

Is it possible that you have a split iso, which needs to be joint with its second half first? It's just a thought because of the 001 in the filename.

Kabuto · 03-17-2005, 06:54 AM

It's the ISO of the first CD of SuSE 9.2

n0sr · 03-17-2005, 06:55 AM

Do you have a loop device? Try

Code:

mknod /dev/loop0 b 7 0

Then try the mount command again

abisko00 · 03-17-2005, 06:59 AM

Please post the output of:

ls -l /mnt | grep iso
ls -l /root/suse
and the exact mount command you used.

Kabuto · 03-17-2005, 07:01 AM

mknod /dev/loop0 b 7 0
mknod: `/dev/loop0': File exists

Kabuto · 03-17-2005, 07:03 AM

linux:~ # ls -l /mnt | grep iso
drwxr-xr-x 2 root root 48 Mar 16 15:46 iso1
drwxr-xr-x 2 root root 48 Mar 16 15:46 iso2
drwxr-xr-x 2 root root 48 Mar 16 15:46 iso3
drwxr-xr-x 2 root root 48 Mar 16 15:46 iso4
drwxr-xr-x 2 root root 48 Mar 16 15:46 iso5
linux:~ # ls -l /root/suse
total 3326036
drwxr-xr-x 2 root root 208 Mar 17 09:49 .
drwx------ 21 root root 776 Mar 17 11:35 ..
-rw-r--r-- 1 root root 680998182 Mar 16 15:29 SU920.001.iso
-rw-r--r-- 1 root root 680778840 Mar 16 15:31 SU920.002.iso
-rw-r--r-- 1 root root 682724127 Mar 16 15:35 SU920.003.iso
-rw-r--r-- 1 root root 679814427 Mar 16 15:37 SU920.004.iso
-rw-r--r-- 1 root root 678212685 Mar 16 15:41 SU920.005.iso

abisko00 · 03-17-2005, 07:19 AM

I simulated this on my machine (SuSE 9.1) with the same filenames. It worked!

Code:

linux:~ # mount -o loop ./suse/SU920.001.iso /mnt/iso1
linux:~ # cd /mnt/iso1
linux:/mnt/iso1 # ls
.  ..  boot  content  media.1  suse

The iso file is the mini-installation.iso that I renamed to SU920.001.iso

enemorales · 03-17-2005, 07:22 AM

Quote:

Originally posted by abisko00
[B]just tried it, no!

EDIT: and now I also know why

[...]

Good to know it. I'll save some typing next time

The error message doesn't lead to this, but could it happen that the ISO is corrupted? Did you download them? If the webpage provides the MD5 sums you can run "md5sum yourisofile.iso" to compare them.

Other choices. Do you have another ISO that mounts?

it looks like I've more questions than answers