
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 27K Views
I followed the steps in the document, but I was asked to give the root password.
Here is what I did:
1. On the Grub menu type e
2. Append rd.break to the end of the line starting with linux
3. Hit Ctrl+x
It boots to this:
Give root password for maintenance
(or press Control-D to continue):_
Any tips, please!?


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 3,094 Views
I'm not sure what you mean by "changed"... Those are the instructions that have been used since RHEL 7.0.
https://www.redhat.com/sysadmin/recover-root-passwd
They will not work for RHEL 9.0
They will work for RHEL 8.x, 9.1, and 9.2.
Estrella Mountain Community College

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 701 Views
Answer not found.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 671 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 702 Views
I am facing this problem in a recent exam. Your solution does not work at all. There may be other problems linking with the OS and VM machine. Most likely the problem lies with the partition system with the VM working machine. So developers should rethink and examinee, what they face. We are not so blind that, we cannot write and solve the simple solution. Otherwise, how can we sit for the exam even though this exam is so hard and time is limited? We do not have enough time to troubleshoot it. Reconsider this problem in all platforms and all scopes. I faced this problem last week in an exam centre. I will not recommend your answer at all. Even in the Red Hat lab, that solution not working as I tried in version 9.1. I try most of the time to reset and rebuild my OS. But working in 9.3 with a VM machine. Why, do you have any answer?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 701 Views
Sent from Outlook for Android<>

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 3,043 Views
I had this issue becouse the creation playbook has failed. After re-running the playbook it worked fine.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 2,512 Views
Hi there,
None of the options indicated in this discussion works. Any chance someone would review the current RH134 9.0 lab and get it fixed?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 2,508 Views
Right, seems to work with init=/bin/sh. Good to know.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 2,507 Views
Well, not really.
/sysroot does not exists, ok, so I mounted /
chroot is not found
and then exit hungs the VM.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- 2,471 Views
@AnaV I have tried this exercise for the nth time succesfully - and did not face any issue since a long time now: simply followed the exercise as instructed and it went on smoothly : Are you selecting the resuce kernel boot loader entry and editing it ?
once the server is up , I was able to login with the updated password :
Please raise a support case in case you are getting error even after follpwing the steps and our support team will help / guide you.