Grub rescue problem



captain-sensible

Well-Known Member
Credits
6,009
maybe just try:

grub rescue > set prefix=(hd0,7)/boot/grub





grub rescue > set root=(hd0,7)

grub rescue > insmod normal


grub rescue > normal
[after this you might get just grub > instead of grub rescue > ]

insmod linux

linux /vmlinuz root=/dev/sda7 ro

initrd /initrd.img

boot
 
Last edited:

captain-sensible

Well-Known Member
Credits
6,009
you might have to play around but (hd0,msdos 7) looks best option

initrd.img is there , old and new vmlinuz etc


if its grub2 equates:

devices start from zero
partitions start from 1

so it should be /dev/sda7 ?


also i see new and old vmlinuz so at some point you upgraded kernels ? maybe forgot update-grub ?
 
Last edited:

wizardfromoz

Super Moderator
Staff member
Gold Supporter
Credits
4,926
Welcome @kushal140

What is the output of

Code:
lsblk
please

Chris Turner
wizardfromoz
 

captain-sensible

Well-Known Member
Credits
6,009
if you can't boot up your OS then it means you (to my limited knowledge) have no access to # lsblk. So i think Wiz means he wants to to boot up a live OS and run that command from the live OS.

I've been reading up grub2 in readiness that at some point in the 12st Century Slackware will adopt Grub2, currently it uses lilo and elio.

Now the difference between grub rescue > and grub > is that in grub rescue, it can't find the .mods which your image confirms.

You can try and look using ls to locate .mod stuff.

If you are going to have to get a USB with a live OS then i would like to suggest you try ventoy 13 relesase which will allow you to save time but putting intact iso to boot up including :
ventoy
├── ISO
│ ├── bionicpup64-8.0-uefi.iso
│ ├── rescatux-0.73.iso
│ ├── slackware64-current-install-dvd.iso
│ ├── super_grub2_disk_hybrid_2.04s1.iso
│ └── systemrescuecd-amd64-6.1.4.iso

the super_grub2_disk_hybrid_2.04s1.iso Obviously Slackware never fails (more humor Wiz) and i'm using uefi and elilo but i used super-grub to to find elilo.efi etc and it booted up slackware. So booting super-grub2- iso might fix your problem. if not it might be a case of using a live OS to mount and re-install grub2. you can't go far wrong with knoppix 8.6 or 8.6.1



also out of interest if you leave out :

grub rescue > insmod normal

and jump to :
grub rescue > insmod linux

//what happens?
 
Last edited:

kushal140

New Member
Credits
81
if you can't boot up your OS then it means you (to my limited knowledge) have no access to # lsblk. So i think Wiz means he wants to to boot up a live OS and run that command from the live OS.

I've been reading up grub2 in readiness that at some point in the 12st Century Slackware will adopt Grub2, currently it uses lilo and elio.

Now the difference between grub rescue > and grub > is that in grub rescue, it can't find the .mods which your image confirms.

You can try and look using ls to locate .mod stuff.

If you are going to have to get a USB with a live OS then i would like to suggest you try ventoy 13 relesase which will allow you to save time but putting intact iso to boot up including :
ventoy
├── ISO
│ ├── bionicpup64-8.0-uefi.iso
│ ├── rescatux-0.73.iso
│ ├── slackware64-current-install-dvd.iso
│ ├── super_grub2_disk_hybrid_2.04s1.iso
│ └── systemrescuecd-amd64-6.1.4.iso

the super_grub2_disk_hybrid_2.04s1.iso Obviously Slackware never fails (more humor Wiz) and i'm using uefi and elilo but i used super-grub to to find elilo.efi etc and it booted up slackware. So booting super-grub2- iso might fix your problem. if not it might be a case of using a live OS to mount and re-install grub2. you can't go far wrong with knoppix 8.6 or 8.6.1



also out of interest if you leave out :

grub rescue > insmod normal

and jump to :
grub rescue > insmod linux

//what happens?
IMG_20200622_153331.JPG
 

arochester

Moderator
Staff member
Gold Supporter
Credits
1,893
Did you read this?
if you can't boot up your OS then it means you (to my limited knowledge) have no access to # lsblk. So i think Wiz means he wants to to boot up a live OS and run that command from the live OS.
 

captain-sensible

Well-Known Member
Credits
6,009
ok so that at least confirms that (hd0,7) was /dev/sda7 i think

now its a case of getting as much info as we can for Wiz to fix it! :^ )

do you remeber which OS you installed last ? linux on /dev/sda7 ?

we might have to take that I386 into account ; also which way to go with grub: mbr or
efi ? ...so

i'm not sure you have efi, mines 100mb i dont see that in partitions


lets do :

# lsblk -o name,label,size,fstype,model

and

# fdisk -l


and lets throw in :

uname -m
for good measure
 


Members online


Top