LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
Search this Thread
Old 06-15-2008, 06:17 PM   #1
Dr.Jono
LQ Newbie
 
Registered: Jun 2008
Location: England
Distribution: Fedora
Posts: 4

Rep: Reputation: 0
Installed Fedora 9 and Vista is gone and unable to dual-boot


Right, first of all I am terribly sorry if this is a common question. I looked in the forums and I tried editing the menu.lst but that did not help, as the files did nto seem to be connected when I added Vista to the boot list. Anyway, my problem :

- I installed Fedora 9 onto my laptop that has Vista as default.
- I logged onto Fedora, and realised that I could not access my Windows documents and files without going on the root account, which frightened me.
- I restarted the laptop to go back to the boot list, but it did not mention "Vista" at all. Just "Fedora [numbers]" and "Other". Clicking on Other did not lead me anywhere.
- I read the help topics in here and it might have been that my menu.lst problem. I checked, and Vista was not added, so I added the Vista script exactly as mentioned in here.
-I rebooted and on the boot list it now said "Vista", I clicked, but to my dissapointment, Dell's troubleshooting window came up with a range of troubleshooting tests I could do.

As you can see, I've tried searching the forums, but some of the stuff is way too technical. I am still a virgin at Linux, as this is my first ever installation. My friend advised me to install it, but he went back to the States for two weeks so I cannot ask him for help.

Could you please help me out here? If you are able to do so, could you please keep it very simple? I'm sorry, but I haven't learnt any jargon...

Thank you so much for your help in advance,



Dr.Jono
 
Old 06-15-2008, 06:24 PM   #2
amani
Senior Member
 
Registered: Jul 2006
Location: Kolkata, India
Distribution: 64-bit GNU/Linux, Kubuntu64, Fedora QA, Slackware,
Posts: 2,758

Rep: Reputation: Disabled
boot into fedora

open shell

#su

#< root passwd>

#grub-install /dev/sda


On rebooting check if you can dual boot


You can use 'super grub disk' if that fails to work or better see similar threads about ubuntu and vista


Best

A. Mani
 
Old 06-15-2008, 06:25 PM   #3
billymayday
Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
Can you post the contents of menu.lst for a start, and the output of

fdisk -l (you probably need to be root for this)

Rgds
 
Old 06-15-2008, 06:32 PM   #4
jailbait
Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Debian Wheezy, Debian Jessie
Posts: 7,554

Rep: Reputation: 182Reputation: 182
Quote:
Originally Posted by Dr.Jono View Post

- I read the help topics in here and it might have been that my menu.lst problem. I checked, and Vista was not added, so I added the Vista script exactly as mentioned in here.

-I rebooted and on the boot list it now said "Vista", I clicked, but to my dissapointment, Dell's troubleshooting window came up with a range of troubleshooting tests I could do.
You used the correct approach. You seem to have added a title section to menu.lst which points to Dell's troubleshooting partition instead of the Vista partition. I suggest that you edit menu.lst again and change the name of this menu entry from Vista to Dell troubleshooting.

The next thing to do is to find the Vista partition. Boot into Fedora and issue this command to list all of your partitions:

fdisk -l

------------------
Steve Stites
 
Old 06-15-2008, 06:37 PM   #5
Dr.Jono
LQ Newbie
 
Registered: Jun 2008
Location: England
Distribution: Fedora
Posts: 4

Original Poster
Rep: Reputation: 0
billmayday - I will do this as soon as I can. Sorry if I keep you waiting but it's late.

Also, could you clarify how I find the output of fdisk -l? Thanks in advance,


Dr.Jono
 
Old 06-15-2008, 06:48 PM   #6
billymayday
Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
Assuming you do it from a terminal session (ie run the program "terminal" from the system or accessories menu - can't recall which in Fedora), it will come up on screen below where you type the command.

Last edited by billymayday; 06-15-2008 at 06:49 PM.
 
Old 06-16-2008, 09:16 AM   #7
Dr.Jono
LQ Newbie
 
Registered: Jun 2008
Location: England
Distribution: Fedora
Posts: 4

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by billymayday View Post
Can you post the contents of menu.lst for a start, and the output of

fdisk -l (you probably need to be root for this)

Rgds
Menu.lst Content

Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,4)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,4)/grub/splash.xpm.gz
title Fedora (2.6.25-14.fc9.x86_64)
	root (hd0,4)
	kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=UUID=f14f003e-9905-49c7-bdd5-c4c2e181ac5f rhgb quiet
	initrd /initrd-2.6.25-14.fc9.x86_64.img
title Other
	rootnoverify (hd0,1)
	chainloader +1
title= Dell Troubleshooting
        rootnoverify (hd0,0)
        chainloader +1
        makeactive
fdisk -l Content


Code:
[root@localhost ~]# fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x08000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1          14      112423+  de  Dell Utility
/dev/sda2   *          15        1320    10485760    7  HPFS/NTFS
/dev/sda3            1320        8455    57311232    7  HPFS/NTFS
/dev/sda4            8456        9729    10233405    5  Extended
/dev/sda5            8456        8481      208813+  83  Linux
/dev/sda6            8482        9729    10024528+  8e  Linux LVM

Disk /dev/dm-0: 8355 MB, 8355053568 bytes
255 heads, 63 sectors/track, 1015 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 1845 MB, 1845493760 bytes
255 heads, 63 sectors/track, 224 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x30307800

Disk /dev/dm-1 doesn't contain a valid partition table

I hope that helps!

Last edited by Dr.Jono; 06-16-2008 at 09:55 AM. Reason: Added codes.
 
Old 06-16-2008, 10:12 AM   #8
yancek
Senior Member
 
Registered: Apr 2008
Distribution: PCLinux, Ubuntu, Slackware
Posts: 4,965

Rep: Reputation: 785Reputation: 785Reputation: 785Reputation: 785Reputation: 785Reputation: 785Reputation: 785
Your fdisk -l output shows two windows partitions, sda2 and sda3. Their equivalents in grub are (hd0,1) and (hd0,2). sda2 is marked active (bootable) by the asterisk. However, this partition is about 6 times smaller than sda3? You have tried booting with this entry unsuccessfully, right?

title Other
rootnoverify (hd0,1)
chainloader +1

You could try this entry:

title= Vista
rootnoverify (hd0,2)
makeactive
chainloader +1

Ordinarily this should work but you have a separate /boot partition and you are using LVM, I'm not really familiar with it.
 
Old 06-16-2008, 10:23 AM   #9
Dr.Jono
LQ Newbie
 
Registered: Jun 2008
Location: England
Distribution: Fedora
Posts: 4

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by yancek View Post
Your fdisk -l output shows two windows partitions, sda2 and sda3. Their equivalents in grub are (hd0,1) and (hd0,2). sda2 is marked active (bootable) by the asterisk. However, this partition is about 6 times smaller than sda3? You have tried booting with this entry unsuccessfully, right?

title Other
rootnoverify (hd0,1)
chainloader +1

You could try this entry:

title= Vista
rootnoverify (hd0,2)
makeactive
chainloader +1

Ordinarily this should work but you have a separate /boot partition and you are using LVM, I'm not really familiar with it.
It worked! Thank you so much

Thanks Amani, Billymayday, Jailbait and Yancek for all your help I shall continue to use F9, and hopefully there won't be any more problems.

Thanks again!



Dr.Jono
 
Old 07-21-2008, 12:22 AM   #10
aishwarya774
LQ Newbie
 
Registered: Jul 2008
Posts: 1

Rep: Reputation: 0
Unhappy

Quote:
Originally Posted by Dr.Jono View Post
It worked! Thank you so much

Thanks Amani, Billymayday, Jailbait and Yancek for all your help I shall continue to use F9, and hopefully there won't be any more problems.

Thanks again!



Dr.Jono
having same problem plz help


[root@localhost ~]# fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x68000000

Device Boot Start End Blocks Id System
/dev/sda1 1 8 64228+ de Dell Utility
/dev/sda2 9 1314 10485760 7 HPFS/NTFS
/dev/sda3 * 1314 10469 73540608 7 HPFS/NTFS
/dev/sda4 10469 19458 72198144 f W95 Ext'd (LBA)
/dev/sda5 10469 14970 36152320 7 HPFS/NTFS
/dev/sda6 14970 17928 23755776 7 HPFS/NTFS
/dev/sda7 17929 19326 11229403+ 83 Linux
/dev/sda8 19327 19457 1052226 82 Linux swap / Solaris


grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,6)
# kernel /boot/vmlinuz-version ro root=/dev/sda7
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,6)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.25-14.fc9.i686)
root (hd0,6)
kernel /boot/vmlinuz-2.6.25-14.fc9.i686 ro root=UUID=030d062a-bb10-43ea-a0dc-7c6826c6eec7 rhgb quiet
initrd /boot/initrd-2.6.25-14.fc9.i686.img
title Windows Vista
rootnoverify (hd0,3)
makeactive
# chainloader +1
 
Old 07-21-2008, 12:31 AM   #11
linuxlover.chaitanya
Senior Member
 
Registered: Apr 2008
Location: Nagpur, India
Distribution: Cent OS 5/6, Ubuntu Server 10.04
Posts: 4,627

Rep: Reputation: Disabled
Is this line commented out by default: "# chainloader +1" ?
If its not a typo mistake remove the "#"
 
Old 07-21-2008, 10:07 AM   #12
yancek
Senior Member
 
Registered: Apr 2008
Distribution: PCLinux, Ubuntu, Slackware
Posts: 4,965

Rep: Reputation: 785Reputation: 785Reputation: 785Reputation: 785Reputation: 785Reputation: 785Reputation: 785
title Windows Vista
rootnoverify (hd0,3)
makeactive
# chainloader +1

In addition to removing the (#) from in front of chainloader, you have an incorrect stanza in your menu.lst for vista. It shows (hd0,3) as the partition to boot from but that is your extended partition (see fdisk output) and you can't boot from extended. Change the entry to (hd0,2) which is marked as active/bootable (*). What do you have on sda2?

If you are not getting a menu to select from upon boot, you need to comment out hiddenmenu as (#hiddenmenu).
 
Old 07-21-2008, 03:48 PM   #13
royce2020
Member
 
Registered: Jan 2003
Posts: 81

Rep: Reputation: 15
If I might throw my two cents in, when dual booting with windows I alaways use grubldr which hooks into the NTldr program which comes with windows.
It has been my experiance that windows is realy, realy bad at dealing with boot sectors that are not its own (such as GRUB or LiLo) and if your machine is set up to hibernate this will regularly destroy your linux boot sector. Several windows only virus scanners think that GRUB boot sectors are boot viruses and "clean" them, too.
Basicaly, Grubldr is a file that you add to your windows boot.ini and then when it boots NTldr (which normaly allows you to chose between various versions of windos) will alow you to chose between windows and GRUB (which then reads menu.lst where you can boot various flavours of linux). I have found it to be the best way to deal with MS buggy and badly thought out attemps at dealing with the boot sector.
 
Old 07-21-2008, 04:20 PM   #14
billymayday
Guru
 
Registered: Mar 2006
Location: Sydney, Australia
Distribution: Fedora, CentOS, OpenSuse, Slack, Gentoo, Debian, Arch, PCBSD
Posts: 6,678

Rep: Reputation: 122Reputation: 122
Quote:
Originally Posted by royce2020 View Post
If I might throw my two cents in, when dual booting with windows I alaways use grubldr which hooks into the NTldr program which comes with windows.
It has been my experiance that windows is realy, realy bad at dealing with boot sectors that are not its own (such as GRUB or LiLo) and if your machine is set up to hibernate this will regularly destroy your linux boot sector. Several windows only virus scanners think that GRUB boot sectors are boot viruses and "clean" them, too.
Basicaly, Grubldr is a file that you add to your windows boot.ini and then when it boots NTldr (which normaly allows you to chose between various versions of windos) will alow you to chose between windows and GRUB (which then reads menu.lst where you can boot various flavours of linux). I have found it to be the best way to deal with MS buggy and badly thought out attemps at dealing with the boot sector.
I've never had this type of issue, but what you say is interesting. Where does grubldr come from? Do you havea link, etc?
 
Old 07-21-2008, 05:43 PM   #15
John VV
Guru
 
Registered: Aug 2005
Posts: 13,057

Rep: Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741Reputation: 1741
i to use the windows boot loader to start grub
/dev/sda1 windows
------------
sdb 1,2 stuff
/dev/sdb3 fedora boot
/dev/sdb4 fedora 8
-----
with ntfs-3g installed
install windows
install fedora with grub on the first partition of fedora ( mine sdb3)
use rescue disk to boot the first time
chroot /mnt/sysimage
------- for my set up change as needed -----
Code:
~]# mkdir /mnt/windows
~]# mount -t ntfs-3g /dev/sda1 /mnt/windows
~]# dd if=/dev/sdb3 of=/Fedora8.bin bs=512 count=1
~]#  cp /Fedora8.bin /mnt/windows
~]# nano /mnt/windows/boot.ini
--- and add
C:\fedora8.bin = " Fedora 8 "
to the end of the windows boot.ini
save and reboot
you will see 2 systems listed in the windows boot screen

also look into using http://neosmart.net/dl.php?id=1
to edit the new vista boot loader
how to
http://neosmart.net/wiki/display/EBCD/Fedora

Last edited by John VV; 07-21-2008 at 06:26 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
New install on vista system, want dual boot for vista and fedora. lhelden Linux - Newbie 9 08-21-2008 10:22 AM
Fedora and Vista Dual Boot (vista installed first) firekid1239 Linux - Newbie 10 05-04-2008 09:35 PM
fedora/vista dual boot - partimage: restored vista - vista won't let me log on redmoon zero Linux - General 1 12-31-2007 07:21 PM
Adding Vista to an already installed Linux machine (dual boot) dongmin Linux - General 2 10-06-2006 07:49 PM


All times are GMT -5. The time now is 10:17 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration