Sign in with
Sign up | Sign in
Your question
Solved

Linux won't boot on ASRock E350M1

Tags:
  • SSD
  • Linux
  • Boot
  • ASrock
  • Servers
Last response: in Linux/Free BSD
Share
May 28, 2014 2:15:11 PM

Hi,
I’m nearly desperate and almost giving up; my first assembled home server:

AsRock E350M1
Kingston 120Gb SSD
2Gb RAM

I boot from usb key and install Lubuntu on SSD, restart the system and it won’t boot and gives me the “Reboot and Select proper boot device..” message; if I reboot from USB and browse the SSD I can see the installation files.
I even tried a noter HDD and I get the same problem.

I check the UEFI and SSD is enabled in storage and first option on the boot list.

Can U please help me??

More about : linux boot asrock e350m1

May 28, 2014 3:12:40 PM

Hi thank you for your quick reply, I did as suggested but I still can't get rid of the problem. I booted in boot-repair and first I get a message about RAID and about a package that has to be downloaded, then it does all the scan and when I choose repair common problem it says I installed a os that it's not EFI compatible and suggests to download and install Ubuntu 64bit.
Really??
m
0
l
Related resources
May 28, 2014 3:38:09 PM

Is the system connected to the internet? I googled "lubuntu efi" and found a result indicating that the bootloader doesn't work without a network connection (apparently a bug in the code somewhere)
m
0
l
May 28, 2014 11:24:39 PM

yes it is... don't u think is something related to the BIOS or UEFI settings? Boot priorities seems right and I can see the HDD
m
0
l
May 29, 2014 7:03:32 AM

I checked the motherboard manual online and see no options that seem to be applicable. However, if you press F11 at startup to access the boot menu, there should be the option to launch the lubuntu installer in UEFI mode (it would preface the thumb drive entry with "UEFI"). Perhaps the installer was initially run in legacy mode.

m
0
l
a b 5 Linux
May 29, 2014 7:05:44 AM

In boot-repair you have advanced options which allows you to designate where to install grub, the boot loader. Try moving it.
m
0
l
May 29, 2014 9:04:29 AM

Sorry wrong button. none of the suggested solution works.
m
0
l

Best solution

a b 5 Linux
May 30, 2014 12:01:04 AM

I unselected so it still shows unsolved.

Boot-repair creates a log that will tell us what it does or doesn't see. Look for the boot-repair.log in /var/log/boot-sav/log/
Post it in a dropbox or some such so we can have a look, it can be fairly long. If it's not there then you need to do a reinstall.
Share
May 30, 2014 1:24:05 AM

SchizTech said:
I checked the motherboard manual online and see no options that seem to be applicable. However, if you press F11 at startup to access the boot menu, there should be the option to launch the lubuntu installer in UEFI mode (it would preface the thumb drive entry with "UEFI"). Perhaps the installer was initially run in legacy mode.



How well it definitely looks like I'm unfamiliar with this forum, and you guys are really kind on helping me.

I'll post boot repair log on Tue, when I'll be back home, in the meanwhile you'll be as disappointed as I am, discovering Win 7 install and boots flawlessly...
m
0
l
June 3, 2014 10:42:57 AM

Ok, ran boot repair and got this link: http://paste.ubuntu.com/7581777/

Just to be clear what I want to do is erase all previous install and be able to install ONLY Amahi or Ubuntu Server or Lubuntu or Mint...

THANKS
m
0
l
June 3, 2014 11:15:51 AM

It appears that the GRUB bootloader isn't correctly reading a required file (core.img). If the same error happens after another wipe out and install you can boot into the system with the install disk in Live CD mode and mount the hard drive, then reinstall grub from the command line. (example in link below)

If this fails, you might need to set up a small grub partition (see notes on grub/gpt in link)

https://help.ubuntu.com/community/Grub2/Installing
m
0
l
June 3, 2014 11:33:19 AM

SchizTech said:
It appears that the GRUB bootloader isn't correctly reading a required file (core.img). If the same error happens after another wipe out and install you can boot into the system with the install disk in Live CD mode and mount the hard drive, then reinstall grub from the command line. (example in link below)

If this fails, you might need to set up a small grub partition (see notes on grub/gpt in link)

https://help.ubuntu.com/community/Grub2/Installing


Thanks, I'll check the link you sent, but now how do I wipe and install??



m
0
l
June 3, 2014 11:37:35 AM

Boot the installer again, delete everything on the disk and start a new installation
m
0
l
a b 5 Linux
June 4, 2014 1:36:04 AM

From the report we get that you are installing a 32 bit version on a 64 bit machine, use a 64 bit iso, it's faster.
Is your bios set to boot from the 120GB drive? That's where it should be set.
Your boot-loader is not set to efi because it did not detect a efi-win install, in advanced settings you can set boot-repair to install efi.
That should work but I recommend you download a 64bit linux and install it. during the install you will be given the option of side by side with the existing or replace it, go ahead and replace it.

"/boot detected. Please check the options.
=================== Repair blockers
64bits detected. Please use this software in a 64bits session. (Please use Linux-Secure-Remix-64bit (www.sourceforge.net/p/linux-secure) which contains a 64bits-compatible version of this software.) This will enable this feature.
=================== Final advice in case of recommended repair
Please do not forget to make your BIOS boot on sda (120GB) disk!

=================== Default settings
Recommended-Repair
This setting would reinstall the grub2 of sda3 into the MBRs of all disks (except USB without OS), using the following options: sda1/boot,
Grub-efi would not be selected by default because: no-win-efi
Additional repair would be performed: unhide-bootmenu-10s

=================== Settings chosen by the user
Boot-Info
This setting will not act on the MBR.



No change has been performed on your computer."
m
0
l
June 4, 2014 10:21:43 AM

I'm getting really frustrated here...
My BIOS is set to boot from SSD first and USB then, in fact with windows everything was up and running.
I tried to repair the EFI with Boot-Repair, but the operation get aborted for some reason, it says I don't have a EFI compatible version and stops.
So I tried to restore the MBR, it does its thing but, after rebooting, I end up with the same error "..not bootable device".
So far I was only able to install Lubuntu from USB, but then I can't boot in, from SSD.
So I tried and download various releases: amahi, zenytal, mint ... and created a bootable usb with Linux Boot Builder (for some reason Unetbootin doesn't do) and all I get, in the best case scenario, booting from USB is a GNU GRUB prompt grub>
What should I do? I even found an old external usb cd-drive that I can use...
m
0
l
June 4, 2014 11:37:17 AM

Let me take this back a step. Bear with me here, but don't take the simple question the wrong way: how are you booting the USB stick? When you access the boot menu, does it show different options for the thumb drive (one not prefaced and another prefaced with "UEFI: )? Many UEFI enabled boards will do this to distinguish booting in legacy BIOS mode and booting in EFI mode.

If so which option have you been using? If the other option is present have you booted in that mode to attempt an installation?
m
0
l
June 5, 2014 1:01:15 AM

Ok,

when I press F11 to boot from USB I usually see:
SATA ...
USB ...
EFI ...
EFI ...
If I choose USB I end up with "No bootable ..." message, if I choose EFI I end up in the grub shell, and get stuck.
But finally I found a solution following these instruction: http://www.ubuntu.com/download/desktop/create-a-usb-sti...
I created a bootable Amahi USB and was able to install, boot and reboot.
For some reasons seems that Fedora install works and I finally got out of the brick mode
m
0
l
!