Bug#884304: Debian 8.10 is not installable via PXE
Netboot installers needs to have core drivers, which it is lacking at this moment. I've added additional drivers into 'initrd.gz' of netboot installer of debian 8.9 and problem is solved. Before adding these drivers was getting the below error into syslog and installation was broken : Jun 25 04:31:12 log-output: Connecting to 192.168.1.34 (192.168.1.34:21) Jun 25 04:31:12 log-output: ^Mconfig_backup.sh 100% |***| 2515 0:00:00 ETA Jun 25 04:31:12 log-output: Connecting to 192.168.1.34 (192.168.1.34:21) Jun 25 04:31:12 log-output: ^Mconfig.sh100% |***| 484 0:00:00 ETA Jun 25 04:31:13 kernel: [ 135.908098] raid6: mmxx1 5755 MB/s Jun 25 04:31:13 md-devices: mdadm: No devices listed in partitions Jun 25 04:31:13 md-devices: mdadm: No devices listed in conf file were found. Jun 25 04:31:13 kernel: [ 135.976109] raid6: mmxx2 6091 MB/s Jun 25 04:31:13 kernel: [ 136.044110] raid6: sse1x14732 MB/s Jun 25 04:31:13 kernel: [ 136.112126] raid6: sse1x25938 MB/s Jun 25 04:31:13 kernel: [ 136.180133] raid6: sse2x19508 MB/s Jun 25 04:31:13 kernel: [ 136.248160] raid6: sse2x2 12015 MB/s Jun 25 04:31:13 kernel: [ 136.248161] raid6: using algorithm sse2x2 (12015 MB/s) Jun 25 04:31:13 kernel: [ 136.248162] raid6: using ssse3x1 recovery algorithm Jun 25 04:31:13 kernel: [ 136.307283] xor: automatically using best checksumming function: Jun 25 04:31:13 kernel: [ 136.344149]avx : 20087.000 MB/sec Jun 25 04:31:13 kernel: [ 136.348442] Btrfs loaded Jun 25 04:31:13 kernel: [ 136.357943] JFS: nTxBlock = 8192, nTxLock = 65536 Jun 25 04:31:13 kernel: [ 136.366371] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled Jun 25 04:31:13 partman: No matching physical volumes found Jun 25 04:31:13 kernel: [ 136.544037] device-mapper: uevent: version 1.0.3 Jun 25 04:31:13 kernel: [ 136.544235] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com Jun 25 04:31:13 partman: Reading all physical volumes. This may take a while... Jun 25 04:31:13 partman: Jun 25 04:31:13 partman: No volume groups found Jun 25 04:31:13 partman: Jun 25 04:31:13 partman-lvm: Jun 25 04:31:13 partman-lvm: No volume groups found Thank you steve for helping in debugging the issue.
Bug#884304: Debian 8.10 is not installable via PXE
> On Sat, Jun 23, 2018 at 11:07 PM, Steve McIntyre wrote: > >> Hi Jaikumar, >> >> AFAICS the problem you're facing is that the d-i kernel modules and >> the kernel you're running don't match up. Here's the kernel version >> you have: > > I used the netboot installer under http://snapshot.debian.org/archive/debian/20171201T034339Z/dists/jessie/main/installer-i386/20150422+deb8u4+b4/images/netboot/netboot.tar.gz and those 'undefined symbols' error is gone, but still It got stuck on the same issue as earlier, look like netboot installer lacks core drivers for disks? It look like that netboot.tar.gz in the above link does belong to debian 8.9 and not 8.10? As there is no versioning scheme available in the image. Thank you.
Bug#884304: Debian 8.10 is not installable via PXE
On Sat, Jun 23, 2018 at 11:07 PM, Steve McIntyre wrote: > Hi Jaikumar, > > AFAICS the problem you're facing is that the d-i kernel modules and > the kernel you're running don't match up. Here's the kernel version > you have: Thank you Steve, Our product used Debian 8.10 as netinstall base image to build on top and we do not manipulate 'udeb' or other stuff in the product DVD and netboot image i'm using also belongs to the same version I believe (though it does not have any versioning scheme in the image (netboot.tar.gz). So, it is surprising to me how kernel modules incompatibility with respect the netboot kernel (which is initiating the boot process) can occur. > > The most common cause of this kind of problem for people netbooting is > them updating *some* of the installer (i.e. the modules in the Debian > archive) without also updating the kernel that's being served by > tftp. Please go and check that... > Though, i'm sure, but will cross check it again. Thank you, Regards.
Bug#884304: Debian 8.10 is not installable via PXE
Hi Jaikumar, AFAICS the problem you're facing is that the d-i kernel modules and the kernel you're running don't match up. Here's the kernel version you have: On Sat, Jun 23, 2018 at 09:47:39PM +0530, Jaikumar Sharma wrote: > >Jun 23 14:20:40 syslogd started: BusyBox v1.22.1 >Jun 23 14:20:40 kernel: klogd started: BusyBox v1.22.1 (Debian >1:1.22.0-9+deb8u1) >Jun 23 14:20:40 kernel: [ 0.00] Initializing cgroup subsys cpuset >Jun 23 14:20:40 kernel: [ 0.00] Initializing cgroup subsys cpu >Jun 23 14:20:40 kernel: [ 0.00] Initializing cgroup subsys cpuacct >Jun 23 14:20:40 kernel: [ 0.00] Linux version 3.16.0-4-586 ( >debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian >3.16.7-ckt9-2 (2015-04-13) ... and here are lots of "Unknown symbol" errors when d-i is trying to load various filesystem modules: >Jun 23 14:22:42 preseed: running preseed command partman/early_command: wget -P >/tmp ftp://192.168.1.34/localrepo/install.scripts/scripts/config.sh >Jun 23 14:22:42 log-output: Connecting to 192.168.1.34 (192.168.1.34:21) >Jun 23 14:22:42 log-output: ^Mconfig_backup.sh 100% | >***| 2515 0:00:00 ETA >Jun 23 14:22:42 kernel: [ 139.713269] ext4: Unknown symbol setattr_prepare >(err 0) >Jun 23 14:22:42 kernel: [ 139.713731] ext4: Unknown symbol __bread_gfp (err 0) >Jun 23 14:22:42 kernel: [ 139.713779] ext4: Unknown symbol __getblk_gfp (err >0) >Jun 23 14:22:42 kernel: [ 139.713809] ext4: Unknown symbol >posix_acl_update_mode (err 0) >Jun 23 14:22:42 kernel: [ 139.814438] raid6: mmxx1 5762 MB/s >Jun 23 14:22:42 md-devices: mdadm: No devices listed in partitions >Jun 23 14:22:42 md-devices: mdadm: No devices listed in conf file were found. >Jun 23 14:22:42 kernel: [ 139.882447] raid6: mmxx2 6136 MB/s >Jun 23 14:22:42 kernel: [ 139.950455] raid6: sse1x1 4760 MB/s >Jun 23 14:22:42 kernel: [ 140.018463] raid6: sse1x2 5924 MB/s >Jun 23 14:22:42 kernel: [ 140.086474] raid6: sse2x1 9564 MB/s >Jun 23 14:22:42 kernel: [ 140.154484] raid6: sse2x2 12018 MB/s >Jun 23 14:22:42 kernel: [ 140.154485] raid6: using algorithm sse2x2 (12018 MB/ >s) >Jun 23 14:22:42 kernel: [ 140.154486] raid6: using ssse3x1 recovery algorithm >Jun 23 14:22:42 kernel: [ 140.220352] xor: automatically using best >checksumming function: >Jun 23 14:22:42 kernel: [ 140.258486] avx : 20146.000 MB/sec >Jun 23 14:22:42 kernel: [ 140.259696] btrfs: Unknown symbol setattr_prepare >(err 0) >Jun 23 14:22:42 kernel: [ 140.260185] btrfs: Unknown symbol >posix_acl_update_mode (err 0) >Jun 23 14:22:42 kernel: [ 140.264461] ext4: Unknown symbol setattr_prepare >(err 0) >Jun 23 14:22:42 kernel: [ 140.264915] ext4: Unknown symbol __bread_gfp (err 0) >Jun 23 14:22:42 kernel: [ 140.264965] ext4: Unknown symbol __getblk_gfp (err >0) >Jun 23 14:22:42 kernel: [ 140.265008] ext4: Unknown symbol >posix_acl_update_mode (err 0) >Jun 23 14:22:42 kernel: [ 140.265748] ext4: Unknown symbol setattr_prepare >(err 0) >Jun 23 14:22:42 kernel: [ 140.266191] ext4: Unknown symbol __bread_gfp (err 0) >Jun 23 14:22:42 kernel: [ 140.266239] ext4: Unknown symbol __getblk_gfp (err >0) >Jun 23 14:22:42 kernel: [ 140.266270] ext4: Unknown symbol >posix_acl_update_mode (err 0) >Jun 23 14:22:42 kernel: [ 140.270835] jfs: Unknown symbol setattr_prepare (err >0) >Jun 23 14:22:42 kernel: [ 140.270975] jfs: Unknown symbol __bread_gfp (err 0) >Jun 23 14:22:42 kernel: [ 140.271009] jfs: Unknown symbol __getblk_gfp (err 0) >Jun 23 14:22:42 kernel: [ 140.271022] jfs: Unknown symbol >posix_acl_update_mode (err 0) >Jun 23 14:22:42 kernel: [ 140.276230] xfs: Unknown symbol setattr_prepare (err >0) >Jun 23 14:22:42 kernel: [ 140.276555] xfs: Unknown symbol >posix_acl_update_mode (err 0) >Jun 23 14:22:42 kernel: [ 140.451316] device-mapper: uevent: version 1.0.3 >Jun 23 14:22:42 kernel: [ 140.451490] device-mapper: ioctl: 4.27.0-ioctl >(2013-10-30) initialised: dm-de...@redhat.com >Jun 23 14:22:42 partman: No matching physical volumes found >Jun 23 14:22:42 partman: Reading all physical volumes. This may take a >while... >Jun 23 14:22:42 partman: >Jun 23 14:22:42 partman: No volume groups found >Jun 23 14:22:42 partman: >Jun 23 14:22:42 partman-lvm: >Jun 23 14:22:42 partman-lvm: No volume groups found >Jun 23 14:22:42 partman-lvm: >Jun 23 14:22:42 kernel: [ 140.486141] efivars: Unknown symbol ucs2_as_utf8 >(err 0) >Jun 23 14:22:42 kernel: [ 140.486163] efivars: Unknown symbol ucs2_utf8size >(err 0) >Jun 23 14:22:42 kernel: [ 140.486164] efivars: disagrees about version of >symbol efivar_validate >Jun 23 14:22:42 kernel: [ 140.486165] efivars: Unknown symbol efivar_validate >(err -22) >Jun 23 14:22:50 init: starting pid 146, tty '/dev/tty2': '-/bin/sh' The most common cause of this kind of problem for people netbooting is them updating *some* of the installer (i.e. the modules in the Debian archive) without also updating the kernel that's
Bug#884304: Debian 8.10 is not installable via PXE
On Sat, Jun 23, 2018 at 9:07 PM, Steve McIntyre wrote: > If you're running with useful networking (e.g. bridged), then you can > grab the log from d-i via a trivial built-in webserver. If not, > probably the easiest way is to plug in a USB stick and copy it > there. You're looking for /var/log/syslog. > Thank you steve. I've attached the syslog below: Jun 23 14:20:40 syslogd started: BusyBox v1.22.1 Jun 23 14:20:40 kernel: klogd started: BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) Jun 23 14:20:40 kernel: [0.00] Initializing cgroup subsys cpuset Jun 23 14:20:40 kernel: [0.00] Initializing cgroup subsys cpu Jun 23 14:20:40 kernel: [0.00] Initializing cgroup subsys cpuacct Jun 23 14:20:40 kernel: [0.00] Linux version 3.16.0-4-586 ( debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 Debian 3.16.7-ckt9-2 (2015-04-13) Jun 23 14:20:40 kernel: [0.00] e820: BIOS-provided physical RAM map: Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0x0010-0xdffe] usable Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0xdfff-0xdfff] ACPI data Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0xfffc-0x] reserved Jun 23 14:20:40 kernel: [0.00] BIOS-e820: [mem 0x0001-0x00021fff] usable Jun 23 14:20:40 kernel: [0.00] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel! Jun 23 14:20:40 kernel: [0.00] SMBIOS 2.5 present. Jun 23 14:20:40 kernel: [0.00] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Jun 23 14:20:40 kernel: [0.00] Hypervisor detected: KVM Jun 23 14:20:40 kernel: [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved Jun 23 14:20:40 kernel: [0.00] e820: remove [mem 0x000a-0x000f] usable Jun 23 14:20:40 kernel: [0.00] e820: last_pfn = 0xdfff0 max_arch_pfn = 0x10 Jun 23 14:20:40 kernel: [0.00] MTRR default type: uncachable Jun 23 14:20:40 kernel: [0.00] MTRR variable ranges disabled: Jun 23 14:20:40 kernel: [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 Jun 23 14:20:40 kernel: [0.00] CPU MTRRs all blank - virtualized system. Jun 23 14:20:40 kernel: [0.00] initial memory mapped: [mem 0x-0x01bf] Jun 23 14:20:40 kernel: [0.00] Base memory trampoline at [c009b000] 9b000 size 16384 Jun 23 14:20:40 kernel: [0.00] init_memory_mapping: [mem 0x-0x000f] Jun 23 14:20:40 kernel: [0.00] [mem 0x-0x000f] page 4k Jun 23 14:20:40 kernel: [0.00] init_memory_mapping: [mem 0x3700-0x373f] Jun 23 14:20:40 kernel: [0.00] [mem 0x3700-0x373f] page 2M Jun 23 14:20:40 kernel: [0.00] init_memory_mapping: [mem 0x3000-0x36ff] Jun 23 14:20:40 kernel: [0.00] [mem 0x3000-0x36ff] page 2M Jun 23 14:20:40 kernel: [0.00] init_memory_mapping: [mem 0x0010-0x2fff] Jun 23 14:20:40 kernel: [0.00] [mem 0x0010-0x003f] page 4k Jun 23 14:20:40 kernel: [0.00] [mem 0x0040-0x2fff] page 2M Jun 23 14:20:40 kernel: [0.00] init_memory_mapping: [mem 0x3740-0x377fdfff] Jun 23 14:20:40 kernel: [0.00] [mem 0x3740-0x377fdfff] page 4k Jun 23 14:20:40 kernel: [0.00] BRK [0x0171a000, 0x0171afff] PGTABLE Jun 23 14:20:40 kernel: [0.00] RAMDISK: [mem 0x7f205000-0x7fff] Jun 23 14:20:40 kernel: [0.00] Allocated new RAMDISK: [mem 0x36a03000-0x377fd7eb] Jun 23 14:20:40 kernel: [0.00] Move RAMDISK from [mem 0x7f205000-0x77eb] to [mem 0x36a03000-0x377fd7eb] Jun 23 14:20:40 kernel: [0.00] ACPI: Early table checksum verification disabled Jun 23 14:20:40 kernel: [0.00] ACPI: RSDP 0x000E 24 (v02 VBOX ) Jun 23 14:20:40 kernel: [0.00] ACPI: XSDT 0xDFFF0030 34 (v01 VBOX VBOXXSDT 0001 ASL 0061) Jun 23 14:20:40 kernel: [0.00] ACPI: FACP 0xDFFF00F0 F4 (v04 VBOX VBOXFACP 0001 ASL 0061) Jun 23 14:20:40 kernel: [0.00] ACPI: DSDT 0xDFFF0410 0021FF (v02 VBOX VBOXBIOS 0002 INTL 20100528) Jun 23 14:20:40 kernel: [0.00] ACPI: FACS 0xDFFF0200 40 Jun 23 14:20:40 kernel: [0.00] ACPI: SSDT 0xDFFF0240 0001CC (v01 VBOX VBOXCPUT 0002 INTL 20100528) Jun 23 14:20:40 kernel: [0.00] 2695MB
Bug#884304: Debian 8.10 is not installable via PXE
On Sat, Jun 23, 2018 at 08:42:47PM +0530, Jaikumar Sharma wrote: >Can you grab a copy of the syslog so we can try to debug this please? > >Thanks, I've a virtual box VM which contains syslog, i've to find out a way to >extract the log file from it, since there is no utility in this system like >scp, ssh or something, sure I will try to extract syslog. If you're running with useful networking (e.g. bridged), then you can grab the log from d-i via a trivial built-in webserver. If not, probably the easiest way is to plug in a USB stick and copy it there. You're looking for /var/log/syslog. -- Steve McIntyre, Cambridge, UK.st...@einval.com "C++ ate my sanity" -- Jon Rabone
Bug#884304: Debian 8.10 is not installable via PXE
> > Can you grab a copy of the syslog so we can try to debug this please? Thanks, I've a virtual box VM which contains syslog, i've to find out a way to extract the log file from it, since there is no utility in this system like scp, ssh or something, sure I will try to extract syslog. thank you.
Bug#884304: Debian 8.10 is not installable via PXE
On Sat, Jun 23, 2018 at 05:54:10PM +0530, Jaikumar Sharma wrote: >I've also been hit by this bug, i've used 32 bit netboot installers (tried all) >under http://ftp.be.debian.org/debian/dists/jessie/main/installer-i386/ but >same issue is being face "No root file system defined" Can you grab a copy of the syslog so we can try to debug this please? -- Steve McIntyre, Cambridge, UK.st...@einval.com You raise the blade, you make the change... You re-arrange me 'til I'm sane...
Bug#884304: Debian 8.10 is not installable via PXE
I've also been hit by this bug, i've used 32 bit netboot installers (tried all) under http://ftp.be.debian.org/debian/dists/jessie/main/installer-i386/ but same issue is being face "No root file system defined"
Bug#884304: Debian 8.10 is not installable via PXE
Package: debian-installer Version: 20150422+deb8u4+b5 Severity: important When installing Debian 8.10 via PXE, installer throws this error: The attempt to mount a file system with type ext4 in RAID device #1 at / failed. You may resume partitioning from the partitioning menu. Do you want to resume partitioning? No matter which option i choose, i'm stuck on this error. Also tried disk erase and nothing changed. Debian 8.9 PXE installation works. Manual installation from nestinst works fine with both 8.10 and 9 versions.
