Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: mkinitrd/dracut error after TW 20200925

  1. #1
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,570

    Default mkinitrd/dracut error after TW 20200925

    Anyone else seeing these dracut errors after TW 20200925

    Just updated one of my TW installs to 20200925 and when initrd runs these errors are now shown.

    Luckily (!) it didn't prevent booting...

    Code:
    snip...
    
    I: memstrack is not available
    I: If you need to use rd.memdebug>=4, please install memstrack
    E: dracut-squash module requires squashfs-tools
    
    snip...
    
    E: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.AhLdD6/initramfs -H -N i2o_scsi --kerneldir /lib/modules/5.8.10-1-default/ -m -o -s ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|scsi_esp_register|register_virtio_device|usb_stor_disconnect|mmc_add_host|sdhci_add_host|scsi_add_host_with_dma =drivers
    
    snip...
    I don't know if the missing "squashfs-tools" is the cause of the "FAILED" message, or if it's coincidental.


    Currently (approx 10:00 BST 2020-09-27) neither "memstrack" or "squashfs-tools" appear to be in the TW repositories...
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201025) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  2. #2
    Join Date
    Feb 2018
    Location
    Romania
    Posts
    459

    Default Re: mkinitrd/dracut error after TW 20200925

    Quote Originally Posted by tannington View Post
    I don't know if the missing "squashfs-tools" is the cause of the "FAILED" message, or if it's coincidental.
    Hello,
    I think it is coincidental.
    I have ”dracut-squash.....” message but I do not have the ”FAILED” message.

  3. #3
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,570

    Default Re: mkinitrd/dracut error after TW 20200925

    Running mkinitrd again from a terminal results in a little more info (the segfault caused by dracut-init.sh: line 252 (?)) than appears in the log.

    Code:
    dracut: *** Including module: kernel-modules ***
    /usr/lib/dracut/dracut-init.sh: line 252:  9956 Segmentation fault      (core dumped) $DRACUT_INSTALL ${dracutsysrootdir:+-r "$dracutsysrootdir"} ${initdir:+-D "$initdir"} ${loginstall:+-L "$loginstall"} ${hostonly:+-H} ${check_supported:+--check-supported} ${omit_drivers:+-N "$omit_drivers"} ${srcmods:+--kerneldir "$srcmods"} -m "$@"
    dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.d0WfeQ/initramfs -H -N i2o_scsi --kerneldir /lib/modules/5.8.7-1-default/ -m -o -s ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|scsi_esp_register|register_virtio_device|usb_stor_disconnect|mmc_add_host|sdhci_add_host|scsi_add_host_with_dma =drivers
    dracut: *** Including module: kernel-modules-extra ***
    ... and this is the section ( lines 252-264 ) of /usr/lib/dracut/dracut-init.sh that is referenced:

    Code:
    dracut_instmods() {
        local _silent=0;
        local i;
        [[ $no_kernel = yes ]] && return
        for i in "$@"; do
            [[ $i == "--silent" ]] && _silent=1
        done
    
        $DRACUT_INSTALL \
            ${dracutsysrootdir:+-r "$dracutsysrootdir"} \
            ${initdir:+-D "$initdir"} ${loginstall:+-L "$loginstall"} ${hostonly:+-H} ${check_supported:+--check-supported} ${omit_drivers:+-N "$omit_drivers"} ${srcmods:+--kerneldir "$srcmods"} -m "$@"
        (($? != 0)) && (($_silent == 0)) && derror FAILED: $DRACUT_INSTALL ${dracutsysrootdir:+-r "$dracutsysrootdir"} ${initdir:+-D "$initdir"} ${loginstall:+-L "$loginstall"} ${hostonly:+-H} ${check_supported:+--check-supported} ${omit_drivers:+-N "$omit_drivers"} ${srcmods:+--kerneldir "$srcmods"} -m "$@" || :
    }
    ... but that's rather beyond me

    I feel a bug report may be in order...
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201025) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  4. #4
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,570

    Default Re: mkinitrd/dracut error after TW 20200925

    Quote Originally Posted by tannington View Post
    I feel a bug report may be in order...
    Reported: https://bugzilla.opensuse.org/show_bug.cgi?id=1177016


    Regards, Paul

    2x Tumbleweed (Snapshot: 20201025) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  5. #5
    Join Date
    Jan 2016
    Location
    UK
    Posts
    688

    Default Re: mkinitrd/dracut error after TW 20200925

    Just checked my zypp log and I got the same errors today running dracut.

    Stuart

  6. #6
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,928
    Blog Entries
    1

    Default Re: mkinitrd/dracut error after TW 20200925

    Got the following error:

    Code:
    I: *** Including module: kernel-modules ***
    E: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.N9BVR0/initramfs -H -N i2o_scsi --kerneldir /lib/modules/5.8.7-1-default/ -m -o -s ahci_platform_get_resources|ata_scsi_ioctl|scsi_add_host|blk_cleanup_queue|register_mtd_blktrans|scsi_esp_register|register_virtio_device|usb_stor_disconnect|mmc_add_host|sdhci_add_host|scsi_add_host_with_dma =drivers
    I: *** Including module: kernel-modules-extra ***
    Rebooted into 5.8.10-1-default and successfully ran both without encountering any errors:

    Code:
    dracut --kver 5.8.10-1-default --force
    dracut --kver 5.8.7-1-default --force
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  7. #7
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,570

    Default Re: mkinitrd/dracut error after TW 20200925

    Quote Originally Posted by another_roadrunner View Post
    I have ”dracut-squash.....” message but I do not have the ”FAILED” message.
    Thanks.

    Quote Originally Posted by broadstairs View Post
    Just checked my zypp log and I got the same errors today running dracut.
    Including the segfault and "Failed" message, or just the others as @another_roadrunner ?

    Quote Originally Posted by karlmistelberger View Post
    Rebooted into 5.8.10-1-default and successfully ran both without encountering any errors:
    I'm consistently getting the error (after rebooting) when attempting to create a new initrd... I wonder if it's related to which modules are included?
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201025) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

  8. #8
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,928
    Blog Entries
    1

    Default Re: mkinitrd/dracut error after TW 20200925

    Quote Originally Posted by tannington View Post
    Thanks.



    Including the segfault and "Failed" message, or just the others as @another_roadrunner ?



    I'm consistently getting the error (after rebooting) when attempting to create a new initrd... I wonder if it's related to which modules are included?
    Code:
    dracut: Will not override existing initramfs (/boot/initrd-5.8.7-1-default) without --force
    erlangen:~ # dracut --kver 5.8.7-1-default --force
    dracut: Executing: /usr/bin/dracut --kver 5.8.7-1-default --force
    dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
    dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found!
    dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found!
    dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found!
    dracut: memstrack is not available
    dracut: If you need to use rd.memdebug>=4, please install memstrack
    dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found!
    dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found!
    dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found!
    dracut: memstrack is not available
    dracut: If you need to use rd.memdebug>=4, please install memstrack
    dracut: *** Including module: bash ***
    dracut: *** Including module: systemd ***
    dracut: *** Including module: systemd-initrd ***
    dracut: *** Including module: i18n ***
    dracut: *** Including module: btrfs ***
    dracut: *** Including module: kernel-modules ***
    dracut: *** Including module: kernel-modules-extra ***
    dracut: *** Including module: rootfs-block ***
    dracut: *** Including module: suse-btrfs ***
    dracut: *** Including module: suse-xfs ***
    dracut: *** Including module: terminfo ***
    dracut: *** Including module: udev-rules ***
    dracut: Skipping udev rule: 40-redhat.rules
    dracut: Skipping udev rule: 50-firmware.rules
    dracut: Skipping udev rule: 50-udev.rules
    dracut: Skipping udev rule: 91-permissions.rules
    dracut: Skipping udev rule: 80-drivers-modprobe.rules
    dracut: *** Including module: dracut-systemd ***
    dracut: *** Including module: haveged ***
    dracut: *** Including module: ostree ***
    dracut: *** Including module: usrmount ***
    dracut: *** Including module: base ***
    dracut: *** Including module: fs-lib ***
    dracut: *** Including module: shutdown ***
    dracut: *** Including module: suse ***
    dracut: *** Including module: suse-initrd ***
    dracut: *** Including modules done ***
    dracut: *** Installing kernel module dependencies ***
    dracut: *** Installing kernel module dependencies done ***
    dracut: *** Resolving executable dependencies ***
    dracut: *** Resolving executable dependencies done ***
    dracut: *** Hardlinking files ***
    dracut: *** Hardlinking files done ***
    dracut: *** Generating early-microcode cpio image ***
    dracut: *** Constructing GenuineIntel.bin ***
    dracut: *** Store current command line parameters ***
    dracut: Stored kernel commandline:
    dracut: rd.driver.pre=btrfs
    dracut:  root=UUID=204f7d0f-979a-41e1-a483-a597d0357e0b rootfstype=btrfs rootflags=rw,relatime,ssd,space_cache,subvolid=2633,subvol=/@/.snapshots/1817/snapshot,subvol=@/.snapshots/1817/snapshot
    dracut: *** Stripping files ***
    dracut: *** Stripping files done ***
    dracut: *** Creating image file '/boot/initrd-5.8.7-1-default' ***
    dracut: *** Creating initramfs image file '/boot/initrd-5.8.7-1-default' done ***
    erlangen:~ #
    I have:
    Code:
    erlangen:~ # zypper if squashfs
    Loading repository data...
    Reading installed packages...
    
    
    Information for package squashfs:
    ---------------------------------
    Repository     : openSUSE-20191106-0
    Name           : squashfs
    Version        : 4.4-3.1
    Arch           : x86_64
    Vendor         : openSUSE
    Installed Size : 430.2 KiB
    Installed      : Yes
    Status         : up-to-date
    Source package : squashfs-4.4-3.1.src
    Summary        : A Read-Only File System with Efficient Compression
    Description    : 
        This package contains the userland utilities to create and read
        squashfs images.
    
    erlangen:~ #
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  9. #9
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    14,429
    Blog Entries
    3

    Default Re: mkinitrd/dracut error after TW 20200925

    Quote Originally Posted by tannington View Post
    I don't know if the missing "squashfs-tools" is the cause of the "FAILED" message, or if it's coincidental.
    Just coincidental, I think.

    I'm getting the squashfs message, but I am not seeing any segfault.

    I don't think the squashfs message is of any concern, unless your system really needs squashfs. But the segfault is of concern, and you were right to report a bug on that.
    openSUSE Leap 15.2; KDE Plasma 5.18.5;

  10. #10
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    1,570

    Default Re: mkinitrd/dracut error after TW 20200925

    Thanks...

    The included modules on mine are somewhat different, these are AMD machines and no btrfs for starters...

    I've just updated a second TW machine and see the same issue. (Added to my earlier bug report and attached full mkinitrd.log for that run)

    I have squashfs installed, same version as yourself, but dracut complains "dracut-squash module requires squashfs-tools" squashfs-tools is AFAIK a separate package.

    I'll wait and see what the outcome of the bug report is... Both machines are bootable and working, so no panic.
    Regards, Paul

    2x Tumbleweed (Snapshot: 20201025) KDE Plasma 5
    2x Leap 15.2 KDE Plasma 5

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •