Doing some baby steps progress here:

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.

1 members found this post helpful.

Yes that should work, however there should be a vmlinuz and initrd in the root directory so this should work also and is simpler to remember.

Then you can attempt to rerun grub-install again to see if that fixes grub.

2 members found this post helpful.

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.

2 members found this post helpful.

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.

1 members found this post helpful.

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.

1 members found this post helpful.

you should be able to ls that partition to make sure those files exist with
if that continues to give you problems, you could try going back to your original suggestion of using the ones in /boot.

1 members found this post helpful.

Thanks cordx!

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.

1 members found this post helpful.

That is odd that you have no /vmlinuz, then you will have to do what you suggested in post 16.
will show you what kernels are in /boot
Another thought did you run
or

1 members found this post helpful.

Hi colorpurple!

yields:

System.map-4.9.0-6-686 config-4.9.0-6-686 initrd.img-4.9.0-6-686 grub/

I tried to run again both options you described but still get "file not found" (it is actually sdb5).

Thanks,
Peperina.

1 members found this post helpful.

that would be why
yields "file not found". /vmlinuz should be a symlink to /boot/vmlinuz-4.9.0-6-686 which you don't have.

When I ls -l, I can see:

.
..
lrwxrwxrwx 1 root root 24 .... vmlinuz -> boot/vmlinuz-4.9.0-6-686 and also
.
.
lrwxrwxrwx 1 root root 27 .... initrd.img -> boot/initrd.img-4.9.0-6-686

Isn't this expected? Thanks,
Peperirna.

1 members found this post helpful.

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.
If you don't find a vmlinuz or a vmlinuz-xxx-yyy somewhere the would suggest re-partition and start over.

1 members found this post helpful.

As always "vmlinuz" exists under ls (hd0,5)/

Thanks,
Peperina.

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.

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.

1 members found this post helpful.

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:

ls -l
.
.
lrwxrwxrwx 1 root root 24 .... vmlinuz -> boot/vmlinuz-4.9.0-6-686
.
.

Does it mean the file is there but it's broken? Thanks,
Peperina.

1 members found this post helpful.