My Oracle Support Banner

Exadata Node unable to boot - os-release file is missing. (Doc ID 2756678.1)

Last updated on APRIL 12, 2022

Applies to:

Exadata X4-2 Full Rack - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.


Exadata Node is unable to boot.


[ 15.627139] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Started Cleanup udevd DB.
[ 15.627347] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Reached target Switch Root.
[ 15.711108] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Started Plymouth switch root service.
[ 15.711965] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Starting Switch Root...
[ 15.730277] <AFFECTEDNODE.DOMAIN.COM> systemctl[1032]: Failed to switch root: Specified switch root path /sysroot does not seem to be an OS tree. os-release file is <<<<<<<<
[ 15.730764] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: initrd-switch-root.service: main process exited, code=exited, status=1/FAILURE
[ 15.731033] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Failed to start Switch Root.
[ 15.731237] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Startup finished in 4.366s (kernel) + 0 (initrd) + 11.364s (userspace) = 15.730s.
[ 15.731438] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Unit initrd-switch-root.service entered failed state.
[ 15.731664] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Triggering OnFailure= dependencies of initrd-switch-root.service.
[ 15.731857] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: initrd-switch-root.service failed.
[ 15.732064] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Started Emergency Shell.
[ 15.732256] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Reached target Emergency Mode.
[ 15.749894] <AFFECTEDNODE.DOMAIN.COM> systemd[1]: Received SIGRTMIN+21 from PID 755 (plymouthd).


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.