Hi,
Colin Williams wrote:
> I seem to have resolved the issue above after rebooting.
Congrats.
I planned to propose lsmod today, but your exploration work was faster.
Nevertheless, i wonder why the loop module was not loaded when you had
the difficulties with your script runs.
Have a nice day
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
wrote:
>
> > --
> >
> > Do you have a file
> > /dev/loop-control
> > ?
> >
> --
>
> 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
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 th
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
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/k
Hi Thomas,
It's not entirely clear that what I was trying to express was
understood. Then in short:
1) A file
./src/build/images/kukui/R94-14125.0.2021_08_05_1510-a1/chromiumos_base_image.bin
is created
2) It seems that commands use a variable called GCLIENT_ROOT and it's
value is set to /mnt/h
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 tha
Hi,
Colin Williams wrote:
> http://ix.io/3v3i
At least this shows an impressive partition table.
(Among them 5 partitions of size 512 bytes.)
> http://ix.io/3v6K
(Best to be downloaded and viewed in a text editor.)
> I believe the issues arise in
> https://github.com/drocsid/cros-scripts/blo
On Fri, Aug 06, 2021 at 09:48:29PM -0700, Colin Williams wrote:
> Hello everyone,
>
> In hindsight after looking at this much too late there were many
> mistakes in my initial mail. The issue may or may not be debian
> related and involves at least analyzing the script. There is a claim
> in the d
Hello everyone,
In hindsight after looking at this much too late there were many
mistakes in my initial mail. The issue may or may not be debian
related and involves at least analyzing the script. There is a claim
in the documentation that
Then I'll make another attempt to further expose my ignor
Hi,
The Wanderer wrote:
> It might be worth filing a documentation-level kernel bug report about
> this, or at least posting to the LKML to ask what the reasoning here is.
... together with a handful of sr and isofs bug fixes, if this was an
ideal world. {:)
I wrote:
> > (Wasn't there a way to
On 2021-08-05 at 09:04, Thomas Schmitt wrote:
> Hi,
>
>> Can someone tell me where I should look for the kernel for the
>> loopback setting?
>
> Quite exactly a year ago i learned the hard way that it's
> CONFIG_BLK_DEV_LOOP which on amd64 should be set to "m" to get /dev/loop*.
> See its descri
Hi,
> Can someone tell me where I should look for the kernel for the
> loopback setting?
Quite exactly a year ago i learned the hard way that it's
CONFIG_BLK_DEV_LOOP which on amd64 should be set to "m" to get /dev/loop*.
See its description at
https://sources.debian.org/src/linux/5.10.46-1/dri
On Thu, Aug 05, 2021 at 04:36:59AM -0700, Colin Williams wrote:
> I'm running bullseye / debian 11.0 testing. I have been running a
> script that is supposed to write a filesystem image (for chromiumOS).
> In short I'm getting the following
>
> losetup: cannot find an unused loop device
> partx: s
I'm running bullseye / debian 11.0 testing. I have been running a
script that is supposed to write a filesystem image (for chromiumOS).
In short I'm getting the following
losetup: cannot find an unused loop device
partx: stat of failed: No such file or directory
partx: stat of failed: No such fi
16 matches
Mail list logo
