Centos 8 DVD boots on one computer but gets stuck on the other

[Woistmeinauto]

First off, burning to a USB stick does boot normally.

Why i need DVD? My old Gigabyte motherboard supports EFI boot only from DVD. It's one of those old hybrid efi boards.

DVD gets stuck regardless of the option.It's stuck on EFI it's stuck on BIOS.

Atm i have a fat32 partition that was created by windows and later i added Manjaro linux. Because the computer does not allow managing EFI i had to replace bootx64.efi of windows with bootx64.efi of Manjaro because otherwise it was booting only to windows.
My EFI folder has 3 folders: Manjaro, Microsoft and Boot.

The problem occurs after grub.
I know it's not a hardware problem because from USB it boots fine.
I know the DVD is fine because my laptop boots it and it's UEFI.

It's stuck on reached target basic system. Removing quiet does not display any error messages.
After a while it starts listing some dracut queue errors and i end up in emergency shell.
1 time it got stuck on starting dracut initqueue hook.

Tried nomodeset, does not help and i wouldn't expect anyways because it's booting usb fine.
I burned the dvd @x4 using k3b app from manjaro.
Any help is greatly appreciated.

[organicchemistry_01]

Well if its after grub, this maybe an indication of driver issue. In my case, its the GPU driver, I add nomodeset in the boot params after pressing `e` to edit the boot.

After it boots with nomodeset, I install the nvidia propriety driver, then I dont need the nomotset anymore.

Edit:

Hmm, since u have tried nomodeset already, I am thingking it must be booting the wrong /dev/sdX, it happens sometimes, it adds the USB as /dev/sdX reference then, when it boots, it looks for the USB and a different /dev/sdX

If you can just give me an `lsblk` of your system.

[Woistmeinauto]

sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 499M 0 part
├─sda2 8:2 0 300M 0 part /boot/efi
├─sda3 8:3 0 321.5G 0 part /run/media/n/E476A46476A438E6
├─sda4 8:4 0 511.7G 0 part /run/media/n/01CFD131F13B1EE0
├─sda5 8:5 0 4G 0 part [SWAP]
└─sda6 8:6 0 52.7G 0 part /
sr0 11:0 1 1.6G 0 rom


A guy suggets changing hd: part with sr0 i tried chaning it to sr0: but didn't work.
Btw as i mentioned in my main post this is not a usb it's a dvd.
Also, i can boot USB with no issues but my system cannot run EFI from usb. It's hybrid efi so not quite uefi, it's a hacked crap firmware really.
There is no driver issue cause USB runs just fine, the dvd cannot boot in BIOS mode either so it's not the EFI that's the problem either.

[Woistmeinauto]

sd 1:0:0:0: [sda] attached SCSI disk
And after that itstarts listing initqueue timeouts.
I have no scsi disks.

[Woistmeinauto]

I think i've located the problem.

When i ls from grub on problematic pc with only the dvd drive plugged in:
(hd) (hd0,msdos2)
On the other working fine pc:
(cd) (cd0,msdos2)

Is hd for hard drives ? Can this be the root of this problem?

[Woistmeinauto]

I manually set inst stage2 entry to (hd0,msdos2)/images/installer.img but it still hangs up on the same place, does not complain about SCSI anymore though.

[organicchemistry_01]

Do you now have 4 folders in efi?

Since your latest install is CentOS 8.

[Woistmeinauto]

No i have 3 folders, i never managed to install CentOS.
I have:
BOOT
Manjaro
Microsoft.

I realised changing disk label does exactly what happens to me.
I now think this is somehow related to label.

[organicchemistry_01]

You may check that the lable should match in EFI/BOOT/grub.cfg from iso and burned version.

[Woistmeinauto]

No, the dvd works on other PC. For some reason it does not work on this PC.
It's an old gigabyte hybrid efi motherboard. Not a shock that it's causing issues.
It might as well be the old dvd drive not being supported by CentOS somehow.
Ubuntu and Manjaro dvds work fine with it.

The DVD drive was being recognized as HDD I think and that caused it to not find required installation files.

Anyways I managed to solve the problem by manually creating a GPT installation HDD disk.

It appears MBR/EFI combination does not work on this motherboard either, that is why i had to use GPT with manual partitioning.

I will make a guide about it sometime. It's simple anyways but wouldn't hurt.