On Sat 18 Feb 2023 at 15:27:29 (+0800), lsg wrote:
> i think error msg i report is precise, i use cell phone to record screen,
> 
> https://pan.baidu.com/s/1a5ADqn1aXo5XmwcDSjVezQ?pwd=1234
> 
> this url is valid for 7 days, i am sorry picture isn't very clear.
> installer search disk for iso file, can't find suitable one, and
> display "No kernel modules found" screen

I think the heading at the top says:
"[!!] Load installer components from an installer ISO"
though ISO is a bit of a guess—it's very unclear.

> does your installer find your iso file?

Yes, as shown by these selected lines from the log.
/dev/sdb1 is the USB stick onto which I copied the log.
It plays no part in the installation.

  main-menu[274]: INFO: Menu item 'iso-scan' selected
  …
  iso-scan: devices found: '/dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5 
/dev/sda6 /dev/sda7 /dev/sda8 /dev/sdb1 /dev/sda /dev/sdb'
  iso-scan: selected_device(s)='/dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 
/dev/sda5 /dev/sda6 /dev/sda7 /dev/sda8 /dev/sdb1 /dev/sda /dev/sdb'
  iso-scan: Mounted /dev/sda1 for first pass
  …
  iso-scan: Failed mounting /dev/sda1 (from /dev/sda1) as an ISO image

and so on until:

  iso-scan: Mounted /dev/sda5 for first pass
  kernel: [   20.221192] EXT4-fs (sda5): mounted filesystem with ordered data 
mode. Opts: (null)
  iso-scan: Found ISO ./boot/debian-11.6.0-amd64-netinst.iso on /dev/sda5
  kernel: [   20.523593] ISO 9660 Extensions: Microsoft Joliet Level 3
  kernel: [   20.538714] ISO 9660 Extensions: RRIP_1991A
  iso-scan: Detected ISO with 'stable' (bullseye) distribution
  iso-scan: Detected ISO with distribution 'stable' (bullseye)
  iso-scan: Debian ISO ./boot/debian-11.6.0-amd64-netinst.iso usable
  iso-scan: Failed mounting /dev/sda5 (from /dev/sda5) as an ISO image

and it always carries on through the partitions, and then comes
back to the successful one:

  iso-scan: ISOS_FOUND='[sda5] /boot/debian-11.6.0-amd64-netinst.iso (stable - 
11.6)'
  iso-scan: Selected ISO: /boot/debian-11.6.0-amd64-netinst.iso on /dev/sda5
  kernel: [   27.639653] EXT4-fs (sda5): mounted filesystem with ordered data 
mode. Opts: (null)
  iso-scan: Mounting /hd-media/boot/debian-11.6.0-amd64-netinst.iso on /cdrom
  kernel: [   27.672606] ISO 9660 Extensions: Microsoft Joliet Level 3
  kernel: [   27.673709] ISO 9660 Extensions: RRIP_1991A
  iso-scan: Detected ISO with 'stable' (bullseye) distribution
  iso-scan: Detected ISO with distribution 'stable' (bullseye)
  …
  main-menu[274]: INFO: Menu item 'load-iso' selected
  cdrom-retriever: warning: File 
/cdrom/dists/bullseye/main/debian-installer/binary-amd64/Packages does not 
exist.
  cdrom-retriever: warning: Unable to find 
contrib/debian-installer/binary-amd64/Packages in /cdrom/dists/bullseye/Release.
  cdrom-retriever: warning: Unable to find 
contrib/debian-installer/binary-amd64/Packages.gz in 
/cdrom/dists/bullseye/Release.
  anna[2256]: DEBUG: resolver (cdrom-detect): package doesn't exist (ignored)
  anna[2256]: DEBUG: resolver (fat-modules): package doesn't exist (ignored)
  anna[2256]: DEBUG: resolver (libsystemd0): package doesn't exist (ignored)
  anna[2256]: DEBUG: resolver (scsi-modules): package doesn't exist (ignored)
  anna[2256]: DEBUG: resolver (cdrom-detect): package doesn't exist (ignored)
  anna[2256]: DEBUG: resolver (fat-modules): package doesn't exist (ignored)
  anna[2256]: DEBUG: resolver (libsystemd0): package doesn't exist (ignored)
  anna[2256]: DEBUG: resolver (scsi-modules): package doesn't exist (ignored)
  anna[2256]: DEBUG: retrieving apt-cdrom-setup 1:0.166
  anna[2256]: DEBUG: retrieving apt-mirror-setup 1:0.166
  anna[2256]: DEBUG: retrieving apt-setup-udeb 1:0.166
  anna[2256]: DEBUG: retrieving base-installer 1.206

… and now it's well under way.

> or do you really install via
> http?

Well, I would do (see below), which is why the Grub menuentry
has that label. But, to replicate your OP, I've used the ISO
debian-11.6.0-amd64-netinst.iso, and consequently my wifi won't
work (no firmware), and I haven't plugged in an ethernet cable.

> network connection isn't needed if you use hard disk
> installation method, with debian-11.6.0-amd64-netinst.iso you can
> install bare minimal debian system

Precisely, that's what it ended up with. The sequence of steps
that should be seen are:

  Language? ✓
  Location? ✓
  Keymap? ✓
  (here it searches for the ISO)
  (loading additional components)
  Firmware from wherever? NO
  Configure network? NO
  Hostname? ✓
  Domain? ✓
  Root password, username and password? ✓ ✓ ✓
  Time zone? ✓
  Partitioner: SELECTED a spare partition for /
  Without swap? YES
  (installs base system)
  Without mirror? YES
  Install what [standard]? STANDARD
  Popularity? NO
  (installs bootloader)
  (os-prober runs)
  RTC is UTC? ✓
  Remove installation before reboot: (no need, of course)

✓ means that your response is likely different from mine.
I didn't install Swap as I only had one spare partition.

With the files you mentioned in your OP:

  debian-11.6.0-amd64-netinst.iso (dated ~ Dec 17 2022)
  vmlinuz (dated ~ Dec 15 2022)
  initrd.gz (dated ~ Dec 15 2022)

the above is what should happen. (The dates on these files
might not agree if your download method does not honour the
files' metadata.)

So could you please post the output of

  $ md5sum debian-11.6.0-amd64-netinst.iso
  $ md5sum vmlinuz
  $ md5sum initrd.gz

for the files that you used, and where in the list above it is
that the process gets stuck.

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

As a partition with a base system and 5.10.0-20-amd64 kernel is
fairly useless, I booted (using the newly installed EFI/Grub) into
my production system on the machine, and renamed the ISOs' filenames
in /boot:

  debian-11.6.0-amd64-netinst.iso → debian-11.6.0-amd64-netinst.iso-hidden
  firmware-11.6.0-amd64-netinst.iso-hidden → firmware-11.6.0-amd64-netinst.iso

Then I repeated the exercise. This time, the firmware was loaded,
I configured the wifi, chose a mirror, and I installed a full
"standard system utilities" from a Debian mirror. This system is
fully up-to-date, with a 5.10.0-21-amd64 kernel. From the syslog's
first and last lines:

  Feb 19 15:07:41 syslogd started: BusyBox v1.30.1

  Feb 19 15:22:24 finish-install: info: Running 
/usr/lib/finish-install.d/94save-logs

that took all of 15 minutes.

How does this compare with a normal expert install from a USB stick?
Well, a few questions are skipped, like:

  NTP pool
  kernel metapackage
  generic/targeted initrd
  download protocol
  source repositories
  updates/backports policy
  update automation
  whether to install Grub
  where    ”    ”      ”
  so-called removable media path

and, most significant to me, no option for remote ssh install.
I'm not a preseeder, so I don't know whether a kernel parameter
on the   linux /boot/vmlinuz   line would fix that.

Cheers,
David.

Reply via email to