http://bugzilla.novell.com/show_bug.cgi?id=1059169 http://bugzilla.novell.com/show_bug.cgi?id=1059169#c14 --- Comment #14 from Marco M. <jjletho67-esus@yahoo.it> ---

Hm, for this to work you should probably replace your mount by UUID for partitions on the root device by the device name (e.g. /dev/sda1 for /boot/efi).

Yes, they already are mounted by UUID. You can check the fstab file I attached.

This device timeout is rather systemd related. After mounting sysroot, systemd creates mount units for partitions on the system root device. These mount units have a dependency on the configured device. It looks like the systemd-gpt-auto-generator is causing this (for details see its manpage). I'm afraid that you will need to switch back from uefi to legacy bios mode if you want to avoid the access to the efi device n the initrd.

Thanks for the suggestion, I read the man page and it says that if efi partitions is already specified in fstab no further mountpoint are autogenerated. In my case /boot/efi is specified in fstab with nofail option, so it shuold not be a problem and any other units which depends on it should not exist. It's illogical to have any dependencies on /boot/efi, because if systemd is running this means that uefi boot has been already completed and you don't need efi partition anymore, at least to complete the boot process. So why systemd abolutely need an efi partition mounted and does not honor the nofail option? -- You are receiving this mail because: You are on the CC list for the bug.