Grub is installed and updated, but doesn't start the system

Questions about SolydX and SolydK installation.
danielx
Posts: 19
Joined: 29 Aug 2018 15:51

Grub is installed and updated, but doesn't start the system

Postby danielx » 21 Sep 2019 11:53

I updated from solydX 9/debian9 to solydX 10/debian buster, as described in this post: viewtopic.php?f=4&t=7642

The update was successfull, but I can boot my system only by grub cli, with the following commands:

Code: Select all

set root=(hd0,gpt2)
linux /boot/vmlinuz-4.19.0-6-amd64 root=/dev/sda2
initrd /boot/initrd.img-4.19.0-6-amd64
boot
So my system starts and i try to update grub with:

Code: Select all

grub-install /dev/sda
update-grub
but at the restart, I have another time the grub cli. I tried more times, but it doesn't work.

Can you help me?
Thanks.

kurotsugi
Posts: 2230
Joined: 09 Jan 2014 00:17

Re: Grub is installed and updated, but doesn't start the system

Postby kurotsugi » 21 Sep 2019 12:15

you need to mount the partitions. you'll have to use a live cd to that. there was a tutorial here but I forgot where

danielx
Posts: 19
Joined: 29 Aug 2018 15:51

Re: Grub is installed and updated, but doesn't start the system

Postby danielx » 21 Sep 2019 12:57

The manual is here: viewtopic.php?f=9&t=7468.
I'll try to follow it.

I don't understand why I need a live demo if i have a system already stated up.
What is the difference?

User avatar
escolar
Posts: 133
Joined: 23 Aug 2013 08:14
Location: Spain

Re: Grub is installed and updated, but doesn't start the system

Postby escolar » 21 Sep 2019 16:37

I have updated to Buster 2 pcs, on of them with SolydX and the other with SolydK. I had the grub's problem with the first one, and I had to install grub with a live usb, but I hadn't any problem in the SolydK updating.

danielx
Posts: 19
Joined: 29 Aug 2018 15:51

Re: Grub is installed and updated, but doesn't start the system

Postby danielx » 22 Sep 2019 11:26

I followed the tutorial, but my system doesn't start.

I mounted the root partition:

Code: Select all

live-chroot /dev/sda2
I searched for the boot partition:

Code: Select all

root@solydxk:/# cat /etc/fstab 
# <file system>	<mount point>	<type>	<options>	<dump>	<pass>
UUID=74068b55-01d8-4f59-84b6-fb2dda834ed2	/	ext4	rw,errors=remount-ro,noatime	0	1
UUID=862F-05BB	/boot/efi	vfat	defaults	0	0
UUID=803645d5-8e58-4ca3-b9c1-60bafa086006	/home	ext4	rw,errors=remount-ro,noatime	0	2
UUID=70ab2903-25be-4ce6-afcf-41b206a568e3	swap	swap	sw	0	0

# RAM disks
...

Code: Select all

root@solydxk:/# sudo blkid
/dev/sda4: LABEL="swap" UUID="70ab2903-25be-4ce6-afcf-41b206a568e3" TYPE="swap" PARTLABEL="swap" PARTUUID="7a046ad3-acca-4bd1-888f-ca43e23e6b96"
/dev/sda2: LABEL="SolydX 9 64-bit" UUID="74068b55-01d8-4f59-84b6-fb2dda834ed2" TYPE="ext4" PARTLABEL="root" PARTUUID="d551a3b0-7e36-4a27-b49c-086a11123d0d"
/dev/sda1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="862F-05BB" TYPE="vfat" PARTLABEL="efi" PARTUUID="14b0f48e-0082-4a67-a039-9186b2b2fd6d"
/dev/sda3: LABEL="Home" UUID="803645d5-8e58-4ca3-b9c1-60bafa086006" TYPE="ext4" PARTLABEL="home" PARTUUID="1321dac6-cdf1-41a1-b9c1-618c9157df98"
/dev/sr0: UUID="2018-07-01-09-52-35-00" LABEL="SOLYDX_9_64BIT" TYPE="iso9660" PTUUID="78e30c53" PTTYPE="dos"
/dev/loop0: TYPE="squashfs"
I only found
UUID=862F-05BB /boot/efi
and
/dev/sda1: LABEL_FATBOOT="EFI" LABEL="EFI" UUID="862F-05BB" TYPE="vfat" PARTLABEL="efi"

Do I have a /boot partition ?

I tried the next steps, as in the tutorial:

Code: Select all

root@solydxk:/# mount /dev/sda1 /boot/efi
root@solydxk:/# grub-install /dev/sda
Installing for x86_64-efi platform.
Installation finished. No error reported.
root@solydxk:/# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.19.0-6-amd64
Found initrd image: /boot/initrd.img-4.19.0-6-amd64
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
  WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
  WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
Adding boot menu entry for EFI firmware configuration
done

root@solydxk:/# umount /boot/efi 
root@solydxk:/# exit
exit
Unmounting /target
It doesn't started at the reboot. Can you help me to find the boot partition and to start the system ?
Thanks

User avatar
ilu
Posts: 2496
Joined: 09 Oct 2013 12:45

Re: Grub is installed and updated, but doesn't start the system

Postby ilu » 22 Sep 2019 13:51

Looking at the blkid output you do not have a boot partition. That's ok. You need a live system because you can't modify the system while it's running.

The udev warning is usually seen with lvm (logical volume management) because of a bug, but you don't use that. This thread indicates that hardware UEFI problems might be involved https://forums.kali.org/showthread.php? ... ootloader).

I'm not much inclined to investigate this for hours if a reinstall takes only 20 minutes. Take the latest ISO from here: https://downloads.solydxk.com/nightly/. The installer will let you reuse your old /home, just watch out that it doesn't get formatted. Re-check the summary screen before you hit "proceed".

If the system after a reinstall still doesn't start, we know that it's either a bug (probably hardware-related) or a problem with your old home. Next step would be a full reinstall.

(I'm very much a friend of full reinstall and just copying over the settings I wish to keep. I also like to always keep 2 systems ready - stable and oldstable or stable and futurestable - to always have a working backup system. That's just me though.)

Don't forget to backup all data and - in case /home can't be reused - all settings that you wish to keep.

Feel free to wait for better advice from somebody else.

danielx
Posts: 19
Joined: 29 Aug 2018 15:51

Re: Grub is installed and updated, but doesn't start the system

Postby danielx » 22 Sep 2019 13:53

What is a multiboot EFi?
I have only one system: SolydX. Not Windows. Not others.

Code: Select all

# ls /boot/efi/EFI/
solydx

# ls /boot/efi/EFI/solydx/
BOOTX64.CSV  fbx64.efi  grub.cfg  grubx64.efi  mmx64.efi  shimx64.efi

# efibootmgr -d /dev/sda
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,2001,2002,3000,0001,2004
Boot0000* solydx
Boot0001* Notebook Hard Drive - KINGSTON SA400S37240G
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot3000* Internal Hard Disk or Solid State Disk

User avatar
ilu
Posts: 2496
Joined: 09 Oct 2013 12:45

Re: Grub is installed and updated, but doesn't start the system

Postby ilu » 22 Sep 2019 14:00

I don't think the problem has anything to do with multiboot or windows. That's just coincidence in the other threads. Everywhere I look it has something to do with incompatibilties between lvm and udev, but I can't see any traces of lvm in you output. You'd also know about lvm if you used it.

danielx
Posts: 19
Joined: 29 Aug 2018 15:51

Re: Grub is installed and updated, but doesn't start the system

Postby danielx » 24 Sep 2019 13:56

I have only a laptop with an hard disk. I don't know about lvm.

ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

Re: Grub is installed and updated, but doesn't start the system

Postby ron_widell » 03 Oct 2019 20:58

If you haven't solved this yet--

What are the contents of /etc/default/grub?

ron

User avatar
Tuna130
Posts: 55
Joined: 10 Aug 2013 05:40
Location: Spain

Re: Grub is installed and updated, but doesn't start the system

Postby Tuna130 » 08 Oct 2019 15:08

I am having the same problem as OP. I can only boot through typing manual commands in the Grub command line.

Even a live usb will not boot by itself, only through manual commands at Grub shell. I have reinstalled grub to /dev/sdb through a minimal Debian live system (Buster), but no change yet. Then tried again to /dev/sdb1. But no change. (My drive setup is: HDD: sda1 /home, sda2 swap SSD: sdb1 /boot/efi, sdb2 / )

Grub is there, but does not seem to know how to proceed. Could there be a corruption at EFI? How to fix?
I have the same as daniel 4 posts above, with the efi files and efibootmgr. Did you solve it?

The update was succesfull, SolydX is fully Busterized and works normal. Just won't boot the normal way. Any ideas?

@ron_widel
It doesn't seem that grub reads any settings. Nothing strange in /etc/default/grub.

User avatar
ilu
Posts: 2496
Joined: 09 Oct 2013 12:45

Re: Grub is installed and updated, but doesn't start the system

Postby ilu » 09 Oct 2019 17:56

Tuna130: Don't describe your setup, post the output of sudo blkid and sudo fdisk -l and cat /etc/fstab so we can see.

Your EFi partitions might be messed up. First check partition type (needs to be FAT32). Then have a look at this thread: viewtopic.php?f=9&t=7468 and see what bootinfoscript and efibootmgr tell you. The grubx64.efi might be pointing to a non-existing root partition. There was a problem we fixed like 8 month ago (viewtopic.php?f=5&t=7469&p=69654) but if your system is older you might still see it.

Danielx: the udev warnings might be misleading. Check bootinfoscript and efibootmgr.

ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

Re: Grub is installed and updated, but doesn't start the system

Postby ron_widell » 12 Oct 2019 17:01

Sorry 'bout the late response. I tried responding a few days ago, but got interrupted and the session had timed out before I got back. In the meantime, real life intervened and I couldn't get back until now.

As @ilu pointed out, there is a dearth of information in your post. More data is needed.

As I read the (U)EFI spec, the firmware looks for a file named bootx64.efi in the /EFI/Boot directory of the ESP. I didn't see that directory in the post from @danielx, so I doubt that his issue is related to yours.

Since you can boot by manually issuing commands to the grub prompt, grub HAS been installed to your boot drive. So in addition to the info @ilu is looking for, I'd like to see the output of

Code: Select all

cat /etc/default/grub
I'd also like to see the entirety of the default boot entry in /boot/grub/grub.cfg

As to not being able to boot live media: There are mobo manufacturers whose firmware implementation of UEFI are truly broken. I have personal experience with two different Gigabyte mobos with broken firmware. They each are (just barely) adequate to boot a Windows installation DVD in EFI mode. Neither one will boot a USB thumb drive in EFI mode. One will only boot a thumb drive in CSM (BIOS legacy) while the other won't boot from ANY thumb drive as long as there's a GPT-partitioned hard drive in the system. Even when booting from a hard drive is explicitly disabled in the firmware it still boots from that drive. Again, you provide no useful data so one can only speculate.

Regards,
ron

User avatar
ilu
Posts: 2496
Joined: 09 Oct 2013 12:45

Re: Grub is installed and updated, but doesn't start the system

Postby ilu » 12 Oct 2019 20:21

sudo bootinfoscript will print all relevant information into a report. Attach that file.

ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

Re: Grub is installed and updated, but doesn't start the system

Postby ron_widell » 13 Oct 2019 02:36

@ilu:
Unless I'm not parsing /usr/bin/bootinfoscript (as delivered in Solydk 9) correctly (A DISTINCT possibility), that script doesn't show the contents of /etc/default/grub.

It WILL show the contents of grub.cfg (wherever it's located), which will almost certainly help in determining why grub won't automatically boot the OS. But /etc/default/grub MAY help explain WHY e.g. any erroneous kernel args are placed in grub.cfg.

I don't know if Solydxk shares this malady, as I installed Solydk 9 using optical media. But I recently installed Linux Mint 19.2-Cinnamon using a thumb drive. Upon boot, the system stopped at an emergency initramfs prompt.

It turns out that the Linux Mint installer had identified the location of the installer kernel as the target of the root= kernel arg in /etc/default/grub (and thus, in grub.cfg). When I used optical media for the same installation, it used the correct location for the root= kernel arg. Apparently, it got confused by the thumb drive being writeable media, and assumed that it would always be present.

I edited the boot entry (within grub) to let the kernel know where the REAL root was and successfully booted. Then I corrected the error in /etc/default/grub, rebuilt /boot/grub/grub.cfg and rebooted successfully.

Just an FYI,
ron

ron_widell
Posts: 10
Joined: 04 Nov 2017 20:23

Re: Grub is installed and updated, but doesn't start the system

Postby ron_widell » 13 Oct 2019 14:26

Oops. I neglected to mention: I also created a new initramfs with the correct root declaration.

ron

User avatar
Tuna130
Posts: 55
Joined: 10 Aug 2013 05:40
Location: Spain

Re: Grub is installed and updated, but doesn't start the system

Postby Tuna130 » 16 Oct 2019 12:13

Back from abroad, thanks for your replies!

Below output of the bootinfoscript. There seems to be a problem with core.img not found...
Ilu, I saw your post, FYI my system is not encrypted, and only one OS, and I could not work out how you solved it...

Also alarming, there is no file bootx64.efi, in /boot/efi/EFI/solydx/ (like danielx).

Code: Select all

                  Boot Info Script 0.61      [1 April 2012]


============================= Boot Info Summary: ===============================

 => No boot loader is installed in the MBR of /dev/sda.
 => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 
    27914640 of the same hard drive for core.img, but core.img can not be 
    found at this location.

sda1: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        

sda2: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info: 

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /efi/solydx/fbx64.efi /efi/solydx/grubx64.efi 
                       /efi/solydx/mmx64.efi /efi/solydx/shimx64.efi

sdb2: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  SolydX 10 64-bit
    Boot files:        /boot/grub/grub.cfg /etc/fstab

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10JPVX-22J
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1                   1 1,953,525,167 1,953,525,167  ee GPT


GUID Partition Table detected.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sda1           2,048 1,885,368,319 1,885,366,272 Data partition (Linux)
/dev/sda2   1,885,368,320 1,953,523,711    68,155,392 Swap partition (Linux)

Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: KINGSTON SM2280S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1                   1   234,441,647   234,441,647  ee GPT


GUID Partition Table detected.

Partition    Start Sector    End Sector  # of Sectors System
/dev/sdb1           2,048       206,847       204,800 EFI System partition
/dev/sdb2         206,848   234,440,703   234,233,856 Data partition (Linux)

"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/loop0                                              squashfs   
/dev/loop1                                              squashfs   
/dev/loop2                                              squashfs   
/dev/loop3                                              squashfs   
/dev/loop4                                              squashfs   
/dev/loop5                                              squashfs   
/dev/loop6                                              squashfs   
/dev/loop7                                              squashfs   
/dev/loop8                                              squashfs   
/dev/sda1        c106e77a-7647-4b91-b139-e8e4980149cc   ext4       Home
/dev/sda2        bda74307-c163-4136-a6d7-d6d6c4f1cb4f   swap       
/dev/sdb1        9102-9A6C                              vfat       EFI
/dev/sdb2        e2407ef8-4088-43be-b22c-87b07e0f8c93   ext4       

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/sda1        /home                    ext4       (rw,noatime,errors=remount-ro)
/dev/sdb1        /boot/efi                vfat       (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/sdb2        /                        ext4       (rw,noatime,errors=remount-ro)


=========================== sdb2/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# 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_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
else
  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1024x768
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
else
  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
fi
insmod gfxmenu
loadfont ($root)/boot/grub/themes/solydx/unifont-16.pf2
loadfont ($root)/boot/grub/themes/solydx/unifont-20.pf2
insmod png
set theme=($root)/boot/grub/themes/solydx/theme.txt
export theme
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd1,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
else
  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
fi
insmod png
if background_image /usr/share/images/desktop-base/desktop-grub.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/07_solydxk_theme ###
set color_normal=white/black
set color_highlight=dark-gray/white
### END /etc/grub.d/07_solydxk_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'SolydX 10 64-bit GNU/Linux' --class solydx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e2407ef8-4088-43be-b22c-87b07e0f8c93' {
	load_video
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
	else
	  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
	fi
	echo	'Loading Linux 4.19.0-6-amd64 ...'
	linux	/boot/vmlinuz-4.19.0-6-amd64 root=UUID=e2407ef8-4088-43be-b22c-87b07e0f8c93 ro  quiet splash
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-4.19.0-6-amd64
}
submenu 'Advanced options for SolydX 10 64-bit GNU/Linux' $menuentry_id_option 'gnulinux-advanced-e2407ef8-4088-43be-b22c-87b07e0f8c93' {
	menuentry 'SolydX 10 64-bit GNU/Linux, with Linux 4.19.0-6-amd64' --class solydx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-6-amd64-advanced-e2407ef8-4088-43be-b22c-87b07e0f8c93' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
		else
		  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
		fi
		echo	'Loading Linux 4.19.0-6-amd64 ...'
		linux	/boot/vmlinuz-4.19.0-6-amd64 root=UUID=e2407ef8-4088-43be-b22c-87b07e0f8c93 ro  quiet splash
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.19.0-6-amd64
	}
	menuentry 'SolydX 10 64-bit GNU/Linux, with Linux 4.19.0-6-amd64 (recovery mode)' --class solydx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-6-amd64-recovery-e2407ef8-4088-43be-b22c-87b07e0f8c93' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
		else
		  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
		fi
		echo	'Loading Linux 4.19.0-6-amd64 ...'
		linux	/boot/vmlinuz-4.19.0-6-amd64 root=UUID=e2407ef8-4088-43be-b22c-87b07e0f8c93 ro single 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.19.0-6-amd64
	}
	menuentry 'SolydX 10 64-bit GNU/Linux, with Linux 4.9.0-11-amd64' --class solydx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.9.0-11-amd64-advanced-e2407ef8-4088-43be-b22c-87b07e0f8c93' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
		else
		  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
		fi
		echo	'Loading Linux 4.9.0-11-amd64 ...'
		linux	/boot/vmlinuz-4.9.0-11-amd64 root=UUID=e2407ef8-4088-43be-b22c-87b07e0f8c93 ro  quiet splash
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.9.0-11-amd64
	}
	menuentry 'SolydX 10 64-bit GNU/Linux, with Linux 4.9.0-11-amd64 (recovery mode)' --class solydx --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.9.0-11-amd64-recovery-e2407ef8-4088-43be-b22c-87b07e0f8c93' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt2 --hint-efi=hd1,gpt2 --hint-baremetal=ahci1,gpt2  e2407ef8-4088-43be-b22c-87b07e0f8c93
		else
		  search --no-floppy --fs-uuid --set=root e2407ef8-4088-43be-b22c-87b07e0f8c93
		fi
		echo	'Loading Linux 4.9.0-11-amd64 ...'
		linux	/boot/vmlinuz-4.9.0-11-amd64 root=UUID=e2407ef8-4088-43be-b22c-87b07e0f8c93 ro single 
		echo	'Loading initial ramdisk ...'
		initrd	/boot/initrd.img-4.9.0-11-amd64
	}
}

### 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 ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
	fwsetup
}
### 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 ###
--------------------------------------------------------------------------------

=============================== sdb2/etc/fstab: ================================

--------------------------------------------------------------------------------
# <file system>	<mount point>	<type>	<options>	<dump>	<pass>
UUID=e2407ef8-4088-43be-b22c-87b07e0f8c93	/		ext4	rw,errors=remount-ro,noatime	0	1
UUID=9102-9A6C					/boot/efi	vfat	defaults			0	0
UUID=c106e77a-7647-4b91-b139-e8e4980149cc	/home		ext4	rw,errors=remount-ro,noatime	0	2
UUID=bda74307-c163-4136-a6d7-d6d6c4f1cb4f	swap		swap	sw				0	0

# RAM disks
tmpfs   /tmp                    tmpfs   defaults,noatime,mode=1777              0       0
#tmpfs   /var/cache/apt/archives tmpfs   defaults,noexec,nosuid,nodev,mode=0755  0       0
tmpfs   /var/tmp                tmpfs   defaults,noatime                        0       0
tmpfs   /var/backups            tmpfs   defaults,noatime                        0       0
# Disable /var/log/* tmpfs dirs when enabling tmpfs on /var/log
#tmpfs   /var/log                tmpfs   defaults,noatime                        0       0
#tmpfs   /var/log/apt            tmpfs   defaults,noatime                        0       0
#tmpfs   /var/log/lightdm        tmpfs   defaults,noatime                        0       0
#tmpfs   /var/log/samba          tmpfs   defaults,noatime                        0       0
tmpfs   /var/log/cups           tmpfs   defaults,noatime                        0       0
tmpfs   /var/log/ConsoleKit     tmpfs   defaults,noatime                        0       0
tmpfs   /var/log/clamav         tmpfs   defaults,noatime                        0       0

#router nfs share
192.168.178.1:/mnt/sda1	/media/Backup nfs rw,hard,intr,rsize=8192,wsize=8192,timeo=14 0 0--------------------------------------------------------------------------------

=================== sdb2: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)


=============================== StdErr Messages: ===============================

cat: /tmp/BootInfo-NFsoNnA5/Tmp_Log: No such file or directory
mdadm: No arrays found in config file or automatically

and cat /etc/default/grub:

Code: Select all

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -d -s 2>/dev/null || echo SolydXK`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=1024x768

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


# Set theme
GRUB_THEME=/boot/grub/themes/solydx/theme.txt
and efibootmgr:

Code: Select all

efibootmgr -d /dev/sdb1
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0004,0003,0002,0000
Boot0000* Windows Boot Manager
Boot0001* solydx
Boot0002* LAN : IBA GE Slot 00C8 v1553
Boot0003* SATA : PORT 0 : WDC WD10JPVX-22JC3T0 : PART 0 : Boot Drive
Boot0004* M.2 SATA :KINGSTON SM2280S3120G : PART 0 : Boot Drive
Attachments
RESULTS.txt
bootinfoscript
(15.24 KiB) Downloaded 4 times

User avatar
ilu
Posts: 2496
Joined: 09 Oct 2013 12:45

Re: Grub is installed and updated, but doesn't start the system

Postby ilu » 16 Oct 2019 16:29

Tuna130: Are you sure you booted the life system into EFI mode when you installed the system? That's necessary for an EFI install. Since booting the live system already went wrong, check your BIOS/UEFI settings. If possible switch off compatibility mode and try to go with EFI only. Get the live system to boot correctly before you install. If that doesn't work, run bootinfoscript on the live system. Does it show the same error?

Edit: Sorry, I forgot that this was an update, not a new install. I still think BIOS/EFI mode got mixed up but no idea why it fails now. The update script doesn't change anything grub-related.

Anyway, try to get the live system to boot correctly into EFI mode. Check the presence of /boot/efi/solydx/grubx64.efi. If USB doesn't work, try to use another port or a DVD. Then reinstall grub from the live system. If that doesn't work, I wouldn't invest more time but backup and reinstall.
Also alarming, there is no file bootx64.efi, in /boot/efi/EFI/solydx/ (like danielx).
Huh? Bootinfoscript says it found the correct files in /boot/efi/. Post ls -al /boot/efi/*. AFAIK only MSWin uses that second EFI directory with capital letters but I can't check since I don't have an EFI system at hand.

User avatar
Tuna130
Posts: 55
Joined: 10 Aug 2013 05:40
Location: Spain

Re: Grub is installed and updated, but doesn't start the system

Postby Tuna130 » 16 Oct 2019 21:22

I'll check bios settings for EFI mode.

Code: Select all

ls -al /boot/efi/*
total 2
drwxr-xr-x 3 root root 512 Jan 13  2019 .
drwxr-xr-x 3 root root 512 Jan  1  1970 ..   <--- 1970 WTF?
drwxr-xr-x 2 root root 512 Oct  4 15:05 solydx

cd /boot/efi/
ls -al
total 5
drwxr-xr-x 3 root root  512 Jan  1  1970 .
drwxr-xr-x 4 root root 4096 Oct  4 21:39 ..
drwxr-xr-x 3 root root  512 Jan 13  2019 EFI

tree
.
└── EFI
    └── solydx
        ├── BOOTX64.CSV
        ├── fbx64.efi
        ├── grub.cfg
        ├── grubx64.efi
        ├── mmx64.efi
        └── shimx64.efi

User avatar
ilu
Posts: 2496
Joined: 09 Oct 2013 12:45

Re: Grub is installed and updated, but doesn't start the system

Postby ilu » 18 Oct 2019 03:04

Tuna130 wrote:
16 Oct 2019 21:22
drwxr-xr-x 3 root root 512 Jan 1 1970 .. <--- 1970 WTF?
This looks like at some point in time your bios buffer battery failed and the setting fell back. This can bollix things up. Maybe, maybe not.


Return to “Installation”

Who is online

Users browsing this forum: Google [Bot] and 2 guests