LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Problem dual booting XP pro and Debian (https://www.linuxquestions.org/questions/linux-newbie-8/problem-dual-booting-xp-pro-and-debian-688749/)

Capt_Krill 12-06-2008 09:46 AM

Problem dual booting XP pro and Debian
 
Hi there,

Im pretty new to linux all together. I have had some experience with it from my uncle showing me the very basics. I enjoyed it so I decided to redo my desktop to dual boot XP pro and Debian i386. First this is my current desktop. My desktop is for gaming and fiddling with the settings cause I am currently attending school for my MSCE in XP and Server 2008/Vista-Win7. Along with my Linux+ N+ and A+ certs

Intel e8500
Asus P5N-D mobo (compatible with linux)
XFX GTX 260 (nVidia provides linux drivers)
LG DVD writer
1x WD Caviar 320GB hdd
2x WD Caviar 160GB hdds

Now here is what I did. Originally i had the 2x 160s set up in a RAID 0 and had XP Pro installed. When i went to linux, since im not fully comfortable with linux i wanted an OS that i am comfortable working with if i have to do errands online and typing documents etc, i got a 320 hdd and installed it into the SATA 1 drive, and the other 2 on my SATA 2 and 3 ports. I cleared the raid and discs from the XP Setup menus. I got XP installed and then when it was loading it got to the XP pro logo and the scrolling bar but then it went to the blue screen of death. Now then, i talked to my uncle and he said go ahead and install debian on the second hdds to get grub on my first hdd. Got debian installed correctly and got it to start up and tried using the command startx. It got an error that means i have not video driver. Which is fine, but i tried rebooting from the root by using shutdown -r now command and it rebooted and i went into the grub OS selection. Selected XP but again blue screen of death. I unplugged the 3rd blank HD and still same thing when going into XP. After a couple hours of unplugging hdds, plugging them back in, and reinstalling in the same manner i got frustrated and said screw it. hehe.

Is there something i am missing or not doing correctly? Is it because of the different size in hdds? Any help would be most appreciated.

secesh 12-06-2008 09:57 AM

1) when creating dual-boot it's easier to install windows first -- windows WILL overwrite your MBR with one that isn't linux friendly.

2) Does Windows BSOD during install? I'm wondering if you fully tore-down the RAID -- check BIOS?

3) I'm not an expert here, but am used to putting /boot at the beginning of HDD1 (HDD0 if that's how you count). This partition is <200M and will just house LILO/GRUB and kernel(s). How are you partitioning your dual-boot?
... but you should be able to get working winXP first -- step 1 is squash the BSOD.

Capt_Krill 12-06-2008 10:29 AM

@ 1. Yeah, my uncle bore that into my skull with a meat tenderizer and a baseball bat...install windows first.

@ 2. It doesn't BSOD during the install. It only does it after completing the install and loading into the desktop. It doesnt get into the desktop but BSOD after a couple of seconds at the loading XP screen. The only way i know of completely erasing the raid and the contents of the disc is by either going through the nVidia raid controller from the BIOS of my mobo and by deleting the partition in the XP Setup window when choosing the drive to partition for XP.

@ 3. On my 320 the #1 primary is 300gb and then #5 logical is set up for i think 80 MB. On the second SATA i have #1 primary 150 GB (JFS system) and then i have something like 30ish MB for the swap.

secesh 12-06-2008 05:48 PM

Well... let's set 1&3 aside for now. The primary issue is the BSOD. What BSOD is it? Going through nVidia RAID controller and breaking it down is a good start. Then you probably have to check the SATA config in BIOS. I built an ASUS/nVidia box a little while back, and while it's not mine, I remember there were RAID settings to turn on in BIOS before running the RAID config (which was a boot option right after BIOS).

Capt_Krill 12-07-2008 08:35 AM

ok I got the entire message of the BSOD

A problem has been detected and Windows has been shut down to prvent damage to your computer.

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again follow these steps:

Check for viruses on your computer. Remove any newly installed hard drive or hard drive controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer

Technical Information:
***STOP: 0x0000007B (0xF789E63C, 0xC0000034, 0x00000000, 0x00000000)

Any ideas?

mrrangerman 12-07-2008 09:26 AM

Quote:

Capt_Krill
Now here is what I did. Originally i had the 2x 160s set up in a RAID 0 and had XP Pro installed.
So why didn't you keep this setup? On my gamer I have a raid0 the same setup as you, but I also have two scsi HD's one with Debian and the other with Gentoo.

If you use the system for gaming and want the raid 0 for speed then set it up that way. First reinstall your raid array install windows and get it running as it was before,(without any other HD's plugged in)after you have it setup the way you want it, unplug the raid 0 drives and plug in your other drive you want to install linux to, (make sure it's using the other sata controler). Now install linux on that drive, your bios should pick that drive as a bootable drive. Make sure you install grub to the MBR of the linux drive, this should be done by default as it will be the only drive linux sees. Now after linux is installed and running reboot and make sure it boots fine, if so then you will need to edit your /boot/grub/menu.lst and make a entry for window so grub will know it's there.

This is what mine looks like

Code:

title Windows XP
root (hd1,0)
map (hd1) (hd0)
map (hd0) (hd1)
chainloader +1

Note: You want to point grub to the first drive in the raid 0 array as this is the drive that window installed the MBR for windows.

Now you can shutdown the system so you can plug in your raid drives, after that is done, boot into your bios and go to boot options and set the linux drive as first boot drive, then make sure the other two drives are in order drive 0 being second then drive 1. Save and exit, the reason for doing this is because your bios would set the raid array as the default boot dev. So now the linux drive will be first in boot order and you can let grub handle booting into the windows side. If you have problems with grub you may need to tweek it a little here is a good Grub booting tips HowTO If you have any problems post back, and I will post my complete grub menu.lst but this should get you going.

sumit dash 12-07-2008 09:41 AM

hi,

Frnd for dual booting ur desktop with linux and windows platform delete some partition from windows and let it as free space and then install linux in the free space u wont face any trouble.

Capt_Krill 12-07-2008 11:14 AM

The reason i didn't keep the 160s in a raid is because i was going to use them to have a tri-boot eventually. The more i read the more i am liking Gnome, gets me the furthest away from the windows feel but still keeps me comfortable with the look and feel of the desktop. But anyway. I didn't wanna partition my 320 to have 2 Linux versions on one hard drive, just wanted to keep it simple. Have XP on the 320, Debian on the first 160 and keep the third one free for Red Hat.

But I am stuck on the BSOD...something is not right with either my hardware or drivers, BTW just made an XP Pro install disc through nLite with the mobo/RAID drivers. I couldnt get my graphics card driver on it however. It wouldn't pull it from the disc because the disc wasn't showing up, tried downloading the driver from nvidia and it wouldnt find it...Anyone have any ideas?

Also can someone point me to instructions or a youtube vid :lol: that explains how to get my nVidia GTX 260 drivers into Debian from the terminal?

Capt_Krill 12-07-2008 09:23 PM

Ok I managed to get closer to what I was hoping. Not exactly what i was going for but it is working so. Ok here is what I did.

Got my 2x 160s in a RAID 0 with XP on it (they were are in my SATA 1 and 2 ports). That seemed the only way it would work was in a RAID...heh oh well. Next what I did was unplug the RAID from the mobo and put in the SATA 3 port my 320. Was recommended Ubuntu or Kubuntu to start out on Linux distros. So i downloaded both and ran them on my laptop and I chose Ubuntu cause i like the feel of it better. Anyhoo used ImgBurn to write the ISO to a disc and ran the installer on the 320GB hd. Now here is where it gets tricky. The only way i can get into Windows is if i set my Boot priority to the RAID first and not go into GRUB. But if i have my Ubuntu drive set up to boot first and use GRUB to go into XP i get the same BSOD.

How can I fix this? I realize its going to be something in GRUB or reinstalling GRUB somehow. But I am a linux and terminal nooblet...think of me in terms of going from Nancy Drew to CoD4 when it comes to linux. So any links with pics or detailed instructions would me most helpful, or if u can post it that would be great too.

secesh 12-08-2008 06:40 AM

let's backup for a minute. You said you don't want RAID, but you never answered my prior question:

Before you get distracted by these other folks telling you to throw your hands up and keep the RAID, please answer:
Quote:

Then you probably have to check the SATA config in BIOS. I built an ASUS/nVidia box a little while back ..., I remember there were RAID settings to turn on in BIOS before running the RAID config (which was a boot option right after BIOS).
Have you checked your SATA config in BIOS yet?


Here's some light reading on your stop issue: http://support.microsoft.com/kb/324103

--Since you're able to get around BSOD when using RAID, I'd imagine this is your root problem. Unplugging peripherals (USB devices and such) during windows install/first boot is always a good idea, too. USB devices are designed to be hot-swapped and should be plugged in (for the first time) while windows is running.

Capt_Krill 12-08-2008 07:58 AM

Sorry yes i did. I had my RAID/SATA settings messed up it was disabled on ports 2 and 4 and the enables on 1 and 3...It was all kinds of jacked up. So before I did the RAID i restored the defaults on my BIOS and then went in a corrected the SATA ports. Made SATA 1 and 2 RAID enabled and then 3 and 4 were disabled. Reset my boot devices to what I had them set as before which was DVD then HD then Removable.

I mean i don't mind the quick easy fix of changing which drive is to boot first to boot into either XP or Ubuntu, but i would like to have it set up with GRUB so i can just click the down d-key and hit enter and be done. Ya know?

aus9 12-08-2008 05:51 PM

pls kill your uncle for introducing you to linux. heh heh

pls read all of post and make your own decision.

ideally you could have just stayed with a good live cd/dvd if you lacked confidence to install linux?

1) since you have made changes...forget all of your old setup. its been changed so now irrelevant.

however bios does make a difference to raid detection and setup as most bios have a software raid cheat.

Therefore, you should be able to set your bios to ATA setting instead of raid.

2) use a linux live cd with a partition tool on it...command line or graphical....graphical is QtParted or gparted....to change all of your drives partitions and change the bootable flag for each drive.

3) as others have suggested......do ms first

put one drive....the 320G into sata slot 1 and assuming you have made it
c 100G ntfs
d 100G data ntfs
e (well xp won't see it) balance of drive...ext3 format

install xp.

now put one 160G drive into slot 1 and 2 and 320 to slot 3
--------------------
slot 1

/ 20G ext3
/data balance of drive ext3
------------
slot 2
/ 160g ext3
-------------
slot 3
nasty xp
---------------

insert linux install cd and install linux with grub to mbr (to slot 1 hard drive)

linux distros...good should find the bootable microsoft drive on slot 3 and give you a grub menu for it

if not read my signature....

4) the empty drive is partitioned as one partition ext3
when you decide to triple boot...the installer of a good linux can be used to change it.

each drive inserted must be modded by a live cd partition tool or by a linux installer partition tool...before you start the microsoft install and then the linux installs.

at a minimum you have

slot 1 bootable flag partition 1
slot 2 bootable flag partition 1
slot 3 bootable flag partition 1

do not let microsoft see any drive other than its own...sitting in slot 1 ...during the install process...its crap so can't handle non-ms formats

after ms is done...it goes to slot 3...then you insert both other drives and can format both in the one live cd boot using gparted etc.

good luck


oh....you need an easy to install Debian style distro not Ubuntu...try sidux? oh its a live cd/dvd as well

http://sidux.com/Article303.html


All times are GMT -5. The time now is 06:45 PM.