yes, ive tried that copr systemd patch and systemctl mask systemd-udev-settle to fix the dracut issue but nothing made any difference. is there anything else to try or should i just follow that bug report? i have separate / and /home partitions so a reformat wont be that bad, just would like to avoid if possible
is there any way to proceed from here re:fedora bug reports or is it safe to say that the sid installation will throw these errors from time to time? if the entire disk is removed, the error doesnt occur. but since those intel packages were upgraded, it went away even with the disks connected. can i submit anything for the fedora community here or just call it a random occurrence and move along?
I’ve got the exact same problem.
I’ve added a SSD to my computer and I’ve installed Fedora 32. But I find that the boot time is almost longer than the one of Fedora 30 on my HDD.
I’ve already masked plymouth-quit-wait.service, NetworkManager-wait-online.service and systemd-udev-settle.service.
My main problem comes from dracut-initqueue.service:
I’ve got 2 HDDs and one SSD. My root, boot and swap partitions are on the SSD. My home partitions is on a HDD. And I’m also using parts of my old home that is on a LVM on the second HDD.
I’ve tried removing the LVM parts of fstab and masking lvm2-monitor.service but it didn’t changed anything.
Is it safe to use the copr patch?
I’ve tried the version of systemd suggested and it was exactly the same.
I’ve also tried the system-preset solution but it did not changed anything either.
And for the intel-media-va-driver update, I’m using an amd processor (Ryzen 3600) with a Nvidia card (GTX 960). So i’s not the cause of the problem.
I know which unit is delaying the boot process, and I’ve already removed Plymouth. It all happens at this point:
[ 3.104375] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[ 3.123628] libphy: r8169: probed
[ 3.124892] r8169 0000:22:00.0 eth0: RTL8168h/8111h, 2c:f0:5d:26:e7:c5, XID 541, IRQ 69
[ 3.125881] r8169 0000:22:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 3.134186] ccp 0000:28:00.1: enabling device (0000 -> 0002)
[ 3.135269] ccp 0000:28:00.1: ccp: unable to access the device: you might be running a broken BIOS.
[ 3.157940] r8169 0000:22:00.0 enp34s0: renamed from eth0
[ 33.725560] ata15: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 34.529167] ata15.00: configured for PIO4
[ 35.355335] audit: type=1130 audit(1595597093.247:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-initqueue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 35.380033] audit: type=1130 audit(1595597093.272:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-fsck-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 35.386696] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
And the ata15 corresponds to my dvd drive. I I unplug it, the pause during the boot process disappears.
I think that the systems tries to “discover” each sata drive, the DVD drive does not respond and there is a timeout:
juil. 24 18:45:17 fixe kernel: ata15: SATA max UDMA/133 abar m2048@0xf7700000 port 0xf7700380 irq 48
juil. 24 18:45:17 fixe kernel: ata15: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
juil. 24 18:45:17 fixe kernel: ata15.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB06, max MWDMA2
juil. 24 18:45:17 fixe kernel: ata15.00: configured for PIO4
juil. 24 18:45:48 fixe kernel: ata15: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
juil. 24 18:45:49 fixe kernel: ata15.00: configured for PIO4
juil. 24 16:46:24 fixe kernel: ata15: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
juil. 24 16:46:25 fixe kernel: ata15.00: configured for PIO4
We can see that there is a 30 second gap during the process. If I compare it with one of my HDD, we can see that there is no gap:
juil. 24 18:45:17 fixe kernel: ata1: SATA max UDMA/133 abar m131072@0xf7680000 port 0xf7680100 irq 39
juil. 24 18:45:17 fixe kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
juil. 24 18:45:17 fixe kernel: ata1.00: ATA-8: TOSHIBA HDWD130, MX6OACF0, max UDMA/133
juil. 24 18:45:17 fixe kernel: ata1.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 32), AA
juil. 24 18:45:17 fixe kernel: ata1.00: configured for UDMA/133
It’s strange that the last 2 lines are repeated 3 times for the DVD drive, each time with 30s between each.
And I’ve checked, I had the same thing with Fedora 30, so it’s not a new problem.
I already did this. And my problem was already in Fedora 30. The problem is not due to dracut, but more about the way my dvd drive is reponding (or not) to the messages sent during boot. I just need to find how to decrease this timeout duration, or to tell the initrd not to care about the dvd drive.