Clarification on partitioning of the dell windows bootable laptop, not sure
how much the surface is like, but some background on what they are since I
don't mount the windoze slices under linux:
nvme0n1p1 == EFI partition
nvme0n1p2 == Windoze boot partition
nvme0n1p3 == Main NTFS/WinFS partition for windoze
nvme0n1p4 == extended partition slice
nvme0n1p5 == linux grub boot slice
nvme0n1p6 == luks cryptsetup volume+pv/vg/lv for rest of ubuntu linux
nvme0n1p7 == Dell Recovery partition
Again same with sata, sda1 == nvme0n1p1, sda2 == nvme0n1p2, and like.
I remember the recovery partition at the end in p7 (end of disk) slice that
I had to resize within that, and not bonk the end partition. Not sure I
documented it, I was more just praying it worked after, but it works well,
and still boot into win10 on it to keep it up to date as an office win10pro
image that came with it off refurb. I haven't tried a dell restore, not
sure I want to... Hey otherwise works dandy.
I suspect the surface isn't far from this for most efi-booting devices,
only recovery partitions/schemes seem to vary between vendors.
HTH!
-mb
On Fri, Sep 21, 2018 at 12:30 AM Michael Butash <
michael@butash.net> wrote:
> I've been doing md+luks+lvm for a long time, and really find no complaints
> moving from spinners, to sata ssd, to nvme m.2. SSD leveling seems less an
> issue in modern samsung and others that auto-level, otherwise I'd love them
> one a year, at best, but not so much lately with 950+ gen samsung m2's. My
> laptop is a single toshiba m2 1tb and is doing great with out active trim
> features enabled.
>
> Here's my basic setups for systems, using both a laptop and my desktop,
> both with m2 disks, but laptop with factory windoze, and desktop native
> linux with all efi disabled. This is no different than my sata
> spinners/ssd, just replace nvme0n*p* with sd*.
>
> Laptop (xps15 9560) retains the factory windoze partition as well as a
> hidden dell restore partitions (3-4), next boot, luks spv0, and rest
> pv/vg/lvm for ubuntu, but mapping /boot/EFI still for upgrades:
>
> host# lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> nvme0n1 259:0 0 953.9G 0 disk
> ├─nvme0n1p1 259:1 0 499M 0 part /boot/efi
> ├─nvme0n1p2 259:2 0 128M 0 part
> ├─nvme0n1p3 259:3 0 131.5G 0 part
> ├─nvme0n1p4 259:4 0 834M 0 part
> ├─nvme0n1p5 259:5 0 499M 0 part /boot
> ├─nvme0n1p6 259:6 0 808.1G 0 part
> │ └─spv0 253:0 0 808.1G 0 spv0
> │ ├─host--vg0-root0 253:1 0 17G 0 lvm /
> │ ├─host--vg0-swap0 253:2 0 4G 0 lvm [SWAP]
> │ ├─host--vg0-var0 253:3 0 6G 0 lvm /var
> │ ├─host--vg0-varlog0 253:4 0 3G 0 lvm /var/log
> │ ├─host--vg0-home0 253:5 0 90G 0 lvm /home
> └─nvme0n1p7 259:7 0 12G 0 part
>
> Vs. my dual-nvme disk desktop system like setup under arch I use normally,
> legacy boot without efi wonkyness:
>
> host# lsblk
> nvme0n1 259:0 0 477G 0 disk
> ├─nvme0n1p1 259:1 0 1G 0 part
> │ └─md0 9:0 0 1023M 0 raid1
> /boot
> └─nvme0n1p2 259:2 0 476G 0 part
> └─md1 9:1 0 475.8G 0 raid1
> └─spv0 253:0 0 475.8G 0 crypt
> ├─host--vg0-swap0 253:1 0 2G 0 lvm
> ├─host--vg0-root0 253:2 0 22G 0 lvm /
> ├─host--vg0-var0 253:3 0 10G 0 lvm
> /var
> ├─host--vg0-varlog0 253:4 0 3G 0 lvm
> /var/log
> ├─host--vg0-home0 253:5 0 80G 0 lvm
> /home
> nvme1n1 259:3 0 477G 0 disk
> ├─nvme1n1p1 259:4 0 1G 0 part
> │ └─md0 9:0 0 1023M 0 raid1
> /boot
> └─nvme1n1p2 259:5 0 476G 0 part
> └─md1 9:1 0 475.8G 0 raid1
> └─spv0 253:0 0 475.8G 0 crypt
> ├─host--vg0-swap0 253:1 0 2G 0 lvm
> ├─host--vg0-root0 253:2 0 22G 0 lvm /
> ├─host--vg0-var0 253:3 0 10G 0 lvm
> /var
> ├─host--vg0-varlog0 253:4 0 3G 0 lvm
> /var/log
> ├─host--vg0-home0 253:5 0 80G 0 lvm
> /home\
>
> Desktop hardware is a precision 7910 desktop with 2x pcie 8x to dual m2
> slot drives, with currently 2x samsung 950 pro 512gb's in it.
>
> Both are working well, and haven't seem to throw any smart alerts to die
> in about 2 years now on each.
>
> New samsung m.2 970 evo's are out now, as are pro's probably shortly too -
> I'd buy em if refreshing. I've filled up my 512's in raid0, almost lust my
> laptop's 1tb, but otherwise added some odd/old 256/512gb ssd's for my kvm
> vm's to run on for bulk pig windoze server instances and fortinet/other
> appliances.
>
> -mb
>
>
> On Thu, Sep 20, 2018 at 4:14 PM Mark Phillips <mark@phillipsmarketing.biz>
> wrote:
>
>> Do you recommend installing Ubuntu 18.04 on an lvm (ie selecting that
>> option when installing) in a dual boot with Windows 10 scenario?
>>
>> My thought is if the Ubuntu setup works well on my Surface Pro 4, is
>> stable, etc. then I would use the lvm to nuke the Windows partition and
>> Windows recovery partition and absorb them into the Ubuntu partition.
>>
>> Will that work?
>>
>> Thanks,
>> Mark
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)