search

tal-zvon / RAM_booster

http://ubuntuforums.org/showthread.php?t=1594694
36 stars 14 forks source link

can't boot into Ubuntu Ram #4

Closed notslang closed 10 years ago

notslang commented 10 years ago

upon booting, I get this error:

error: file /boot/initrd.img-3.11.0-14-generic.efi.signed not found

which seems to be due to this section of /boot/grub/grub.cfg:

### BEGIN /etc/grub.d/06_RAMSESS ###

menuentry "Ubuntu to RAM" {
  set uuid_grub_boot=4bc52961-1f5e-46bf-b1c8-d6ba2231c1fe
  set uuid_os_root=4bc52961-1f5e-46bf-b1c8-d6ba2231c1fe

  search --no-floppy --fs-uuid $uuid_grub_boot --set=grub_boot

  set grub_boot=($grub_boot)

  if [ $uuid_grub_boot == $uuid_os_root ] ; then                 
     set grub_boot=$grub_boot/boot
  fi

  linux $grub_boot/vmlinuz-3.11.0-14-generic.efi.signed bootfrom=/dev/disk/by-uuid/$uuid_os_root boot=live toram=filesystem.squashfs apparmor=0 security="" root=/dev/disk/by-uuid/$uuid_os_root ro quiet splash
  initrd $grub_boot/initrd.img-3.11.0-14-generic.efi.signed
}
### END /etc/grub.d/06_RAMSESS ###

oh, and these are the files that are actually present in /boot:

abi-3.11.0-12-generic         memtest86+.bin
abi-3.11.0-13-generic         memtest86+_multiboot.bin
abi-3.11.0-14-generic         System.map-3.11.0-12-generic
config-3.11.0-12-generic      System.map-3.11.0-13-generic
config-3.11.0-13-generic      System.map-3.11.0-14-generic
config-3.11.0-14-generic      vmlinuz-3.11.0-12-generic
efi                           vmlinuz-3.11.0-13-generic
grub                          vmlinuz-3.11.0-13-generic.efi.signed
initrd.img-3.11.0-12-generic  vmlinuz-3.11.0-14-generic
initrd.img-3.11.0-13-generic  vmlinuz-3.11.0-14-generic.efi.signed
initrd.img-3.11.0-14-generic

Any clue as to why the grub config is wrong?

PS: I'm running Ubuntu 13.10 and booting into the regular Ubuntu install works fine.

tal-zvon commented 10 years ago

initrd.img-3.11.0-14-generic.efi.signed is probably the signed version of an initrd image. It sounds like you have a very new system that uses efi. Regular grub doesn't handle EFI well, which is why grub-efi-amd64 was created. Unfortunately, my script was never written to handle EFI at all, so unless you can tell your bios to try to boot in legacy mode (which may or may not help), the script is unlikely to work for you. I may try to update it to work with EFI in the future, but it's unlikely to happen anytime soon.