Jump to content











Photo
- - - - -

Grub4Dos and Ubuntu - Same code, different results

ubuntu 16.04 18.04 g4d 0.4.4

  • Please log in to reply
2 replies to this topic

#1 Jwate

Jwate
  • Members
  • 1 posts
  •  
    United States

Posted 3 weeks ago

I have a Dell XPS with multiple drives, one for each OS.  I can boot Ubuntu 16.04 fine with the G4D code:

"UUID=c292e65b-1416-4774-9198-45c434fdb940

Kernel /vmlinuz root=/dev/sda1 ro

initrd /initrd.img"

I get no errors

 

With Ubuntu 18.04, I use:

"UUID=eddffeb2-6d53-4c9d-96e5-504a838324b4

kernel /vmlinuz root=/dev/sdb1 ro

initrd /initrd.img"

 

I get a error 13 after the UUID line.  It says "Booting Ubuntu 18.04.2 LTS (sdb1).  Setting root to (hd1,0). Filetype is ext2fs, partition type 0x83" and stops with error 13.

 

 

I've always used G4D quite successfully until Ubuntu 18.04.  18.04 boots okay under native Grub2.  I'm  very confused.  I might point out that the 16.04 drive is a Toshiba 500GB and the 18.04 is a WDC 500GB.  Any help will be appresiated!



#2 tinybit

tinybit

    Gold Member

  • Developer
  • 1117 posts
  •  
    China

Posted 3 weeks ago

you might want to try grub4dos 2019 here: http://grub4dos.chenall.net/



#3 steve6375

steve6375

    Platinum Member

  • Developer
  • 6935 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars, www.easy2boot.com
  •  
    United Kingdom

Posted 3 weeks ago

Are these internal drives or USB drives?

What do you see if you try each of the commands from the command line?

Is it the kernel line that is failing? grub4dos usually reports the failing line.

try

blocklist /vmlinuz

before the kernel command







Also tagged with one or more of these keywords: ubuntu, 16.04, 18.04, g4d 0.4.4

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users