Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Startx is something one might do after succeeding to load and boot the kernel and initrd from the Grub prompt. You're getting the boot from Grub prompt procedure out of order entering a password at a Grub prompt. Try using the 2nd link in post #11.
You cannot use a / where a , belongs and expect useful results.
Nope, I am getting the same problem again. So what should I do? Should I make a rescue disc/drive as has been suggested for the grub manual seems like to much info?
The commands in those posts must be adapted to your hardware and installation. Without knowing exactly what you typed or what the responses were, there's no way to tell what went wrong.
Do you not have a backup from which grub.cfg can be examined and utilized? If not, what to type is more difficult to determine.
Before typing linux and initrd commands at a grub> prompt, enter these commands:
Code:
insmod gzio
insmod part_msdos
insmod ext2
Not using them when necessary results in unknown filesystem errors.
If this doesn't work, it's probably best to give up trying to boot from the grub> prompt manually this way, and resort to performing a boot repair using one of the more common methods.
It would help us help you if you would boot a live DVD or USB to collect some data to paste here using code tags. This includes the content of /etc/fstab and /etc/default/grub on the installed 18.04 system, /boot/grub/grub.cfg if the /boot directory on the root filesystem contains files, or /grub/grub.cfg from the /boot filesystem if it is separate from the root filesystem. Also please provide output from:
Code:
efibootmgr -v
blkid
ls -l /sys/firmware/efi
and output from either 'fdisk -l' and/or 'parted -l'.
As an alternative to the above data, boot DVD or USB, download and run bootinfoscript, upload it to http://pastebin.com or equivalent, and paste the resulting URL here.
The presence of lvm in a grub environment is something I'm totally unfamiliar with. I don't use lvm, and can't recall ever having used it myself. Likely this means you may need help I cannot provide, at least, not without seeing the content of fstab on the installed system, and even then you may need help from someone who does have lvm experience. Lvm may be why the "usual hacks" didn't work for you.
Ok thanks, let me first try the grub commands that you suggested and see if anything changes. And sorry, I don't have a backup of any of the files from the OS.
Sorry, it didn't solve the problem. I am sending you the photos of the commands that I gave.
The second photo cuts off an important part of what you typed on the linux line. It looks like you typed /dev/sda1 where you may have needed /dev/sda2, or no root= at all. Without fdisk -l output, we don't know where your root filesystem lives. Retry without any root=/dev/sdanything:
We need to see output from those commands that I put in post #20 run from a live DVD or USB boot. There might be another insmod that needs to be run for lvm support. As I wrote, I'm not familiar with lvm, so don't don't know if or what it may be. Kernel and initrd are being found, but not the root filesystem. Probably most important is that the root filesystem get mounted temporarily while live booted and /etc/fstab and /boot/grub/grub.cfg be captured from it to paste here using code tags. From them we should be able to determine the root filesystem to use with root= for linux at grub> prompt. From grub.cfg we can see if some other insmod is being utilized.
Regarding post#20, do the things that you want show up on the output of the boot done with the live USB?
Between 'It would help us help' and 'resulting URL here.' in #20 is about using a live DVD or USB boot. The rest is about trying to boot from a grub> prompt.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.