Results 1 to 2 of 2

Thread: dracut-pre-udev condition failed

  1. #1

    Post dracut-pre-udev condition failed

    Hi guys, cant understand why on clear install on aarch64 system i have this error from the start
    If i try to start service after boot i got this
    but system is bootable and seems functional... i just dont want got stuck in future

    systemctl status dracut-pre-udev.service

    dracut-pre-udev.service - dracut pre-udev hook
    Loaded: loaded (/usr/lib/dracut/modules.d/98dracut-systemd/dracut-pre-udev.service; static)
    Active: inactive (dead)
    Condition: start condition failed at Tue 2021-06-08 09:43:38 UTC; 18s ago
    |- ConditionPathExists=/usr/lib/initrd-release was not met
    |- ConditionDirectoryNotEmpty=|/lib/dracut/hooks/pre-udev was not met
    |- ConditionKernelCommandLine=|rd.break=pre-udev was not met
    |- ConditionKernelCommandLine=|rd.driver.blacklist was not met
    |- ConditionKernelCommandLine=|rd.driver.pre was not met
    |- ConditionKernelCommandLine=|rd.driver.post was not met
    `- ConditionPathExistsGlob=|/etc/cmdline.d/*.conf was not met
    Docs: man:dracut-pre-udev.service(8)


    Jun 08 09:27:37 localhost systemd[1]: Condition check resulted in dracut pre-udev hook being skipped.
    Jun 08 09:43:38 cloud systemd[1]: Condition check resulted in dracut pre-udev hook being skipped.

  2. #2

    Default Re: dracut-pre-udev condition failed

    thanks no one this is surely bug cuz on x86-64 tumblweed it works just fine while on aarch64 got this error i list in the post but it can be "fixed" by
    changin uuid to /dev/sda or to partuuid BUT it slow down system

    Code:
    2.837s dracut-pre-udev.service
     626ms initrd-switch-root.service
     229ms systemd-resolved.service
     144ms initrd-parse-etc.service
     134ms initrd-cleanup.service
     119ms modprobe@drm.service
      96ms systemd-networkd.service
      92ms user@1000.service
      90ms systemd-sysctl.service
      88ms modprobe@fuse.service
      86ms systemd-udev-trigger.service
      85ms systemd-logind.service
      82ms sshd.service
      72ms sys-kernel-tracing.mount
      69ms tmp.mount
      68ms dev-hugepages.mount
      67ms dev-mqueue.mount
      67ms sys-kernel-debug.mount
      66ms kmod-static-nodes.service
      60ms systemd-udevd.service
      58ms dracut-cmdline.service
      56ms systemd-journald.service
      54ms systemd-remount-fs.service
      53ms boot-efi.mount
      48ms systemd-tmpfiles-setup-dev.service
      40ms systemd-random-seed.service
      38ms systemd-fsck-root.service
      33ms systemd-modules-load.service
      33ms systemd-journal-flush.service
      26ms systemd-update-utmp.service
      23ms systemd-tmpfiles-setup.service
      22ms systemd-vconsole-setup.service
      22ms sysroot.mount
      17ms sys-fs-fuse-connections.mount
      16ms dracut-mount.service
      14ms initrd-udevadm-cleanup-db.service
      13ms modprobe@configfs.service
       8ms user-runtime-dir@1000.service
       7ms systemd-update-utmp-runlevel.service
       7ms systemd-user-sessions.service
       5ms sys-kernel-config.mount
       3ms dracut-shutdown.service
    who can say how fix boot with uuid or fix slow boot on dracut-pre-udev?

Tags for this Thread

Posting Permissions

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