[Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi, I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: Console log: ============= [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Kernel parameter: ================== dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 ======= The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? Any idea is welcome! Thanks Marcel
This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ -----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout Hi, I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: Console log: ============= [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Kernel parameter: ================== dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 ======= The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? Any idea is welcome! Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I am using the release ISO centos-20190206T060000Z.
"Penney, Don" <Don.Penney@windriver.com> hat am 14. Februar 2019 um 19:50 geschrieben:
This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue
What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi,
I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error:
Console log: =============
[ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
dracut:/#
Kernel parameter: ==================
dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 =======
The message "[Warning: /dev/root does not exist" make me nervous. What does that mean?
Any idea is welcome!
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Don, which build do you recommend? Is there a workaround so I can keep my installation for now? Thanks Marcel Von meinem iPhone gesendet
Am 14.02.2019 um 19:50 schrieb Penney, Don <Don.Penney@windriver.com>:
This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue
What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi,
I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error:
Console log: =============
[ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
dracut:/#
Kernel parameter: ==================
dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 =======
The message "[Warning: /dev/root does not exist" make me nervous. What does that mean?
Any idea is welcome!
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues. -----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 2:41 PM To: Penney, Don Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout Hi Don, which build do you recommend? Is there a workaround so I can keep my installation for now? Thanks Marcel Von meinem iPhone gesendet
Am 14.02.2019 um 19:50 schrieb Penney, Don <Don.Penney@windriver.com>:
This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue
What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi,
I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error:
Console log: =============
[ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
dracut:/#
Kernel parameter: ==================
dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 =======
The message "[Warning: /dev/root does not exist" make me nervous. What does that mean?
Any idea is welcome!
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Don, your analysis was correct. Our interface ist not supported by the initrd. Do you know by chance how to unpack and pack the initrd correctly? Thanks Marcel
"Penney, Don" <Don.Penney@windriver.com> hat am 14. Februar 2019 um 20:48 geschrieben:
Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues.
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 2:41 PM To: Penney, Don Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi Don,
which build do you recommend?
Is there a workaround so I can keep my installation for now?
Thanks
Marcel
Von meinem iPhone gesendet
Am 14.02.2019 um 19:50 schrieb Penney, Don <Don.Penney@windriver.com>:
This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue
What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi,
I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error:
Console log: =============
[ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
dracut:/#
Kernel parameter: ==================
dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 =======
The message "[Warning: /dev/root does not exist" make me nervous. What does that mean?
Any idea is welcome!
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
If it's not supported by the initrd, it's not supported by the runtime load. The installer images are updated with the runtime kernel and drivers, to align with runtime. What type of NIC are you using? -----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Friday, February 15, 2019 12:17 PM To: Penney, Don Cc: starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout Hi Don, your analysis was correct. Our interface ist not supported by the initrd. Do you know by chance how to unpack and pack the initrd correctly? Thanks Marcel
"Penney, Don" <Don.Penney@windriver.com> hat am 14. Februar 2019 um 20:48 geschrieben:
Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues.
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 2:41 PM To: Penney, Don Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi Don,
which build do you recommend?
Is there a workaround so I can keep my installation for now?
Thanks
Marcel
Von meinem iPhone gesendet
Am 14.02.2019 um 19:50 schrieb Penney, Don <Don.Penney@windriver.com>:
This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue
What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi,
I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error:
Console log: =============
[ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
dracut:/#
Kernel parameter: ==================
dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 =======
The message "[Warning: /dev/root does not exist" make me nervous. What does that mean?
Any idea is welcome!
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
It is the ixgbevf driver. I have packed into the pxeboot image and it works now. Thanks again for your support! Marcel
"Penney, Don" <Don.Penney@windriver.com> hat am 15. Februar 2019 um 19:58 geschrieben:
If it's not supported by the initrd, it's not supported by the runtime load. The installer images are updated with the runtime kernel and drivers, to align with runtime.
What type of NIC are you using?
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Friday, February 15, 2019 12:17 PM To: Penney, Don Cc: starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi Don,
your analysis was correct. Our interface ist not supported by the initrd.
Do you know by chance how to unpack and pack the initrd correctly?
Thanks
Marcel
"Penney, Don" <Don.Penney@windriver.com> hat am 14. Februar 2019 um 20:48 geschrieben:
Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues.
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 2:41 PM To: Penney, Don Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi Don,
which build do you recommend?
Is there a workaround so I can keep my installation for now?
Thanks
Marcel
Von meinem iPhone gesendet
Am 14.02.2019 um 19:50 schrieb Penney, Don <Don.Penney@windriver.com>:
This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue
What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/
-----Original Message----- From: Marcel Schaible [mailto:marcel@schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout
Hi,
I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error:
Console log: =============
[ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.
dracut:/#
Kernel parameter: ==================
dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/ins... inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 =======
The message "[Warning: /dev/root does not exist" make me nervous. What does that mean?
Any idea is welcome!
Thanks
Marcel
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (2)
-
Marcel Schaible
-
Penney, Don