cant install xp and ubuntu on separate sata drives
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.
Here's my latest details, after fresh install of both OS's. Still get same error.
installed windows on only drive hooked up in system at the time (channel 2 sata)
plugged in channel 1 sata drive, installed ubuntu on it, and chose to put grub on sda
that didn't work, so I reinstalled ubuntu from scratch and chose sda1 for grub. still doesn't work. My other sane choice is (hd0), but isn't that the same as choosing 'sda'?, anyway, I've chosen (hd0) with the past installs so I thought I'd try something different.
I'm still feeling that the boot.ini needs customization (because grub was getting to the boot.ini menu before). and/or I have some issue with sata with which I'm ignorant. On my abit ab9-pro motherboard, I have sata channels 1 thru 6 that can be set up for raid 0/1/5/10... but I never use raid. My onchip sata is in IDE mode - other options are RAID, and AHCI. There is an "IDE Bus Master" option which I have disabled. Abit manual says this is for IDE Bus Mastering capability under DOS environment. I enabled it to see if it'd make a difference, but now that I think about it, perhaps I'd need to set some jumpers on the drives to truly test this option.
BIOS boots to channel 1 / ubuntu disk
/dev/sda1: UUID="5dcc8d8a-173f-4a09-bee1-0a3200483ce4" TYPE="ext3"
/dev/sda5: TYPE="swap" UUID="656c348a-eaab-4bdb-ac65-817a52651f53"
/dev/sdb1: UUID="FA8C62EC8C62A33D" TYPE="ntfs"
root@ubuwide:~# cat /etc/fstab
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
UUID=5dcc8d8a-173f-4a09-bee1-0a3200483ce4 / ext3 relatime,errors=remount-ro 0 1
UUID=656c348a-eaab-4bdb-ac65-817a52651f53 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
root@ubuwide:~# cat /boot/grub/menu.lst
title Ubuntu 8.10, kernel 2.6.27-7-generic
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=5dcc8d8a-173f-4a09-bee1-0a3200483ce4 ro quiet splash
title Ubuntu 8.10, kernel 2.6.27-7-generic (recovery mode)
kernel /boot/vmlinuz-2.6.27-7-generic root=UUID=5dcc8d8a-173f-4a09-bee1-0a3200483ce4 ro single
title Ubuntu 8.10, memtest86+
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
title Other operating systems:
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sdb1
title Microsoft Windows XP Professional
map (hd0) (hd1)
map (hd1) (hd0)
root@ubuwide:~# cat /boot/grub/device.map
Here is windows boot.ini (mounted windows disk from within ubuntu to get this.)
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
can anyone refer me to a good mbr tutorial and/or editor... I'd like to inspect the windows bootloader - which, as I understand presently, is called by grub, and should reside in a certain sector on the windows disk.
ok, last post on this... I think I have been beat by the computer
I just tried switching the sata connectors to another controller, using JMicron drivers instead of intel
I did notice that the windows install saw both disks as Bus 0, Target 0, and LUN 0 - I thought that seemed odd, but I don't know anything about how scsi should act, or sata should be set up when the OS interprets the sata drive as scsi. Ubuntu install reported it was installing on scsi4(0,0,0). Other than that, ubuntu seems to have correctly identified sda (hd0) and sdb (hd1).
I'm still interested in learning more about the MBR, as I did see one post where a guy with ntoskrnl problem had to edit his windows MBR. Have found a few articles googling, but am interested in any suggestions for tutorials as well.
I thought, what-the-heck, why not try another distro.
So I loaded windows again, on first drive, then opensuse 11.1 (gnome) on 2nd drive, and it works!!!! Somehow, opensuse's implementation of grub allows it all to work.
I haven't even checked out menu.lst yet (and I"m on another computer at the moment)... will post the menu.lst here later so those with similar issues can investigate the differences.
Right away, I'm wondering if the mess has to do with this UUID stuff.
Or... I did notice *this time* when installing windows, that I had different ID's for the disks, which winXP installer interprets as scsi (since I moved the cables to the JMB controller.
When installing this time, I used both the intel sata driver disk as an extra storage manufacturer disk, and the JMB (or JMicron) disk. Both of these drivers were made on floppies from booting with the ab9-pro *motherboard* CD.
Note: my sata drives are attached to the JMB controller.
On previous installs, I had tried to use the sil, intel, and JMB drivers, and windows balked at one of them .. think it was the sil. Also, on one install I had used only the JMB driver.
I'm not really sure which things that I did differently will matter to others, but I wanted to document so others may find at least "a path" to explore with their own ntoskrnl.exe problems.