Bug 1678634
Summary: | Installation of RHEL 8 fails to boot with message "Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing." | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jose Castillo <jcastillo> | ||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 8.0 | CC: | Claude.Frantz, jcastillo, jkonecny, jstodola, sbueno | ||||||
Target Milestone: | rc | ||||||||
Target Release: | 8.0 | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-02-12 18:22:32 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Jose Castillo
2019-02-19 09:27:51 UTC
Does a basic installation work, e.g. without running the "linux_trailer" script? Would it be possible to attach installation logs (in /tmp before reboot)? Right now it's difficult to pinpoint what might have gone wrong/where. I observe the same behaviour on a 32 bit Fedora 30, after the system upgrade, using "dnf system-upgrade", coming from Fedora 28. When calling "systemctl status initrd-switch-root.service", the same status about missing os-release file and /sysroot can be seen here, on my system. I have a simple laptop with a single HD drive. Is there an interim solution available ? I seems difficult to me to copy the installation log in /tmp, because, in the state where the error occurs, I cannot mount an USB stick and I have no access to /boot. Only very few executables are available. In the past, a very similar error has been reported to bugzilla, related to an older release. Created attachment 1575861 [details]
/run/initramfs/rdsosreport.txt in the failed state
Remember that I'm reporting about Fedora 30
When trying to boot using the F28 kernel, which is still available after the upgrade, the problem reported here appears too. Before the upgrade, this kernel worked well. While observing the supplied log, I'm surprised about this sequence: [ 11.889392] deby audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 11.889871] deby audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ....... [ 12.147882] deby audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=initrd-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Created attachment 1576339 [details]
rdsosreport.txt with rd.debug and rd.shell options set
In the emergency shell, I have entered:
ln -s /dev/sda7 /dev/root
exit
Later, the system stops again.
I'm closing this bug based on comment 6. Claude, could you please report the issue you are seeing against Fedora Product if you are still able to reproduce it? |