unable to mount ISO's on kernel 2.6.3
Hey, I was able to mount ISO's on kernel 2.4.22 with the following command
mount -t iso9660 -o loop <imagefile> <mount point> but in kernel 2.6.3 I can't do that and yes I have turned on loop support in the kernel I get this instead: mount -t iso9660 -o loop k3b_0.iso /mnt/iso mount: wrong fs type, bad option, bad superblock on /dev/loop0, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) when I do a mount it shows this: bash-2.05b# mount /dev/hda3 on / type ext2 (rw) /dev/hda6 on /var type ext2 (rw) /dev/hda7 on /home type ext2 (rw) /dev/hda8 on /usr type ext2 (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) proc on /proc type proc (rw) usbfs on /proc/bus/usb type usbfs (rw) can anyone help me? chanks! |
Are you doing this as root? Does the device /dev/loop0 actually exist? What are its permissions?
|
As root, here are the premissions for loop
bash-2.05b# ls -l |grep loop brw-rw---- 1 root disk 7, 0 Jun 3 1996 loop0 brw-rw---- 1 root disk 7, 1 Jun 3 1996 loop1 brw-rw---- 1 root disk 7, 10 Mar 19 2002 loop10 brw-rw---- 1 root disk 7, 11 Mar 19 2002 loop11 brw-rw---- 1 root disk 7, 12 Mar 19 2002 loop12 brw-rw---- 1 root disk 7, 13 Mar 19 2002 loop13 brw-rw---- 1 root disk 7, 14 Mar 19 2002 loop14 brw-rw---- 1 root disk 7, 15 Mar 19 2002 loop15 brw-rw---- 1 root disk 7, 2 Jun 3 1996 loop2 brw-rw---- 1 root disk 7, 3 Jun 3 1996 loop3 brw-rw---- 1 root disk 7, 4 Jun 3 1996 loop4 brw-rw---- 1 root disk 7, 5 Jun 3 1996 loop5 brw-rw---- 1 root disk 7, 6 Jun 3 1996 loop6 brw-rw---- 1 root disk 7, 7 Jun 3 1996 loop7 brw-rw---- 1 root disk 7, 8 Jun 3 1996 loop8 brw-rw---- 1 root disk 7, 9 Mar 19 2002 loop9 Maybe there is something wrong with my kernel configuration, what should I have enabled in order to mount ISO's? I have loop device enabled, is there anything else I need to enable in order to mount ISO's? |
Can anyone that uses 2.6.3 kernel please try to mount a CDImage and if you can and you please post your kernel config and fstab and anything else I need to know... cause this has really got me ..
Chanks! |
forget it if it doesnt work it doesnt work ... until linus resoves this issue I'm pretending loop doesnt exist .. because its clearly a bug .. i can mount my digital camera but not mount an ISO so to me there is no proof i ever could ...that function has not been implmented yet in my eyes...
|
Hello,
yes, I'm also working with a self compiled 2.6.3 kernel, and I don't have any problem mounting an iso image! Example (as "root", of course): Code:
mount -t iso9660 -o loop filename.iso /mnt/cdrom/ cu hp_tux |
Quote:
I'm starting to HATE unix based OS's because for one there is no readmes for anything that your actully need like configureing your loop device ....people just assume it works ...lol I can mount my digial camera but not my ISO's ... plz... I think Linus was smoking too much crack when he made kernel 2.6.3 Like I said from day one! If your going to release something provide proper documentation and make sure it works! mount -t iso9660 -o loop filename.iso /mnt/cdrom/ doesnt do anything all it does is make linux cry about some retarted message which I'm not even sure its real, it's being gay and not wanting to mount the filesystem This is when I get pissed, when software refuses to work FOR NO REASON what so ever! I feel like "zero" writing all my linux partitions and saying now look laphing linus you bitch! |
Hello,
oh, I'm sorry: I couldn't suspect that you DON'T want to solve your problem! :rolleyes: :rolleyes: :rolleyes: Good bye hp_tux |
Quote:
I already sovled it.... I'm zero wrting all my partitions .. thats what I do to software that fails to do its job for no reason what so ever. |
Hello,
well, I know about a computer which will fit for you perfectly: It's called "ABACUS"! :cool: :cool: :cool: cu hp_tux |
Yo Guy just chill alright, I've had this probem for ages and ages at frist I thought everyone was ingoring me (care they are) but who cares wow you can't mount ISO's big deal.
I know it seems like everyone is against you but were not, we are only trying to help (well some of us are) anyways just simmer down, I don;t think anyone will help you with you going all nuts in people faces like that... just relax.. |
Sorry for double posting, But can someone help if not me ... us? I have the same probem as him.. it seems there maybe a bug causing some system to lose there loop fuctionality...
I have the exact probem and my permissions are the same as CryptDragoons's these are the things I have already tryed. mount -t iso9660 -o ro,loop=/dev/loop0 /home/tim/test.iso /mnt/iso And I get this: mount: wrong fs type, bad option, bad superblock on /dev/loop0, or too many mounted file systems (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) Then I tryed this: losetup /dev/loop0 And got this: loop: can't get info on device /dev/loop0: No such device or address and if I do this: ls -l /dev/ |grep loop I get this: brw-rw---- 1 root disk 7, 0 Jun 3 1996 loop0 brw-rw---- 1 root disk 7, 1 Jun 3 1996 loop1 brw-rw---- 1 root disk 7, 10 Mar 19 2002 loop10 brw-rw---- 1 root disk 7, 11 Mar 19 2002 loop11 brw-rw---- 1 root disk 7, 12 Mar 19 2002 loop12 brw-rw---- 1 root disk 7, 13 Mar 19 2002 loop13 brw-rw---- 1 root disk 7, 14 Mar 19 2002 loop14 brw-rw---- 1 root disk 7, 15 Mar 19 2002 loop15 brw-rw---- 1 root disk 7, 2 Jun 3 1996 loop2 brw-rw---- 1 root disk 7, 3 Jun 3 1996 loop3 brw-rw---- 1 root disk 7, 4 Jun 3 1996 loop4 brw-rw---- 1 root disk 7, 5 Jun 3 1996 loop5 brw-rw---- 1 root disk 7, 6 Jun 3 1996 loop6 brw-rw---- 1 root disk 7, 7 Jun 3 1996 loop7 brw-rw---- 1 root disk 7, 8 Jun 3 1996 loop8 brw-rw---- 1 root disk 7, 9 Mar 19 2002 loop9 and if I do this: mke2fs /dev/loop0 1024 I get this: mke2fs 1.34 (25-Jul-2003) mke2fs: Filesystem larger than apparent device size. Proceed anyway? (y,n) y Warning: could not erase sector 2: Invalid argument Filesystem label= OS type: Linux Block size=1024 (log=0) Fragment size=1024 (log=0) 128 inodes, 1024 blocks 51 blocks (4.98%) reserved for the super user First data block=1 1 block group 8192 blocks per group, 8192 fragments per group 128 inodes per group Warning: could not read block 0: Attempt to read block from filesystem resulted in short read Warning: could not erase sector 0: Attempt to write block from filesystem resulted in short write mke2fs: Invalid argument while zeroing block 960 at end of filesystem Writing inode tables: 0/1 Could not write 8 blocks in inode table starting at 5: Invalid argument my fstab looks like this : /dev/hda5 swap swap defaults 0 0 /dev/hda3 / ext2 defaults 1 1 /dev/hda6 /var ext2 defaults 1 2 /dev/hda7 /home ext2 defaults 1 2 /dev/hda8 /usr ext2 defaults 1 2 /dev/cdrom /mnt/cdrom iso9660 noauto,users,owner,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,users,owner 0 0 /dev/sda1 /mnt/camera auto defaults,user,noauto 0 $ devpts /dev/pts devpts gid=5,mode=620 0 0 proc /proc proc defaults 0 0 I have been looking for along time .. this problem happends to me everytime I recompile my kernel :( |
All times are GMT -5. The time now is 05:43 PM. |