[Bug 1858300] [NEW] Ubuntu crashed unexpectedly, couldn't find i386-pc/normal.mod, system doesn't boot

[Santiago Ramos]

Public bug reported:

I'm not sure. First I tried to locate where is the i386-pc/normal.mod from which start the system, it didn't work. Tried to reinstall Ubuntu deleting the previous one, and couldn't find EFI file, so the system won't boot, installation didn't end right. It's not clear for me if there is a relationship between those situations. I just would like to have access back to my computer after the whole day trying solutions.
Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan  4 23:45:23 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1858300

Title:
  Ubuntu crashed unexpectedly, couldn't find i386-pc/normal.mod, system
  doesn't boot

Status in grub-installer package in Ubuntu:
  New

Bug description:
  I'm not sure. First I tried to locate where is the i386-pc/normal.mod from which start the system, it didn't work. Tried to reinstall Ubuntu deleting the previous one, and couldn't find EFI file, so the system won't boot, installation didn't end right. It's not clear for me if there is a relationship between those situations. I just would like to have access back to my computer after the whole day trying solutions.
  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubiquity 19.04.9
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CasperVersion: 1.405
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  4 23:45:23 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: grub-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1858300/+subscriptions