Debian I had destroyed grub

beginstart · 12-05-2023, 08:51 AM

I hope I did it now not to much stupid.

Thank You.

Here are 2 codes.

Quote:

$ ls /boot
config-4.9.0-18-686-pae System.map-4.9.0-18-686-pae
config-5.10.0-13-686-pae System.map-5.10.0-13-686-pae
config-5.10.0-15-686-pae System.map-5.10.0-15-686-pae
grub vmlinuz-4.9.0-18-686-pae
initrd.img-4.9.0-18-686-pae vmlinuz-5.10.0-13-686-pae
initrd.img-5.10.0-13-686-pae vmlinuz-5.10.0-15-686-pae
initrd.img-5.10.0-15-686-pae
ah@ah:~$

The /boot/grub/grub.cfg

Quote:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}

if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=de_DE
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=50
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=50
fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
insmod png
if background_image /usr/share/desktop-base/homeworld-theme/grub/grub-4x3.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
echo 'Loading Linux 5.10.0-15-686-pae ...'
linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-15-686-pae
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
menuentry 'Debian GNU/Linux, with Linux 5.10.0-15-686-pae' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-15-686-pae-advanced-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
echo 'Loading Linux 5.10.0-15-686-pae ...'
linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-15-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 5.10.0-15-686-pae (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-15-686-pae-recovery-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
echo 'Loading Linux 5.10.0-15-686-pae ...'
linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-15-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 5.10.0-13-686-pae' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-13-686-pae-advanced-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
echo 'Loading Linux 5.10.0-13-686-pae ...'
linux /boot/vmlinuz-5.10.0-13-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-13-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 5.10.0-13-686-pae (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-13-686-pae-recovery-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
echo 'Loading Linux 5.10.0-13-686-pae ...'
linux /boot/vmlinuz-5.10.0-13-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-5.10.0-13-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 4.9.0-18-686-pae' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.9.0-18-686-pae-advanced-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
echo 'Loading Linux 4.9.0-18-686-pae ...'
linux /boot/vmlinuz-4.9.0-18-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.9.0-18-686-pae
}
menuentry 'Debian GNU/Linux, with Linux 4.9.0-18-686-pae (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.9.0-18-686-pae-recovery-f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1' f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
else
search --no-floppy --fs-uuid --set=root f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc
fi
echo 'Loading Linux 4.9.0-18-686-pae ...'
linux /boot/vmlinuz-4.9.0-18-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-4.9.0-18-686-pae
}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###

yancek · 12-05-2023, 11:29 AM

The kernel (vmlinuz) files to boot Debian show in the /boot directory as do the initrd files. If it still does not boot, I would suggest you run the blkid command and compare the UUID for sda1 with the UUID on the linux line in the menuentry for Debian. Also check the UUID for the swap partition and see if it the same as the UUID for swap in the /etc/fstab file.

beginstart · 12-06-2023, 09:53 AM

" I would suggest you run the blkid command and compare the UUID for sda1 with the UUID on the linux line in the menuentry for Debian. Also check the UUID for the swap partition and see if it the same as the UUID for swap in the /etc/fstab file."

Please talk slowly.
Thank You.
Booting is still not working.

" blkid command and compare the UUID for sda1 with the UUID on the linux line"

To do:

su- in terminal.
blkid
?
What is UUID

So blkid will bring a result
I save it in gedit.
Then I compare it with...?

Thank You.

yancek · 12-06-2023, 11:42 AM

UUID is Universally Unique IDentifier. In the grub.cfg file you posted earlier the line below shows the UUID Grub is looking for, the 32 characters after root=UUID. If you run blkid from a terminal, it will show the UUID for each partition. Since the same UUID shown in the failing first Debian entry shows in the Advanced options, that is not likely the problem. When you run blkid in a terminal, check the UUID for swap and make sure it is the same as the UUID for swap in the /etc/fstab file. You can review that file by using the command: cat /etc/fstab. These command won't change anything or solve the problem but will give information.

Quote:

linux /boot/vmlinuz-5.10.0-15-686-pae root=UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc ro quiet

Do you still see the same kernel panic error message when you boot?

beginstart · 12-07-2023, 09:53 AM

Code:



:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=f0295e7e-ea3f-42c4-bef6-e7df6ef9d9bc /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda5 during installation
UUID=b372616b-6d70-4ed3-a74f-55adebae5ac5 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
:~$

And the screenshot:

https://ibb.co/VQRYhG6

I hope I did my best

Thank You.

yancek · 12-07-2023, 11:02 AM

That eliminates a possible problem. The grub.cfg entry is pointing to a kernel that exists, it has the correct UUID for both the / filesystem and swap partitions so it is some else that is the problem. I don't know what to suggest as I was unable to read the image you posted earlier with the kernel panic message as the font were too small.

Can you post some information on your hardware and the age of the computer, processor, drive types, drive age, graphics info, etc. If you have inxi installed you can use that from a terminal:

Quote:

inxi -F

That should output a lot of information and you can post it with a link here.

mrmazda · 12-07-2023, 06:15 PM

I still don't understand what "cannot boot" means here. What are the last things you see when you try a normal boot?

I get error 502 trying to open the last image uploaded.

The difference in grub stanzas between normal and recovery consist solely of changing from ro quiet to ro single, so the problem could be related to any number of actions during init. An easy way to try something less drastic than booting to single is:

strike E key at Grub menu
move cursor to quiet
remove quiet
type just a 3 where quiet was
after 3, type a space and then type plymouth.enable=0
strike F10 key

Does this produce a login prompt on any tty (Alt-F1 through Alt-F6)?

yancek · 12-08-2023, 03:48 AM

Quote:

I get error 502 trying to open the last image uploaded.

It's a hosting site with the output of the /etc/fstab file which could have been posted here in quote tags. From another image he posted, there is a kernel panic on boot but I was unable to read anything more than the kernel panic on the last line of the image, fonts were too small for me.

hazel · 12-08-2023, 04:04 AM

Please do not post images (or links to images) of plain text outputs unless there really is no other way to capture them. A lot of people find such images hard to read. Either put the text itself into your post between [code][/code] tags or create a plain text file with the .txt filename extension and use the site's go-advanced attachment option to attach it to your post.

beginstart · 12-10-2023, 05:53 AM

Quote:

Originally Posted by mrmazda

I still don't understand what "cannot boot" means here. What are the last things you see when you try a normal boot?

I get error 502 trying to open the last image uploaded.

The difference in grub stanzas between normal and recovery consist solely of changing from ro quiet to ro single, so the problem could be related to any number of actions during init. An easy way to try something less drastic than booting to single is:

strike E key at Grub menu
move cursor to quiet
remove quiet
type just a 3 where quiet was
after 3, type a space and then type plymouth.enable=0
strike F10 key

Does this produce a login prompt on any tty (Alt-F1 through Alt-F6)?

Thank You for the instruction.
I did it.
The operation was fine,
but then "panic" again.

Question:
How should I upload pics?
Im sorry, the pic hoster img-load did delete the pics.

mrmazda · 12-10-2023, 11:24 AM

Quote:

Originally Posted by beginstart

How should I upload pics?

You may attach images to your reply here. Please be sure the filesize is reasonable, not gigantic as is the default on most cellphones. The program convert using -quality option can trim images down nicely in filesize, and using -resize can shrink the display size e.g. from 3840x2880 to 1600x1200 or less, which also reduces filesize.

beginstart · 12-12-2023, 05:50 AM

Are 20 to 50 KB ok?

mrmazda · 12-12-2023, 07:36 AM

Quote:

Originally Posted by beginstart

Are 20 to 50 KB ok?

Might be perfect. If too small, viewers with high resolution screens might have trouble making out what they contain.

beginstart · 12-13-2023, 07:00 AM

Its just for information.
I dont upload 10 MB-pics.
Thank You.
Xan somebody read this?

I did find these URLs in the www,
but I cannot understand it.

Can somebody please help?
Thank You.

https://www.codementor.io/@sauravjai...x-it-yxb0cl4zy

https://askubuntu.com/questions/9221...o-text-console
https://askubuntu.com/questions/4926...g-kernel-panic
https://askubuntu.com/questions/4710...a-kernel-panic
https://askubuntu.com/questions/9567...able-processes
https://github.com/pi-hole/pi-hole/issues/3498
https://bugs.debian.org/cgi-bin/bugr...cgi?bug=944196
https://bbs.archlinux.org/viewtopic.php?id=272932

https://unix.stackexchange.com/quest...anic-in-debian
https://www.redhat.com/sysadmin/linux-kernel-panic
https://www.liainfraservices.com/blo...rror-in-linux/

mrmazda · 12-13-2023, 12:35 PM

Apparently I neglected to answer the first part of post #13:

Quote:

Originally Posted by beginstart

"When you boot and see the Grub menu, hit the 'e' key on the keyboard to edit. "
When do I have to stop.

Before or after I do the choice to recovery?
Or during I see the menu?

Before. The object is to modify the default menu selection, and to not use the recovery selection.