[SOLVED]system does not boot

Strike0 · 2023-09-19 10:27:58

No, just boot the ISO and use a partitioning tool (e.g. gdisk/cgdisk) to change the type to EF00/Efi system. Then try booting it again.

b42 · 2023-09-19 10:51:17

changed it to EFI system but it does not boot nonetheless

http://0x0.st/HOOx.txt

Strike0 · 2023-09-19 11:05:43

Hm, too bad. Perhaps the grub-install did not work originally, in this pic, if states (hd0,msdos2). That reads fishy, because you clearly use gpt now.

Try to repeat the grub-install command you used, after chrooting again.

b42 · 2023-09-19 11:14:57

did that but it still shows hd0, msdos

Strike0 · 2023-09-19 11:24:34

b42 wrote:

seth wrote:
As Strike0 suggested, the partition type is wrong.
may I ask where did you find it? Could you elaborate on this matter please?

Seth found that by looking the output of 1 which you then changed to the correct EFI system type (2). The partition type is independent of the used filesystem, it denotes what filesystem the partition is supposed to contain. A system booting with UEFI must exactly have one active EFI system partition (3), a system booting with legacy Bios must have one partition marked as "bootable".

Strike0 · 2023-09-19 11:47:54

b42 wrote:

did that but it still shows hd0, msdos

And I suppose grub-install did not complain with errors.(?)

Frankly, I'm at a loss. Have you looked in the bios, if there is an option to explicitly set it to UEFI?
I'd check that and if it does not help/is available, try to install grub without chrooting next. See the note, but we have to recheck how to excute it.

From reading the note I would currently: mount /dev/sda2 root to /mnt, next mount /dev/sda1 to /mnt/boot and execute the install with

grub-install --target=x86_64-efi --efi-directory=/mnt/boot --bootloader-id=GRUB --boot-directory=/mnt/boot --removable --recheck

But I can't remember right now, if --efi-directory is supposed to be /boot or /mnt/boot in this exception of installing outside the chroot.

seth · 2023-09-19 11:56:16

https://imgbb.com/fC0ZZxV is from the install iso
https://0x0.st/HOOx.txt says the partition is GPT

Run the command in #31 and post the complete output.
In doubt you can log it into a file in a "script" session.

b42 · 2023-09-19 12:14:23

Installing for x86_64-efi platform

Installation finished. No error reported.

seth · 2023-09-19 12:23:03

So is grub now found?

b42 · 2023-09-19 14:12:59

Strike0 wrote:

b42 wrote:
did that but it still shows hd0, msdos
From reading the note I would currently: mount /dev/sda2 root to /mnt, next mount /dev/sda1 to /mnt/boot and execute the install with
grub-install --target=x86_64-efi --efi-directory=/mnt/boot --bootloader-id=GRUB --boot-directory=/mnt/boot --removable --recheck

It did work!

Now, have you guys got any idea why the usual grub-install did not work if it did work a week ago on the same machine with the same disk?

and the interesting thing is that my /dev/sda1 is not partitioned as EFI System and it still boots.

Last edited by b42 (2023-09-19 14:46:58)

b42 · 2023-09-21 07:54:49

any thoughts on that?

2ManyDogs · 2023-09-21 10:50:49

b42 wrote:

any thoughts on that?

Don't do that. https://wiki.archlinux.org/title/Genera … es#Bumping

seth · 2023-09-21 12:45:03

If "grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub" was literal (nb. the capitalization) and possibly you did this outside a chroot, there're obvious differences between that and the ultimately succesful command.
We can't tell you what you did wrong 10 days ago, evidently "something"

b42 · 2023-09-21 15:29:29

seth wrote:

If "grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub" was literal (nb. the capitalization) and possibly you did this outside a chroot, there're obvious differences between that and the ultimately succesful command.
We can't tell you what you did wrong 10 days ago, evidently "something"

Yes, now I did that outside of chroot, but those 10 days ago I did this while chrooted:

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub

and I was able to successfully launch the system.

Strike0 · 2023-09-22 11:34:46

b42 wrote:

and the interesting thing is that my /dev/sda1 is not partitioned as EFI System and it still boots.

You write you get a grub menu without a partition type of EFI system for it?

I think that is wrong. Do you mean it?
My speculation would be you had an EFI ssytem partition 10 days ago, installed grub's efi into it, later decided to wipe the disk incl. partition table to reinstall fresh and did not re-set the partition type. hence, it failed to boot.

Arch Linux

#26 2023-09-19 10:27:58

Re: [SOLVED]system does not boot

#27 2023-09-19 10:51:17

Re: [SOLVED]system does not boot

#28 2023-09-19 11:05:43

Re: [SOLVED]system does not boot

#29 2023-09-19 11:14:57

Re: [SOLVED]system does not boot

#30 2023-09-19 11:24:34

Re: [SOLVED]system does not boot

#31 2023-09-19 11:47:54

Re: [SOLVED]system does not boot

#32 2023-09-19 11:56:16

Re: [SOLVED]system does not boot

#33 2023-09-19 12:14:23

Re: [SOLVED]system does not boot

#34 2023-09-19 12:23:03

Re: [SOLVED]system does not boot

#35 2023-09-19 14:12:59

Re: [SOLVED]system does not boot

#36 2023-09-21 07:54:49

Re: [SOLVED]system does not boot

#37 2023-09-21 10:50:49

Re: [SOLVED]system does not boot

#38 2023-09-21 12:45:03

Re: [SOLVED]system does not boot

#39 2023-09-21 15:29:29

Re: [SOLVED]system does not boot

#40 2023-09-22 11:34:46

Re: [SOLVED]system does not boot

Board footer