[arch-releng] module 'loop' not loaded

newer
[arch-releng] [PATCH] [archiso]...

older
[arch-releng] ISO 2014.11.01:...

Christian Hesse

12 Nov 2014 12 Nov '14

6:16 a.m.

Hello everybody, I just built a fresh image that fails to boot with: losetup: cannot find an unused loop device Looks like modules 'loop' is no longer loaded automatically when needed. It is included in initramfs, though. Any idea what package changed it's behavior? Forcing to load the module is easy, but what's the clean way to fix this? -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];) putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}

Attachments:

attachment.sig (application/pgp-signature — 473 bytes)

Show replies by date

Gerardo Exequiel Pozzi

14 Nov 14 Nov

12:22 a.m.

On 11/12/2014 03:16 AM, Christian Hesse wrote:

...

Hello everybody,

I just built a fresh image that fails to boot with:

losetup: cannot find an unused loop device

Looks like modules 'loop' is no longer loaded automatically when needed. It is included in initramfs, though. Any idea what package changed it's behavior? Forcing to load the module is easy, but what's the clean way to fix this?

maybe systemd, maybe kmod... also there is a error about missing hwdb.bin in initramfs maybe related, maybe not, i need some time to research... use earlymodules=loop for now.

Karol Blazewicz

12:57 a.m.

On Fri, Nov 14, 2014 at 1:22 AM, Gerardo Exequiel Pozzi wrote:

...

On 11/12/2014 03:16 AM, Christian Hesse wrote:

...
Hello everybody,

I just built a fresh image that fails to boot with:

losetup: cannot find an unused loop device

Looks like modules 'loop' is no longer loaded automatically when needed. It is included in initramfs, though. Any idea what package changed it's behavior? Forcing to load the module is easy, but what's the clean way to fix this?

maybe systemd, maybe kmod... also there is a error about missing hwdb.bin in initramfs maybe related, maybe not, i need some time to research...

use earlymodules=loop for now.

Not sure if helpful / related, but there's a hwdb.bin thread: https://bbs.archlinux.org/viewtopic.php?id=189536

Dave Reisner

1:43 a.m.

On Thu, Nov 13, 2014 at 09:22:49PM -0300, Gerardo Exequiel Pozzi wrote:

...

On 11/12/2014 03:16 AM, Christian Hesse wrote:

...
Hello everybody,

I just built a fresh image that fails to boot with:

losetup: cannot find an unused loop device

Looks like modules 'loop' is no longer loaded automatically when needed. It is included in initramfs, though. Any idea what package changed it's behavior? Forcing to load the module is easy, but what's the clean way to fix this?

maybe systemd, maybe kmod... also there is a error about missing hwdb.bin in initramfs maybe related, maybe not, i need some time to research...

use earlymodules=loop for now.

Looks pretty straight-forward. /run/tmpfiles.d/kmod.conf is generated, but systemd-tmpfiles isn't included in the initramfs. d

Gerardo Exequiel Pozzi

4:06 a.m.

On 11/13/2014 10:43 PM, Dave Reisner wrote:

...

On Thu, Nov 13, 2014 at 09:22:49PM -0300, Gerardo Exequiel Pozzi wrote:

...
On 11/12/2014 03:16 AM, Christian Hesse wrote:

...
Hello everybody,

I just built a fresh image that fails to boot with:

losetup: cannot find an unused loop device

Looks like modules 'loop' is no longer loaded automatically when needed. It is included in initramfs, though. Any idea what package changed it's behavior? Forcing to load the module is easy, but what's the clean way to fix this?

maybe systemd, maybe kmod... also there is a error about missing hwdb.bin in initramfs maybe related, maybe not, i need some time to research...

use earlymodules=loop for now.

Looks pretty straight-forward. /run/tmpfiles.d/kmod.conf is generated, but systemd-tmpfiles isn't included in the initramfs.

d

Yes, is here, but does nothing, none of the static devices are created. [rootfs /]# ls -l /dev/fuse /dev/loop-control /dev/mapper/control ls: /dev/fuse: No such file or directory ls: /dev/loop-control: No such file or directory ls: /dev/mapper/control: No such file or directory [rootfs /]# systemd-tmpfiles --prefix=/dev --create --same thing--

Tom Gundersen

12:25 p.m.

Probably caused by kmod being more recent than systemd? With current kmod, tmpfiles needs to be passed --boot to get the device nodes created (which the must recent systemd does). On 14 Nov 2014 05:06, "Gerardo Exequiel Pozzi" wrote:

...

On 11/13/2014 10:43 PM, Dave Reisner wrote:

...
On Thu, Nov 13, 2014 at 09:22:49PM -0300, Gerardo Exequiel Pozzi wrote:

...
On 11/12/2014 03:16 AM, Christian Hesse wrote:

...
Hello everybody,

I just built a fresh image that fails to boot with:

losetup: cannot find an unused loop device

Looks like modules 'loop' is no longer loaded automatically when needed. It is included in initramfs, though. Any idea what package changed it's behavior? Forcing to load the module is easy, but what's the clean way to fix this?

maybe systemd, maybe kmod... also there is a error about missing hwdb.bin in initramfs maybe related, maybe not, i need some time to research...

use earlymodules=loop for now.

Looks pretty straight-forward. /run/tmpfiles.d/kmod.conf is generated, but systemd-tmpfiles isn't included in the initramfs.

d

Yes, is here, but does nothing, none of the static devices are created.

[rootfs /]# ls -l /dev/fuse /dev/loop-control /dev/mapper/control ls: /dev/fuse: No such file or directory ls: /dev/loop-control: No such file or directory ls: /dev/mapper/control: No such file or directory

[rootfs /]# systemd-tmpfiles --prefix=/dev --create

--same thing--

Gerardo Exequiel Pozzi

12:45 p.m.

On 11/14/2014 09:25 AM, Tom Gundersen wrote:

...

Probably caused by kmod being more recent than systemd? With current kmod, tmpfiles needs to be passed --boot to get the device nodes created (which the must recent systemd does).

Yes, this fixes the issue. So udev hook in systemd package must be fixed. Thanks.

...

On 14 Nov 2014 05:06, "Gerardo Exequiel Pozzi" wrote:

...
On 11/13/2014 10:43 PM, Dave Reisner wrote:

...
On Thu, Nov 13, 2014 at 09:22:49PM -0300, Gerardo Exequiel Pozzi wrote:

...
On 11/12/2014 03:16 AM, Christian Hesse wrote:

...
Hello everybody,

I just built a fresh image that fails to boot with:

losetup: cannot find an unused loop device

Looks like modules 'loop' is no longer loaded automatically when needed. It is included in initramfs, though. Any idea what package changed it's behavior? Forcing to load the module is easy, but what's the clean way to fix this?

maybe systemd, maybe kmod... also there is a error about missing hwdb.bin in initramfs maybe related, maybe not, i need some time to research...

use earlymodules=loop for now.

Looks pretty straight-forward. /run/tmpfiles.d/kmod.conf is generated, but systemd-tmpfiles isn't included in the initramfs.

d

Yes, is here, but does nothing, none of the static devices are created.

[rootfs /]# ls -l /dev/fuse /dev/loop-control /dev/mapper/control ls: /dev/fuse: No such file or directory ls: /dev/loop-control: No such file or directory ls: /dev/mapper/control: No such file or directory

[rootfs /]# systemd-tmpfiles --prefix=/dev --create

--same thing--

Dave Reisner

3:34 p.m.

On Fri, Nov 14, 2014 at 01:25:08PM +0100, Tom Gundersen wrote:

...

Probably caused by kmod being more recent than systemd? With current kmod, tmpfiles needs to be passed --boot to get the device nodes created (which the must recent systemd does).

Ah yes, that's indeed missing from the udev hook. Added locally, I'll push out with the next systemd package (or shortly before EOM, whichever is first).

3450

Age (days ago)

3452

Last active (days ago)

List overview

Download

7 comments

5 participants

participants (5)

Christian Hesse
Dave Reisner
Gerardo Exequiel Pozzi
Karol Blazewicz
Tom Gundersen

[arch-releng] module 'loop' not loaded

tags

participants (5)