I'm running a fresh install of Centos 7 from DVD 1810 kernel version 3.10.0-957.el7.x86_64.
My server is an HP DL325 Gen10. It has a 4 port 1 Gig ethernet adapter and a 2 port 10 Gig converged network adapter. They show up in Centos as eno1 - eno6 where 5 and 6 are the ports on the 10 gig ethernet device. I am configuring my server to boot via iSCSI on eno5. Installation works just fine, however when the server boots up, it's fetching a DHCP address on eno1 instead of using the statically configured IP I give it during install. If I check the configuration file at /etc/sysconfig/network-scripts/ifcfg-eno1, it says at the top Generated by dracut initrd. I attempted to pass the IP information to dracut by creating a file at /etc/cmdline with the IP information for both eno1 and eno5, but that doesn't seem to do anything. I also disabled ifcfg from dracut, and while that makes it not overwrite my network configuration files, it still boots up with a DHCP lease instead of using my static IP address. I can manually do an ifdown eno1 ifup eno1 and then it has the appropriate IP, but this is suboptimal and undesired. I've also tried passing the IP lines in the kernel boot up of grub, however I get a kernel panic when I do that whcih shows dracut-cmdline Warning: Empty autoconf values default to dhcp, the next line says dracut FATAL For argument ip=host_ip:gateway_ipeno1:off' Sorry, setting client-ip does not make sense for 'dhcp'. Note I did remove the ips to protect the innocent So I'm not sure where else to check where I can configure the IP for dracut so that it's not configuring my adapters as DHCP.
dracut initrd resets networking on boot
Re: dracut initrd resets networking on boot
Check for other ifcfg files that are for the same device by a different name.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 8
- Joined: 2018/05/04 16:09:13
Re: dracut initrd resets networking on boot
The only ifcfg files in there are for the 6 eno devices I expected, and of course the one for local host.
Re: dracut initrd resets networking on boot
Do you use static address because there is no DHCP server?
Do you use NetworkManager.service or network.service?
"Generated by dracut" does not mean "maintained by dracut". The generation is oneshot
during install. Otherwise it would overwrite custom config on every boot.
If dracut indeed retouches, then it does so according to instructions in initrd.
The initrd is created based on active configuration of the running system. It can be recreated.
Each new kernel install does create initrd for that kernel.
PS.
Please explain the boot process. I've had only one partial encounter with iSCSI and thus curious.
As far as I know:
- EFI/BIOS/PXE configures a network interface with DHCP
- PXE loads boot loader from tftp server
- Bootloader loads kernel and initrd from tftp
- Kernel uses drivers, utilities, and instructions from initrd to configure a network interface
- Kernel initiates connection to iSCSI target
- Kernel mounts iSCSI volume as root
- Network service is loaded from volume to start the rest of interfaces
-
- Posts: 8
- Joined: 2018/05/04 16:09:13
Re: dracut initrd resets networking on boot
There is a DHCP server, and I've currently set a reservation for the preferred IP until I can resolve the situationDo you use static address because there is no DHCP server?
We're using the NetworkManager.serviceDo you use NetworkManager.service or network.service?
This is the exact behavior I'm having, it's overwriting my configuration file on boot."Generated by dracut" does not mean "maintained by dracut". The generation is oneshot
during install. Otherwise it would overwrite custom config on every boot.
What is interesting is that it doesn't even seem to matter if I remove ifcfg from the initrd, and it doesn't overwrite my config files. It still uses DHCP even though I have it configured in there to use a static IP.If dracut indeed retouches, then it does so according to instructions in initrd.
The initrd is created based on active configuration of the running system. It can be recreated.
Each new kernel install does create initrd for that kernel.
Mine is much more simple than this. I'm using a controller that does iSCSI boot in hardware, so it presents as a local hard drive for the most part. The operating system does see that it's an iSCSI adapter and initializes the driver, but there is no PXE environment or tftp at all.PS.
Please explain the boot process. I've had only one partial encounter with iSCSI and thus curious.
As far as I know:I have a feeling that this is not how "boot via iSCSI" actually goes.
- EFI/BIOS/PXE configures a network interface with DHCP
- PXE loads boot loader from tftp server
- Bootloader loads kernel and initrd from tftp
- Kernel uses drivers, utilities, and instructions from initrd to configure a network interface
- Kernel initiates connection to iSCSI target
- Kernel mounts iSCSI volume as root
- Network service is loaded from volume to start the rest of interfaces
Re: dracut initrd resets networking on boot
What's the output from rpm -qa dracut\*
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 8
- Joined: 2018/05/04 16:09:13