[opensuse] Problem mounting an iso file

newer
[opensuse] how to zypper search...

Terry Eck

1 Jul 2013 1 Jul '13

01:19

Hi I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1. I tried to mount the iso file with the following: mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage. System responds with: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) I tried 'modprobe loop' resulting in the following: FATAL: Could not load /lib/modules/3.1.10-1.19-desktop/modules.dep: No such file or directory Could someone please give me an idea of how to solve this problem? Thanks, Terry -- OpenSuSE 12.1 --- Kernel 3.1.9-1.4-desktop --- 08:05PM --- Sun 06/30/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

John Andersen

1 Jul 1 Jul

01:32

On 6/30/2013 6:19 PM, Terry Eck wrote:

...

Hi

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

I tried to mount the iso file with the following:

mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage.

System responds with: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.)

I tried 'modprobe loop' resulting in the following: FATAL: Could not load /lib/modules/3.1.10-1.19-desktop/modules.dep: No such file or directory

Could someone please give me an idea of how to solve this problem?

Thanks, Terry

mount -o loop file.iso /mnt/isoimage You shouldn't need to do the -t However, using KDE4 on OS 12.3, you can just use Dolphin, and click the ISO and tell it to use ark to open it or select Browse the ISO, without having to mount it. Unless you had a specific reason to need it mounted. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Terry Eck

01:44

On 06/30/2013 08:32 PM, John Andersen wrote:

...

On 6/30/2013 6:19 PM, Terry Eck wrote:

...
Hi

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

I tried to mount the iso file with the following:

mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage.

System responds with: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.)

I tried 'modprobe loop' resulting in the following: FATAL: Could not load /lib/modules/3.1.10-1.19-desktop/modules.dep: No such file or directory

Could someone please give me an idea of how to solve this problem?

Thanks, Terry

mount -o loop file.iso /mnt/isoimage

You shouldn't need to do the -t

However, using KDE4 on OS 12.3, you can just use Dolphin, and click the ISO and tell it to use ark to open it or select Browse the ISO, without having to mount it. Unless you had a specific reason to need it mounted.

Thanks for the reply. I can open it using Dolphin as you suggested. However when is issue the command: mount -o loop file.iso /mnt/isoimage I still get the following: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) I would still like to know what is wrong with my system where I cannot mount the loop device. Thanks Terry -- OpenSuSE 12.1 --- Kernel 3.1.9-1.4-desktop --- 08:40PM --- Sun 06/30/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen

01:49

On 6/30/2013 6:44 PM, Terry Eck wrote:

...

Thanks for the reply. I can open it using Dolphin as you suggested. However when is issue the command: mount -o loop file.iso /mnt/isoimage I still get the following: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) I would still like to know what is wrong with my system where I cannot mount the loop device. Thanks Terry

Oddly, I have no loop device in 12.3 either. l /dev/l* shows something called /loop-control . My older machines show /dev/loop0 thru loop7 This shows often I've needed to use this! ;-) I'm pretty sure it was there in 11.4. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen

01:56

On 6/30/2013 6:49 PM, John Andersen wrote:

...

On 6/30/2013 6:44 PM, Terry Eck wrote:

...
Thanks for the reply. I can open it using Dolphin as you suggested. However when is issue the command: mount -o loop file.iso /mnt/isoimage I still get the following: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) I would still like to know what is wrong with my system where I cannot mount the loop device. Thanks Terry

Oddly, I have no loop device in 12.3 either. l /dev/l* shows something called /loop-control . My older machines show /dev/loop0 thru loop7

This shows often I've needed to use this! ;-) I'm pretty sure it was there in 11.4.

No, wait, I was doing that as user. When I do it as root I see all the /dev/loop0 --->7 and the mount command works for me as root. /me: facepalm. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

01:59

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-06-30 at 18:56 -0700, John Andersen wrote:

...

...
Oddly, I have no loop device in 12.3 either. l /dev/l* shows something called /loop-control . My older machines show /dev/loop0 thru loop7

This shows often I've needed to use this! ;-) I'm pretty sure it was there in 11.4.

No, wait, I was doing that as user. When I do it as root I see all the /dev/loop0 --->7 and the mount command works for me as root.

/me: facepalm.

As user: cer@Telcontar:~> l /dev/l* srw-rw-rw- 1 root root 0 Jun 24 11:43 /dev/log= crw------- 1 root root 10, 237 Jun 28 20:59 /dev/loop-control brw-rw---- 1 root disk 7, 0 Jun 28 21:00 /dev/loop0 brw-rw---- 1 root disk 7, 1 Jun 28 20:59 /dev/loop1 brw-rw---- 1 root disk 7, 2 Jun 28 20:59 /dev/loop2 brw-rw---- 1 root disk 7, 3 Jun 28 20:59 /dev/loop3 Of course, the mounting has to be done as root. It works for me. And I use 12.3, too. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHQ4n4ACgkQtTMYHG2NR9WGmwCeOLcL6bDgRzlMQ/BfxtARK0AN LU4AoIroug6z6RUkA7L0xsiF2iaMyN0W =6TBT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan

03:12

* John Andersen [06-30-13 21:57]: [...]

...

No, wait, I was doing that as user. When I do it as root I see all the /dev/loop0 --->7 and the mount command works for me as root.

I have Tumbleweed and only see: crw------- 1 root root 10, 237 Jun 29 00:07 /dev/loop-control Is it possible that no loop device exists until it is needed, controlled by systemd ??? I have previously loop mounted iso's but not recently and perhaps not since 12.3.... Indeed, something of the above does happen. As root I loop mounted an iso from disk to an existing directory and the following appears: crw------- 1 root root 10, 237 Jun 30 23:09 /dev/loop-control brw-rw---- 1 root disk 7, 0 Jun 30 23:09 /dev/loop0 brw-rw---- 1 root disk 7, 1 Jun 30 23:09 /dev/loop1 brw-rw---- 1 root disk 7, 2 Jun 30 23:09 /dev/loop2 brw-rw---- 1 root disk 7, 3 Jun 30 23:09 /dev/loop3 brw-rw---- 1 root disk 7, 4 Jun 30 23:09 /dev/loop4 brw-rw---- 1 root disk 7, 5 Jun 30 23:09 /dev/loop5 brw-rw---- 1 root disk 7, 6 Jun 30 23:09 /dev/loop6 brw-rw---- 1 root disk 7, 7 Jun 30 23:09 /dev/loop7 and they persist after umounting the iso, possibly until the next reboot. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen

06:54

Patrick Shanahan wrote:

...

* John Andersen [06-30-13 21:57]: [...]

...
No, wait, I was doing that as user. When I do it as root I see all the /dev/loop0 --->7 and the mount command works for me as root.

I have Tumbleweed and only see: crw------- 1 root root 10, 237 Jun 29 00:07 /dev/loop-control

Is it possible that no loop device exists until it is needed,

Yes, the 'loop' module isn't loaded until it is needed.

...

Indeed, something of the above does happen. As root I loop mounted an iso from disk to an existing directory and the following appears:

crw------- 1 root root 10, 237 Jun 30 23:09 /dev/loop-control brw-rw---- 1 root disk 7, 0 Jun 30 23:09 /dev/loop0 brw-rw---- 1 root disk 7, 1 Jun 30 23:09 /dev/loop1 brw-rw---- 1 root disk 7, 2 Jun 30 23:09 /dev/loop2 brw-rw---- 1 root disk 7, 3 Jun 30 23:09 /dev/loop3 brw-rw---- 1 root disk 7, 4 Jun 30 23:09 /dev/loop4 brw-rw---- 1 root disk 7, 5 Jun 30 23:09 /dev/loop5 brw-rw---- 1 root disk 7, 6 Jun 30 23:09 /dev/loop6 brw-rw---- 1 root disk 7, 7 Jun 30 23:09 /dev/loop7

and they persist after umounting the iso, possibly until the next reboot.

Or until you unload the 'loop' module. -- Per Jessen, Zürich (15.2°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

13:24

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-06-30 at 23:12 -0400, Patrick Shanahan wrote:

...

Is it possible that no loop device exists until it is needed, controlled by systemd ???

The kernel can load modules when needed, it is automatic. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHRgzEACgkQtTMYHG2NR9W0jACeOEHbkJ3m2r0C9aM90XpmBs9T a3AAnAsFjhywP4063Stcg8lud56XgyZD =CKjz -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Cristian Rodríguez

3 Jul 3 Jul

03:19

On 07/01/2013 09:24 AM, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

On Sunday, 2013-06-30 at 23:12 -0400, Patrick Shanahan wrote:

...
Is it possible that no loop device exists until it is needed, controlled by systemd ???

The kernel can load modules when needed, it is automatic.

The "loop" module does not load magically like others ..and no.. systemd does nothing with the loop device except getting notified about where you have mounted the image in the filesystem so it can be umount'ed at shutdown. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

04:10

On 2013-07-03 05:19, Cristian Rodríguez wrote:

...

On 07/01/2013 09:24 AM, Carlos E. R. wrote:

...

...
The kernel can load modules when needed, it is automatic.

The "loop" module does not load magically like others

Apparently, it loaded automatically here. I have not modprobed it. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Carlos E. R.

4 Jul 4 Jul

23:00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2013-07-03 at 06:10 +0200, Carlos E. R. wrote:

...

On 2013-07-03 05:19, Cristian Rodríguez wrote:

...
On 07/01/2013 09:24 AM, Carlos E. R. wrote:

...
...
The kernel can load modules when needed, it is automatic.

The "loop" module does not load magically like others

Apparently, it loaded automatically here. I have not modprobed it.

Look. As I rebooted recently, I tried again. cer@Telcontar:~> uptime 00:57 up 1 day 1:01, 32 users, load average: 0,26, 0,21, 0,21 cer@Telcontar:~> Telcontar:/data/storage_b/Isos/isos_12.3 # lsmod | grep loop Telcontar:/data/storage_b/Isos/isos_12.3 # mount -t iso9660 -o ro,loop openSUSE-12.3-DVD-x86_64.iso mnt Telcontar:/data/storage_b/Isos/isos_12.3 # ls mnt ARCHIVES.gz GPLv2.txt README boot content.key docu gpg-pubkey-3dbdc284-4be1884d.asc ls-lR.gz openSUSE12_3_NET.exe ChangeLog GPLv3.txt SuSEgo.ico content control.xml dosutils images media.1 suse EFI INDEX.gz autorun.inf content.asc directory.yast gpg-pubkey-307e3d54-4be01a65.asc license.tar.gz openSUSE12_3_LOCAL.exe Telcontar:/data/storage_b/Isos/isos_12.3 # lsmod | grep loop loop 27944 2 Telcontar:/data/storage_b/Isos/isos_12.3 # See? I do not need to modprobe it, the module is added automatically as soon as I request a loop mount. Trust the kernel to do it right ;-) - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHV/oEACgkQtTMYHG2NR9WkogCfddjdOhzgr4N6gKc3OIDvBwZ5 vtIAnRvsFT76BdhPkK9kGc6SDtyUbE6l =DS00 -----END PGP SIGNATURE-----

Carlos E. R.

1 Jul 1 Jul

01:42

On 2013-07-01 03:19, Terry Eck wrote:

...

Hi

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

I tried to mount the iso file with the following:

mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage.

Someone asked a very similar question recently on the forums. I tried myself, and it worked (openSUSE 12.3).

...

...
# mount -t iso9660 -o ro,loop openSUSE-12.3-DVD-x86_64.iso mnt # ls mnt ARCHIVES.gz INDEX.gz content docu license.tar.gz suse

However... in your example, notice that you created "mnt/isoimage", but you are attempting to mount on "/mtn/isoimage" - that can not work. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Terry Eck

01:49

On 06/30/2013 08:42 PM, Carlos E. R. wrote:

...

On 2013-07-01 03:19, Terry Eck wrote:

...
Hi

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

I tried to mount the iso file with the following:

mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage. Someone asked a very similar question recently on the forums. I tried myself, and it worked (openSUSE 12.3).

...
...
# mount -t iso9660 -o ro,loop openSUSE-12.3-DVD-x86_64.iso mnt # ls mnt ARCHIVES.gz INDEX.gz content docu license.tar.gz suse

However... in your example, notice that you created "mnt/isoimage", but you are attempting to mount on "/mtn/isoimage" - that can not work.

Sorry but that was a typo in this email. The actual command had /mnt/isoimage. -- OpenSuSE 12.1 --- Kernel 3.1.9-1.4-desktop --- 08:45PM --- Sun 06/30/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

02:04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-06-30 at 20:19 -0500, Terry Eck wrote:

...

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

Remember that 12.1 is EOL.

...

I tried 'modprobe loop' resulting in the following: FATAL: Could not load /lib/modules/3.1.10-1.19-desktop/modules.dep: No such file or directory

cer@Telcontar:~> lsmod | grep loop loop 27944 0 cer@Telcontar:~> And I have: - -rw-r--r-- 1 root root 42920 May 25 10:02 /lib/modules/3.7.10-1.11-desktop/kernel/drivers/block/loop.ko - -rw-r--r-- 1 root root 296415 Jun 13 09:24 /lib/modules/3.7.10-1.11-desktop/modules.dep - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHQ48EACgkQtTMYHG2NR9XINQCfWUxijLLHDiOT2dBeBMQDixtU T8AAn0lQ9o1lnmrAFYW4kLGzxjCwPetR =mcSD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen

02:45

"Carlos E. R." wrote:

...

Remember that 12.1 is EOL.

Lol. Carlos, I have 10.2 running in production here. Its isolated from the net and I'm trying really hard to convince myself that I should upgrade it. But I keep losing that argument. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

03:35

New subject: [opensuse] EOL favorites (was: Problem mounting...)

On 2013-06-30 22:45 (GMT-0400) John Andersen composed:

...

...
Remember that 12.1 is EOL.

...

Lol. Carlos, I have 10.2 running in production here.

...

Its isolated from the net and I'm trying really hard to convince myself that I should upgrade it. But I keep losing that argument.

The releases I've been happiest with, in decreasing order: 11.2 11.0 10.2 10.0 11.4 After all the time I've spent with the three newer than 11.4 releases, in spite of its position in the list, I sure am glad 11.4 went Evergreen, thus keeping me from needing to "up" grade to anything newer. YaST has been rather crippled since systemd usurped sysvinit. It's supposedly being rewritten in Ruby for 13.1. I'm not going to hold my breath expecting it will actually be done that soon. Between it and other post-11.4 "improvements" it likely means I'll be staying with 11.4 until 13.2's planned GA in July 2014. It also gives KDE4 another year to maybe catch up with KDE3/TDE satisfaction. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

13:27

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-06-30 at 19:45 -0700, John Andersen wrote:

...

"Carlos E. R." <> wrote:

...

...
Remember that 12.1 is EOL.

Lol. Carlos, I have 10.2 running in production here.

Its isolated from the net and I'm trying really hard to convince myself that I should upgrade it. But I keep losing that argument.

X'-) Make sure you have a backup of the repos you use, in case you need to reinstall something or add something. They will disapear soon. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHRg8IACgkQtTMYHG2NR9XHUQCfVzNQq71lNyKH3kHUcww5CvDc oVcAn2KaUfkHznfQ4NAl7Uraoz+GNmf+ =0WMl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen

06:58

Terry Eck wrote:

...

Hi

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

I tried to mount the iso file with the following:

mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage.

System responds with: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.)

I tried 'modprobe loop' resulting in the following: FATAL: Could not load /lib/modules/3.1.10-1.19-desktop/modules.dep: No such file or directory

Could someone please give me an idea of how to solve this problem?

Try running "depmod" as root, then try mounting the iso again. -- Per Jessen, Zürich (15.0°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Terry Eck

14:53

On 07/01/2013 01:58 AM, Per Jessen wrote:

...

Terry Eck wrote:

...
Hi

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

I tried to mount the iso file with the following:

mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage.

System responds with: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.)

I tried 'modprobe loop' resulting in the following: FATAL: Could not load /lib/modules/3.1.10-1.19-desktop/modules.dep: No such file or directory

Could someone please give me an idea of how to solve this problem? Try running "depmod" as root, then try mounting the iso again.

Ran depmod as root. When that command was issued nothing was displayed in the terminal. Then ran "mount -o loop -t iso9660 file.iso /mtn/isoimage" and the following was displayed: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) Thanks, Terry -- OpenSuSE 12.1 --- Kernel 3.1.9-1.4-desktop --- 09:50AM --- Mon 07/01/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

John Andersen

15:56

On 7/1/2013 7:53 AM, Terry Eck wrote:

...

On 07/01/2013 01:58 AM, Per Jessen wrote:

...
Terry Eck wrote:

...
Hi

I use to be able to mount and iso file under previous OpenSuse version (11.3). Currently using version 12.1.

I tried to mount the iso file with the following:

mount -o loop -t iso9660 file.iso /mtn/isoimage where /mnt/isoimage was created with: mkdir -p /mnt/isoimage.

System responds with: mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.)

I tried 'modprobe loop' resulting in the following: FATAL: Could not load /lib/modules/3.1.10-1.19-desktop/modules.dep: No such file or directory

Could someone please give me an idea of how to solve this problem? Try running "depmod" as root, then try mounting the iso again.

Ran depmod as root. When that command was issued nothing was displayed in the terminal.

Then ran "mount -o loop -t iso9660 file.iso /mtn/isoimage" and the following was displayed:

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.)

Thanks, Terry

Can you confirm that you did BOTH steps as root? -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Terry Eck

2 Jul 2 Jul

02:04

On 07/01/2013 10:56 AM, John Andersen wrote:

...

On 7/1/2013 7:53 AM, Terry Eck wrote:

...
On 07/01/2013 01:58 AM, Per Jessen wrote:

...
Try running "depmod" as root, then try mounting the iso again.

Ran depmod as root. When that command was issued nothing was displayed in the terminal.

Then ran "mount -o loop -t iso9660 file.iso /mtn/isoimage" and the following was displayed:

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.)

Thanks, Terry

Can you confirm that you did BOTH steps as root?

linux-m1kc:~ # pwd /root linux-m1kc:~ # depmod linux-m1kc:~ # mount -o loop -t iso9660 grub.iso /mnt/isoimage mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) linux-m1kc:~ # I do not know how else to confirm being root! Thanks, Terry -- OpenSuSE 12.1 --- Kernel 3.1.9-1.4-desktop --- 09:00PM --- Mon 07/01/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

02:34

On 2013-07-02 04:04, Terry Eck wrote:

...

On 07/01/2013 10:56 AM, John Andersen wrote:

...

linux-m1kc:~ # pwd /root linux-m1kc:~ # depmod linux-m1kc:~ #

Silence means "success".

...

mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) linux-m1kc:~ #

Did you try "modprobe loop" after running depmod? If it fails, run "locate loop.ko". If the module is not found, there is a problem with your kernel install. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

Per Jessen

07:22

Carlos E. R. wrote:

...

On 2013-07-02 04:04, Terry Eck wrote:

...
On 07/01/2013 10:56 AM, John Andersen wrote:

...
linux-m1kc:~ # pwd /root linux-m1kc:~ # depmod linux-m1kc:~ #

Silence means "success".

...
mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) linux-m1kc:~ #

Did you try "modprobe loop" after running depmod? If it fails, run "locate loop.ko". If the module is not found, there is a problem with your kernel install.

Yes, loop.ko sems to be missing, which is pretty odd. Maybe try "find /lib/modules -name loop.ko" to verify. -- Per Jessen, Zürich (19.2°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Stephan Barth

07:33

Hi, On Tue, Jul 02, 2013 at 09:22:59AM +0200, Per Jessen wrote:

...

Yes, loop.ko sems to be missing, which is pretty odd.

Maybe try "find /lib/modules -name loop.ko" to verify.

That might only confirm the suspicion. I think the root cause is that the installed kernel is not installed properly. This can only be remedied by re-installing it or install a different one. -- Bye, Stephan Barth SUSE MaintenanceSecurity - SUSE LINUX GmbH GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Terry Eck

14:57

On 07/02/2013 02:22 AM, Per Jessen wrote:

...

Carlos E. R. wrote:

...
On 2013-07-02 04:04, Terry Eck wrote:

...
On 07/01/2013 10:56 AM, John Andersen wrote:

...
linux-m1kc:~ # pwd /root linux-m1kc:~ # depmod linux-m1kc:~ # Silence means "success".

...
mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) linux-m1kc:~ # Did you try "modprobe loop" after running depmod? If it fails, run "locate loop.ko". If the module is not found, there is a problem with your kernel install. Yes, loop.ko sems to be missing, which is pretty odd.

Maybe try "find /lib/modules -name loop.ko" to verify.

The following is copied from the terminal: eck@linux-m1kc:~> su Password: linux-m1kc:/home/eck # find /lib/modules -name loop.ko /lib/modules/3.1.10-1.29-desktop/kernel/drivers/block/loop.ko linux-m1kc:/home/eck # depmod linux-m1kc:/home/eck # modprobe loop FATAL: Module loop not found. linux-m1kc:/home/eck # locate loop.ko linux-m1kc:/home/eck # find /lib/modules -name loop.ko /lib/modules/3.1.10-1.29-desktop/kernel/drivers/block/loop.ko linux-m1kc:/home/eck # I've added blank lines after each command to make it more readable. Thanks, Terry -- OpenSuSE 12.1 --- Kernel 3.1.9-1.4-desktop --- 09:50AM --- Tue 07/02/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen

15:32

Terry Eck wrote:

...

On 07/02/2013 02:22 AM, Per Jessen wrote:

...
Carlos E. R. wrote:

...
On 2013-07-02 04:04, Terry Eck wrote:

...
On 07/01/2013 10:56 AM, John Andersen wrote:

...
linux-m1kc:~ # pwd /root linux-m1kc:~ # depmod linux-m1kc:~ # Silence means "success".

...
mount: Could not find any loop device. Maybe this kernel does not know about the loop device? (If so, recompile or `modprobe loop'.) linux-m1kc:~ # Did you try "modprobe loop" after running depmod? If it fails, run "locate loop.ko". If the module is not found, there is a problem with your kernel install. Yes, loop.ko sems to be missing, which is pretty odd.

Maybe try "find /lib/modules -name loop.ko" to verify.

The following is copied from the terminal:

eck@linux-m1kc:~> su Password:

linux-m1kc:/home/eck # find /lib/modules -name loop.ko /lib/modules/3.1.10-1.29-desktop/kernel/drivers/block/loop.ko

linux-m1kc:/home/eck # depmod

linux-m1kc:/home/eck # modprobe loop FATAL: Module loop not found.

linux-m1kc:/home/eck # locate loop.ko

linux-m1kc:/home/eck # find /lib/modules -name loop.ko /lib/modules/3.1.10-1.29-desktop/kernel/drivers/block/loop.ko

Your kernel appears to be 3.1.10-1.19-desktop (judging by your first post), but your modules are for 3.1.10-1.29-desktop. Which kernels do you have in /boot ? -- Per Jessen, Zürich (25.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Terry Eck

5 Jul 5 Jul

00:46

On 07/02/2013 10:32 AM, Per Jessen wrote:

...

Your kernel appears to be 3.1.10-1.19-desktop (judging by your first post), but your modules are for 3.1.10-1.29-desktop. Which kernels do you have in /boot ?

I believe you obtained kernel info from my signature line but that is hard wired and incorrect. the kernel in /boot is lrwxrwxrwx 1 root root 27 Jun 16 16:21 vmlinuz -> vmlinuz-3.1.10-1.29-desktop -rw-r--r-- 1 root root 4958272 Jun 7 05:06 vmlinuz-3.1.10-1.29-desktop which matches the modules. Sorry for the false information. I'm correcting the signature. -- OpenSuSE 12.1 -- Kernel 3.1.10-1.29-desktop --- 07:45PM --- Thu 07/04/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Rajko

04:59

On Thu, 04 Jul 2013 19:46:49 -0500 Terry Eck wrote: ...

...

I believe you obtained kernel info from my signature line but that is hard wired and incorrect.

It wasn't signature, but the line posted in a message body.

...

the kernel in /boot is lrwxrwxrwx 1 root root 27 Jun 16 16:21 vmlinuz -> vmlinuz-3.1.10-1.29-desktop -rw-r--r-- 1 root root 4958272 Jun 7 05:06 vmlinuz-3.1.10-1.29-desktop which matches the modules. Sorry for the false information. I'm correcting the signature.

Now that you have 3.1.10-1.29-desktop and line in initial post tells it is 3.1.10-1.19-desktop, it seems that you updated kernel. Check: uname -r to see what kernel is running. It must match installed kernel. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Terry Eck

15:17

On 07/04/2013 11:59 PM, Rajko wrote:

...

On Thu, 04 Jul 2013 19:46:49 -0500 Terry Eck wrote:

...

...
I believe you obtained kernel info from my signature line but that is hard wired and incorrect. It wasn't signature, but the line posted in a message body.

...
the kernel in /boot is lrwxrwxrwx 1 root root 27 Jun 16 16:21 vmlinuz -> vmlinuz-3.1.10-1.29-desktop -rw-r--r-- 1 root root 4958272 Jun 7 05:06 vmlinuz-3.1.10-1.29-desktop which matches the modules. Sorry for the false information. I'm correcting the signature. Now that you have 3.1.10-1.29-desktop and line in initial post tells it is 3.1.10-1.19-desktop, it seems that you updated kernel.

Check: uname -r to see what kernel is running. It must match installed kernel.

OK, you provided a clue to what went wrong, Thanks! uname -r 3.1.10-1.19-desktop This is from a boot cdrom I made quite awhile ago. It appears the kernel was updated to 3.1.10-1.29-desktop while I was still booting from the original cdrom. I booted without the cdrom and uname -r shows 3.1.10-1.29-desktop and now I can mount an iso-file. Bottom line: if something can go wrong it will! Thanks to all who replied to my original request. Terry Eck -- OpenSuSE 12.1 -- Kernel 3.1.10-1.29-desktop --- 10:05AM --- Fri 07/05/13 There are 10 types of people, those who know binary and those who don't -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

3952

Age (days ago)

3956

Last active (days ago)

List overview

Download

29 comments

9 participants

participants (9)

Carlos E. R.
Cristian Rodríguez
Felix Miata
John Andersen
Patrick Shanahan
Per Jessen
Rajko
Stephan Barth
Terry Eck