LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   PC ignores boot menu and BIOS boot priority settings (http://www.linuxquestions.org/questions/linux-newbie-8/pc-ignores-boot-menu-and-bios-boot-priority-settings-915091/)

trillian 11-23-2011 07:08 AM

PC ignores boot menu and BIOS boot priority settings
 
My PC previously had a single 80G hard drive. When I upgraded to Fedora 14 I removed the old drive and did a clean install to a new 500G drive, which has given no problems. A week ago I installed Fedora 16 on the old drive, just to play with and see if I can get my mind around Gnome 3. The F14 drive is set as first boot priority in boot menu and in the BIOS settings, and is recognised by the computer as the master drive, but now the only way I can boot from it is by physically disconnecting the F16 drive ~ as long as that drive is connected, the computer tries to boot from it. I have even set that drive to "disabled" in the BIOS, but it makes no difference. F14 is still my main system and the one I use to actually get stuff done; I want it as the default boot drive, but I'd like to be able to leave the other drive connected and get to it via boot menu or BIOS without having to physically connect and disconnect it every time. I'm not sure whether this is a hardware or software issue, and I haven't been able to find anyone with the same problem on the forums. I'd appreciate any suggestions from people who know more about it than I do!

akuthia 11-23-2011 07:24 AM

are these sata or ide drives? I had a thought about the jumper settings, but if they're not ide, that doesnt matter.

ronlau9 11-23-2011 07:28 AM

Where did you install GRUB ?
And I mean both GRUB ?
One on the old drive and the other on the new drive ?
Or both on the same drive .

trillian 11-23-2011 07:37 AM

akuthia: Sorry, should have thought to specify: they are SATA drives.

ronlau9: Remember I'm a noob ~ I installed both releases from live ISO CDs, and grub is installed wherever it goes when you click on "Install to hard drive".

trillian 11-23-2011 07:41 AM

Would the F16 GRUB have priority over F14? What exactly does GRUB do?

ronlau9 11-23-2011 07:53 AM

GRUB is you're boot loader .
The last installed boot loader will normally boot all the installed OS .
Just imagine you have a 2 drives and you will boot it separately .
Install each boot loader on its own drive , and change the boot sequence in the BIOS to chance OS
Fedora should give you the choice where to install GRUB

michaelk 11-23-2011 08:00 AM

If you are using LVM then it might be due to the fact that the VG name is the same for both versions. The boot loader finds the 16 drive first and so that is the one that boots. You can use the vgrename utility to change the desired version. I might suggest using a live CD so you manipulate both versions at the same time as well as modify fstab.

trillian 11-23-2011 08:11 AM

I'm sorry to be a pain in the neck, but you need to spell things out in idiot-proof steps for me ~ both the last posts make sort of sense to me, but I'm not sure what to do next. There's a huge gulf between being able to install an OS and use it for everyday stuff, and knowing how it works behind the scenes. You probably assume that I have more knowledge than I do, because things are obvious to you, but I'm a 50-something mom and not a 20-something geek!

yancek 11-23-2011 08:12 AM

You might go to the site below and download and run the bootinfoscript and review it or post the results.txt file here for help. This will give some actual details about your setup and boot files:

http://bootinfoscript.sourceforge.net/

trillian 11-23-2011 08:17 AM

How do I make sure each drive has GRUB installed separately? How do I use vgrename?

trillian 11-23-2011 08:22 AM

Thank you, I'll try the bootinfoscript download

trillian 11-24-2011 08:05 AM

Quote:

Originally Posted by yancek (Post 4531696)
You might go to the site below and download and run the bootinfoscript and review it or post the results.txt file here for help. This will give some actual details about your setup and boot files:

http://bootinfoscript.sourceforge.net/

Could not get this to work. The file is extracted and sitting on my desktop, but I just get the message "No such file or directory" when I try to access it.

trillian 11-24-2011 08:08 AM

Quote:

Originally Posted by michaelk (Post 4531680)
If you are using LVM then it might be due to the fact that the VG name is the same for both versions. The boot loader finds the 16 drive first and so that is the one that boots. You can use the vgrename utility to change the desired version. I might suggest using a live CD so you manipulate both versions at the same time as well as modify fstab.

I've done some more ferreting around, and you're right, there is a conflict with duplicate VG names. LVM was enabled by default when I installed F16; can't remember but it probably was for F14 too. What should I do to resolve this? (Step by step instructions if you have the patience, please)

yancek 11-24-2011 08:19 AM

Quote:

Could not get this to work. The file is extracted and sitting on my desktop, but I just get the message "No such file or directory" when I try to access it.
You need to be logged in to a terminal as root (su, hit the enter key, prompted for password, enter password, hit the enter key)
Change directories to the Desktop. If it is /home/trillian/Desktop/ then just do: cd /home/trillian/Desktop. If you have a different user name, replace trillian with whatever it is.
Run the script: bash boot_info_script.sh
This should output the results.txt file. You will need to have both disks attached for meaningful output.

trillian 11-24-2011 08:36 AM

Quote:

Originally Posted by yancek (Post 4532781)
You need to be logged in to a terminal as root (su, hit the enter key, prompted for password, enter password, hit the enter key)
Change directories to the Desktop. If it is /home/trillian/Desktop/ then just do: cd /home/trillian/Desktop. If you have a different user name, replace trillian with whatever it is.
Run the script: bash boot_info_script.sh
This should output the results.txt file. You will need to have both disks attached for meaningful output.

I was logged in as root, but used the command from the sourceforge site: bash ~/Desktop/boot_info_script.sh which gave me the error message. I now cannot boot either system with the other drive connected, so will running the script in either one tell you anything useful? I'm guessing the conflict is because both systems were installed with only one drive connected, so both think they are the primary system? I was scared of messing up my F14 which is why I disconnected it when I installed F16. Would it help to reinstall F16 and configure GRUB differently?


All times are GMT -5. The time now is 01:59 PM.