Ask Your Question

Fedora 18 first boot: "Missing operating system."

asked 2013-03-17 12:37:53 -0600

cmannett85 gravatar image

I installed Fedora 18 via Live USB onto a blank RAID 0 drive 'successfully' (no error messages, etc.). But on the first reboot I just get:

Loading operating system...
Missing operating system.

I checked that the 512MB boot/efi partition was indeed bootable and had some sensible contents - and both seemed to be the case. What else could cause this problem?

I created the bootable stick using the openSUSE ImageWriter; I've heard people have had problems with this, dd, unetbootin, and the Ubuntu equivalent - so are they all as bad as each other?

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2013-03-17 22:40:47 -0600

chandank gravatar image

I had similar problem, it may help in your case. I would check below things to troubleshoot

  1. Check whether the OS was installed in the USB itself? Remember, by default the OS is installed in /dev/sda and if you are booting with USB, Annaconda detects it as SDA and your hard drive as SDB. So just double check that.

  2. Has it installed Grub properly? If not then you have to manually install grub using a another live CD. If Grub is installed properly then, please go to Grub edit menu "e" while grub prompt appears and see where it is trying to find the root file system.

  3. As you said /boot does show some sensible data, then you should check whether your BIOS supports EFI boot or BIOS? If it is UFI based system then you need to create the /boot/efi as vfast and /boot as ext4.

Hope this helps.

edit flag offensive delete link more

answered 2013-03-21 13:04:25 -0600

First, try using supported utilities as described in . I prefer to use dd .

From your description, it is the BIOS that cannot find a bootloader, not the bootloader being unable to find Fedora. You can attempt to reinstall the bootloader, but it may not be possible on a striped volume; GRUB is typically installed to the mbr of a single drive. /boot can be a RAID volume, however.

I also recommend avoiding BIOS-driven raid0 if possible. If you want to have such a configuration, it can be done easily within the installer. Relying on your motherboard's firmware for disk arrays ties you down to that motherboard, making the installation less portable and more prone to failure with BIOS updates.

Additionally, I don't recommend you use raid0 at all. Doing so may increase throughput for large sequential file transfers, but it lowers access latency - which is the most noticeable metric during normal use. You're also doubling the likelyhood of failure and halving the expected lifespan of each drive.

edit flag offensive delete link more

Question Tools


Asked: 2013-03-17 12:37:53 -0600

Seen: 2,590 times

Last updated: Mar 21 '13