jochen-blacha
October 6th, 2014, 07:16 PM
Hi!
I have a rather strange "Installation" problem with Ubuntu 14.04.1 and UEFI...
Before I dig into the actual problem there's one thing I'm curious about, because I can't figure out why it doesn't want to work:
When I tried installing Ubuntu onto a USB 3.0 connected SSD (Crucial M500 240GB in a Sharkoon QuickPort XT dock connected to a Gigabyte 990FXA-UD3) the installation actually works (grub was written to the MBR of the SSD to "dual-boot" via the firmware boot-menu therefore keeping it from messing about with Windows Loader) but upon trying to boot the installed system all that happens is that the drive just "sits there" doing some I/O for some prolonged amount of time (~20 seconds?) until grub throws a "Attempted to read beyond partition boundaries" error back. Funnily enough, it works once the drive is connected to a USB 2.0 port, but that leaves more transfer-speed to be desired. Any chance Linux not yet being able to fire up itself from a USB 3.0 drive?
Anyway, back to the UEFI problem (the SSD is now internally connected to the SATA ports)...
I created the partitioning according to the Wiki (BIOS data area, grub area, boot partition, root partition, home partition, swap) and am able to successfully install Ubuntu. After the installation is done it boots up just fine (the firmware's boot-menu even shows me "ubuntu" instead of the device identifier) ... BUT ... once I let it install a kernel update it self-destructs. This means that upon re-boot grub will throw an error about not being able to load the kernel and call it a day. Even manual intervention (messing about with that pile of grub - sorry, I don't like grub at all, never had) doesn't get the system to boot again.
Setting the firmware (BIOS) of the motherboard to activate "Legacy BIOS support", re-partitioning and re-installing in a classic MBR scheme (just boot, root and swap partitions) works just fine (not really to any greater surprise when we "fake" a legacy BIOS system).
Any thoughts why the system "self-destructs" when running UEFI exclusively and how to rectify the problem?
I have a rather strange "Installation" problem with Ubuntu 14.04.1 and UEFI...
Before I dig into the actual problem there's one thing I'm curious about, because I can't figure out why it doesn't want to work:
When I tried installing Ubuntu onto a USB 3.0 connected SSD (Crucial M500 240GB in a Sharkoon QuickPort XT dock connected to a Gigabyte 990FXA-UD3) the installation actually works (grub was written to the MBR of the SSD to "dual-boot" via the firmware boot-menu therefore keeping it from messing about with Windows Loader) but upon trying to boot the installed system all that happens is that the drive just "sits there" doing some I/O for some prolonged amount of time (~20 seconds?) until grub throws a "Attempted to read beyond partition boundaries" error back. Funnily enough, it works once the drive is connected to a USB 2.0 port, but that leaves more transfer-speed to be desired. Any chance Linux not yet being able to fire up itself from a USB 3.0 drive?
Anyway, back to the UEFI problem (the SSD is now internally connected to the SATA ports)...
I created the partitioning according to the Wiki (BIOS data area, grub area, boot partition, root partition, home partition, swap) and am able to successfully install Ubuntu. After the installation is done it boots up just fine (the firmware's boot-menu even shows me "ubuntu" instead of the device identifier) ... BUT ... once I let it install a kernel update it self-destructs. This means that upon re-boot grub will throw an error about not being able to load the kernel and call it a day. Even manual intervention (messing about with that pile of grub - sorry, I don't like grub at all, never had) doesn't get the system to boot again.
Setting the firmware (BIOS) of the motherboard to activate "Legacy BIOS support", re-partitioning and re-installing in a classic MBR scheme (just boot, root and swap partitions) works just fine (not really to any greater surprise when we "fake" a legacy BIOS system).
Any thoughts why the system "self-destructs" when running UEFI exclusively and how to rectify the problem?