Ask Your Question
2

Fedora in installed but there are no bootable device

asked 2015-01-07 18:40:40 -0600

Monster gravatar image

updated 2017-03-27 05:10:12 -0600

hhlp gravatar image

Hello,

Excuse me for my English but I will explain as good as I can.

I deleted everything on my pc to put fedora 21 using usb. I made the installation and no problem occured until I reboot my computer. There is no way to boot Fedora: 'no bootable device' is printed.

I did the installation again and again but the problem is still here.

At the end of installation I can use the terminal and the commands work. I can read and write file and also download software with yum. But I cannot solve the problem. I already tried this link:

but it does not work. I think the problem comes from the grub. I have access to the bios and it detects my hard drive (I think). If somebody could help me, it would be really nice. If you need more information, don't hesitate.

Thank you and one more time excuse me for my English.

EDIT:

I finally found why I couldn't boot Fedora. I made some research and the problem was someting with UEFI. I changed it to legacy and it worked!

edit retag flag offensive close merge delete

Comments

Pouvez-vous essayer de prendre des screenshots de votre ordinateur alors qu'il est le problème et essayer de nous montrer ? Aucune infraction , mais je ne pouvais pas comprendre votre problème.

SantoshHoropter gravatar imageSantoshHoropter ( 2015-01-08 17:52:05 -0600 )edit
1

@SantoshHoropter , I think what he meant was he is able to use the Live USB and it functions fine. He is able to use terminal in live session and he successfully installed the OS to HDD. But if he reboots his PC, he gets error saying "No bootable device (probably from BIOS)" I don't think he can take screenshot of that.

deadrat gravatar imagedeadrat ( 2015-01-08 23:27:32 -0600 )edit
1

@rat. You are right. That's exactly my problem. I also tried ubuntu but I got the same result. Then I tried boot-repair but it still doesn't work. When I try to install windows 8 from a usb, it simply works. So I don't think the problem comes from my hardware. My computer is an Acer Aspire R13.

If it can help you to help me, I can send some pictures but no screenshots.

Monster gravatar imageMonster ( 2015-01-10 08:22:34 -0600 )edit

@rat I couldn't get how he managed to access terminal and yum after installation and also get the error. Now, I understand that terminal operations must have been done from liveUSB mode itself.

SantoshHoropter gravatar imageSantoshHoropter ( 2015-01-11 15:39:02 -0600 )edit

Yes, @SantoshHoropter , u r right. He must have run them from live session run from LiveUSB.

deadrat gravatar imagedeadrat ( 2015-01-12 01:48:22 -0600 )edit

3 Answers

Sort by » oldest newest most voted
1

answered 2015-01-13 06:10:30 -0600

Monster gravatar image

I finally found why I couldn't boot Fedora. I made some research and the problem was someting with UEFI. I changed it to legacy and it worked!

edit flag offensive delete link more

Comments

please paste the link or source of the answer, people who stop by this question should be able to see the answer right? Save them the trouble.

SantoshHoropter gravatar imageSantoshHoropter ( 2015-01-13 10:22:58 -0600 )edit

UEFI is supposed to work with fedora. Please consider filing a bug with detailed description on what happened.

deadrat gravatar imagedeadrat ( 2015-01-14 06:04:22 -0600 )edit
0

answered 2017-03-27 01:13:51 -0600

paravasta gravatar image

If I'm not mistaken, there's really no answer to this question from anyone here, except that the questioner said that when he changed to legacy boot, his problem disappeared? I've got the same problem now, and I also tried changing to legacy boot, with absolutely no change in the problem. I get a black screen with the message "no bootable device." It seems in the past whenever I've tried to do a fresh install of Fedora to a Windows computer, there's always some crazy issue that comes up, and it's starting to seem to me that Fedora itself simply isn't a user friendly OS when it comes to installs. It's been around long enough, it seems like someone could have figured out how to improve it. Who knows... perhaps people who use Linux just thrive on labyrinthine complexity or something.

it seems every time something like this comes up, forums like this never hold the answer. It seems almost like no one really knows what they're doing, as I've never once gotten any answer I didn't find myself...It makes me wonder why I still keep trying by coming back to these forums. But it would be nice to get some help for a change, so here I go - I'm trying again.

edit flag offensive delete link more
0

answered 2019-03-25 14:25:03 -0600

updated 2019-03-25 16:07:18 -0600

I know this is an older topic. However, since its the first to come up in google and theres no real answer on here i wanted to share what made it work for me.

Mind you that I've only started using Linux a month ago - so please don't mind possible nonsense (hey at least I got it to work!). I'm always open to correction.

I was thinking that either my boot partition was messed up or the automatic partitioning in combination with encrypted harddrives might be buggy. I have an SSD and a HDD installed.

I looked up my partitons with:

blkid

I started a live disk and deleted the first sector of my SSD:

dd if=/dev/zero of=/dev/sda ibs=512 count=1

Then, I deleted the partition labeled msdos. Fdisk wouldn't work, so I used dd:

dd if=/dev/zero of=/dev/sda3

I rebooted and started installation. I decided to put root, var and swap as separate partitions on my SSD (unencrypted) and /home on my HDD (encrypted). Mind you, if you want to encrypt all, remember to create an unencrypted /boot partition.

Anyways, this worked for me without having to buzz around in the BIOS.

edit flag offensive delete link more

Comments

Depending on how busy or loaded your system is, it may not be a good idea to put your swap partition on your solid state drive. Write/erase cycles to an SSD can eat away at the lifetime cycles of an ssd. If swap is very busy you may run into problems over time with ssd cell failures. Newer ssd's have improved lifetimes but I think it can still be an issue.

nmgiffin gravatar imagenmgiffin ( 2019-03-25 19:18:54 -0600 )edit

Hi there,

Thanks a ton for the answer, always good to learn something new. In my specific case I'm using my old pc as a test environment mainly for learning. ATM I don't need swap, just wanted to make sure that I have enough once I start setting up some stuff.

Xiallacia gravatar imageXiallacia ( 2019-03-27 12:48:44 -0600 )edit

Question Tools

Stats

Asked: 2015-01-07 18:40:40 -0600

Seen: 4,363 times

Last updated: Mar 25 '19