Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1978218 - it takes over 90s to go past "Reached target Initrd Root Device."
Summary: it takes over 90s to go past "Reached target Initrd Root Device."
Keywords:
Status: CLOSED DUPLICATE of bug 1976653
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 34
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-01 10:54 UTC by Harish Pillay
Modified: 2021-07-01 11:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-01 11:04:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Bootup screen waiting at line 9 "Reached target Initrd Root Device." (115.78 KB, image/jpeg)
2021-07-01 10:54 UTC, Harish Pillay
no flags Details

Description Harish Pillay 2021-07-01 10:54:14 UTC
Created attachment 1796765 [details]
Bootup screen waiting at line 9 "Reached target Initrd Root Device."

Description of problem:
Latest kernel (Linux gillman 5.12.13-300.fc34.x86_64 #1 SMP Wed Jun 23 16:18:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux), on boot, stalls at "Reached target Initrd Root Device" for over 90seconds before proceeding to successfully bootup.

Version-Release number of selected component (if applicable):
5.12.13-300

How reproducible:
Have the 5.12.13 kernel, reboot and see it wait.

Steps to Reproduce:
1. Ensure kernel is 5.12.13
2. Reboot
3. Hit ESC to see the boot messages (see attached photo).

Actual results:
Should have gone past quickly and booted up but waited for atleast 90seconds

Rebooted to 5.12.12 version and it did not wait at that target and booted up as quickly as it has always been.

Comment 1 Hans de Goede 2021-07-01 11:04:24 UTC

*** This bug has been marked as a duplicate of bug 1976653 ***


Note You need to log in before you can comment on or make changes to this bug.