[opensuse] setup dual boot on dell xps13
Hi everyone, I just purchased a dell xps 13 and I am getting ready to set up dual boot. I noticed that the hard drive (in windows) has 3 partitions in this order: 500mb EFI partition, the operating system (C drive, 117gb), and an 850mb recovery drive after that. Using the windows shrink tool, I am freeing up 83gb of the windows partition to install opensuse. I know that I will have a swap, the root partition, and a data partition. My question is, is this likely to present a problem for the windows recovery partition, since it is at the end of the drive, and my windows and linux partitions are in the middle? I have no idea what windows will do when all of a sudden there are 3 extra partitions in between it and the recovery partition. -- George Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Box #2: 13.1 | KDE 4.7.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.7.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2016 05:54 PM, tech@reachthetribes.org wrote:
Hi everyone, I just purchased a dell xps 13 and I am getting ready to set up dual boot. I noticed that the hard drive (in windows) has 3 partitions in this order: 500mb EFI partition, the operating system (C drive, 117gb), and an 850mb recovery drive after that.
Using the windows shrink tool, I am freeing up 83gb of the windows partition to install opensuse. I know that I will have a swap, the root partition, and a data partition.
My question is, is this likely to present a problem for the windows recovery partition, since it is at the end of the drive, and my windows and linux partitions are in the middle? I have no idea what windows will do when all of a sudden there are 3 extra partitions in between it and the recovery partition.
My main laptop has two hard drives. Windows knows there is another hard drive because the system tells it it's there but it can't access it. Windows, at least up to 7, is blind to Linux file systems. My guess is that Windows will not even know there are new partitions between it and swap. Just a big hole in the hard drive. Linux has no problem at all reading the Windows drive. -- Fast is fine, but accuracy is final. You must learn to be slow in a hurry. -Wyatt Earp- _ _... ..._ _ _._ ._ ..... ._.. ... .._ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/09/2016 06:41 PM, Billie Walsh wrote:
On 04/09/2016 05:54 PM, tech@reachthetribes.org wrote:
Hi everyone, I just purchased a dell xps 13 and I am getting ready to set up dual boot. I noticed that the hard drive (in windows) has 3 partitions in this order: 500mb EFI partition, the operating system (C drive, 117gb), and an 850mb recovery drive after that.
Using the windows shrink tool, I am freeing up 83gb of the windows partition to install opensuse. I know that I will have a swap, the root partition, and a data partition.
My question is, is this likely to present a problem for the windows recovery partition, since it is at the end of the drive, and my windows and linux partitions are in the middle? I have no idea what windows will do when all of a sudden there are 3 extra partitions in between it and the recovery partition.
My main laptop has two hard drives. Windows knows there is another hard drive because the system tells it it's there but it can't access it. Windows, at least up to 7, is blind to Linux file systems. My guess is that Windows will not even know there are new partitions between it and swap. Just a big hole in the hard drive.
Linux has no problem at all reading the Windows drive.
Ok, great! I have installed Leap now and I am kind of able to get it to run, but I am running into issues with getting the network card to work. I will start a new thread on that one. -- George Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Box #2: 13.1 | KDE 4.7.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.7.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2016-04-09 at 17:54 -0500, tech@reachthetribes.org wrote:
Using the windows shrink tool, I am freeing up 83gb of the windows partition to install opensuse. I know that I will have a swap, the root partition, and a data partition.
83GB is not that much; I would consider not using a separate home. And certainly do not use btrfs.
My question is, is this likely to present a problem for the windows recovery partition, since it is at the end of the drive, and my windows and linux partitions are in the middle? I have no idea what windows will do when all of a sudden there are 3 extra partitions in between it and the recovery partition.
Not likely, I have a similar setup. However, I think it is better that you image that partition to somewhere else, then delete it, because running that recovery destroys Linux and your partitions, making it impractical except for returning the machine to the repair service or manufacturer on warranty. I think it is better to image the entire disk, using something like clonezilla (it makes files for each partition), so that in case of disaster you can recover Windows to a previous working state, but shrinked and with double boot. Or recover Linux, too. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcKnXIACgkQtTMYHG2NR9VwNQCghczUZQEUN82oh3sU9ac5Bc8H ku4An1VDtOL2enrjPuB6MM/lyV3xyjyl =7UAd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On April 10, 2016 11:37:38 AM PDT, "Carlos E. R." <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2016-04-09 at 17:54 -0500, tech@reachthetribes.org wrote:
Using the windows shrink tool, I am freeing up 83gb of the windows partition to install opensuse. I know that I will have a swap, the root partition, and a data partition.
83GB is not that much; I would consider not using a separate home. And certainly do not use btrfs.
My question is, is this likely to present a problem for the windows recovery partition, since it is at the end of the drive, and my windows and linux partitions are in the middle? I have no idea what windows will do when all of a sudden there are 3 extra partitions in between it and the recovery partition.
Not likely, I have a similar setup. However, I think it is better that you image that partition to somewhere else, then delete it, because running that recovery destroys Linux and your partitions, making it impractical except for returning the machine to the repair service or manufacturer on warranty.
I think it is better to image the entire disk, using something like clonezilla (it makes files for each partition), so that in case of disaster you can recover Windows to a previous working state, but shrinked and with double boot. Or recover Linux, too.
- -- Cheers, Carlos E. R.
Probably too late for this advice, but in addition to agreeing with Carlos, I would go one step further, and get another disk drive and drive tray, and reserve one for windows and the other for Linux, because you don't have enough drive Space for EITHER system,let alone both. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
As for the size concerns, Windows 10 wants 16G minimum, and openSUSE says 5G minimum recommended for graphical install, which is probably due for revision. Anyway, it'll be tight, but is not a problem to share 128GiB drive with both Windows and Linux. It just takes some planning about what you're going to use each of them for. The more cloud or NAS dependent your work is, the less of a problem this will be. Another option that saves space is to choose a primary OS and then put the other one in a VM. This is a bit tricky, but the license supposedly allows you to *install* one instance of the software on the hardware, either baremetal or VM. The trick will be whether you go down the OVMF rabbit hole to get the Dell OEM Windows to run (it's UEFI only) or if you figure out how to get non-OEM Windows from Microsoft and feed that to a conventional BIOS VM. I personally prefer virt-manager for this but gnome-boxes works also. So it really depends on your use case, what what rabbit holes you do and don't want to go down. Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10 April 2016 at 00:54, tech@reachthetribes.org <tech@reachthetribes.org> wrote:
Hi everyone, I just purchased a dell xps 13 and I am getting ready to set up dual boot. I noticed that the hard drive (in windows) has 3 partitions in this order: 500mb EFI partition, the operating system (C drive, 117gb), and an 850mb recovery drive after that.
Using the windows shrink tool, I am freeing up 83gb of the windows partition to install opensuse. I know that I will have a swap, the root partition, and a data partition.
My question is, is this likely to present a problem for the windows recovery partition, since it is at the end of the drive, and my windows and linux partitions are in the middle? I have no idea what windows will do when all of a sudden there are 3 extra partitions in between it and the recovery partition.
With only 83GB of space for openSUSE I'd recommend against using a separate data partition While the minimal recommend root partition size for btrfs with snapshots is 40GB, that really is 'minimal', and there really is no harm in having /home on the same partition as a btrfs root file system now we have a subvolume for /home. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/10/2016 01:41 PM, Richard Brown wrote:
With only 83GB of space for openSUSE I'd recommend against using a separate data partition
While the minimal recommend root partition size for btrfs with snapshots is 40GB, that really is 'minimal', and there really is no harm in having /home on the same partition as a btrfs root file system now we have a subvolume for /home.
That's good, thanks Richard and Carlos. I actually thought the same thing too, so I ordered a 500Gb drive to replace it. But for now I am trying to just get opensuse to work - when the 500gb comes I will clone the windows and linux partitions and then swap the drive over. -- George Box: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB Laptop #2: 42.1 | Gnome new | Core i5?? | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Apr 9, 2016 at 4:54 PM, tech@reachthetribes.org <tech@reachthetribes.org> wrote:
Hi everyone, I just purchased a dell xps 13 and I am getting ready to set up dual boot. I noticed that the hard drive (in windows) has 3 partitions in this order: 500mb EFI partition, the operating system (C drive, 117gb), and an 850mb recovery drive after that.
Using the windows shrink tool, I am freeing up 83gb of the windows partition to install opensuse. I know that I will have a swap, the root partition, and a data partition.
My question is, is this likely to present a problem for the windows recovery partition, since it is at the end of the drive, and my windows and linux partitions are in the middle? I have no idea what windows will do when all of a sudden there are 3 extra partitions in between it and the recovery partition.
Windows won't care so long as it doesn't recognize the partition type GUID for those partitions. Older versions of parted improperly set the partition type GUID for Linux partitions to the GUID for Windows, and Windows will actively encourage the user to format those partitions because a.) it properly thinks it owns them, seeing as they have a Windows partition type GUID and b.) doesn't recognize the contents of the partition, since it doesn't know what Linux file systems are. The easiest way to check this and fix it if wrong is with gdisk. # gdisk -l /dev/sdX If any of the Linux paritions have type code 0700, it should be changed to 8300. Only Windows partitions should have type code 0700. Note that those type codes are disk vernacular, the actual code used on disk is a GUID (rather long). -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Billie Walsh -
Carlos E. R. -
Chris Murphy -
John Andersen -
Richard Brown -
tech＠reachthetribes.org