- Package:
- installation-reports
- Source:
- installation-reports
- Submitter:
- Bud Heal
- Date:
- 2023-03-06 06:57:14 UTC
- Severity:
- normal
Boot method: DVD (3/2/2023) then daily CD (3/4/2023) Image version: debian-testing-amd64-DVD-1.jigdo <https://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/debian-testing-amd64-DVD-1.jigdo> debian-testing-amd64-netinst.jigdo <https://cdimage.debian.org/cdimage/daily-builds/daily/20230304-7/amd64/jigdo-cd/debian-testing-amd64-netinst.jigdo> debian-testing-amd64-netinst.template <https://cdimage.debian.org/cdimage/daily-builds/daily/20230304-7/amd64/jigdo-cd/debian-testing-amd64-netinst.template> Date: 3/2/2023 (into 3/3/2023) and 3/4/2023 Machine: Acer Nitro 5 Processor: i7, 14-core Memory: 32GB Partitions: too hard to pick up - simple partition on a 4TB M.2 - with the DVD install, 4TB 2.5" SATA - in each case the partitions set up were identical Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [O] Detect media: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system: [O] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] Overall install: [E] Comments/Problems: I intend to mirror the SATA and the M.2 4TB - the installer still does not support encrypted partitions - unless it is setting up a new one. The installer finishes and reboots but the reboot immediately aborts: /dev/mapper/...-vg-root has unsupported feature(s): FEATURE_C12 e2fsck: Get a newer [copy] of e2fsck! It was not clear how to obtain an updated e2fsck and how to insert it into the workflow; I can wait for the next (pre-)release. The daily CD's template may have been mismatched to the jigdo - jigdo-lite prompted for '42' in lieu of 'OK'. The install complained about /media/lairdheal/USB DISK/iwlwifi-so-a0-hr-b0-71.ucode (which I found it on github) and 72 (which I found in firmware-iwlwifi_20230210-1_all.deb) The installer did not open the .deb to use its contents. Since I was not using wifi, I did not bother to unpack it either. It looks much neater than the wild goose chase when I set up this HP Omen in 2020 or 2021. Maybe the 4TB partitions are throwing the monkey wrench into the e2fsck works. The installer said that was the maximum.
Hi, and thanks for your report. Bud Heal <budheal508@gmail.com> (2023-03-05): Why not using the official release? You wouldn't have run into the e2fsprogs problems that have been plaguing unstable for weeks (a fix was only uploaded hours ago). I'm not sure what you mean by that. See #1031622, #1030939, etc. Using an official release would have avoided running into that… No idea about that particular bit. Can you please share the whole /var/log/installer/syslog file (attaching it compressed)? iwlwifi requests many files (several dozens…), but it should be happy once the firmware-iwlwifi found on the installation image is found and unpacked. You shouldn't have to touch any files, found on GitHub or in Debian packages. Cheers,
Thank you for telling me to try again! Now I can access the installer's syslog, which I attach, and a picture of the installer asking for iwlwifi files. # apt-get install firmware-iwlwifi reports the latest is installed. I did try the Bullseye DVDs which installed nicely, but the reboot lopped, complaining about USB. I did not try the last Bookworm DVD set, starting at the latest weekly set. Here, RAID 1 was set on the large partitions but I was not confident that the installer would mount them as encrypted. In the past, I have wished the installer would mount encrypted partitions and installed there, Perhaps the Debian repository was shut down before an dist upgrade, and although I tried to supply the needed files, the installer or apt gave up and I spent days downloading and manually installing .deb files, one dependency at a time. Then a dist upgrade aborted and I had even more fun, starting with the standalone shell. The installer can show its fragility. Bullseye installed but looped with a message about an USB error. I did not try the second bookworm beta. jigdo-lite said, maybe the daily .template is mismatched to the .jigdo, enter '42' to use it anyway. And to you. Laird Heal