Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
hard disk installation method fails
82 views
Skip to first unread message
lsg
Feb 16, 2023, 4:20:06 PM2/16/23
to
this is quite unbelievable, it's most widely-used platform: amd64
installer says "No kernel modules found", probably due to kernel mismatch
debian-11.6.0-amd64-netinst.iso is at sdb1, vfat partition, i've checked
it with sha256sum
vmlinuz and initrd.gz are copied from:
http://ftp.sunet.se/debian/dists/bullseye/main/installer-amd64/current/images/hd-media/
installer says "No kernel modules found", probably due to kernel mismatch
debian-11.6.0-amd64-netinst.iso is at sdb1, vfat partition, i've checked
it with sha256sum
vmlinuz and initrd.gz are copied from:
http://ftp.sunet.se/debian/dists/bullseye/main/installer-amd64/current/images/hd-media/
Charles Curley
Feb 16, 2023, 10:20:06 PM2/16/23
to
able to boot directly to the iso image. Depending on how talented your
computer's firmware is, you may have to copy the iso image to sdb, not
sdb1. E.g.:
dd if=<iso.image.file>.iso of=/dev/sdX
What instructions did you start with? Exact URL, please.
I've been playing with a separate partition to house a Debian installer
ISO should I ever need it for rescue or re-installation. But that
depends on having grub installed and a suitable entry for the d-i iso
image. If that's what you want to do, I can help with that also.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
lsg
Feb 17, 2023, 12:10:06 AM2/17/23
to
On 2/16/23 22:10, Charles Curley wrote:
> You shouldn't need separate vmlinuz and initrd.gz files. You should be
> able to boot directly to the iso image. Depending on how talented your
> computer's firmware is, you may have to copy the iso image to sdb, not
> sdb1. E.g.:
>
> dd if=<iso.image.file>.iso of=/dev/sdX
>
> What instructions did you start with? Exact URL, please.
>
> I've been playing with a separate partition to house a Debian installer
> ISO should I ever need it for rescue or re-installation. But that
> depends on having grub installed and a suitable entry for the d-i iso
> image. If that's what you want to do, I can help with that also.
>
Thank Charles!
> You shouldn't need separate vmlinuz and initrd.gz files. You should be
> able to boot directly to the iso image. Depending on how talented your
> computer's firmware is, you may have to copy the iso image to sdb, not
> sdb1. E.g.:
>
> dd if=<iso.image.file>.iso of=/dev/sdX
>
> What instructions did you start with? Exact URL, please.
>
> I've been playing with a separate partition to house a Debian installer
> ISO should I ever need it for rescue or re-installation. But that
> depends on having grub installed and a suitable entry for the d-i iso
> image. If that's what you want to do, I can help with that also.
>
https://www.debian.org/releases/stable/amd64/ch04s04.en.html
to reproduce my problem, you need 3 files: vmlinuz, initrd.gz and
corresponding iso file
add entry to grub menu, boot it to see if it can locate iso file, there
is no need to re-partition your disk
my pc can boot usb stick, but during installation it prompts me for usb
disk with non-free firmware , this step fails
Charles Curley
Feb 17, 2023, 1:30:05 AM2/17/23
to
On Thu, 16 Feb 2023 23:57:31 -0500
lsg <loushan...@sina.com> wrote:
> https://www.debian.org/releases/stable/amd64/ch04s04.en.html
>
> to reproduce my problem, you need 3 files: vmlinuz, initrd.gz and
> corresponding iso file
>
> add entry to grub menu, boot it to see if it can locate iso file,
> there is no need to re-partition your disk
Right. A couple of caveats, based on reading that. I've not
lsg <loushan...@sina.com> wrote:
> https://www.debian.org/releases/stable/amd64/ch04s04.en.html
>
> to reproduce my problem, you need 3 files: vmlinuz, initrd.gz and
> corresponding iso file
>
> add entry to grub menu, boot it to see if it can locate iso file,
> there is no need to re-partition your disk
experimented with this exact method. (I have a separate partition just
for the iso image.)
* At some point the installation will offer to reformat the main
partition. If that's the partition your iso image is on, reformatting
will clobber the iso image. Whether that will end the installation or
not depends on whether the installer has read the iso image into
memory. I believe it does not, and so formatting that partition will
break your installation partway through.
* Be sure the kernel and initrd are exactly the ones on the iso image.
The best way to do that is to mount the iso image on a loopback device
and extract those files from the iso image.
* You may have to adapt the grub file to your local situation. That
will take some reading. For example, the partition (hd0,msdos1 in the
example) may be wrong.
If you are going to use grub to do this, I know my method works. It's
not ready for prime time, though. It needs better documentation so
users can customize it, and I should take out some of my local
peculiarities.
>
> my pc can boot usb stick, but during installation it prompts me for
> usb disk with non-free firmware , this step fails
the sha*sum files you want from:
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/11.6.0+nonfree/amd64/iso-cd/
Brian
Feb 17, 2023, 9:40:05 AM2/17/23
to
issue thats happens after Linux kernel updates. The installer is
now out of step. It gets automatically fixed after some time.
--
Brian.
lsg
Feb 17, 2023, 8:20:05 PM2/17/23
to
On 2/17/23 22:29, Brian wrote:
> There isn't much you can do about this. It is usually a temporary
> issue thats happens after Linux kernel updates. The installer is
> now out of step. It gets automatically fixed after some time.
>
Thanks! i've thought updating iso image and hard disk installer are
> There isn't much you can do about this. It is usually a temporary
> issue thats happens after Linux kernel updates. The installer is
> now out of step. It gets automatically fixed after some time.
>
automatic
it's very frustrating, i've never been so disappointed with debian
it will be easier if i can determine if they match by matching file name
of iso file with that of vmlinuz and initrd pair (their file names shall
all include same version number)
i have successfully used bullseye hard disk installation method for i386
about one month ago, i don't know why it doesn't work this time
Charles Curley
Feb 17, 2023, 10:20:06 PM2/17/23
to
On Sat, 18 Feb 2023 09:17:43 +0800
lsg <loushan...@sina.com> wrote:
> it will be easier if i can determine if they match by matching file
> name of iso file with that of vmlinuz and initrd pair (their file
> names shall all include same version number)
That wouldn't help. My method pulls the kernel and initrd from the iso
lsg <loushan...@sina.com> wrote:
> it will be easier if i can determine if they match by matching file
> name of iso file with that of vmlinuz and initrd pair (their file
> names shall all include same version number)
itself. I got the same error you did.
I used the weekly build, so I shall wait until the next build and see
if that works.
lsg
Feb 17, 2023, 11:10:06 PM2/17/23
to
On 2/18/23 11:12, Charles Curley wrote:
>
> That wouldn't help. My method pulls the kernel and initrd from the iso
> itself. I got the same error you did.
>
> I used the weekly build, so I shall wait until the next build and see
> if that works.
>
program that search disk for iso file, as pair in hd-media directory does
Debian11.6/main/installer-amd64/current/images/hd-media
though it's possible to boot iso file with grub, but it's too complicated
it seems few users are using hard disk installation method theses days
David Wright
Feb 17, 2023, 11:40:06 PM2/17/23
to
so I stopped the debian-installer when it gets to the partitioner.
What I need to know is how far /you/ got before you received the error
you paraphrased as:
"No kernel modules found", probably due to kernel mismatch
Here's what I did, and it all worked perfectly (as far as the
partitioner step):
I downloaded the files you did (here with their SHA256):
e482910626b30f9a7de9b0cc142c3d4a079fbfa96110083be1d0b473671ce08d debian-11.6.0-amd64-netinst.iso
7f161a705077f231d282dc4a8961f17c5d4a6182877ca930eca280958f86dfe9 firmware-11.6.0-amd64-netinst.iso
and these from http://ftp.us.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/hd-media/
b00b339f8b1aada1841d86650377dd8e7299eaa7f34d0bbf21deb561467015cd vmlinuz
ab34a60082dee4b18fe3c1e6131cd27e876d6877a3b81c6490814f0a594608ef initrd.gz
Note to Charles: that happens to be the same kernel as on the ISOs,
but you must use the hd-media's initrd. I assume that's because it
knows how to look for the .iso file. You can't just extract it from
the netinst ISO.
OK. I placed these four files into /boot on a regular Debian machine.
I intended to check both ISOs, so I hid one by appending -hidden to
the filename: firmware-11.6.0-amd64-netinst.iso-hidden
Next, I edited the file /boot/grub/grub.cfg and added a few lines at
the end. You can see where they go by the BEGIN/END and 40:
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Install Debian via HTTP" {
search --no-floppy --label --set=root swan05
linux /boot/vmlinuz
initrd /boot/initrd.gz
}
### END /etc/grub.d/40_custom ###
OK, I use LABELs, and this Debian system's root filesystem is on
/dev/sda5 with the LABEL swan05. If you only have a UUID, then that
line will become:
search --no-floppy --fs-uuid --set=root 12345678-abcd-fedc-0000-1234567890ab
or whatever the root filesystem's UUID is.
Then I rebooted the system, and when Grub started (blue screen),
I downarrow'd to Install Debian via HTTP and pressed Return.
A few seconds, and many messages, later I got:
┌───────────────────────────┤ [!!] Select a language ├────────────────────────────┐
│ │
│ Choose the language to be used for the installation process. The selected │
│ language will also be the default language for the installed system. │
│ │
As I say, I went as far as the partitioner. With no firmware for wifi,
I had to skip out of configuring the network.
I then rebooted to my Debian system, juggled the ISOs' names to:
/boot/debian-11.6.0-amd64-netinst.iso-hidden
/boot/firmware-11.6.0-amd64-netinst.iso
rebooted, and repeated the exercise, with a working wifi network
this time. I stopped again at the partitioner step.
All that took about fifteen or twenty minutes, but that might be
because I've done it before, and the extra grub.cfg lines are in
my backups.
Cleanup: the extra files in /boot do no harm unless you're short of
space. The extra menu will disappear whenever Grub is reconfigured:
kernel update, or grub update. Just ignore it.
Cheers,
David.
Charles Curley
Feb 18, 2023, 12:30:06 AM2/18/23
to
On Sat, 18 Feb 2023 12:05:11 +0800
lsg <loushan...@sina.com> wrote:
> Really? i am afraid vmlinuz and initrd pair in iso file don't include
> program that search disk for iso file, as pair in hd-media directory
> does
>
> Debian11.6/main/installer-amd64/current/images/hd-media
>
> though it's possible to boot iso file with grub, but it's too
> complicated
>
> it seems few users are using hard disk installation method theses days
I haven't been entirely clear about what I do. I do boot d-i using
lsg <loushan...@sina.com> wrote:
> Really? i am afraid vmlinuz and initrd pair in iso file don't include
> program that search disk for iso file, as pair in hd-media directory
> does
>
> Debian11.6/main/installer-amd64/current/images/hd-media
>
> though it's possible to boot iso file with grub, but it's too
> complicated
>
> it seems few users are using hard disk installation method theses days
grub. The following should make it a bit less opaque.
root@dti386:~# cat /etc/grub.d/50_netinst
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Install Debian 12 OS (preseeded)" {
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
set root='hd0,msdos5'
set isofile=/firmware-testing-i386-netinst.iso
insmod part_msdos
insmod loopback
loopback loop (hd0,msdos5)$isofile
linux (loop)/install.386/vmlinuz auto=true file=/media/preseed.cfg
initrd (loop)/install.386/initrd.gz
}
menuentry "Install Debian 12 OS (Expert)" {
set root='hd0,msdos5'
set isofile=/firmware-testing-i386-netinst.iso
insmod part_msdos
insmod loopback
loopback loop (hd0,msdos5)$isofile
linux (loop)/install.386/vmlinuz rescue/enable=true
initrd (loop)/install.386/initrd.gz
}
root@dti386:~#
The key is the loopback module: grub mounts the iso file as a loopback
device, pulls what it needs from the iso file, and goes from there.
Using the loopback facility eliminates the necessity of a separate
initrd and kernel.
The iso file is on /dev/[vs]da5, the first extended partition, with a
FAT file system. The idea is that the main partitions could get badly
mangled, but grub and this partition survive. This gives you a rescue
or re-installation capability without CD-ROMs, USB sticks, etc.
And, yes, these use Testing/Bookworm's weekly build, not Bullseye's.
The same principle applies to Bullseye.
David Wright
Feb 18, 2023, 1:12:55 AM2/18/23
to
completely different from the one in the OP. The latter is the
method documented in the Installation Guide, typically at § 4.4 and
§ 5.1, and dating back at least to lenny (when I stopped buying media).
You have to choose one method or the other, and not mix them.
BTW, in my post, I should have pointed out that the 11.6 hd-media and
ISOs are based on linux-image-5.10.0-20-amd64_5.10.158-2_amd64,
whereas it's likely that linux-image-5.10.0-21-amd64_5.10.162-1_amd64
is installed on most systems.
Cheers,
David.
lsg
Feb 18, 2023, 2:30:05 AM2/18/23
to
Thank David Wright very much!
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
does your installer find your iso file? or do you really install via
http? 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
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
does your installer find your iso file? or do you really install via
http? 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
lsg
Feb 18, 2023, 2:40:05 AM2/18/23
to
i am sorry link in my last mail may not work outside china
Max Nikulin
Feb 18, 2023, 7:00:06 AM2/18/23
to
On 18/02/2023 12:26, Charles Curley wrote:
> menuentry "Install Debian 12 OS (preseeded)" {
> set root='hd0,msdos5'
> set isofile=/firmware-testing-i386-netinst.iso
> insmod part_msdos
> insmod loopback
> loopback loop (hd0,msdos5)$isofile
> linux (loop)/install.386/vmlinuz auto=true file=/media/preseed.cfg
> initrd (loop)/install.386/initrd.gz
> }
Due to the following message I am confused if it should work for Debian:
> menuentry "Install Debian 12 OS (preseeded)" {
> set root='hd0,msdos5'
> set isofile=/firmware-testing-i386-netinst.iso
> insmod part_msdos
> insmod loopback
> loopback loop (hd0,msdos5)$isofile
> linux (loop)/install.386/vmlinuz auto=true file=/media/preseed.cfg
> initrd (loop)/install.386/initrd.gz
> }
Brian to debian-user. Re: problem with loading installer (hard disk
method) Thu, 29 Dec 2022 17:42:59 +0000.
https://lists.debian.org/msgid-search/?m=2912202217284...@desktop.copernicus.org.uk
> GRUB's loopback facility will not work with installer images.
> They do not contain iso-scan.
>
> https://bugs.debian.org/618000
> https://bugs.debian.org/724931
Brian
Feb 18, 2023, 9:30:06 AM2/18/23
to
needs to contain loop.ko. 'lsinitramfs initrd.gz' is a useful
command. Bother items show in the hd-media intitrd but not in
the initrd of debian-testing-amd64-netinst.iso.
I am mystified as to Charles Curley's experience.
--
Brian.
Charles Curley
Feb 18, 2023, 11:10:06 AM2/18/23
to
On Sat, 18 Feb 2023 18:55:03 +0700
Max Nikulin <mani...@gmail.com> wrote:
> Due to the following message I am confused if it should work for
> Debian:
>
> Brian to debian-user. Re: problem with loading installer (hard disk
> method) Thu, 29 Dec 2022 17:42:59 +0000.
> https://lists.debian.org/msgid-search/?m=2912202217284...@desktop.copernicus.org.uk
>
> > GRUB's loopback facility will not work with installer images.
> > They do not contain iso-scan.
> >
> > https://bugs.debian.org/618000
Date: 2011.
Max Nikulin <mani...@gmail.com> wrote:
> Due to the following message I am confused if it should work for
> Debian:
>
> Brian to debian-user. Re: problem with loading installer (hard disk
> method) Thu, 29 Dec 2022 17:42:59 +0000.
> https://lists.debian.org/msgid-search/?m=2912202217284...@desktop.copernicus.org.uk
>
> > GRUB's loopback facility will not work with installer images.
> > They do not contain iso-scan.
> >
> > https://bugs.debian.org/618000
> > https://bugs.debian.org/724931
Date 2013, last entry dated 2020.
Neither one is marked as resolved.
loopback.mod (not .ko) is available in grub for both Bullseye and
Bookworm.
root@cdtest:~# find /boot/ -iname loop*
/boot/grub/i386-pc/loopback.mod
root@cdtest:~#
I can't find iso-scan anywhere except as a part of the package
dracut-live, so I'm not sure it's relevant here. I conjecture that
telling the kernel where to find the iso image bypasses any need for
iso-scan. (See the first email in #724931.)
As I have mentioned earlier in this thread, I do have a rough script
which automates most of the process of building the separate partition
I use for these d-i images. I'll see if I can get that cleaned up and
ready for prime time in the next few days.
Brian
Feb 18, 2023, 2:20:06 PM2/18/23
to
On Sat 18 Feb 2023 at 09:06:11 -0700, Charles Curley wrote:
> On Sat, 18 Feb 2023 18:55:03 +0700
> Max Nikulin <mani...@gmail.com> wrote:
>
> > Due to the following message I am confused if it should work for
> > Debian:
> >
> > Brian to debian-user. Re: problem with loading installer (hard disk
> > method) Thu, 29 Dec 2022 17:42:59 +0000.
> > https://lists.debian.org/msgid-search/?m=2912202217284...@desktop.copernicus.org.uk
> >
> > > GRUB's loopback facility will not work with installer images.
> > > They do not contain iso-scan.
> > >
> > > https://bugs.debian.org/618000
>
> Date: 2011.
>
> > > https://bugs.debian.org/724931
>
> Date 2013, last entry dated 2020.
>
> Neither one is marked as resolved.
>
> loopback.mod (not .ko) is available in grub for both Bullseye and
> Bookworm.
>
> root@cdtest:~# find /boot/ -iname loop*
> /boot/grub/i386-pc/loopback.mod
> root@cdtest:~#
Irrelevant when it comes to what the kernel wants to do.
> On Sat, 18 Feb 2023 18:55:03 +0700
> Max Nikulin <mani...@gmail.com> wrote:
>
> > Due to the following message I am confused if it should work for
> > Debian:
> >
> > Brian to debian-user. Re: problem with loading installer (hard disk
> > method) Thu, 29 Dec 2022 17:42:59 +0000.
> > https://lists.debian.org/msgid-search/?m=2912202217284...@desktop.copernicus.org.uk
> >
> > > GRUB's loopback facility will not work with installer images.
> > > They do not contain iso-scan.
> > >
> > > https://bugs.debian.org/618000
>
> Date: 2011.
>
> > > https://bugs.debian.org/724931
>
> Date 2013, last entry dated 2020.
>
> Neither one is marked as resolved.
>
> loopback.mod (not .ko) is available in grub for both Bullseye and
> Bookworm.
>
> root@cdtest:~# find /boot/ -iname loop*
> /boot/grub/i386-pc/loopback.mod
> root@cdtest:~#
> I can't find iso-scan anywhere except as a part of the package
> dracut-live, so I'm not sure it's relevant here. I conjecture that
> telling the kernel where to find the iso image bypasses any need for
> iso-scan. (See the first email in #724931.)
installer ISO to access its contents. But it is not
present in the installer's initrd. lsinitramfs reveals
that fact. The first email at #724931 has it right:
> The module 'loop.ko' is not shipped with the Debian
> testing netinstall ISO. It should reside in
> /lib/modules/3.10-2-amd64/kernel/drivers/block/.
> Because it is missing, it is impossible to mount ISO
> images during the install and thus preventing
> installation from ISO, if the module is not manually
> imported.
As for iso-scan:
https://packages.debian.org/sid/iso-scan
Joey Hess is a well-respected ex-Debian developer who
was very influential in installer development. He says
at https://lists.debian.org/debian-boot/2013/09/msg00097.html
> iso-scan is part of the Debian installer[1].
>
> However, it is only included in the hd-media initrd.
> There is no reason to include it on the regular CD
> initrd, because isohybrid allows mounting the USB
> stick directly. (Not a loop-mount of an iso file
> included in some disk, which the hd-media initrd
> handles.)
>
> [1] I wrote it. Always nice to have my Debian work
> cited as another reason Ubuntu is better than Debian!
--
Brian.
Charles Curley
Feb 18, 2023, 4:10:06 PM2/18/23
to
On Sat, 18 Feb 2023 19:09:39 +0000
Brian <ad...@cityscape.co.uk> wrote:
> loop.ko is a kernel module. It is needed to mount an
> installer ISO to access its contents. But it is not
> present in the installer's initrd. lsinitramfs reveals
> that fact. The first email at #724931 has it right:
Oops. I was talking about grub, you about the initrd. Sorry for the
Brian <ad...@cityscape.co.uk> wrote:
> loop.ko is a kernel module. It is needed to mount an
> installer ISO to access its contents. But it is not
> present in the installer's initrd. lsinitramfs reveals
> that fact. The first email at #724931 has it right:
confusion.
I'm no expert on the initrd. So I mounted
firmware-testing-amd64-netinst.iso on a local directory. As you say,
running 'lsinitramfs initrd.gz | grep -i loop' does not turn up
loop.ko.
All I know is that using that iso image I can boot to the installer, so
something is making the contents of that iso image available to the d-i
kernel. As Alice would say, curiouser and curiouser.
Charles Curley
Feb 18, 2023, 5:40:06 PM2/18/23
to
On Sat, 18 Feb 2023 14:05:20 -0700
Charles Curley <charle...@charlescurley.com> wrote:
> Oops. I was talking about grub, you about the initrd. Sorry for the
> confusion.
I did some more testing.
Charles Curley <charle...@charlescurley.com> wrote:
> Oops. I was talking about grub, you about the initrd. Sorry for the
> confusion.
I have three machines set up for testing this setup.
dti386: virtual machine, 1 GB memory, pentium2 processor. It will run
all the way through its preseed configuration and stop at partitioning
the hard drive, where it is supposed to stop.
711983104 Jan 15 20:24 firmware-testing-i386-netinst.iso
cdtest: virtual machine, 1 GB memory, Haswell-noTSX processor. I can
boot the iso image. It immediately reports not finding the CD-ROM.
728760320 Jan 1 20:35 firmware-testing-amd64-netinst.iso
The third one, white, has less than 256MB of memory. It complains of
not enough memory after d-i boots. Using the same iso image as dti386,
it does not find the iso image.
On dti386, the output from mount once the installer has stopped
running the preseed is:
rootfs on / type rootfs (rw,size=1022128k,nr_inodes=125454)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=102216k,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=501832k,nr_inodes=125458,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sr0 on /cdrom type iso9660 (ro,relatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8)
/dev/sda5 on /media type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
lsmod does not show "loop". It does show "cdrom" and "isofs", but then
so do the other two.
I conjecture there is some difference between the i386 iso image and the
amd64 iso image. Any ideas?
David Wright
Feb 19, 2023, 1:10:06 PM2/19/23
to
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:
> 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
"[!!] 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?
/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?
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
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.
0 new messages