yast bootloader/dracut ignores config /etc/dracut.conf.d/

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

yast bootloader/dracut ignores config /etc/dracut.conf.d/

Paul Neuwirth-3
Hello,

first, what seems to be a bug for me, installing a new bootloader,
respectivly creating a new initrd using "yast bootloader" results in an
initrd creation, which ignores my config I placed
into /etc/dracut.conf.d/:
# ls -l /etc/dracut.conf.d/
total 12
-rw-r--r-- 1 root root  22 22. Dez 14:13 02-early-microcode.conf
-rw-r--r-- 1 root root  41 13. Jan 08:32 10-iscsi.conf
-rw-r--r-- 1 root root 487 22. Dez 14:13 99-debug.conf
drwxr-xr-x 1 root root  12 12. Jan 08:39 modules.d
# cat /etc/dracut.conf.d/10-iscsi.conf
add_dracutmodules+="debug network iscsi"

If I run dracut manually, these configs get considered..

from /var/log/YaST2/mkinitrd.log using yast bootloader - these initrds will never work...:
I: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.4.76-1-default 4.4.76-1-default
I: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
I: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
I: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
I: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
I: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
I: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
I: *** Including module: bash ***
I: *** Including module: systemd ***
I: *** Including module: warpclock ***
I: *** Including module: systemd-initrd ***
I: *** Including module: i18n ***
W: Could not find FONT_MAP none!
I: *** Including module: btrfs ***
I: *** Including module: kernel-modules ***
I: *** Including module: resume ***
I: *** Including module: rootfs-block ***
I: *** Including module: suse-btrfs ***
I: *** Including module: terminfo ***
I: *** Including module: udev-rules ***
I: Skipping udev rule: 40-redhat.rules
I: Skipping udev rule: 50-firmware.rules
I: Skipping udev rule: 50-udev.rules
I: Skipping udev rule: 91-permissions.rules
I: Skipping udev rule: 80-drivers-modprobe.rules
I: *** Including module: dracut-systemd ***
I: *** Including module: haveged ***
I: *** Including module: usrmount ***
I: *** Including module: base ***
I: *** Including module: fs-lib ***
I: *** Including module: shutdown ***
I: *** Including module: suse ***
I: *** Including modules done ***
I: *** Installing kernel module dependencies and firmware ***
I: *** Installing kernel module dependencies and firmware done ***
I: *** Resolving executable dependencies ***
I: *** Resolving executable dependencies done***
I: *** Hardlinking files ***
I: *** Hardlinking files done ***
I: *** Stripping files ***
I: *** Stripping files done ***
I: *** Generating early-microcode cpio image ***
I: *** Store current command line parameters ***
I: Stored kernel commandline:
I:  resume=UUID=d42cd64d-675a-48e8-bfa9-53fad8a06298
I:  root=UUID=cd3e81a2-0281-43d2-ba77-5e4765bbfe36 rootfstype=btrfs rootflags=rw,relatime,ssd,space_cache,subvolid=257,subvol=/@,subvol=@
I: *** Creating image file '/boot/initrd-4.4.76-1-default' ***
I: *** Creating initramfs image file '/boot/initrd-4.4.76-1-default'
done ***

running the command manually - (I still need to test if it works):
I: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.4.76-1-default 4.4.76-1-default
I: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
I: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
I: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
I: dracut module 'crypt' will not be installed, because command 'cryptsetup' could not be found!
I: dracut module 'mdraid' will not be installed, because command 'mdadm' could not be found!
I: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found!
I: *** Including module: bash ***
I: *** Including module: systemd ***
I: *** Including module: warpclock ***
I: *** Including module: systemd-initrd ***
I: *** Including module: i18n ***
W: Could not find FONT_MAP none!
I: *** Including module: network ***
I: *** Including module: btrfs ***
I: *** Including module: kernel-modules ***
I: *** Including module: kernel-network-modules ***
I: *** Including module: debug ***
I: *** Including module: iscsi ***
I: *** Including module: rootfs-block ***
I: *** Including module: suse-btrfs ***
I: *** Including module: terminfo ***
I: *** Including module: udev-rules ***
I: Skipping udev rule: 40-redhat.rules
I: Skipping udev rule: 50-firmware.rules
I: Skipping udev rule: 50-udev.rules
I: Skipping udev rule: 91-permissions.rules
I: Skipping udev rule: 80-drivers-modprobe.rules
I: *** Including module: dracut-systemd ***
I: *** Including module: haveged ***
I: *** Including module: usrmount ***
I: *** Including module: base ***
I: *** Including module: fs-lib ***
I: *** Including module: shutdown ***
I: *** Including module: suse ***
I: *** Including modules done ***
I: *** Installing kernel module dependencies and firmware ***
I: *** Installing kernel module dependencies and firmware done ***
I: *** Resolving executable dependencies ***
I: *** Resolving executable dependencies done***
I: *** Hardlinking files ***
I: *** Hardlinking files done ***
I: *** Stripping files ***
I: *** Stripping files done ***
I: *** Generating early-microcode cpio image ***
I: *** Store current command line parameters ***
I: Stored kernel commandline:
I: ip=eth0:dhcp ifname=eth0:00:16:3e:37:02:1c rd.iscsi.initiator=iqn.1996-04.de.suse:01:6b57893c841f
netroot=iscsi:172.18.0.1:::1:iqn.2018-01.net.swabian:alif_disks
rd.neednet=1
I:  root=UUID=701327b1-4c4b-49d9-9eef-5463501ba94c rootfstype=btrfs rootflags=rw,relatime,space_cache,subvolid=257,subvol=/@,subvol=@
I: *** Creating image file '/boot/initrd-4.4.76-1-default' ***
I: *** Creating initramfs image file '/boot/initrd-4.4.76-1-default'
done ***

is there anything I should know about dracut execution from yast bootloader?

Thank you

Paul

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: yast bootloader/dracut ignores config /etc/dracut.conf.d/

Andrei Borzenkov
13.01.2018 10:57, Paul Neuwirth пишет:

> Hello,
>
> first, what seems to be a bug for me, installing a new bootloader,
> respectivly creating a new initrd using "yast bootloader" results in an
> initrd creation, which ignores my config I placed
> into /etc/dracut.conf.d/:
> # ls -l /etc/dracut.conf.d/
> total 12
> -rw-r--r-- 1 root root  22 22. Dez 14:13 02-early-microcode.conf
> -rw-r--r-- 1 root root  41 13. Jan 08:32 10-iscsi.conf
> -rw-r--r-- 1 root root 487 22. Dez 14:13 99-debug.conf
> drwxr-xr-x 1 root root  12 12. Jan 08:39 modules.d
> # cat /etc/dracut.conf.d/10-iscsi.conf
> add_dracutmodules+="debug network iscsi"
>

The correct syntax is

add_dracutmodules+=" debug network iscsi "

(note extra spaces around value) and it works using "mkinitrd" here.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: yast bootloader/dracut ignores config /etc/dracut.conf.d/

Paul Neuwirth-3
On Sat, 13 Jan 2018 11:24:19 +0300
Andrei Borzenkov <[hidden email]> wrote:

> 13.01.2018 10:57, Paul Neuwirth пишет:
> > Hello,
> >
> > first, what seems to be a bug for me, installing a new bootloader,
> > respectivly creating a new initrd using "yast bootloader" results
> > in an initrd creation, which ignores my config I placed
> > into /etc/dracut.conf.d/:
> > # ls -l /etc/dracut.conf.d/
> > total 12
> > -rw-r--r-- 1 root root  22 22. Dez 14:13 02-early-microcode.conf
> > -rw-r--r-- 1 root root  41 13. Jan 08:32 10-iscsi.conf
> > -rw-r--r-- 1 root root 487 22. Dez 14:13 99-debug.conf
> > drwxr-xr-x 1 root root  12 12. Jan 08:39 modules.d
> > # cat /etc/dracut.conf.d/10-iscsi.conf
> > add_dracutmodules+="debug network iscsi"
> >  
>
> The correct syntax is
>
> add_dracutmodules+=" debug network iscsi "
>
> (note extra spaces around value) and it works using "mkinitrd" here.
>

fixed that.. but as mentioned, it works running the command manually..
but config is not getting applied if it's called from yast bootloader.

appearently.. there isn't any bootloader created by yast bootloader..
even if I change the command line parameters? ok.. maybe I interpret
that wrong.. and no new initrd was created at all.. I expected yast
bootloader to do that..

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: yast bootloader/dracut ignores config /etc/dracut.conf.d/

Andrei Borzenkov
13.01.2018 12:10, Paul Neuwirth пишет:

> On Sat, 13 Jan 2018 11:24:19 +0300
> Andrei Borzenkov <[hidden email]> wrote:
>
>> 13.01.2018 10:57, Paul Neuwirth пишет:
>>> Hello,
>>>
>>> first, what seems to be a bug for me, installing a new bootloader,
>>> respectivly creating a new initrd using "yast bootloader" results
>>> in an initrd creation, which ignores my config I placed
>>> into /etc/dracut.conf.d/:
>>> # ls -l /etc/dracut.conf.d/
>>> total 12
>>> -rw-r--r-- 1 root root  22 22. Dez 14:13 02-early-microcode.conf
>>> -rw-r--r-- 1 root root  41 13. Jan 08:32 10-iscsi.conf
>>> -rw-r--r-- 1 root root 487 22. Dez 14:13 99-debug.conf
>>> drwxr-xr-x 1 root root  12 12. Jan 08:39 modules.d
>>> # cat /etc/dracut.conf.d/10-iscsi.conf
>>> add_dracutmodules+="debug network iscsi"
>>>  
>>
>> The correct syntax is
>>
>> add_dracutmodules+=" debug network iscsi "
>>
>> (note extra spaces around value) and it works using "mkinitrd" here.
>>
>
> fixed that.. but as mentioned, it works running the command manually..

Does it work when running mkinitrd?

> but config is not getting applied if it's called from yast bootloader.
>

YaST bootloader should not create any initrd at all.

> appearently.. there isn't any bootloader created by yast bootloader..
> even if I change the command line parameters? ok.. maybe I interpret
> that wrong.. and no new initrd was created at all.. I expected yast
> bootloader to do that..
>


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: yast bootloader/dracut ignores config /etc/dracut.conf.d/

Paul Neuwirth-3
On Sat, 13 Jan 2018 12:12:37 +0300
Andrei Borzenkov <[hidden email]> wrote:

> 13.01.2018 12:10, Paul Neuwirth пишет:
> > On Sat, 13 Jan 2018 11:24:19 +0300
> > Andrei Borzenkov <[hidden email]> wrote:
> >  
> >> 13.01.2018 10:57, Paul Neuwirth пишет:  
> >>> Hello,
> >>>
> >>> first, what seems to be a bug for me, installing a new bootloader,
> >>> respectivly creating a new initrd using "yast bootloader" results
> >>> in an initrd creation, which ignores my config I placed
> >>> into /etc/dracut.conf.d/:
> >>> # ls -l /etc/dracut.conf.d/
> >>> total 12
> >>> -rw-r--r-- 1 root root  22 22. Dez 14:13 02-early-microcode.conf
> >>> -rw-r--r-- 1 root root  41 13. Jan 08:32 10-iscsi.conf
> >>> -rw-r--r-- 1 root root 487 22. Dez 14:13 99-debug.conf
> >>> drwxr-xr-x 1 root root  12 12. Jan 08:39 modules.d
> >>> # cat /etc/dracut.conf.d/10-iscsi.conf
> >>> add_dracutmodules+="debug network iscsi"
> >>>    
> >>
> >> The correct syntax is
> >>
> >> add_dracutmodules+=" debug network iscsi "
> >>
> >> (note extra spaces around value) and it works using "mkinitrd"
> >> here.
> >
> > fixed that.. but as mentioned, it works running the command
> > manually..  
>
> Does it work when running mkinitrd?
>

that also worked.

> > but config is not getting applied if it's called from yast
> > bootloader.
>
> YaST bootloader should not create any initrd at all.
>
the message "Create initrd" is misleading then.

2018-01-13 10:05:15 <1> alif(9203) [Ruby] modules/Progress.rb:344
Progress::New(Saving Boot Loader Configuration, 2, ["Create initrd",
"Save boot loader configuration"])

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: yast bootloader/dracut ignores config /etc/dracut.conf.d/

Andrei Borzenkov
13.01.2018 16:07, Paul Neuwirth пишет:

> On Sat, 13 Jan 2018 12:12:37 +0300
> Andrei Borzenkov <[hidden email]> wrote:
>
>> 13.01.2018 12:10, Paul Neuwirth пишет:
>>> On Sat, 13 Jan 2018 11:24:19 +0300
>>> Andrei Borzenkov <[hidden email]> wrote:
>>>  
>>>> 13.01.2018 10:57, Paul Neuwirth пишет:  
>>>>> Hello,
>>>>>
>>>>> first, what seems to be a bug for me, installing a new bootloader,
>>>>> respectivly creating a new initrd using "yast bootloader" results
>>>>> in an initrd creation, which ignores my config I placed
>>>>> into /etc/dracut.conf.d/:
>>>>> # ls -l /etc/dracut.conf.d/
>>>>> total 12
>>>>> -rw-r--r-- 1 root root  22 22. Dez 14:13 02-early-microcode.conf
>>>>> -rw-r--r-- 1 root root  41 13. Jan 08:32 10-iscsi.conf
>>>>> -rw-r--r-- 1 root root 487 22. Dez 14:13 99-debug.conf
>>>>> drwxr-xr-x 1 root root  12 12. Jan 08:39 modules.d
>>>>> # cat /etc/dracut.conf.d/10-iscsi.conf
>>>>> add_dracutmodules+="debug network iscsi"
>>>>>    
>>>>
>>>> The correct syntax is
>>>>
>>>> add_dracutmodules+=" debug network iscsi "
>>>>
>>>> (note extra spaces around value) and it works using "mkinitrd"
>>>> here.
>>>
>>> fixed that.. but as mentioned, it works running the command
>>> manually..  
>>
>> Does it work when running mkinitrd?
>>
>
> that also worked.
>

YaST calls mkinitrd. It is very unlikely that it will fail if it works
when called manually.

>>> but config is not getting applied if it's called from yast
>>> bootloader.
>>
>> YaST bootloader should not create any initrd at all.
>>
> the message "Create initrd" is misleading then.
>
> 2018-01-13 10:05:15 <1> alif(9203) [Ruby] modules/Progress.rb:344
> Progress::New(Saving Boot Loader Configuration, 2, ["Create initrd",
> "Save boot loader configuration"])
>

Yes, initrd may be regenerated at this point, but should not on x86.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]