After deleting a large number of duplicate video and image files plus a couple of tiny misc files it appears my system (Fedora 40) is taking hours to reboot.
Have I borked Fedora?
After deleting a large number of duplicate video and image files plus a couple of tiny misc files it appears my system (Fedora 40) is taking hours to reboot.
Have I borked Fedora?
Hi Chuck!
Do you mean your system now takes a longer time to reboot than before?
Normally, deleting your large/duplicate video files shouldn’t cause any of this, but perhaps there is something else on your system that is causing this.
Can you please run the following command to see which services are taking a long time to start the system?
systemd-analyze blame
And paste the output here.
Thanks for the prompt reply Hanny!
Unfortunately the system failed to boot at all. I will save the command for future reference.
I am presently researching for the best way to a recovery. Perhaps reinstalling Fedora 40 from USB ?
Regards,
Chuck
Oh I see.
In that case, if you want, we can try to fix it before you go ahead with reinstallation, or you can just reinstall Fedora from the USB if you don’t have any valuable files on your system.
In order to figure out what service is causing this long boot time, you can try to press the Esc key multiple times after the GRUB menu entry is selected for Fedora (after you start booting the installed Fedora) so that the system will switch to displaying service status and other information. From there we can learn what might be the problem.
Best.
I do have important files and a backup that is not up to date. Made a live USB with Balena Etcher thinking that I may be able to do a repair install keeping my Home folder with all my files.
Your ESC key advice helped me get to the grub screen, BIG HELP, it took many hits but I’m there.
After years of breaking and repairing Linux systems you might call me an experienced newbie. That is to say I have been persistent in seeking information that resolved issues. Even a blind squirrel will find an acorn sometimes! I do have a backup drive with most of my HOME directory internally plus a second external SSD.
This is the first time I am unable to enter the BIOS to boot from the USB drive. I think the grub menu offers limited editing ability–got a link on that stashed somewhere. Should I attempt to repair the GRUB next?
Thanks again for your kind attention! 8-)
I found my copy of: REPAIRING FROM A GRUB PROMPT
FIND YOUR HARD DRIVE.
This goes on to GRUB Rescue and Fix GRUB permanently.
I am not sure what the issue is here; as long as you can access the GRUB menu and see Fedora and Fedora rescue option in the boot menu, then your GRUB is working perfectly and there is nothing to repair here.
If you can’t even access it then you need to repair it, using a tool like Boot Repair maybe.
If you actually have access to GRUB, then you should at least see these two options at boot time:
The second one allows you to start a root prompt to fix any possible issues at your OS. However, since Fedora disables the root account by default, this option does nothing extra than your normal boot option (the first one).
Thus, you should try to enable the root account like this guide explains:
Which will require that you chroot from a live Fedora system to your installed system and run the passwd root
command on it to activiate it.
After that, you can go with the rescue option I talked about earlier.
Once you access the root shell, you can now run the first command that I told you to see what’s going on. You can also run some other commands to explore your system logs like systemctl --failed
, sudo dmesg
and journalctl -b
. The outputs of these commands will help us determine the problem with your system.
Hope this helps! And you are most welcome.
At age 78 I can spend all day working a problem. Initially the grub screen offered limited command options. Then the ESC key stopped working keeping me out of the GRUB screen. Along the way I got a kernel panic message. Then I struggled with getting into the BIOS to change the boot order–had to key it at the exact time it took many efforts. The ASRock motherboard bios is more complicated than the simple old one I was used to. Eventually I got into Fedora with the Live USB disc and was able to update the GRUB. This got me into the system without reinstalling Fedora40.
Then I made copies of the files I wanted to secure on an SSD and copied them to this PC (running Manjaro). I now have multiple copies!
Also ran the systemd-analyze blame command which produced a very long list of items I have yet to read through. It’s Friday 10:09 AM on the Florida Space Coast. I will look at your other commands.
LESSONS LEARNED: I love Linux because it can be fixed, or at least there are kind people like you that are willing to help even when the student has limited knowledge. When researching online it is helpful to accurately state the problem. Years of using windows taught me that one has to pay to get help and the “help” may not be very competent. It’s hard for a master to help correct when they can’t see what’s happening and must rely on the student. With Linux I have always found competent and patient assistance. Next time I break something I will try to write down the sequence of events.
I liked CZAWKA (was it the cause?) but I think it’s safer to use an older program like FDUPES.
Thanks again, wish you a great day.
Oh that’s nice to hear, Chuck! So you are a senior warrior using Linux and facing its ups and downs alone haha. Glad that you were able to copy your precious files, and glad that you are with us here on FOSS Outpost.
Best!