Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Look at "sudo /sbin/fdisk -l". You fstab doesn't indicate which device is being used because "LABEL=" is used instead of a device node. The only indication is /dev/sdb1 used for boot which indicates that the second drive was used to install linux. You may only need to add and entry in /boot/grub/menu.lst to boot windows.
My windows entry looks like this:
Code:
###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,5)
chainloader (hd0,0)+1
Your rootnoverify will be different. Use the "root (hdN,N)" value from the Linux section. The chainloader line is for when windows is on the first partition of the first disk drive.
Magic thank you that worked a treat, I was starting to get worried that the linux install had deleted it.... Still have not quite worked out yet hoe to configure grub.. I tried using settings similar to yours but it didn't work..
sudo /sbin/fdisk -l gives
Code:
Disk /dev/sda: 160.0 GB, 160000000000 bytes
255 heads, 63 sectors/track, 19452 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 19451 156240126 7 HPFS/NTFS
Disk /dev/sdb: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 83 Linux
/dev/sdb2 14 19929 159975270 8e Linux LVM
Disk /dev/dm-0: 161.6 GB, 161698807808 bytes
255 heads, 63 sectors/track, 19658 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 2080 MB, 2080374784 bytes
255 heads, 63 sectors/track, 252 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/sdc: 4110 MB, 4110417920 bytes
16 heads, 32 sectors/track, 15680 cylinders
Units = cylinders of 512 * 512 = 262144 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 15680 4014064 c W95 FAT32 (LBA)
Disk /dev/sdd: 2 MB, 2097152 bytes
2 heads, 32 sectors/track, 64 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 1 64 2032 1 FAT12
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.