[i am liveuser usb rescue? ISO image? real fedora? etc? ]
[liveuser@localhost-live ~]$ sudo mkdir /mnt/root
[liveuser@localhost-live ~]$ sudo mount UUID=6fec64c0-a806-464e-9e7e-a72a403ba06e /mnt/root
[liveuser@localhost-live ~]$ sudo chroot /mnt/root/root
cat: /proc/31789/comm: No such file or directory
[root@localhost-live /]# sudo chroot /mnt/root/root
sudo: account validation failure, is your account locked?
sudo: a password is required
[root@localhost-live /]# su
su: cannot open session: Permission denied
[root@localhost-live /]#
You did the chroot command twice. You just need it once. The second chroot cannot work. Therefore, do the chrootonly once. As I described above.
The su was just to ensure that the journalctl commands are with root privileges. If you are already root, it normally does not cause an issue. However, in this case, just remove it: so, do notsu.
Therefore, do the following as described, but without su, and do each command only once:
Then show us the output of the threejournalctl commands.
If you try it again, I suggest to use a new live instance (= restart the system, and boot again the live system). So, all the above has to be done within a live system but on the machine with the damaged Fedora you want to repair.
As suggested, you may first focus on the approach of @jakfrost . These are two different things:
Stephen snow — i am windows 10 Fedora Media Writer to Fedora 36, and General Udisk (1TB). i am boot fedora 36 and not disks! i am “start fedora 36” it checked. (do i is “test disk image & fedora 36”?)
i am not find “repair already installed system”?
christpher klooz –
Yes.
[liveuser@localhost-live ~]$ sudo mkdir /mnt/root
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[liveuser@localhost-live ~]$ sudo mount UUID=6fec64c0-a806-464e-9e7e-a72a403ba06e /mnt/root
[liveuser@localhost-live ~]$ sudo chroot /mnt/root/root
cat: /proc/3670/comm: No such file or directory
[root@localhost-live /]# journalctl --boot=0
[root@localhost-live /]# journalctl --boot=-1
[root@localhost-live /]# journalctl --boot=-2
[root@localhost-live /]#
→ Choose the USB drive you want to use for the rescue system.
→ As soon as the download has finished, click on Write to Disk
I hope your memory is sufficient for the server image. The dnf remove command above ensures that a 4096 MB memory is sufficient for making the rescue live stick.
After the stick is ready, shutdown, and then boot from the just created rescue USB stick:
→ Choose Troubleshooting Fedora 36
→ Choose Rescue a Fedora system
I think the rescue option is the best approach for the moment. Hopefully, it will help you.
Maybe @jakfrost has some hints about using the rescue option because I have not used it myself before.
Unfortunately, the option currently only exists on the server (and possibly on “everything”, but I assume it is the same in both cases). It seems to have been removed from workstation at all. Hopefully, the rescue works as easy for Perry as it worked for you.
Hopefully for sure. This is a pain point for many it seems. I will try my image I burned yesterday to see if the menu is there, although I was assured it is on the Dev mailing list. I need to boot it though since boxes won’t work with it. So give me a couple of hours since it’s nearly end of day. I’ll get back after dinner with results.
[Edit]: So I tried and you’re correct there is no rescue on the Workstation. So …
@perryt, sorry for this but you need to use either the Server image or the Everything image to get a rescue option, I just checked and the Workstation image does not have a rescue option!?!? @perryt the everything ISO can be found at https://alt.fedoraproject.org/, sorry for the inconvenience.
You have the server image, that’s good. If you use Fedora Media Writer in Windows 10 to create a Bootable USB stick of the Server or Everything, it will actually write the image then resize the USB stick to the size to the image written. This can be returned to the normal size with media writer after you repair the system. In media writer, if you look at the options available, you can see it already will install WorkstationServer and IoT without having to download them manually first (the links are built in for official releases). For the Everything image you do have to download it though and media writer looks for iSO Images in Downloads folder, or simply point it to the correct image you want to burn.
Do you only have the one USB stick for trying this? And the media writer wants to wipe it to write the ISO, which you can restore after repairing your system but if data on it is important, it should be backed up first.
I assumed that you are working on the notebook with the broken Fedora installation. Therefore, you could only start this notebook with a live system, as you did it before. Therefore, you need the USB drive that contains the running live system, on which you are working, and an additional USB drive on which the server image can be written by the mediawriter tool.
If you also have a Windows 10 installation that you can use, you do not need an additional USB drive. In this case, download and use the mediawriter installation @jakfrost suggested above.
Unfortunately, the answer is no. At the moment, you need to use the server or everything image for the rescue option.
I am fedora server. I am seating run liveuser fedora … server. i am have linux fedora in laptop. Not everything . i am library using Fedora-Server-netinst-x86_64-36-1.5.iso. do i am copying General Udisk (1tb)?
i am seating windows 10. i am not server. i am not Fedora Media Writer and not server.
Hello @perryt,
I am going to list the step by step I would take to use Fedora Media Writer on Windows 10 to write a Fedora Linux Server or Everything ISO to use to repair.
Install Media Writer on Windows 10 (it is a windows exe file.)
Start Fedora Media Writer on Win 10 (Will start after install if you don’t deselect it)
Select to write Fedora Server
Select destination USB stick
Write the USB image
Boot laptop into Server installation freshly put on USB
Select Rescue option under advance troubleshooting
I am currently at Write the USB image on my Win 10 Laptop, will post results soon as can
edit 08:34AM EST
Media Writer created a bootable USB stick of Server that has Rescue a Fedora System as an option in the Advanced Troubleshooting submenu. This should work for your case if the laptop already has a Fedora System installed just not booting correctly. Let me know how you do.
Hi @perryt ,
Sorry for the delay, I had to take care of some household duties I had let slip.
So after continuing, were you able to boot your system? If not then the rescue option didn’t solve your problem and @py0xc3 and @computersavvy will be able to assist you further with what they had started.
If it does boot into a read only mounted system then that is a good point to recover from I would think. At least the journal logs would still be viewable for the time frame where your problems began.
