[opensuse] setting up a dual boot system
Ok, my next project is to migrate my work laptop over to a dual boot system. It has a windows vista installation on a 500gb hard drive. (It was originally a 320 gb hard drive, and I made a mirror image of that to a 500gb hard drive, changed it out, so that I would have extra room.) Here is the setup that the Yast analysis suggested while I am installing SUSE linux from the installation disk. You can see that the extra 167gb is used entirely for Linux: /dev/sda 465.76 GB TOSHIBA-MK5065GS 0 60800 /dev/sda1 39.06 GB HPFS/NTFS NTFS /windows/C 0 5099 /dev/sda2 259.03 GB HPFS/NTFS NTFS kep /windows/D 5099 38912 /dev/sda3 167.67 GB Extended 38913 68000 /dev/sda5 2.01 GB Linux swap swap swap 38913 39176 /dev/sda6 20.00 GB Linux native Ext4 / 39176 41786 /dev/sda7 145.65 GB Linux native Ext4 /home 41787 60800 (by the way, I had to type this in by hand, as I can't copy and paste here during the installation) My original thought was that I wanted to shrink the windows D volume "kep" down to 70 GB and start the Linux swap at that point on the system, so that my /home directory would be bigger by about 200GB. So I tried to "move" the extended partition using the expert partitioner (I am still in the install program), and it would not let me, saying that the drive had already been created. (this probably happened when the power went out in the middle of the first install, and I am having to reinstall now, but I don't know for sure). So my question is, if I shrink the windows D volume to 70 GB (I only have 55 gb of data on it), will I be able to format those sectors later and mount it as another partition, like /sda4, and use it to store more data? The expert partitioner will not let me do anything with the empty space at this point in the installation, but here is what the table looks like: /dev/sda 465.76 GB TOSHIBA-MK5065GS 0 60800 /dev/sda1 39.06 GB HPFS/NTFS NTFS /windows/C 0 5099 /dev/sda2 70.00 GB HPFS/NTFS NTFS kep /windows/D 5099 14236 /dev/sda3 167.67 GB Extended 38913 68000 /dev/sda5 2.01 GB Linux swap swap swap 38913 39176 /dev/sda6 20.00 GB Linux native Ext4 / 39176 41786 /dev/sda7 145.65 GB Linux native Ext4 /home 41787 60800 So you see, sectors 14237 (are they called sectors or something else?) through 383912 are unused and unformatted if I shrink the volume. Would it be better to just go on and keep it as NTFS? The only way that would help me out is that I could store files on that drive that would be usable to both windows and linux. However, the only thing I am really planning to use windows for is updating my ipod, and a particular work program I have that won't run under anything besides windows. What are the disadvantages to keeping it as NTFS? Does linux access the files more slowly if they are in NTFS format? Thanks in advance for your help, George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/08/29 19:30 (GMT+0800) George OLson composed:
Here is the setup that the Yast analysis suggested while I am installing SUSE linux from the installation disk. You can see that the extra 167gb is used entirely for Linux:
/dev/sda 465.76 GB TOSHIBA-MK5065GS 0 60800 /dev/sda1 39.06 GB HPFS/NTFS NTFS /windows/C 0 5099 /dev/sda2 259.03 GB HPFS/NTFS NTFS kep /windows/D 5099 38912 /dev/sda3 167.67 GB Extended 38913 68000 /dev/sda5 2.01 GB Linux swap swap swap 38913 39176 /dev/sda6 20.00 GB Linux native Ext4 / 39176 41786 /dev/sda7 145.65 GB Linux native Ext4 /home 41787 60800
Instead of making it dual boot (exactly two operating systems), make it multiboot (more than one installed operating system). Start in Windows. Use Windows' partition resizer to shrink D:. You can also use the Windows partitioner to create new partitions for use by Linux, and without an arbitrary location for the start of the extended (which is nothing but a partition table entry used to identify the location of a logical partition, not a real partition). The Linux installer can use these existing new partitions by resetting to the proper types and formatting as Linux native types. Instead of creating one 20G for /, I suggest you consider making two 20G. Then when upgrade (or before, like for a devel beta release) time comes you can test the waters without disturbing your existing installation, installing the new on the extra /. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 08/29/2011 10:23 PM, Felix Miata wrote:
On 2011/08/29 19:30 (GMT+0800) George OLson composed:
Instead of making it dual boot (exactly two operating systems), make it multiboot (more than one installed operating system). Start in Windows. Use Windows' partition resizer to shrink D:. You can also use the Windows partitioner to create new partitions for use by Linux, and without an arbitrary location for the start of the extended (which is nothing but a partition table entry used to identify the location of a logical partition, not a real partition). The Linux installer can use these existing new partitions by resetting to the proper types and formatting as Linux native types.
Instead of creating one 20G for /, I suggest you consider making two 20G. Then when upgrade (or before, like for a devel beta release) time comes you can test the waters without disturbing your existing installation, installing the new on the extra /.
I think I may have a bigger problem now. For some reason I cannot boot into windows at all. It gives the initial windows splash screen for vista, which is just the little bar at the bottom middle of the screen moving side to side, and then there is a blue screen flash, and the boot sequence starts all over again. I am going to go ahead and load Linux (I can always put my original hard drive back in and try to recover using that), and see if the grub loader will allow me to dual boot to windows. Here is my idea, and you all can tell me if this will work: 1. Install linux now (since I can't boot to windows at all, though the drives are still there) - I will keep the larger ntfs partition unchanged at this point 2. once grub is installed, I will boot to windows and use the windows tools to shrink the D drive 3. in windows tools create the new partitions like you suggested, with 2 20G 4. re-install linux on the new partitions (I will not have used it for anything anyway) the challenge is the boot loader. Since I will already have grub installed, will this be a problem to re-install linux? Thanks George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 30 Aug 2011 05:18:51 +0800 george olson <grglsn765@gmail.com> wrote: <snipped
I think I may have a bigger problem now. For some reason I cannot boot into windows at all. It gives the initial windows splash screen for vista, which is just the little bar at the bottom middle of the screen moving side to side, and then there is a blue screen flash, and the boot sequence starts all over again.
When you wrote that you'd imaged the 320 GB drive onto a 500 GB drive I was concerned that you would run into this problem. What you're trying to do can certainly be done. But you need to first create the larger Windows partitions on the new drive, using Windows tools. Then (e.g. using clonezilla) clone the original Windows partitions into their larger counterparts on the new drive. When done this way, Windows will not fail to boot. Instead, it will recognize that it is booting from a different drive and demand to be activated again. At this point, you should be able to proceed with the Linux installation without complications. Under the circumstances, if I were you, I would just reinstall the 320 GB hard drive and start over, beginning with preparing the Windows partitions on the new drive using Windows tools. good luck! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 08/30/2011 06:32 AM, Carl Hartung wrote:
On Tue, 30 Aug 2011 05:18:51 +0800 george olson<grglsn765@gmail.com> wrote:
<snipped
I think I may have a bigger problem now. For some reason I cannot boot into windows at all. It gives the initial windows splash screen for vista, which is just the little bar at the bottom middle of the screen moving side to side, and then there is a blue screen flash, and the boot sequence starts all over again.
When you wrote that you'd imaged the 320 GB drive onto a 500 GB drive I was concerned that you would run into this problem.
What you're trying to do can certainly be done. But you need to first create the larger Windows partitions on the new drive, using Windows tools. Then (e.g. using clonezilla) clone the original Windows partitions into their larger counterparts on the new drive.
When done this way, Windows will not fail to boot. Instead, it will recognize that it is booting from a different drive and demand to be activated again.
At this point, you should be able to proceed with the Linux installation without complications.
Under the circumstances, if I were you, I would just reinstall the 320 GB hard drive and start over, beginning with preparing the Windows partitions on the new drive using Windows tools.
good luck!
Carl
Thanks so much! I will be working on this over the next week or so and will keep the list updated as to my progress. George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 29 Aug 2011 19:30:01 +0800 George OLson <grglsn765@gmail.com> wrote: <snipped>
Would it be better to just go on and keep it as NTFS? The only way that would help me out is that I could store files on that drive that would be usable to both windows and linux. However, the only thing I am really planning to use windows for is updating my ipod, and a particular work program I have that won't run under anything besides windows.
Hi George, "Been there, done that". Your use case is nearly identical to mine except I don't have the added impetus of a 'work program' that only runs under Windows. (My iPod Classic _requires_ iTunes, however, due to the encrypted firmware ... discovered months after my purchase, thereby precluding a return for refund. Ugh! grrrrr! ^%$@!) You'll have the fewest headaches and complications if you start by using native Windows tools to get your NTFS partitions configured the way you want them and /then/ proceeding with the Linux installation.
What are the disadvantages to keeping it as NTFS? Does linux access the files more slowly if they are in NTFS format?
There is no disadvantage that I'm aware of but that's not the point. The point is iTunes can only 'talk' to partitions where Windows is able to read/write. Therefore, the media files it manages _must_ reside at this point in time on a) the NTFS side, or, b) removable media. The drawback is it takes many extra steps to add new media files to your iTunes Library from the Linux side: a) place the new files on removable media or into a designated 'import from' directory on the NTFS side b) boot into Windows c) launch iTunes d) import into your iTunes Library e) reboot to Linux FYI, if I were able to do this all over again, I would only buy an 'iPod like' device and accessories if it were _guaranteed in writing_ that it could be used and maintained 100% with Linux tools. hth & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 29/08/11 15:50, Carl Hartung wrote:
On Mon, 29 Aug 2011 19:30:01 +0800 George OLson<grglsn765@gmail.com> wrote:
<snipped>
Would it be better to just go on and keep it as NTFS? The only way that would help me out is that I could store files on that drive that would be usable to both windows and linux. However, the only thing I am really planning to use windows for is updating my ipod, and a particular work program I have that won't run under anything besides windows. Hi George,
"Been there, done that". Your use case is nearly identical to mine except I don't have the added impetus of a 'work program' that only runs under Windows. (My iPod Classic _requires_ iTunes, however, due to the encrypted firmware ... discovered months after my purchase, thereby precluding a return for refund. Ugh! grrrrr! ^%$@!)
You'll have the fewest headaches and complications if you start by using native Windows tools to get your NTFS partitions configured the way you want them and /then/ proceeding with the Linux installation.
What are the disadvantages to keeping it as NTFS? Does linux access the files more slowly if they are in NTFS format? There is no disadvantage that I'm aware of but that's not the point. The point is iTunes can only 'talk' to partitions where Windows is able to read/write. Therefore, the media files it manages _must_ reside at this point in time on a) the NTFS side, or, b) removable media.
The drawback is it takes many extra steps to add new media files to your iTunes Library from the Linux side:
a) place the new files on removable media or into a designated 'import from' directory on the NTFS side
b) boot into Windows
c) launch iTunes
d) import into your iTunes Library
e) reboot to Linux
FYI, if I were able to do this all over again, I would only buy an 'iPod like' device and accessories if it were _guaranteed in writing_ that it could be used and maintained 100% with Linux tools.
hth& regards,
Carl
There is an alternative: http://www.ext2fsd.com/ Now with ext4 support, needs a few hacks to get around windows driver issues, and for safety probably best to only use readonly, but works for me. Regards, Tejas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 29 Aug 2011 16:38:23 +0100 Tejas Guruswamy <tejas.guruswamy@opensuse.org> wrote:
On 29/08/11 15:50, Carl Hartung wrote:
On Mon, 29 Aug 2011 19:30:01 +0800 George OLson<grglsn765@gmail.com> wrote:
<snipped>
Would it be better to just go on and keep it as NTFS? The only way that would help me out is that I could store files on that drive that would be usable to both windows and linux. However, the only thing I am really planning to use windows for is updating my ipod, and a particular work program I have that won't run under anything besides windows. Hi George,
"Been there, done that". Your use case is nearly identical to mine except I don't have the added impetus of a 'work program' that only runs under Windows. (My iPod Classic _requires_ iTunes, however, due to the encrypted firmware ... discovered months after my purchase, thereby precluding a return for refund. Ugh! grrrrr! ^%$@!)
You'll have the fewest headaches and complications if you start by using native Windows tools to get your NTFS partitions configured the way you want them and /then/ proceeding with the Linux installation.
What are the disadvantages to keeping it as NTFS? Does linux access the files more slowly if they are in NTFS format? There is no disadvantage that I'm aware of but that's not the point. The point is iTunes can only 'talk' to partitions where Windows is able to read/write. Therefore, the media files it manages _must_ reside at this point in time on a) the NTFS side, or, b) removable media.
The drawback is it takes many extra steps to add new media files to your iTunes Library from the Linux side:
a) place the new files on removable media or into a designated 'import from' directory on the NTFS side
b) boot into Windows
c) launch iTunes
d) import into your iTunes Library
e) reboot to Linux
FYI, if I were able to do this all over again, I would only buy an 'iPod like' device and accessories if it were _guaranteed in writing_ that it could be used and maintained 100% with Linux tools.
hth& regards,
Carl
There is an alternative:
Now with ext4 support, needs a few hacks to get around windows driver issues, and for safety probably best to only use readonly, but works for me.
Like 'ltools', this allows functional (not necessarily 'elegant' or 'safe') r/w access to Linux partitions from within Windows, right? IMHO, this is a good 'rescue/repair/restore mode' tool to keep in the kit bag for emergencies. In my case, which is nearly identical to the OP's use case, contemporary NTFS support within Linux is 'seamless' and 'elegant' enough that complicating matters further by adding new Windows tools with possibly 'a few hacks' to make it integrate just isn't worth the effort. YMMV, of course. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carl Hartung -
Felix Miata -
george olson -
George OLson
-
Tejas Guruswamy