Re: help getting grub to see Windows 7 on second drive
On Wednesday 08 December 2010 19:04:36 Camaleón wrote: On Wed, 08 Dec 2010 15:58:02 +, Lisi wrote: On Wednesday 08 December 2010 15:47:19 Peter Hillier-Brook wrote: sudo update-grub should do the trick. With grub2 the configuration file (grub.cfg) should not be edited by hand; it's updated every time update-grub is run. Lenny uses grub 1. I think that it is called grub-legacy in Squeeze, but am not sure. Hum... are you sure? :-? IIRC, last time I installed lenny the default option was set to Grub2, I had to manually change it to get Grub legacy instead. It was a 64 bits and an expert install. According to aptitude show, the default in Lenny is GRUB version 0.97-47lenny2, simply called GRUB. If you want GRUB 2 you have to ask for grub-pc. : quote l...@tux:~$ aptitude show grub Package: grub State: installed Automatically installed: no Version: 0.97-47lenny2 Priority: optional Section: admin Maintainer: Grub Maintainers pkg-grub-de...@lists.alioth.debian.org Uncompressed Size: 872k Depends: libc6 (= 2.7-1), libncurses5 (= 5.6+20071006-3), grub-common Suggests: grub-legacy-doc, multiboot-doc, mdadm Provided by: grub-efi, grub-ieee1275, grub-linuxbios, grub-pc Description: GRand Unified Bootloader (Legacy version) GRUB is a GPLed bootloader intended to unify bootloading across x86 operating systems. In addition to loading the Linux kernel, it implements the Multiboot standard, which allows for flexible loading of multiple boot images (needed for modular kernels such as the GNU Hurd). Please note that GRUB Legacy is in maintainance mode and new features are only accepted in GRUB 2 (grub-pc package). l...@tux:~$ /quote Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101061545.38594.lisi.re...@gmail.com
Re: help getting grub to see Windows 7 on second drive
On Thu, 06 Jan 2011 15:45:38 +, Lisi wrote: On Wednesday 08 December 2010 19:04:36 Camaleón wrote: Lenny uses grub 1. I think that it is called grub-legacy in Squeeze, but am not sure. Hum... are you sure? :-? IIRC, last time I installed lenny the default option was set to Grub2, I had to manually change it to get Grub legacy instead. It was a 64 bits and an expert install. According to aptitude show, the default in Lenny is GRUB version 0.97-47lenny2, simply called GRUB. If you want GRUB 2 you have to ask for grub-pc. : (...) How can aptitute show tell you what is the default grub to be installed in lenny? :-P I also have Grub legacy installed in Lenny (and also in Squeeze) but IIRC (I'm speaking from memory, it was a year ago when I installed Lenny), it was _my_ decision. I dunno for the auto-installer because I chose the expert install and I remember that the bootloader screen asked two main questions, a) what grub to install (grub 1 or grub 2) and b) where to put the bootloader (mbr, first sector of partition). I can be wrong because time passes very quickly and my memory abilities decreases at the same speed O:-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.06.17.26...@gmail.com
Re: sudo command not necessary (was Re: help getting grub to see Windows 7 on second drive)
On Mon, Dec 13, 2010 at 6:36 AM, Chris Bannister mockingb...@earthlight.co.nz wrote: On Mon, Dec 13, 2010 at 11:52:23PM +1300, Chris Bannister wrote: On Mon, Dec 13, 2010 at 03:48:52AM -0500, Doug wrote: I suspect it will work in any Linux, if you modify the sudoers file to add Right! *IF* you modify the sudoers file. It does not work out of the box as it does in Ubuntu. In fact: r...@fischer:~# apt-cache show sudo Package: sudo Priority: optional ... which means the sudo package isn't even installed by default. Not quite; sudo is installed by default when you install the GNOME desktop (but only root is allowed to run sudo by default). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim=02cbh_rriz-ykyj6sgecysowfkdxug0kt...@mail.gmail.com
Re: sudo command not necessary (was Re: help getting grub to see Windows 7 on second drive)
In fact: r...@fischer:~# apt-cache show sudo Package: sudo Priority: optional ... which means the sudo package isn't even installed by default. Imagine you are new to Debian, and manage to send a message to debian-user where the advice: sudo command is given. You try it, get command not found, think wtf and try another distro or you write back mentioning the error about sudo not found and end up not dealing with your problem at all but on how to install the sudo package. Ya know, slackware didn't used to come with sudo - I remember downloading a tarball, compiling, and installing it. But, hell, my mac comes with sudo so I can almost see your point - almost, but not quite.
Re: help getting grub to see Windows 7 on second drive
On 12/12/2010 11:03 PM, Chris Bannister wrote: On Wed, Dec 08, 2010 at 04:43:17PM +, Peter Hillier-Brook wrote: On 08/12/2010 15:58, Lisi wrote: On Wednesday 08 December 2010 15:47:19 Peter Hillier-Brook wrote: sudo update-grub should do the trick. With grub2 the configuration file (grub.cfg) should not be edited by hand; it's updated every time update-grub is run. Lenny uses grub 1. I think that it is called grub-legacy in Squeeze, but am not sure. Lisi The past is a foreign country: they do things differently there. They also do things differently in Ubuntu!! (sudocommand is an Ubuntu thing) /snip/ I suspect it will work in any Linux, if you modify the sudoers file to add yourself to it. Frinstance, PCLinuxOs would prefer that you don't know anything about sudo, but if you edit the file that's already there (using visudo) and add yourself, then sudo will work. The bottom of my sudoers file reads thus: # User privilege specification rootALL=(ALL) ALL # Uncomment to allow people in group wheel to run all commands #%wheel ALL=(ALL) ALL # Same thing without a password #%wheel ALL=(ALL) NOPASSWD: ALL # %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom # %users localhost=/sbin/shutdown -h now doug ALL=(ALL) ALL added ___ In use: $ sudo command Password: you enter your password, and just this one command runs. (I haven't tried multiple commands separated by ; but I would expect it to work.) It does not leave you in root, like su root does. --doug Blesssed are the peacemakers...for they shall be shot at from both sides. --A. M. Greeley -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d05ddf4.7020...@optonline.net
Re: help getting grub to see Windows 7 on second drive
On Mon, Dec 13, 2010 at 03:48:52AM -0500, Doug wrote: On 12/12/2010 11:03 PM, Chris Bannister wrote: They also do things differently in Ubuntu!! (sudocommand is an Ubuntu thing) /snip/ I suspect it will work in any Linux, if you modify the sudoers file to add Right! *IF* you modify the sudoers file. It does not work out of the box as it does in Ubuntu. -- Religion is excellent stuff for keeping common people quiet. -- Napoleon Bonaparte -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101213105223.gg20...@fischer
sudo command not necessary (was Re: help getting grub to see Windows 7 on second drive)
On Mon, Dec 13, 2010 at 11:52:23PM +1300, Chris Bannister wrote: On Mon, Dec 13, 2010 at 03:48:52AM -0500, Doug wrote: I suspect it will work in any Linux, if you modify the sudoers file to add Right! *IF* you modify the sudoers file. It does not work out of the box as it does in Ubuntu. In fact: r...@fischer:~# apt-cache show sudo Package: sudo Priority: optional ... which means the sudo package isn't even installed by default. Imagine you are new to Debian, and manage to send a message to debian-user where the advice: sudo command is given. You try it, get command not found, think wtf and try another distro or you write back mentioning the error about sudo not found and end up not dealing with your problem at all but on how to install the sudo package. -- Religion is excellent stuff for keeping common people quiet. -- Napoleon Bonaparte -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101213113630.gh20...@fischer
Re: help getting grub to see Windows 7 on second drive
On Wed, Dec 08, 2010 at 04:43:17PM +, Peter Hillier-Brook wrote: On 08/12/2010 15:58, Lisi wrote: On Wednesday 08 December 2010 15:47:19 Peter Hillier-Brook wrote: sudo update-grub should do the trick. With grub2 the configuration file (grub.cfg) should not be edited by hand; it's updated every time update-grub is run. Lenny uses grub 1. I think that it is called grub-legacy in Squeeze, but am not sure. Lisi The past is a foreign country: they do things differently there. They also do things differently in Ubuntu!! (sudo command is an Ubuntu thing) Debian apparently, lives for the stable release. It is therefore a reasonable assumption (unless stated otherwise) that any queries/questions is about the current stable, which is still Lenny!! Sorry. No prob, we all make misteaks :) -- Religion is excellent stuff for keeping common people quiet. -- Napoleon Bonaparte -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101213040351.gh19...@fischer
Re: help getting grub to see Windows 7 on second drive
Dear folks, Thanks for the suggestions here. In the end pressure to get the Windows installed fast meant I cheated and reinstalled Debian on the first drive. So I didn't run grub-update. Also I was so busy I didn't get time to read your emails before the great Lenny download and re-installation began. I think the grub update idea might have worked. Now Windows boots when I start up the PC however, F8 allows me to alter the disk boot order using the BIOS and then the other disk fires up and I get GRUB which gives me a nice menu with the Debian and Windows to choose from.. Maybe if I ran grub-update then the next time I boot up I wouldn't see Windows appearing by default. I have another PC at home with two drives on it. At christmas I will delete the 64studio linux OS I have on the second drive and then put Windows on as an experiment having disconnected the other drive with Debian on it. Then I will hook it up again, fire up grub and Debian and then try grub-update to see what happens I have paid a penalty for reinstalling Debian as I knew I would. I can't get my Brother DCP7030 scanner working again using the brscan and brscan-skey software deb files produced by Brother to run it. It takes quite a bit of farting around and one step has not worked. I can't be bothered trying to figure out what is wrong. I will also need to reinstall Opera in Debian which is also a bit of magical mystery tour but I will get there Windows of course saw the scanner right off the bat and then scanned some files and rebooted into Debian mounted the Windows disk on the linux tree and ran gscantopdf on the scanned files and worked round my scanning problem. But of course if I had realised to try the grub update idea before I reinstalled it might have worked and I would have got away without having to reinstall. It really ought to be possible to find a way to install Windows after Debian has been installed and not have to reinstall the Debian to fix the booting problems. If the grub update would work then we would have a generic recipe for anyone to use. 1. Get a new disk and install it. 2 Disconnect the existing disk(s) with Debian on them. 3. Install Windows 4. Reconnect Debian drive 5. Fire up Debian and run grub-update 6. Et voila. hermetically sealed sterilised Windows and unruffled Debian installation I will try again later. Regards Michael Fothergill -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimkctlopvkuxmdgwkvjewdyx1etqm51bhhph...@mail.gmail.com
help getting grub to see Windows 7 on second drive
Dear folks, Thanks for the suggestions here. In the end pressure to get the Windows installed fast meant I cheated and reinstalled Debian on the first drive. So I didn't run grub-update. Also I was so busy I didn't get time to read your emails before the great Lenny download and re-installation began. I think the grub update idea might have worked. Now Windows boots when I start up the PC however, F8 allows me to alter the disk boot order using the BIOS and then the other disk fires up and I get GRUB which gives me a nice menu with the Debian and Windows to choose from.. Maybe if I ran grub-update then the next time I boot up I wouldn't see Windows appearing by default. I have another PC at home with two drives on it. At christmas I will delete the 64studio linux OS I have on the second drive and then put Windows on as an experiment having disconnected the other drive with Debian on it. Then I will hook it up again, fire up grub and Debian and then try grub-update to see what happens I have paid a penalty for reinstalling Debian as I knew I would. I can't get my Brother DCP7030 scanner working again using the brscan and brscan-skey software deb files produced by Brother to run it. It takes quite a bit of farting around and one step has not worked. I can't be bothered trying to figure out what is wrong. I will also need to reinstall Opera in Debian which is also a bit of magical mystery tour but I will get there Windows of course saw the scanner right off the bat and then scanned some files and rebooted into Debian mounted the Windows disk on the linux tree and ran gscantopdf on the scanned files and worked round my scanning problem. But of course if I had realised to try the grub update idea before I reinstalled it might have worked and I would have got away without having to reinstall. It really ought to be possible to find a way to install Windows after Debian has been installed and not have to reinstall the Debian to fix the booting problems. If the grub update would work then we would have a generic recipe for anyone to use. 1. Get a new disk and install it. 2 Disconnect the existing disk(s) with Debian on them. 3. Install Windows 4. Reconnect Debian drive 5. Fire up Debian and run grub-update 6. Et voila. hermetically sealed sterilised Windows and unruffled Debian installation I will try again later. Regards Michael Fothergill -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimwpk3ycub+pnlzwdhl3t7xknosvj7u7m3ny...@mail.gmail.com
Re: help getting grub to see Windows 7 on second drive
On 10/12/2010 11:42, Michael Fothergill wrote: I think the grub update idea might have worked. Now Windows boots when I start up the PC however, F8 allows me to alter the disk boot order using the BIOS and then the other disk fires up and I get GRUB which gives me a nice menu with the Debian and Windows to choose from.. Maybe if I ran grub-update then the next time I boot up I wouldn't see Windows appearing by default. Couldn't you just set the disk with GRUB as the default boot device in the BIOS? That way your Windows will still boot if some disaster happens and you have to put that drive in another machine. Cheers, Tom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d02166c.9030...@furie.org.uk
help getting grub to see Windows 7 on second drive
Dear Debian Folks, I think this query is better sent to this list not debian amd64 so I have relayed it here. I run Lenny AMD64 on an AMD64 box with 8GB RAM and have two SATA drives. The first drive has the Lenny on it. I installed the other drive the other day so I could put Windows 7 on it that I need for some numerical integration calculations. I am trying to avoid reinstalling the Debian if I can but dual booting the two Oses e.g. using Grub in some way.. I tried installing the Windows on the new disk but it wouldn't install with the first drive present. It said it couldn't create or locate an existing partition or something. The cure here according to Windows folks seemed to be to disconnect the other drive (with the Linux on it) from the motherboard and then reboot and install the Windows. This worked a treat. It couldn't see the other drive with the funny primary logical partition and swap space (to Windows but not to Linux folks) because it wasn't there. It just saw one lonely unformatted unallocated unused SATA drive and installed itself on it. It was simple enough that it went for it without grumbling. After I finished the installation, I then rebooted the machine after reconnecting the other hard drive with Debian on it to the motherboard. I then rebooted the PC to find out what on earth would happen then (brave eh?!! maybe just foolhardy.) Then the PC rebooted and Grub fired up and only saw the first drive (sda) and Debian booted up just fine. I didn't look like grub had seen the new drive with the Windows on it. (I had actually run the Debian installer the other day just to see if it could detect the new drive and it did do - so grub should have no problem booting it providing I can encourage it to notice it a little bit but I'm not quite sure how to get it do that just yet). I have a feeling that if it could see the other drive it might end up being known as /dev/sdb etc. But it needs a bit of a stage prompt here. Can anyone suggest a way to get grub to see the new drive and the Windows? I could try mounting the Windows drive onto the Linux file tree. Would that encourage grub to see it on a reboot and allow me the option of booting the Windows OS itself? I looked around on google and read a few suggestions in this area and wondered if I couldn't put something like this into the grub menu file (by the way in what directory does the grub menu file live?) : title Windows 7 map (sd0) (sd1) map (sd1) (sd1) rootnoverify (sd 0,0) chainloader +1 I am not exactly sure if that would work or precisely what it does but would it be helpful here? Would it be helpful if I ran /sbin/grub-install --recheck Suggestions welcome. If this works, then it could be a general way to allow people to install Linux first, not Windows and not have to reinstall the Linux to get grub to work or use e.g. EasyBCD or Partition Magic on Windows to get a dual boot set up to fire up the unreinstalled Linux from Windows and not use grub from then on etc. What you want to be able to do is to start with Linux and Grub, add the Windows and then get Grub to see both and give you the choice of which to fire up. Then if you have to use Windows (I can't get around this), Linux and grub are still taking precedence. Regards Michael Fothergill Date: Wed, 8 Dec 2010 09:58:43 -0200 From: edua...@kalinowski.com.br To: debian-am...@lists.debian.org Subject: Re: dumb question about dual booting debian and Windows 7 on separate drives. There's nothing amd64 specific in this question, debian-user would have been better. On Qua, 08 Dez 2010, Michael Fothergill wrote: I bought an extra SATA drive and hooked it up so now I have two one with Debian on it. My plan is to install Windows on the new drive.. If you installed Windows on the new drive and then installed Debian grub would see the Windows on the other drive and create a boot option for you to fire it up if you wanted to when you boot the PC up. But if you installed debian first as I have on one disk and then add Windows on the other one then if you boot up the machine it will load Windows and you won't get a choice to fire up Linux (at least I don't expect it). Yeah, installing Windows will probably overwrite you MBR and make you linux unbootable. But that's easy to recover. Just boot any linux CD (the debian installer CD will probably work, or use some live distro) and recover grub: http://www.cyberciti.biz/tips/restore-debian-linux-grub-boot-loader.html There are many other similar guides. It is possible I think to modify the bootloader in Windows (without using e.g. Partition Magic) to sniff out the Linux and allow you to choice of booting it when you boot up the PC.. That is possible, but I have never tried. I personally don't like that solution much, I'd rather trust grub to boot Windows that trust Windows to boot anything
help getting grub to see Windows 7 on second drive
Dear Debian Folks, I think this query is better sent to this list not debian amd64 so I have relayed it here. I run Lenny AMD64 on an AMD64 box with 8GB RAM and have two SATA drives. The first drive has the Lenny on it. I installed the other drive the other day so I could put Windows 7 on it that I need for some numerical integration calculations. I am trying to avoid reinstalling the Debian if I can but dual booting the two Oses e.g. using Grub in some way.. I tried installing the Windows on the new disk but it wouldn't install with the first drive present. It said it couldn't create or locate an existing partition or something. The cure here according to Windows folks seemed to be to disconnect the other drive (with the Linux on it) from the motherboard and then reboot and install the Windows. This worked a treat. It couldn't see the other drive with the funny primary logical partition and swap space (to Windows but not to Linux folks) because it wasn't there. It just saw one lonely unformatted unallocated unused SATA drive and installed itself on it. It was simple enough that it went for it without grumbling. After I finished the installation, I then rebooted the machine after reconnecting the other hard drive with Debian on it to the motherboard. I then rebooted the PC to find out what on earth would happen then (brave eh?!! maybe just foolhardy.) Then the PC rebooted and Grub fired up and only saw the first drive (sda) and Debian booted up just fine. I didn't look like grub had seen the new drive with the Windows on it. (I had actually run the Debian installer the other day just to see if it could detect the new drive and it did do - so grub should have no problem booting it providing I can encourage it to notice it a little bit but I'm not quite sure how to get it do that just yet). I have a feeling that if it could see the other drive it might end up being known as /dev/sdb etc. But it needs a bit of a stage prompt here. Can anyone suggest a way to get grub to see the new drive and the Windows? I could try mounting the Windows drive onto the Linux file tree. Would that encourage grub to see it on a reboot and allow me the option of booting the Windows OS itself? I looked around on google and read a few suggestions in this area and wondered if I couldn't put something like this into the grub menu file (by the way in what directory does the grub menu file live?) : title Windows 7 map (sd0) (sd1) map (sd1) (sd1) rootnoverify (sd 0,0) chainloader +1 I am not exactly sure if that would work or precisely what it does but would it be helpful here? Would it be helpful if I ran /sbin/grub-install --recheck Suggestions welcome. If this works, then it could be a general way to allow people to install Linux first, not Windows and not have to reinstall the Linux to get grub to work or use e.g. EasyBCD or Partition Magic on Windows to get a dual boot set up to fire up the unreinstalled Linux from Windows and not use grub from then on etc. What you want to be able to do is to start with Linux and Grub, add the Windows and then get Grub to see both and give you the choice of which to fire up. Then if you have to use Windows (I can't get around this), Linux and grub are still taking precedence. Regards Michael Fothergill Date: Wed, 8 Dec 2010 09:58:43 -0200 From: edua...@kalinowski.com.br To: debian-am...@lists.debian.org Subject: Re: dumb question about dual booting debian and Windows 7 on separate drives. There's nothing amd64 specific in this question, debian-user would have been better. On Qua, 08 Dez 2010, Michael Fothergill wrote: I bought an extra SATA drive and hooked it up so now I have two one with Debian on it. My plan is to install Windows on the new drive.. If you installed Windows on the new drive and then installed Debian grub would see the Windows on the other drive and create a boot option for you to fire it up if you wanted to when you boot the PC up. But if you installed debian first as I have on one disk and then add Windows on the other one then if you boot up the machine it will load Windows and you won't get a choice to fire up Linux (at least I don't expect it). Yeah, installing Windows will probably overwrite you MBR and make you linux unbootable. But that's easy to recover. Just boot any linux CD (the debian installer CD will probably work, or use some live distro) and recover grub: http://www.cyberciti.biz/tips/restore-debian-linux-grub-boot-loader.html There are many other similar guides. It is possible I think to modify the bootloader in Windows (without using e.g. Partition Magic) to sniff out the Linux and allow you to choice of booting it when you boot up the PC.. That is possible, but I have never tried. I personally don't like that solution much, I'd rather trust grub to boot Windows that trust Windows to boot anything
Re: help getting grub to see Windows 7 on second drive
On Wed, Dec 8, 2010 at 9:36 AM, Michael Fothergill michael.fotherg...@googlemail.com wrote: title Windows 7 map (sd0) (sd1) map (sd1) (sd1) rootnoverify (sd 0,0) chainloader +1 Just looking at the above and not the rest of your email, I'd correct it as follows title Windows 7 map (hd0) (hd1) map (hd1) (hd0) rootnoverify (hd 0,0) chainloader +1 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikd_a_naeuryxwij4o2jzbrbkgerwi4g7xrr...@mail.gmail.com
Re: help getting grub to see Windows 7 on second drive
I tried installing the Windows on the new disk but it wouldn't install with the first drive present. It said it couldn't create or locate an existing partition or something. The cure here according to Windows folks seemed to be to disconnect the other drive (with the Linux on it) from the motherboard and then reboot and install the Windows. I had similar situation (Windows7+Debian, 2 hdd). I was disconnected Debian hdd, install Windows 7 without messing with grub. When I power box pressing F8 (boot menu) and chose should I boot Debian hdd or Windows7 hdd. In this way I don't have to mess with grub if I remove Windows7. -- Bye, Goran Dobosevic Hrvatski: www.dobosevic.com English: www.dobosevic.com/en/ Registered Linux User #503414 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cffa293.2070...@dobosevic.com
Re: help getting grub to see Windows 7 on second drive
On Wed, 8 Dec 2010 14:36:38 + Michael Fothergill michael.fotherg...@googlemail.com wrote: I tried installing the Windows on the new disk but it wouldn't install with the first drive present. It said it couldn't create or locate an existing partition or something. The cure here according to Windows folks seemed to be to disconnect the other drive (with the Linux on it) from the motherboard and then reboot and install the Windows. This worked a treat. It couldn't see the other drive with the funny primary logical partition and swap space (to Windows but not to Linux folks) because it wasn't there. It just saw one lonely unformatted unallocated unused SATA drive and installed itself on it. It was simple enough that it went for it without grumbling. After I finished the installation, I then rebooted the machine after reconnecting the other hard drive with Debian on it to the motherboard. I then rebooted the PC to find out what on earth would happen then (brave eh?!! maybe just foolhardy.) Then the PC rebooted and Grub fired up and only saw the first drive (sda) and Debian booted up just fine. I didn't look like grub had seen the new drive with the Windows on it. (I had actually run the Debian installer the other day just to see if it could detect the new drive and it did do - so grub should have no problem booting it providing I can encourage it to notice it a little bit but I'm not quite sure how to get it do that just yet). I have a feeling that if it could see the other drive it might end up being known as /dev/sdb etc. But it needs a bit of a stage prompt here. Can anyone suggest a way to get grub to see the new drive and the Windows? I could try mounting the Windows drive onto the Linux file tree. Would that encourage grub to see it on a reboot and allow me the option of booting the Windows OS itself? I believe what you need to do is to boot into Linux and run update-grub. That should regenerate the grub configuration file(s) without the need for manual tweaking. Make sure you have os-prober installed first, though it should be there already. By the way, be prepared for Windows not to boot. It will be aware of the change in disc configuration, whether it admits the fact or not. I've never tried this with Vista or Win7 so I've no idea what will happen. You may need to revert to one drive and reconfigure the Windows bootloader. That's not as simple as it was with NT/XP but it's still possible. You may ultimately find it easier to have the Windows drive as drive 0, with the Windows bootloader configured to run Linux. Let us know how you get on. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101208152607.38222...@jresid.jretrading.com
Re: help getting grub to see Windows 7 on second drive
On 08/12/2010 14:36, Michael Fothergill wrote: Dear Debian Folks, I think this query is better sent to this list not debian amd64 so I have relayed it here. I run Lenny AMD64 on an AMD64 box with 8GB RAM and have two SATA drives. The first drive has the Lenny on it. I installed the other drive the other day so I could put Windows 7 on it that I need for some numerical integration calculations. I am trying to avoid reinstalling the Debian if I can but dual booting the two Oses e.g. using Grub in some way.. I tried installing the Windows on the new disk but it wouldn't install with the first drive present. It said it couldn't create or locate an existing partition or something. The cure here according to Windows folks seemed to be to disconnect the other drive (with the Linux on it) from the motherboard and then reboot and install the Windows. This worked a treat. It couldn't see the other drive with the funny primary logical partition and swap space (to Windows but not to Linux folks) because it wasn't there. It just saw one lonely unformatted unallocated unused SATA drive and installed itself on it. It was simple enough that it went for it without grumbling. After I finished the installation, I then rebooted the machine after reconnecting the other hard drive with Debian on it to the motherboard. I then rebooted the PC to find out what on earth would happen then (brave eh?!! maybe just foolhardy.) Then the PC rebooted and Grub fired up and only saw the first drive (sda) and Debian booted up just fine. I didn't look like grub had seen the new drive with the Windows on it. (I had actually run the Debian installer the other day just to see if it could detect the new drive and it did do - so grub should have no problem booting it providing I can encourage it to notice it a little bit but I'm not quite sure how to get it do that just yet). I have a feeling that if it could see the other drive it might end up being known as /dev/sdb etc. But it needs a bit of a stage prompt here. Can anyone suggest a way to get grub to see the new drive and the Windows? I could try mounting the Windows drive onto the Linux file tree. Would that encourage grub to see it on a reboot and allow me the option of booting the Windows OS itself? I looked around on google and read a few suggestions in this area and wondered if I couldn't put something like this into the grub menu file (by the way in what directory does the grub menu file live?) : title Windows 7 map (sd0) (sd1) map (sd1) (sd1) rootnoverify (sd 0,0) chainloader +1 I am not exactly sure if that would work or precisely what it does but would it be helpful here? Would it be helpful if I ran /sbin/grub-install --recheck Suggestions welcome. If this works, then it could be a general way to allow people to install Linux first, not Windows and not have to reinstall the Linux to get grub to work or use e.g. EasyBCD or Partition Magic on Windows to get a dual boot set up to fire up the unreinstalled Linux from Windows and not use grub from then on etc. What you want to be able to do is to start with Linux and Grub, add the Windows and then get Grub to see both and give you the choice of which to fire up. Then if you have to use Windows (I can't get around this), Linux and grub are still taking precedence. [cut] sudo update-grub should do the trick. With grub2 the configuration file (grub.cfg) should not be edited by hand; it's updated every time update-grub is run. Have a look in /etc/grub.d and make sure that the file 30_os-prober is present and has execute permissions. This is what searches for Windows during the grub update. Peter HB -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cffa887.6000...@hbsys.plus.com
Re: help getting grub to see Windows 7 on second drive
On Wednesday 08 December 2010 15:47:19 Peter Hillier-Brook wrote: sudo update-grub should do the trick. With grub2 the configuration file (grub.cfg) should not be edited by hand; it's updated every time update-grub is run. Lenny uses grub 1. I think that it is called grub-legacy in Squeeze, but am not sure. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201012081558.02999.lisi.re...@gmail.com
Re: help getting grub to see Windows 7 on second drive
On 08/12/2010 15:58, Lisi wrote: On Wednesday 08 December 2010 15:47:19 Peter Hillier-Brook wrote: sudo update-grub should do the trick. With grub2 the configuration file (grub.cfg) should not be edited by hand; it's updated every time update-grub is run. Lenny uses grub 1. I think that it is called grub-legacy in Squeeze, but am not sure. Lisi The past is a foreign country: they do things differently there. Sorry. Peter HB -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cffb5a5.6040...@hbsys.plus.com
Re: help getting grub to see Windows 7 on second drive
On Wed, 08 Dec 2010 15:58:02 +, Lisi wrote: On Wednesday 08 December 2010 15:47:19 Peter Hillier-Brook wrote: sudo update-grub should do the trick. With grub2 the configuration file (grub.cfg) should not be edited by hand; it's updated every time update-grub is run. Lenny uses grub 1. I think that it is called grub-legacy in Squeeze, but am not sure. Hum... are you sure? :-? IIRC, last time I installed lenny the default option was set to Grub2, I had to manually change it to get Grub legacy instead. It was a 64 bits and an expert install. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2010.12.08.19.04...@gmail.com
