Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Ryan Tandy]

Hi, thanks for the quick follow-up.

On Wed, Apr 28, 2021 at 07:35:00AM +0200, Cyril Brulebois wrote:

Or are you already aware of this, and don't know how to pass the extra
option via TFTP?


The latter: I don't have any access to the bootloader (serial or 
otherwise) so I don't think I have a way to append kernel args for TFTP 
boot.


I've just remembered, though, that the config-debian script that lives 
beside the images demonstrates how to change the bootloader config, so I 
can probably do it that way if I put the installer images on disk. I'll 
try that next (pending figuring out why fw_printenv/setenv seem to be 
unhappy with my fw_env.config).

Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Cyril Brulebois]

Hi Ryan,

Ryan Tandy  (2021-04-27):
> I am booting this network-console image over TFTP... I guess there's no 
> easy way to provide the 'lowmem' boot parameter. I'd have to modify and 
> rebuild the install image (probably the initrd)?

I don't know anything about lowmem, but glancing at its code, I think
you can?


https://salsa.debian.org/installer-team/lowmem/-/blob/master/debian-installer-startup.d/S15lowmem#L112-119

Or are you already aware of this, and don't know how to pass the extra
option via TFTP?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Re: Speed up installation: increase priority of eatmydata-udeb to standard

[Cyril Brulebois]

Hi,

ValdikSS  (2021-04-28):
> eatmydata-udeb package is designed to speed up the installation process.
> However, it's not used by default and could be activated only with preseed
> file or kernel cmdline argument.
> 
> Please consider increasing eatmydata-udeb priority to standard in
> debian-installer overrides, for it to be used by default. This will speed up
> installation by an order on slower HDDs.
> 
> It will be perfect to include this change before final Bullseye ISO release.
> 
> For more information, read the post in debian-boot:
> https://lists.debian.org/debian-boot/2021/03/msg00121.html

We already have a lot of serious problems to solve in the installer;
I wouldn't want to see possible extra perturbations due to a syscall
interceptor.

The best would be to have that kind of change happen right at the
beginning of a release cycle, rather than in the last few weeks
before a release…

A compromise might be thinking about backporting the change to
bullseye once it's been tested with some D-I Bookworm Alpha 1 (but
that would also be a rather important change to backport to a stable
release…).

Happy to hear other opinions.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#987701: installation-reports: installation failed on Linkstation Pro: Out of memory during partitioning

[Ryan Tandy]

Package: installation-reports
Severity: important
Tags: d-i

Dear Maintainer,

Bullseye RC1 fails to install on my Linkstation Pro (LS-GL). It runs out 
of memory just after confirming the partitions, when it starts to format 
the disk, and the installation process gets killed. Ironically, I think 
this is happening only seconds before it would format and activate the 
swap partition.

The Linkstation Pro is an orion5x NAS with 128MB RAM. I checked the 
Installation Guide; it says that the installer's memory requirement is 
80 MB. https://www.debian.org/releases/testing/armel/ch02s05.en.html

The installation images were retrieved from: 
https://deb.debian.org/debian/dists/testing/main/installer-armel/current/images/orion5x/network-console/buffalo/lspro_ls-gl/

I have (re-)installed buster successfully. The installation process uses 
some swap (especially during 'apt-get update') but does eventually 
complete. I upgraded it to bullseye, no problem.

I am attaching the full syslog from a failed attempt at installing 
bullseye. Please let me know if I can provide any other information.

I am booting this network-console image over TFTP... I guess there's no 
easy way to provide the 'lowmem' boot parameter. I'd have to modify and 
rebuild the install image (probably the initrd)?

thanks,
Ryan
Jan  1 00:00:16 syslogd started: BusyBox v1.30.1
Jan  1 00:00:16 kernel: klogd started: BusyBox v1.30.1 (Debian 1:1.30.1-6+b1)
Jan  1 00:00:16 kernel: [0.00] Booting Linux on physical CPU 0x0
Jan  1 00:00:16 kernel: [0.00] Linux version 5.10.0-6-marvell 
(debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU 
ld (GNU Binutils for Debian) 2.35.2) #1 Debian 5.10.28-1 (2021-04-09)
Jan  1 00:00:16 kernel: [0.00] CPU: Feroceon [41069260] revision 0 
(ARMv5TEJ), cr=a005317f
Jan  1 00:00:16 kernel: [0.00] CPU: VIVT data cache, VIVT instruction 
cache
Jan  1 00:00:16 kernel: [0.00] OF: fdt: Machine model: Buffalo 
Linkstation Pro/Live
Jan  1 00:00:16 kernel: [0.00] Memory policy: Data cache writeback
Jan  1 00:00:16 kernel: [0.00] Zone ranges:
Jan  1 00:00:16 kernel: [0.00]   Normal   [mem 
0x-0x07ff]
Jan  1 00:00:16 kernel: [0.00]   HighMem  empty
Jan  1 00:00:16 kernel: [0.00] Movable zone start for each node
Jan  1 00:00:16 kernel: [0.00] Early memory node ranges
Jan  1 00:00:16 kernel: [0.00]   node   0: [mem 
0x-0x07ff]
Jan  1 00:00:16 kernel: [0.00] Initmem setup node 0 [mem 
0x-0x07ff]
Jan  1 00:00:16 kernel: [0.00] On node 0 totalpages: 32768
Jan  1 00:00:16 kernel: [0.00]   Normal zone: 256 pages used for memmap
Jan  1 00:00:16 kernel: [0.00]   Normal zone: 0 pages reserved
Jan  1 00:00:16 kernel: [0.00]   Normal zone: 32768 pages, LIFO batch:7
Jan  1 00:00:16 kernel: [0.00] pcpu-alloc: s0 r0 d32768 u32768 
alloc=1*32768
Jan  1 00:00:16 kernel: [0.00] pcpu-alloc: [0] 0 
Jan  1 00:00:16 kernel: [0.00] Built 1 zonelists, mobility grouping on. 
 Total pages: 32512
Jan  1 00:00:16 kernel: [0.00] Kernel command line: 
console=ttyS0,115200 root=/dev/sda2 rw initrd=0x00800040,15M panic=5 
BOOTVER=1.10 tftpboot=yes
Jan  1 00:00:16 kernel: [0.00] Dentry cache hash table entries: 16384 
(order: 4, 65536 bytes, linear)
Jan  1 00:00:16 kernel: [0.00] Inode-cache hash table entries: 8192 
(order: 3, 32768 bytes, linear)
Jan  1 00:00:16 kernel: [0.00] mem auto-init: stack:off, heap alloc:on, 
heap free:off
Jan  1 00:00:16 kernel: [0.00] Memory: 106908K/131072K available (4732K 
kernel code, 830K rwdata, 1312K rodata, 292K init, 224K bss, 24164K reserved, 
0K cma-reserved, 0K highmem)
Jan  1 00:00:16 kernel: [0.00] random: get_random_u32 called from 
cache_random_seq_create+0x60/0x110 with crng_init=0
Jan  1 00:00:16 kernel: [0.00] SLUB: HWalign=32, Order=0-3, 
MinObjects=0, CPUs=1, Nodes=1
Jan  1 00:00:16 kernel: [0.00] ftrace: allocating 8 entries in 44 
pages
Jan  1 00:00:16 kernel: [0.00] ftrace: allocated 44 pages with 3 groups
Jan  1 00:00:16 kernel: [0.00] NR_IRQS: 16, nr_irqs: 16, preallocated 
irqs: 16
Jan  1 00:00:16 kernel: [0.00] clocksource: orion_clocksource: mask: 
0x max_cycles: 0x, max_idle_ns: 11467562657 ns
Jan  1 00:00:16 kernel: [0.28] sched_clock: 32 bits at 166MHz, 
resolution 6ns, wraps every 12884901885ns
Jan  1 00:00:16 kernel: [0.000116] Switching to timer-based delay loop, 
resolution 6ns
Jan  1 00:00:16 kernel: [0.000349] Calibrating delay loop (skipped), value 
calculated using timer frequency.. 333.33 BogoMIPS (lpj=66)
Jan  1 00:00:16 kernel: [0.000417] pid_max: default: 32768 minimum: 301
Jan  1 00:00:16 kernel: [0.001220] LSM: Security Framework initializing
Jan  1 00:00:16 kernel: [0.001775] Yama: di

Bug#939585: marked as done (installation-reports: Unable to boot from LVM on encrypted volume - missing cryptsetup in initramfs)

[Debian Bug Tracking System]

Your message dated Wed, 28 Apr 2021 06:32:15 +0200
with message-id <20210428043215.aeytn4obsv735...@mraw.org>
and subject line Re: Bug#939585: installation-reports: confirmed with current 
installer
has caused the Debian Bug report #939585,
regarding installation-reports: Unable to boot from LVM on encrypted volume - 
missing cryptsetup in initramfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
939585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Installation using manually partioned disk by installer containing LVM on 
encrypted volume


   * What exactly did you do (or not do) that was effective (or

Manually partition drive by installer:
- primary boot partition
- encrypted volume
- LVM on encrypted volume containing root and swap partitions

Continue installation to the end.

An alternative would be trying to encrypt the whole disk. This fails in a more 
complete way.

This used to work fine with buster as testing release already.


   * What was the outcome of this action?

After reboot and some error messages about missing LVM volumes you will be 
dropped to an initramfs shell.
Obviously cryptsetup is missing although installed by d-i with no errors and 
there are no errors reported by d-i during generaton of initramfs.


   * What outcome did you expect instead?

A working installation where cryptsetup with or without plymouth asking for 
passphrase and setting up encrypted volumes.


Cause:

cryptsetup-initramfs is not installed. I was able to fix the situation by 
chroot and installing it in the end of the installation.


-- System Information:
Debian Release: bullseye/sid
  APT prefers: -
  APT policy: -
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.02-generic
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: -
--- End Message ---
--- Begin Message ---
Norbert Preining  (2021-04-27):
> On Fri, 23 Apr 2021, Cyril Brulebois wrote:
> > Please share the installer's syslog (/var/log/installer), preferably
> > compressed due to mail size limits.
> 
> Not available anymore, I trashed the whole system.
> 
> My guess is - why it worked on second run - is that one has to activate
> LVM otherwise it doesn't work. If you just add an encrypted partition
> it seems that the necessary packages are missing.

Sorry, but you're not reporting anything actionable, so I'll just stick
to my initial assessment: Arne's original problem was fixed a long while
ago:

partman-crypto (106) unstable; urgency=high

  * Merge patch by Guilhem Moulin to pull cryptsetup-initramfs instead of
cryptsetup, since the former is now responsible for the cryptsetup
initramfs integration (Closes: #930228).

 -- Cyril Brulebois   Thu, 28 Nov 2019 10:50:19 +0100

and I'm pretty sure you're not running into this problem. Installing on
encrypted LVM is one of my test scenarios and that works like a charm.

Feel free to open a fresh bug report with details if you run into this
again.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

Bug#987377: rescue-mode: when in graphical mode, locks up one prompt before the shell

[Cyril Brulebois]

Hi Étienne,

Étienne Mollier  (2021-04-26):
> Cyril Brulebois, on 2021-04-26 02:18:49 +0200:
> > Are you happy to trust me with a netboot/gtk/mini.iso build that you
> > would deploy on some USB device (like you would with a Netinst ISO,
> > except it'll need network access to download all d-i components that
> > aren't in the initramfs), to see if the problem goes away entirely for
> > you?
> 
> Sure!

Let's see if this helps!
  https://people.debian.org/~kibi/bug-987377/

For transparency, this was built from the master branch of the
debian-installer git repository, with the following command:

make -C build/ rebuild_netboot-gtk USE_UDEBS_FROM=testing

with a deb-reversion'd pango udeb stashed into build/localudebs
beforehand.

kibi@tokyo:~/debian-installer/installer$ dpkg --info 
build/localudebs/libpango1.0-udeb_1.42.4-8_amd64.udeb 
…
 Version: 1:1.42.4-8
…

just adding an epoch to make sure that the latest known good version
(1.42.4-8) is picked instead of the current one (1.46.2-3), as per:
  https://bugs.debian.org/987587


Also, thanks for all the tests so far, I've seen the follow-ups… that's
much appreciated (even if slightly frightening if the image linked above
doesn't make the problem go away altogether).


Merci,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#987699: installation-reports: bullseye background art covers kernel commandline on legacy BIOS

[Federico Grau]

Package: installation-reports
Severity: normal

Boot method: netinst ISO image for kvm VM
Image version: 
https://cdimage.debian.org/cdimage/bullseye_di_rc1/amd64/iso-cd/debian-bullseye-DI-rc1-amd64-netinst.iso
 2021-04-23
Date: 2021-04-27 21:00  UTC-4

Machine: VM
Partitions: N/A


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [E]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

The current (d-i RC1) bullseye background art covers or obfuscates the grub
kernel command line, at least on a legacy BIOS boot (likely less of an issue
with UEFI BIOS).

While it's a nice addition to include the "Debian 11" version text in the
background image, that text is currently located in the bottom left corner of
the screen which is where the kernel command line text can be if it is two
lines long.

Maybe relocate the "Debian 11" text to the top left corner of the background
image.


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="11 (bullseye) - installer build 20210415"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux saltdev14 5.10.0-6-amd64 #1 SMP Debian 5.10.28-1 (2021-04-09) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ata_generic
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL 
paravirtual graphic card [1b36:0100] (rev 04)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: 00:03.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network 
device [1af4:1000]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0001]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:04.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:05.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #1 [8086:2934] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #2 [8086:2935] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #3 [8086:2936] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB2 EHCI Controller #1 [8086:293a] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:06.0 Communication controller [0780]: Red Hat, Inc. Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:07.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block 
device [1af4:1001]
lspci -knn: Subsystem: Red Hat, Inc. Device [1af4:0002]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: Kernel modules: virtio_pci
lspci -knn: 00:08.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory 
balloon [1af4:1002]
lspci -knn: Subsystem: Red Hat,

Bug#987688: Please add more filesystem drivers to hd-media

[Phillip Susi]

Package: debian-installer
Version: 20210415

I just tried using the hd-media build to boot from an existing hard disk
and install without using removable media and was not able to do so
because I used btrfs on the hard disk, and most filesystems are packaged
as separate udebs rather than being built into the initrd.  I think it
was only iso9660, fat, and ext4 that were in there.  Please consider
moving btrfs and probably a few other filesystem modules into the
hd-media initrd so that it can be used outside of ext4 and fat.

Bug#987377: rescue-mode: when in graphical mode, locks up one prompt before the shell

[Étienne Mollier]

Hi Cyril,

Since the LVM result I caught seemed to contradict your own
findings, I did a few more tests in that configuration.  I'm
afraid I failed to identify any regular pattern, although I did
try hard to see whether things such as word wrapping might be
involved in some way, so I'm just putting a list of the locales,
VG and LV names I tested today:

Locale  Block device nameResult
--  ---  --
en_US   /dev/debian-vg/root  ok(default LVM config)
/dev/m/0 ok
/dev/vg/0ok
/dev/md/0blank (silly! for debug purpose)
/dev/mx/0blank
/dev/mm/0blank
/dev/mmx/0   ok
/dev/mmm/0   ok
/dev//0  ok
/dev//0  ok
/dev/m/0 ok
/dev/mm/0ok
--  ---  --
fr_FR   /dev/debian-vg/root  blank (default LVM config)
/dev/debian-vg/0 blank
/dev/xx-xx/0 blank
/dev/-/0 blank
/dev/x-xxx/0 blank
/dev/-/0 ok(!)
/dev/mm-mm/0 ok
/dev/x/0 ok
/dev/xxixx/0 ok
/dev/x-xx/0  ok
/dev/x-/0ok
/dev/x-x/0   ok
/dev/debianxvg/0 ok
/dev/vg/0ok
/dev//0  ok
/dev/mx/0ok
/dev/mm/0ok
/dev/debian-vg/operatingsystemblank

Thankfully, vgrename allowed me to change quickly between each
try.  I guess this is very long winded, but hope this helps.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#987682: Netboot teres installer does not accept a local file mirror

[Karl Semich]

Package: installation-reports

Boot method: sd card
Image version: bullseye
http://ftp.nl.debian.org/debian/dists/bullseye/main/installer-arm64/20210415/images/netboot/SD-card-images/partition.img.gz
and firmware.teres_i.img.gz
Date: 2021-04-27

Machine: Teres I
Processor: arm
Memory: n/a
Partitions: n/a

Output of lspci -knn (or lspci -nn): n/a

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [E]
Detect media:   [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:

The installer is forcing me to configure a wireless network before
selecting a debian mirror, such that I cannot install without wifi.
As this is the only installer for teres, it's important to be able to
use a local file mirror.

Re: problem with GPT/UEFI in debian 11 / debian 10.9 installer

[Lennart Sorensen]

On Mon, Apr 26, 2021 at 08:24:59PM +0300, Alexandru Goia wrote:
> Greetings !
> I tried to install debian 11 on my machine, but since it is a Dell
> with UEFI and GPT, i have not succeded. Still, Ubuntu 2020.10
> went ok. Can you put in debian-installer the option to format/create
> a EFI partition ?

The debian installer certainly does do that if booted in UEFI mode.
Many systems allow you to boot USB devices in legacy or UEFI mode.
You have to boot in UEFI mode to install with GPT and UEFI.  If you boot
legacy mode, then it won't.

Also you of course must be using the amd64 installer not the i386
installer (probably just about no one should use that anymore).

-- 
Len Sorensen