Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #238311 > unrolled thread

Re: losetup: cannot find an unused loop device , kernel config of loopback device

Started by"Thomas Schmitt" <scdbackup@gmx.net>
First post2021-08-07 10:30 +0200
Last post2021-08-07 19:40 +0200
Articles 6 — 3 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: losetup: cannot find an unused loop device , kernel config of loopback device "Thomas Schmitt" <scdbackup@gmx.net> - 2021-08-07 10:30 +0200
    Re: losetup: cannot find an unused loop device , kernel config of  loopback device Colin Williams <colin.williams.seattle@gmail.com> - 2021-08-07 14:30 +0200
      Re: losetup: cannot find an unused loop device , kernel config of loopback device "Thomas Schmitt" <scdbackup@gmx.net> - 2021-08-07 15:20 +0200
        Re: losetup: cannot find an unused loop device , kernel config of  loopback device Colin Williams <colin.williams.seattle@gmail.com> - 2021-08-07 22:50 +0200
          Re: losetup: cannot find an unused loop device , kernel config of  loopback device Colin Williams <colin.williams.seattle@gmail.com> - 2021-08-08 05:50 +0200
      Re: losetup: cannot find an unused loop device , kernel config of  loopback device David Wright <deblis@lionunicorn.co.uk> - 2021-08-07 19:40 +0200

#238311 — Re: losetup: cannot find an unused loop device , kernel config of loopback device

From"Thomas Schmitt" <scdbackup@gmx.net>
Date2021-08-07 10:30 +0200
SubjectRe: losetup: cannot find an unused loop device , kernel config of loopback device
Message-ID<CJpSp-2J1-3@gated-at.bofh.it>
Hi,

Colin Williams:
> 3) When trying to create the loopback device the script tries to use a
> path
> /mnt/host/src/rc/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin
> which does not exist

The error message of losetup does not match this theory.

Did you make sure that the file really does not exist when the losetup
command fails ?
E.g. by performing
  ls -ld "${image}"
immediately before
  lb_dev=$(sudo losetup --show -f "$@" "${image}")


> Let me know if I need to re-read your email.

Is there a hard reason why you don't show the output of

  losetup -l -a

before, after, and maybe during the script run ?

(I'm not alone with this proposal. See
   https://lists.debian.org/debian-user/2021/08/msg00353.html
 which was not Cd'ed to you.
)


Have a nice day :)

Thomas

[toc] | [next] | [standalone]

#238315 — Re: losetup: cannot find an unused loop device , kernel config of loopback device

FromColin Williams <colin.williams.seattle@gmail.com>
Date2021-08-07 14:30 +0200
SubjectRe: losetup: cannot find an unused loop device , kernel config of loopback device
Message-ID<CJtCF-4WS-3@gated-at.bofh.it>
In reply to#238311
Hi Thomas,

>The error message of losetup does not match this theory.

Re-reading http://ix.io/3v6K and it does appear that possibly
/mnt/src/host/ does exist based on some of the debugging output.
Thanks for making me look back. I made this "theory" on trying to `ls
/mnt/host/src/rc/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin`
after the script had been executed. I received an error the path
didn't exist. But perhaps it was cleaned up after the script finished
executing.

>Is there a hard reason why you don't show the output of  losetup -l -a

I will now modify the script and also provide before and after below:

before:

(cr) ((b1688d0...)) colin@M00974055-VM ~/chromiumos/src/scripts $ losetup -l -a
-bash: losetup: command not found
(cr) ((b1688d0...)) colin@M00974055-VM ~/chromiumos/src/scripts $ sudo
losetup -l -a
(cr) ((b1688d0...)) colin@M00974055-VM ~/chromiumos/src/scripts $

no output appears

during:

I've added losetup here:
https://github.com/drocsid/cros-scripts/blob/feature/deb11-II/common.sh#L641

ourput after running ./build_image
https://chromium.googlesource.com/chromiumos/docs/+/main/developer_guide.md#Build-a-disk-image-for-your-board
with above changes: http://ix.io/3vfj

after:

colin@M00974055-VM:~/chromiumos/src/scripts$ cat ~/losetup-error.txt |
curl -F 'f:1=<-' ix.io
http://ix.io/3vfj
colin@M00974055-VM:~/chromiumos/src/scripts$ losetup -l -a
-bash: losetup: command not found
colin@M00974055-VM:~/chromiumos/src/scripts$ sudo losetup -l -a
[sudo] password for colin:
colin@M00974055-VM:~/chromiumos/src/scripts$

no output appears.



On Sat, Aug 7, 2021 at 1:19 AM Thomas Schmitt <scdbackup@gmx.net> wrote:
>
> Hi,
>
> Colin Williams:
> > 3) When trying to create the loopback device the script tries to use a
> > path
> > /mnt/host/src/rc/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin
> > which does not exist
>
> The error message of losetup does not match this theory.
>
> Did you make sure that the file really does not exist when the losetup
> command fails ?
> E.g. by performing
>   ls -ld "${image}"
> immediately before
>   lb_dev=$(sudo losetup --show -f "$@" "${image}")
>
>
> > Let me know if I need to re-read your email.
>
> Is there a hard reason why you don't show the output of
>
>   losetup -l -a
>
> before, after, and maybe during the script run ?
>
> (I'm not alone with this proposal. See
>    https://lists.debian.org/debian-user/2021/08/msg00353.html
>  which was not Cd'ed to you.
> )
>
>
> Have a nice day :)
>
> Thomas
>

[toc] | [prev] | [next] | [standalone]

#238318

From"Thomas Schmitt" <scdbackup@gmx.net>
Date2021-08-07 15:20 +0200
Message-ID<CJup4-5s6-7@gated-at.bofh.it>
In reply to#238315
Hi,

Colin Williams wrote:
> http://ix.io/3vfj

Where i read

  +++ sudo losetup --show -f /mnt/host/source/src/build/ima
  ges/kukui/R94-14125.0.2021_08_07_0451-a1/chromiumos_base_
  image.bin
  losetup: cannot find an unused loop device
  ++ lb_dev=
  ++ sudo losetup -l -a
  +++ sudo partx -v -d ''

Now that kills the theory about all loop devices being occupied.

I had a look into
  https://sources.debian.org/src/util-linux/2.36.1-7/sys-utils/losetup.c
where i find two occurences of
  "cannot find an unused loop device"
Each happens after a call to loopcxt_find_unused() at
  https://sources.debian.org/src/util-linux/2.36.1-7/lib/loopdev.c/#L1544
which seems to try two different methods to get the number of an unused
loop device.
No other external reason is to see for getting the losetup error message.

Any theory about bad program parameters seems unlikely.

----------------------------------------------------------------------

Do you have a file
  /dev/loop-control
?

What is listed by

  ls -ld /dev/loop*

?
(/dev/loop files do not vanish after losetup -d. So if there are none, then
it is likely that there never have been any.)

----------------------------------------------------------------------

What happens if you try to create a loop device manually ?

  not_yet_existing_file="some_file_path"
  dd if=/dev/zero bs=512 count=2 of="$not_yet_existing_file"
  sudo losetup loop0 "$not_yet_existing_file"

There should be no messages from losetup.
  sudo wc -c </dev/loop0
should yield "1024".

To clean up do:

  losetup -d /dev/loop0
  rm "$not_yet_existing_file"


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#238351 — Re: losetup: cannot find an unused loop device , kernel config of loopback device

FromColin Williams <colin.williams.seattle@gmail.com>
Date2021-08-07 22:50 +0200
SubjectRe: losetup: cannot find an unused loop device , kernel config of loopback device
Message-ID<CJBqy-13z-3@gated-at.bofh.it>
In reply to#238318
> ----------------------------------------------------------------------
>
> Do you have a file
>   /dev/loop-control
> ?
>
> What is listed by
>
>   ls -ld /dev/loop*
>

colin@M00974055-VM:~$ sudo ls  /dev/loop-control
[sudo] password for colin:
ls: cannot access '/dev/loop-control': No such file or directory
colin@M00974055-VM:~$ sudo  ls -ld /dev/loop*
ls: cannot access '/dev/loop*': No such file or directory



> ----------------------------------------------------------------------
>
> What happens if you try to create a loop device manually ?
>

not_yet_existing_file="some_file_path"
dd if=/dev/zero bs=512 count=2 of="$not_yet_existing_file"
sudo losetup loop0 "$not_yet_existing_file"

not_yet_existing_file="/tmp/does_not_exist_yet"
dd if=/dev/zero bs=512 count=2 of="$not_yet_existing_file"
sudo losetup loop0 "$not_yet_existing_file"
2+0 records in
2+0 records out
1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000187826 s, 5.5 MB/s
losetup: /dev/loop0: failed to set up loop device: No such file or directory

> There should be no messages from losetup.

But we see one above ^^

>   sudo wc -c </dev/loop0
> should yield "1024".

sudo wc -c </dev/loop0
bash: /dev/loop0: No such file or directory


> To clean up do:
>
losetup -d /dev/loop0
rm "$not_yet_existing_file"


colin@M00974055-VM:~$ sudo losetup -d /dev/loop0
losetup: /dev/loop0: failed to use device: No such device
colin@M00974055-VM:~$ rm "$not_yet_existing_file"
colin@M00974055-VM:~$

______________________________________________________________________

>
>
> Have a nice day :)
>
> Thomas


Thank you Thomas. Thanks again for looking at my issue. Not sure where
to go from here.

________________________________________________________________________

colin@M00974055-VM:~$ uname -r
5.10.0-3-amd64
colin@M00974055-VM:~$ cat /etc/debian_version
11.0colin@M00974055-VM:~$ lsmod | grep loop
colin@M00974055-VM:~$ sudo modprobe loop
colin@M00974055-VM:~$ lsmod | grep loop
loop                   36864  0
colin@M00974055-VM:~$ dd if=/dev/zero bs=512 count=2 of="$not_yet_existing_file"
2+0 records in
2+0 records out
1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000134838 s, 7.6 MB/s
colin@M00974055-VM:~$ sudo losetup loop0 "$not_yet_existing_file"

No error here ^^ Guess we needed to load the module?

colin@M00974055-VM:~$ sudo wc -c </dev/loop0
bash: /dev/loop0: Permission denied
colin@M00974055-VM:~$ sudo -i
root@M00974055-VM:~# wc -c </dev/loop0
1024
root@M00974055-VM:


wc -c </dev/loop0
1024
root@M00974055-VM:~# losetup -d /dev/loop0
rm "$not_yet_existing_file"
rm: cannot remove '': No such file or directory

I think we are on to something after loading the module

_____________________________________________________________

I re-ran the script after the module. It looks like it's making more
progress but still getting an eventual error related to loopback
devices:

http://ix.io/3vi8


^^ This is probably the most useful to look at moving forward ^^

Now I will re-run the inital commands below

sudo ls -ld /dev/loop*
brw-rw---- 1 root disk   7,   0 Aug  7 13:07 /dev/loop0
brw-rw---- 1 root disk 259,  12 Aug  7 13:07 /dev/loop0p1
brw-rw---- 1 root disk 259,  21 Aug  7 13:07 /dev/loop0p10
brw-rw---- 1 root disk 259,  22 Aug  7 13:07 /dev/loop0p11
brw-rw---- 1 root disk 259,  23 Aug  7 13:07 /dev/loop0p12
brw-rw---- 1 root disk 259,  13 Aug  7 13:07 /dev/loop0p2
brw-rw---- 1 root disk 259,  14 Aug  7 13:07 /dev/loop0p3
brw-rw---- 1 root disk 259,  15 Aug  7 13:07 /dev/loop0p4
brw-rw---- 1 root disk 259,  16 Aug  7 13:07 /dev/loop0p5
brw-rw---- 1 root disk 259,  17 Aug  7 13:07 /dev/loop0p6
brw-rw---- 1 root disk 259,  18 Aug  7 13:07 /dev/loop0p7
brw-rw---- 1 root disk 259,  19 Aug  7 13:07 /dev/loop0p8
brw-rw---- 1 root disk 259,  20 Aug  7 13:07 /dev/loop0p9
brw-rw---- 1 root disk   7,   1 Aug  7 13:01 /dev/loop1
brw-rw---- 1 root disk 259,   0 Aug  7 13:01 /dev/loop1p1
brw-rw---- 1 root disk 259,   9 Aug  7 13:01 /dev/loop1p10
brw-rw---- 1 root disk 259,  10 Aug  7 13:01 /dev/loop1p11
brw-rw---- 1 root disk 259,  11 Aug  7 13:01 /dev/loop1p12
brw-rw---- 1 root disk 259,   1 Aug  7 13:01 /dev/loop1p2
brw-rw---- 1 root disk 259,   2 Aug  7 13:01 /dev/loop1p3
brw-rw---- 1 root disk 259,   3 Aug  7 13:01 /dev/loop1p4
brw-rw---- 1 root disk 259,   4 Aug  7 13:01 /dev/loop1p5
brw-rw---- 1 root disk 259,   5 Aug  7 13:01 /dev/loop1p6
brw-rw---- 1 root disk 259,   6 Aug  7 13:01 /dev/loop1p7
brw-rw---- 1 root disk 259,   7 Aug  7 13:01 /dev/loop1p8
brw-rw---- 1 root disk 259,   8 Aug  7 13:01 /dev/loop1p9
brw-rw---- 1 root disk   7,   2 Aug  7 13:09 /dev/loop2
brw-rw---- 1 root disk 259,  24 Aug  7 13:09 /dev/loop2p1
brw-rw---- 1 root disk 259,  33 Aug  7 13:09 /dev/loop2p10
brw-rw---- 1 root disk 259,  34 Aug  7 13:09 /dev/loop2p11
brw-rw---- 1 root disk 259,  35 Aug  7 13:09 /dev/loop2p12
brw-rw---- 1 root disk 259,  25 Aug  7 13:09 /dev/loop2p2
brw-rw---- 1 root disk 259,  26 Aug  7 13:09 /dev/loop2p3
brw-rw---- 1 root disk 259,  27 Aug  7 13:09 /dev/loop2p4
brw-rw---- 1 root disk 259,  28 Aug  7 13:09 /dev/loop2p5
brw-rw---- 1 root disk 259,  29 Aug  7 13:09 /dev/loop2p6
brw-rw---- 1 root disk 259,  30 Aug  7 13:09 /dev/loop2p7
brw-rw---- 1 root disk 259,  31 Aug  7 13:09 /dev/loop2p8
brw-rw---- 1 root disk 259,  32 Aug  7 13:09 /dev/loop2p9
brw-rw---- 1 root disk   7,   3 Aug  7 12:59 /dev/loop3
brw-rw---- 1 root disk   7,   4 Aug  7 12:59 /dev/loop4
brw-rw---- 1 root disk   7,   5 Aug  7 12:59 /dev/loop5
brw-rw---- 1 root disk   7,   6 Aug  7 12:59 /dev/loop6
brw-rw---- 1 root disk   7,   7 Aug  7 12:59 /dev/loop7
crw-rw---- 1 root disk  10, 237 Aug  7 12:59 /dev/loop-control
(cr) (feature/deb11-II) colin@M00974055-VM ~/chromiumos/src/scripts $
sudo ls /dev/loop-control
/dev/loop-control


_________________________________________________________________

[toc] | [prev] | [next] | [standalone]

#238355 — Re: losetup: cannot find an unused loop device , kernel config of loopback device

FromColin Williams <colin.williams.seattle@gmail.com>
Date2021-08-08 05:50 +0200
SubjectRe: losetup: cannot find an unused loop device , kernel config of loopback device
Message-ID<CJHYZ-53g-1@gated-at.bofh.it>
In reply to#238351
I seem to have resolved the issue above after rebooting. Thanks for
helping to debug Thomas and everyone.

On Sat, Aug 7, 2021 at 1:29 PM Colin Williams
<colin.williams.seattle@gmail.com> wrote:
>
> > ----------------------------------------------------------------------
> >
> > Do you have a file
> >   /dev/loop-control
> > ?
> >
> > What is listed by
> >
> >   ls -ld /dev/loop*
> >
>
> colin@M00974055-VM:~$ sudo ls  /dev/loop-control
> [sudo] password for colin:
> ls: cannot access '/dev/loop-control': No such file or directory
> colin@M00974055-VM:~$ sudo  ls -ld /dev/loop*
> ls: cannot access '/dev/loop*': No such file or directory
>
>
>
> > ----------------------------------------------------------------------
> >
> > What happens if you try to create a loop device manually ?
> >
>
> not_yet_existing_file="some_file_path"
> dd if=/dev/zero bs=512 count=2 of="$not_yet_existing_file"
> sudo losetup loop0 "$not_yet_existing_file"
>
> not_yet_existing_file="/tmp/does_not_exist_yet"
> dd if=/dev/zero bs=512 count=2 of="$not_yet_existing_file"
> sudo losetup loop0 "$not_yet_existing_file"
> 2+0 records in
> 2+0 records out
> 1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000187826 s, 5.5 MB/s
> losetup: /dev/loop0: failed to set up loop device: No such file or directory
>
> > There should be no messages from losetup.
>
> But we see one above ^^
>
> >   sudo wc -c </dev/loop0
> > should yield "1024".
>
> sudo wc -c </dev/loop0
> bash: /dev/loop0: No such file or directory
>
>
> > To clean up do:
> >
> losetup -d /dev/loop0
> rm "$not_yet_existing_file"
>
>
> colin@M00974055-VM:~$ sudo losetup -d /dev/loop0
> losetup: /dev/loop0: failed to use device: No such device
> colin@M00974055-VM:~$ rm "$not_yet_existing_file"
> colin@M00974055-VM:~$
>
> ______________________________________________________________________
>
> >
> >
> > Have a nice day :)
> >
> > Thomas
>
>
> Thank you Thomas. Thanks again for looking at my issue. Not sure where
> to go from here.
>
> ________________________________________________________________________
>
> colin@M00974055-VM:~$ uname -r
> 5.10.0-3-amd64
> colin@M00974055-VM:~$ cat /etc/debian_version
> 11.0colin@M00974055-VM:~$ lsmod | grep loop
> colin@M00974055-VM:~$ sudo modprobe loop
> colin@M00974055-VM:~$ lsmod | grep loop
> loop                   36864  0
> colin@M00974055-VM:~$ dd if=/dev/zero bs=512 count=2 of="$not_yet_existing_file"
> 2+0 records in
> 2+0 records out
> 1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000134838 s, 7.6 MB/s
> colin@M00974055-VM:~$ sudo losetup loop0 "$not_yet_existing_file"
>
> No error here ^^ Guess we needed to load the module?
>
> colin@M00974055-VM:~$ sudo wc -c </dev/loop0
> bash: /dev/loop0: Permission denied
> colin@M00974055-VM:~$ sudo -i
> root@M00974055-VM:~# wc -c </dev/loop0
> 1024
> root@M00974055-VM:
>
>
> wc -c </dev/loop0
> 1024
> root@M00974055-VM:~# losetup -d /dev/loop0
> rm "$not_yet_existing_file"
> rm: cannot remove '': No such file or directory
>
> I think we are on to something after loading the module
>
> _____________________________________________________________
>
> I re-ran the script after the module. It looks like it's making more
> progress but still getting an eventual error related to loopback
> devices:
>
> http://ix.io/3vi8
>
>
> ^^ This is probably the most useful to look at moving forward ^^
>
> Now I will re-run the inital commands below
>
> sudo ls -ld /dev/loop*
> brw-rw---- 1 root disk   7,   0 Aug  7 13:07 /dev/loop0
> brw-rw---- 1 root disk 259,  12 Aug  7 13:07 /dev/loop0p1
> brw-rw---- 1 root disk 259,  21 Aug  7 13:07 /dev/loop0p10
> brw-rw---- 1 root disk 259,  22 Aug  7 13:07 /dev/loop0p11
> brw-rw---- 1 root disk 259,  23 Aug  7 13:07 /dev/loop0p12
> brw-rw---- 1 root disk 259,  13 Aug  7 13:07 /dev/loop0p2
> brw-rw---- 1 root disk 259,  14 Aug  7 13:07 /dev/loop0p3
> brw-rw---- 1 root disk 259,  15 Aug  7 13:07 /dev/loop0p4
> brw-rw---- 1 root disk 259,  16 Aug  7 13:07 /dev/loop0p5
> brw-rw---- 1 root disk 259,  17 Aug  7 13:07 /dev/loop0p6
> brw-rw---- 1 root disk 259,  18 Aug  7 13:07 /dev/loop0p7
> brw-rw---- 1 root disk 259,  19 Aug  7 13:07 /dev/loop0p8
> brw-rw---- 1 root disk 259,  20 Aug  7 13:07 /dev/loop0p9
> brw-rw---- 1 root disk   7,   1 Aug  7 13:01 /dev/loop1
> brw-rw---- 1 root disk 259,   0 Aug  7 13:01 /dev/loop1p1
> brw-rw---- 1 root disk 259,   9 Aug  7 13:01 /dev/loop1p10
> brw-rw---- 1 root disk 259,  10 Aug  7 13:01 /dev/loop1p11
> brw-rw---- 1 root disk 259,  11 Aug  7 13:01 /dev/loop1p12
> brw-rw---- 1 root disk 259,   1 Aug  7 13:01 /dev/loop1p2
> brw-rw---- 1 root disk 259,   2 Aug  7 13:01 /dev/loop1p3
> brw-rw---- 1 root disk 259,   3 Aug  7 13:01 /dev/loop1p4
> brw-rw---- 1 root disk 259,   4 Aug  7 13:01 /dev/loop1p5
> brw-rw---- 1 root disk 259,   5 Aug  7 13:01 /dev/loop1p6
> brw-rw---- 1 root disk 259,   6 Aug  7 13:01 /dev/loop1p7
> brw-rw---- 1 root disk 259,   7 Aug  7 13:01 /dev/loop1p8
> brw-rw---- 1 root disk 259,   8 Aug  7 13:01 /dev/loop1p9
> brw-rw---- 1 root disk   7,   2 Aug  7 13:09 /dev/loop2
> brw-rw---- 1 root disk 259,  24 Aug  7 13:09 /dev/loop2p1
> brw-rw---- 1 root disk 259,  33 Aug  7 13:09 /dev/loop2p10
> brw-rw---- 1 root disk 259,  34 Aug  7 13:09 /dev/loop2p11
> brw-rw---- 1 root disk 259,  35 Aug  7 13:09 /dev/loop2p12
> brw-rw---- 1 root disk 259,  25 Aug  7 13:09 /dev/loop2p2
> brw-rw---- 1 root disk 259,  26 Aug  7 13:09 /dev/loop2p3
> brw-rw---- 1 root disk 259,  27 Aug  7 13:09 /dev/loop2p4
> brw-rw---- 1 root disk 259,  28 Aug  7 13:09 /dev/loop2p5
> brw-rw---- 1 root disk 259,  29 Aug  7 13:09 /dev/loop2p6
> brw-rw---- 1 root disk 259,  30 Aug  7 13:09 /dev/loop2p7
> brw-rw---- 1 root disk 259,  31 Aug  7 13:09 /dev/loop2p8
> brw-rw---- 1 root disk 259,  32 Aug  7 13:09 /dev/loop2p9
> brw-rw---- 1 root disk   7,   3 Aug  7 12:59 /dev/loop3
> brw-rw---- 1 root disk   7,   4 Aug  7 12:59 /dev/loop4
> brw-rw---- 1 root disk   7,   5 Aug  7 12:59 /dev/loop5
> brw-rw---- 1 root disk   7,   6 Aug  7 12:59 /dev/loop6
> brw-rw---- 1 root disk   7,   7 Aug  7 12:59 /dev/loop7
> crw-rw---- 1 root disk  10, 237 Aug  7 12:59 /dev/loop-control
> (cr) (feature/deb11-II) colin@M00974055-VM ~/chromiumos/src/scripts $
> sudo ls /dev/loop-control
> /dev/loop-control
>
>
> _________________________________________________________________

[toc] | [prev] | [next] | [standalone]

#238346 — Re: losetup: cannot find an unused loop device , kernel config of loopback device

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2021-08-07 19:40 +0200
SubjectRe: losetup: cannot find an unused loop device , kernel config of loopback device
Message-ID<CJysG-7Mg-5@gated-at.bofh.it>
In reply to#238315
On Sat 07 Aug 2021 at 05:03:10 (-0700), Colin Williams wrote:
> >The error message of losetup does not match this theory.
> 
> Re-reading http://ix.io/3v6K and it does appear that possibly
> /mnt/src/host/ does exist based on some of the debugging output.
> Thanks for making me look back. I made this "theory" on trying to `ls
> /mnt/host/src/rc/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin`

                ↑↑

Is this a typo. This is the second time of posting:

> after the script had been executed. I received an error the path
> didn't exist. But perhaps it was cleaned up after the script finished
> executing.
> 
> On Sat, Aug 7, 2021 at 1:19 AM Thomas Schmitt <scdbackup@gmx.net> wrote:
> > Colin Williams:
> > > 3) When trying to create the loopback device the script tries to use a
> > > path
> > > /mnt/host/src/rc/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin
> > > which does not exist

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web