BodhiThis forum is for the discussion of Bodhi Linux.
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.
1- I ran sequence of commands as per post #13
2- Reboot PC and modified BIOS to boot from (HDD1/sdb)
3- Got a screen with a "GNU GRUB 2.02" header, a statement like "Minimal BASH-like editing..." and the "grub>" prompt.
4- Researched a bit on how to move on from there and found this article https://www.linux.com/training-tutor...-grub-2-linux/
5- Followed some indications there
6- When grub> ls, I got (hd0) (hd0,msdos5) (hd0,msdos1) (hd1) (hd1,msdos1)
7- Then grub> ls (hd0,1)/ and got lost+found swapfile etc/ media/
8- Then grub> ls (hd0,5) and got a similar display as previous step, plus the expected boot, initrd.img and vmlinuz stuff.
9- Seems grub "inverts" labels; like HDD1/sdb comes to be hdd0 and HDD0/sda comes to be hdd1, right?
So now the question is if I should run:
grub> set root=(hd0,5)
grub> linux /boot/vmlinuz-xxx-yyy root=/dev/sdb5
grub> initrd /boot/initrd.img-www-zzz
grub> boot
Would it be safe to run this last sequence? Thanks a lot!
Peperina.
Seems grub "inverts" labels; like HDD1/sdb comes to be hdd0 and HDD0/sda comes to be hdd1, right?
This is often the case when booting from an external drive and/or a flash drive. In the latter, my experience is that the flash will see itself as the first drive in most cases (/dev/sda) so that is always something to watch for.
The thing you're doing different from most people is your step #2. Most people leave their PC booting from first hard drive,and let grub go on there. Grub gives you the choice to boot OS on 2nd hard drive.
Seems you're trying to use your BIOS to switch between windows and bodhi, instead of just letting grub do its normal thing.
Switching your disk order in bios is why changing sda vs sdb.
Hi! Stuck (it seems) in some silly file location issue today, but unable to solve it myself so far...
1- When running grub> linux /boot/vmlinuz root=/dev/sdb5 I get error:file '/boot/vmlinuz' not found.
2- Same when I run grub> linux /vmlinuz root=/dev/sdb5
When in the live-session console, I was able to see the vmlinuz file under /.
Not sure what's going on. Thanks for any help!
Peperina.
No success. When I ls, I do see "vmlinuz".
I did try build the command through TAB autocompletion, and eventually got again to grub> linux /vmlinuz root=dev/sdb5 and still "file not found".
As previously stated, using the /boot directories also failed.
Best regards,
Peperina.
It appears that you are missing the kernel. Maybe it is located somewherer else. You didn't happen to create a boot partition at anytime?
Lets search with grub ls to see if there is a vmlinuz somewhere.
Code:
ls (hd0,1)/
ls (hd0,1)/boot
ls (hd0.5)/
ls (hd1,1)/
ls (hd1,1)/boot
ls (hd1,5)/
ls (hd1,5)/boot
ls (hd2,1)/
ls (hd2,1)/boot
ls (hd2,5)/
ls (hd2,5)/boot
ls (hd3,1)/
ls (hd3,1)/boot
ls (hd3,5)/
ls (hd3,5)/boot
If you don't find a vmlinuz or a vmlinuz-xxx-yyy somewhere the would suggest re-partition and start over.
If you have no other vmlinuz files on any of the partitions, you need to start over again. The /vmlinuz is linked to /boot/vmlinuz-4.9.0-6-686 which doesn't exist and the /initrd.img linked to /boot/initrd.img-4.9.0-6-686.
It doesn't make sense that you have a initrd.img-4.9.0-6-686 but no kernel to go with it.
Quote:
Would you suggest a complete re-install of Bodhi
from your first post, that would be yes, and a redo
of your partitioning. The sdc was the live usb but you never did say what the 2gb sdd1 was.
Last edited by colorpurple21859; 05-22-2020 at 07:33 PM.
Thanks colorpurple!
At one moment I had two thumb drives attached. One with the Bodhi image and the second one temporarily hosting the bootinfoscript.
Regarding the vmlinuz symlink, what about what I posted before:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.