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
ath
> 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 wrote:
> > Colin Williams:
> > > 3) When trying to create the loopback device the script tries to use a
> > > pa
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
ot 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 wrote:
>
> Hi,
>
> Colin Williams:
> > 3) When trying to create the loopba
et to /mnt/host/src
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
4) I'm stuck trying to figure out why GCLIENT_ROOT can't be set to the
actua
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 y
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
--board=${BOARD}
--noenable_rootfs_verification dev whose output is shown in
http://ix.io/3v3i
4) I assume the script is supposed to create a file used as a loopback
device to write the image contents
5) The issue then might likely be script related and not debian related
6) I also posted to the chromium-dev google gro
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
"m" to get /dev/loop*.
> See its description at
> https://sources.debian.org/src/linux/5.10.46-1/drivers/block/Kconfig/#L174
>
> But i'm somewhat puzzled by this statement at the end
> "Most users will answer N here."
That does seem odd; at least in the mo
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
properly, it is quite simple if you need common settings.
Hi,
i am having trouble with my network manager,
when i do `ifconfig` i can't see loopback device although it shows my
machine's ip ,mac address and other info.
also,i cant perform
`#ifdown eth0` , ` #ifdown lo ` ,`
On Thu, Dec 28, 2006 at 03:02:43PM +0800, Trace Green wrote:
> Hello, I have one question to ask:
>
> When I try to use Knoppix 5.0 liveCD, I can mount any of
> my partitoin using loopback device, that's say:
>
> mount -t vfat -o offset=`expr 234567821 "*" 512` /
Hello, I have one question to ask:
When I try to use Knoppix 5.0 liveCD, I can mount any of my partitoin
using loopback device, that's say:
mount -t vfat -o offset=`expr 234567821 "*" 512` /dev/hda /mnt/hda5 as
an example. But in my own Debian system . I can't do th
Hi,
maybe you have an initial ramdisk which contains the module for your scsi
controller.
If not, compile the same kernle, without the loopback device, and see what
goes wrong.
Greetz,
Sebastiaan
On Tue, 13 Mar 2001, Scott E.Graves wrote:
> Why is it necessary to have the loopback device
On Tue, Mar 13, 2001 at 03:13:45AM -0600, Scott E. Graves wrote:
> Why is it necessary to have the loopback device in order to boot Linux from a
> SCSI controller? I've been searching for the answer, but can't seem to find
> any information.
Why do you think it's necessa
Why is it necessary to have the loopback device in order to boot Linux from a
SCSI controller? I've been searching for the answer, but can't seem to find
any information.
Scott
Hello,
I am interested in helping a friend install Debian. His father
is unsure of repartioning and trying Linux. I thought about using distro's
like PhatLinux or WinLinux, which install to a disk image instead of a
raw partition, but they just aren't debian. Is there already boot
disks/in
s i was wondering if there
was
dhamil >> any complications that anyone has encountered with having all 8 (or
dhamil >> perhaps more?) in use, they won't be very active but i've never worked
dhamil >> with the loopback device till today, so im not sure what to
dhamil &
same time have all the files
> there. I see there are 8 loopback devices i was wondering if there was
> any complications that anyone has encountered with having all 8 (or
> perhaps more?) in use, they won't be very active but i've never worked
> with the loopback device
that anyone has encountered with having all 8 (or
perhaps more?) in use, they won't be very active but i've never worked
with the loopback device till today, so im not sure what to
expect. Running kernel 2.2.10 debian slink
thanks!
nate
[mai
amm)
> CD-ROM from Cheapbytes. What I want to do is install Debian onto my D:
> hard drive partition in a file using the loopback device. The problem
> is that the Debian installer program seems hard-wired to offer me only
> /dev/hda1 but not /dev/loop0. I can switch to the second vir
amm)
> CD-ROM from Cheapbytes. What I want to do is install Debian onto my D:
> hard drive partition in a file using the loopback device. The problem
> is that the Debian installer program seems hard-wired to offer me only
> /dev/hda1 but not /dev/loop0. I can switch to the second vir
install Debian onto my D:
hard drive partition in a file using the loopback device. The problem
is that the Debian installer program seems hard-wired to offer me only
/dev/hda1 but not /dev/loop0. I can switch to the second virtual console
and mount the D: drive and use losetup to associate a loopback
29 matches
Mail list logo
