Problems with mounting .ISO files

Posted by user89599 on Ask Ubuntu See other posts from Ask Ubuntu or by user89599
Published on 2012-09-14T14:16:49Z Indexed on 2012/09/14 15:49 UTC
Read the original article Hit count: 401

Filed under:
|
|

I'm using Precise, with GNOME. I've attempted to install some retro,
multi-cd games (KOTOR1) via .ISO images and WINE,

but I can't get the ISO's to mount correctly. First I tried GMountISO, which showed a read-only warning but worked - until I went to unmount. When the installation program asked for CD 2 I couldn't unmount from the /cdrom folder because neither GMountISO or umount from terminal could detect the mount.

After a reboot, I changed to GISOMount (different somehow, I guess?), but when I attempt to mount the ISO I get an error window explaining the syntax of the mount command and, which is also what I get when I attempt to use mount from terminal. After checking /media from terminal on a lark I see the disc mounted there twice over, but umount won't recognize it, even when I specify the full path sudo umount /media/KOTOR_1.iso. It cleared up upon reboot.

Can someone please assist?

UPDATE :: Thanks for the quick response. What's weird, is the images are like stuck in limbo... I'll show you:

sc@sc-HP-110-3700:/media$ ls
cdrom KOTOR_1(0)(vcd) KOTOR_1(vcd)
sc@sc-HP-110-3700:/media$ cd cdrom
sc@sc-HP-110-3700:/media/cdrom$ ls
sc@sc-HP-110-3700:/media/cdrom$ cd ..
sc@sc-HP-110-3700:/media$ umount KOTOR_1(vcd)
bash: syntax error near unexpected token `('
sc@sc-HP-110-3700:/media$ umount KOTOR_1.ISO
umount: KOTOR_1.ISO is not mounted (according to mtab)
sc@sc-HP-110-3700:/media$ sudo umount -a
umount: /run/shm: device is busy.
(In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
umount: /run: device is busy.
(In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
umount: /dev: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
umount: /: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1))
sc@sc-HP-110-3700:/media$

© Ask Ubuntu or respective owner

Related posts about mount

  • 12.10 update breaks NFS mount

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I've just upgraded to the latest 12.10 beta. Rebooted twice. The problem is with the NFS folders not mounting, here's a verbose log. # mount -v myserver:/nfs_shared/tools /tools/ mount: no type was given - I'll assume nfs because of the colon mount.nfs: timeout set for Mon Oct 1 11:42:28 2012 mount… >>> More

  • Mount SMB / AFP 13.10

    as seen on Ask Ubuntu - Search for 'Ask Ubuntu'
    I cannot seem to get Ubuntu to mount a mac share via SMB or AFP. I've tried the following... AFP: apt-get install afpfs-ng-utils mount_afp afp://user:password@localip/share /mnt/share Error given: "Could not connect, never got a reponse to getstatus, Connection timed out". Which is odd as I can… >>> More

  • Mount Return Code for CIFS mount

    as seen on Server Fault - Search for 'Server Fault'
    When I run the following command (as root or via sudo) from a bash script I get an exit status (or return code in mount man page parlance) of 1: mount -v -t cifs //nasbox/volume /tmpdir/ --verbose -o credentials=/root/cifsid & /tmp/mylog It outputs the following into the myflog file: parsing… >>> More

  • Disable raid member check upon mount to mount damaged nvidia raid1 member

    as seen on Server Fault - Search for 'Server Fault'
    Hi, A friend of mine destroyed his Nvidia RAID1 array somehow and in trying to fix it, he ended up with a non-working array. Because of the RAID metadata, the actual disk data was stored at an offset from the beginning. I was able to identify this offset with dd and a hexeditor and then I used losetup… >>> More

  • Network shares do not mount.

    as seen on Super User - Search for 'Super User'
    My network shares were mounting fine yesterday.. suddenly they are not. They were mounting fine for the last two weeks or however long since I added them. When I run sudo mount -a I get the following error: topsy@monolyth:~$ sudo mount -a mount error(12): Cannot allocate memory Refer to the mount… >>> More

Related posts about iso