Re: How do I rebuild Grub/Boot/initramfs from a Live USB?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/28/22 12:26, Jake D wrote:

What does "ls -l /dev/mapper/fedora_crypt" show?

Do I run this from...'within' the 'chroot' thing, or just in the live USB after i do 'luks open'?

within the chroot.

That's one of the possible places for it to write the files.  Did it
find the right place?  If not, you'll have to specify the file yourself.

I don't know? I don't know where or what any of this should be doing, or it I'm doing the right thing.

Do you have any initramfs files in /boot?

"rpm -q kernel-core"
e.g. kernel-core-5.18.13-200.fc36.x86_64
"dracut /boot/initramfs-5.18.13-200.fc36.x86_64.img 5.18.13-200.fc36.x86_64"
You will also have to re-install the kernel-core package to the vmlinuz
file installed.

I'm sorry, I'm not quite understanding the instructions here?

is "rpm -q kernel-core" a command I should run? if so, where/when?

Yes. You need to find out which kernel version(s) you have installed in order to run the following command.

"e-install the kernel-core package to the vmlinuz " may as well be fre nch to me - I've been using linux for 4 weeks now and I'm sorry but I just don't understand this rapid fire technical jargon.

First try "dnf upgrade kernel". If there's a new kernel available, then it's much easier, you don't have to worry about the initramfs or reinstalling the kernel.

Otherwise, "dnf reinstall kernel-core".

At this point, it might just be easier to do a backup and re-install.

Not an option.

If it comes to that, I'm done with my linux experiment. Theres a month of  work gone into fixing all the bugs and glitches and problems I've run into, and the whole reason this thing started was because I couldn't get snapper to work properly to back up that work, and I was trying to troubleshoot that by testing it on a clean fresh 'test' installation, so I wouldn't risk my main one. Instead, it's killed it.

Then you're probably done. This much damage is difficult to repair without some knowledge about what you're doing. I'm curious about all the issues you were having because that's unusual. Did you ask here about those issues?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux