You are not logged in.

#1 2014-05-28 02:35:50

burkaman
Member
Registered: 2014-05-28
Posts: 2

Messed up bootloader, can no longer boot computer with CD in drive

I'm trying to dual boot Arch Linux and Windows 8.1, on a Lenovo Y580 that already has Windows on it. I went through the whole installation mostly following the Beginner's Guide, picked the Syslinux bootloader and tried to set it to chainload Windows, everything seemed to go smoothly. When I restarted the computer, it just skipped straight to Windows. I figured I must have messed up the bootloader so I put the live CD back in to try to fix it, but now nothing will boot while a CD is in the drive. It hangs at the Lenovo splash screen; I can't get to the boot menu, I can't get to the BIOS, I can't do anything. When I take the CD out and restart it boots into Windows.

Presumably I messed up setting the boot flag, or something? I have absolutely no idea how to diagnose this problem, I don't even know how to investigate it because I can't boot anything besides Windows. Please let me know if you need more information, I wasn't really sure what details would be relevant to this issue.

Offline

#2 2014-05-28 14:32:51

gay
Member
Registered: 2012-12-16
Posts: 90

Re: Messed up bootloader, can no longer boot computer with CD in drive

Welcome to the Arch Forum

Issue 1 (it doesn't boot from the Arch CD):
The first thing to try would be to verify that the CD is not damaged (Can you boot from another CD or is it just this one? Can you boot this CD in another computer?).

Issue 2 (the BIOS):
Further, if your Windows boots, you should be able to get into the BIOS (usually by hitting F1, F2, F10, ESC or something like that just before the boot process starts; it should not be hard to figure out which one it is from the internet, your computer's manual, or maybe your Lenovo splash screen even says which it is). However, you probably don't need the BIOS. As it doesn't boot with a CD in the drive the boot order is probably fine.

Issue 3 (after installing Arch, it didn't start the bootloader but Windows):
Yes, you are right, it sounds as if something went wrong when you tried to install the bootloader. But to diagnose, what, you'll need to get into the Arch CD again first. I'd probably simply try it again. (1. Boot the Arch CD. 2. mount the partitions, https://wiki.archlinux.org/index.php/Be … partitions 3. Chroot into your Arch (arch-chroot /mnt /bin/bash) 4. Try installing the bootloader again, as describet in the Beginner's Guide, here https://wiki.archlinux.org/index.php/Be … bootloader 5. reboot and hope that it worked this time. Good luck.)


We are exactly the people our parents always warned us about.

Offline

#3 2014-06-01 00:49:19

burkaman
Member
Registered: 2014-05-28
Posts: 2

Re: Messed up bootloader, can no longer boot computer with CD in drive

It doesn't seem to be the disk, I tried writing Arch onto a new CD, same problem. The laptop stops at the Lenovo splash screen and accepts no input if the Arch CD is in the drive. Is there any other way to get to my stranded Arch installation, or maybe change the boot flags some other way?

Offline

#4 2014-06-01 08:02:23

henk
Member
From: Weert, Netherlands
Registered: 2013-01-01
Posts: 334

Re: Messed up bootloader, can no longer boot computer with CD in drive

I think your problem is not the disk, because it worked the first time you used it. As gay mentioned: try to get into the BIOS/Firmware and check what has happened to the boot sequence.
When Windows 8 or 8.1 is pre-installed, which seems the case, you will have to do this from configuration within Windows.

http://forums.lenovo.com/t5/Windows-8-a … a-p/942279
http://www.makeuseof.com/tag/how-to-acc … -computer/

Offline

#5 2014-06-02 12:19:04

gay
Member
Registered: 2012-12-16
Posts: 90

Re: Messed up bootloader, can no longer boot computer with CD in drive

What is odd is that the system reacts to a CD being in the device (i.e. it doesn't boot Windows while it does if there is no CD in the device). This is why I think that the boot order is probably fine. Nevertheless, I don't see why it wouldn't boot the Arch CD. I could imaging some potential reasons none of which is either likely or common or easy to resolve.

(So for now, the interesting questions about that would be:

  • 1. How did you get the Computer to boot from the Arch CD when you tried to install Arch? Did you just reboot with the CD in the drive or did you do anything specific with your Windows and/or BIOS first; if so, what?

  • 2. If you put another CD (say, your favorite audio CD) into the drive, does it still hang at the Lenovo splash screen? Normal behavior would be that it just boots Windows.

  • 3. Following henk's advise and checking the boot sequence in the BIOS, what exactly do you see, what is the exact boot sequence?)

burkaman wrote:

Is there any other way to get to my stranded Arch installation

Sure. Just none that would be easier than from the Arch CD. You could for instance write the Arch ISO to a USB flash memory and boot from USB, like so: https://wiki.archlinux.org/index.php/US … In_Windows
If your problems booting from CD persist, this might be worth a try. (However, you will still have to make sure that your boot order lists USB before the hard drive.)

burkaman wrote:

maybe change the boot flags some other way?

Sure. But it is

  • (1) overwhelmingly unlikely that your problem with Arch has anything to do with boot flags and

  • (2) without a deeper understanding of how partition tables are designed and how disk partitioning utilities work, you are much more likely to seriously damage your other (Windows) partition(s) than to fix your Arch Linux partition(s).

If you feel compelled to try nevertheless, have a look at wikipedia's list of disk partitioning software: https://en.wikipedia.org/wiki/List_of_d … g_software

One more thought on your Arch installation and its non-working bootloader: If you by any chance set the default boot option to Windows and the timeout to 0 the behavior you describe (booting Windows instead of showing the bootloader) would be the expected one. If not, the bootloader has not been installed to the harddisk since the bootsector is obviously still occupied by Windows' own bootloader. (Otherwise, there would be no way for Windows to boot.)

Last edited by gay (2014-06-02 15:47:18)


We are exactly the people our parents always warned us about.

Offline

Board footer

Powered by FluxBB