Linux - NewbieThis 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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi, I have gone to that link, but no go.........
I am not able to understand whats the problem.
Things have been working for so many people, but I don't understand whats the problem with my installation.
Hey Thanks for responce, let me know if i can do anything else
1. What kind of partition is VISTA installed on?
Is it a volume, virtual-drive (as mentioned in the article I linked before) or a normal NTFS partition?
2. Also, do you have XP AND VISTA installed on the same computer?
3. If so, in what order did you install them?
Was it XP, VISTA and then Linux? This should help pinpoint what boot loader you're using (for XP/Vista).
4. Also post the result of "fdisk -l" and mark what partitions each OS is installed on.
5. Do you have any kind of RAID setup?
I could also mention that the NTFS modules are irrelevant for anything but reading NTFS partitions. So if you're trying to access the VISTA partition from Linux, you should know you'll only get read access (unless you formated the Vista partition during install, then I'm not sure if you can access it at all. Vista uses a new version of NTFS, so I'm not sure if linux supports that yet).
To get both read and write access to the XP version of NTFS, you should use ntfs-3g (google it).
Before actually accessing a NTFS partition, I suggest you disable the System-Restore service in XP though. Or you might get a scan-disc msg everytime you boot XP.
It just hit me that your trying to boot Vista off an extended partition!
Maybe Vista doesn't like booting from those?
If that's not the problem, then I'm not sure what might help you.
With a quick Google, I came up with a LOT of problems with the Vista bootloader and Linux, but most of the solutions have been covered here. The only difference from your setup seem to be that they all install Vista to a Primary Partition. So all I can suggest is to reinstall Vista to either a new HD, or at least a primary partition on your current hd.
This is not a simple solution, but it's all I can come up with.
Hopefully someone in here can confirm if Vista has a problem booting off an extended partition?
When you install Vista, it writes a disk serial number in the Master Boot Record (MBR). That's the first sector of the hard disk that contains the partition table. When you install anything else like GRUB or LILO to the MBR that will write over the disk serial number (with zeroes) and then Vista will not boot. You can repair the Vista MBR but then you won't be able to boot GRUB or LILO.
Microsoft made that change to the Vista bootloader at some point and not all of the earlier (beta / release candidate) versions care if you change the MBR. The officially released version of Vista does care about changes to the MBR. The Vista boot loader generates some kind of UUID (Universally Unique Identifier) based on the disk serial number and uses that to verify if it can access the boot volume. Windows XP doesn't check the disk serial number when it boots, and later will write some kind of disk serial number back in the MBR (probably saying that it detected a new disk volume).
There are a couple of ways to solve the problem. One way is to install GRUB or LILO to the Linux partition boot sector instead of the MBR. Then you have to make a copy of the Linux partition boot sector into a file using "dd". Copy the boot sector file to Vista, and then add a Vista boot manager entry using the "bcedit" command in Vista.
ID is a very long number (UUID) that you get after using the first command.
The file "bootsect.lnx" can have any name providing that it contains a copy of the Linux partition boot sector (that loads GRUB).
You should be able to use "/addfirst" instead of "/addlast" if you want Linux to appear in the boot menu before Vista.
If you're familiar with creating a bootsector file to add Linux into the Windows XP boot menu, you create the "bootsect.lnx" file for Vista in exactly the same way. Use a "dd" command similar to this in Linux.
dd if=/dev/hda2 of=bootsect.lnx bs=512 count=1
How you copy the "bootsect.lnx" file to the Vista NTFS root directory is up to you. You can use an MS-DOS floppy, a FAT32 partition, or a version of Linux with NTFS write support.
If you don't mind dumping and editing disk sectors you can also do this.
Install or repair Vista so that it boots.
Dump out the Vista MBR and note the disk serial number bytes at offset 0x1B8. The disk serial number is four bytes (0x1B8 through 0x1BB) stored in Little-Endian order.
Install GRUB or LILO to the MBR (I recommend GRUB).
Patch the MBR written by GRUB or LILO to have the correct disk serial number bytes.
NOTE: Neither GRUB nor LILO has any code or other needed information in those bytes.
The reason that I recommend using GRUB is so that you will only need to do this once. If you use LILO you will have to do this every time you change the LILO boot menu and run the "lilo" command.