|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
OpenBSD 6.0 amd64 install partitioning
I currently have Windows 10 x64 EFI on an UEFI MOBO and want to replace it with OpenBSD 6.0 amd64.
1. Is it possible to delete the "Recovery Partition", the "EFI System Partition" and the "C: Windows" primary partition and keep the other partitions? I mean, will OpenBSD recognize them or should I delete them all? 2. Should I use MBR or GPT? Will either work? 1TB HDD partitioned like this: Disk Management shows: HTML Code:
Volume Layout Type File System Status Capacity Simple Basic Recovery Partition 450MB Simple Basic EFI System Partition 100MB C: Windows Simple Basic NTFS Primary Partition 100GB D: mp3 Simple Basic NTFS Primary Partition 100GB E: videos Simple Basic NTFS Primary Partition 100GB F: backup Simple Basic NTFS Primary Partition 100GB The rest of the HDD is unallocated free space. Last edited by terrymillers; 26th September 2016 at 03:15 PM. |
|
||||
One correction - my EFI hardware doesn't have a "disable" secure boot, but:
A secure boot partition cannot be booted except when set as the default boot device. It cannot be selected or booted when choosing from a list. The system can be removed from the list of possible boot devices .. which I've tested only after removing the OS. |
|
|||
I guess I have 2 options. Will any of the 2 options destroy the last 3 NTFS partitions?
1. 1a.) Simply delete "Recovery Partition" 1b.) Delete & Repartition the first Primary Partition to OpenBSD Code:
File System Status Capacity unallocated 450MB (deallocated) EFI System Partition 100MB (left intact) OpenBSD Primary Partition 100GB (deallocated & partitioned to OpenBSD) NTFS Primary Partition 100GB (left intact) NTFS Primary Partition 100GB (left intact) NTFS Primary Partition 100GB (left intact) The rest of the HDD is unallocated free space. 2.a) Delete the first 3 partitions 2.b) Create First Partition: 100MB EFI System Partition 2.c) Create Second Partition: 100GB+450MB OpenBSD partition. Code:
File System Status Capacity EFI System Partition 100MB (created) OpenBSD Primary Partition 100GB+450MB (partitioned to OpenBSD) NTFS Primary Partition 100GB (left intact) NTFS Primary Partition 100GB (left intact) NTFS Primary Partition 100GB (left intact) The rest of the HDD is unallocated free space. |
|
||||
I've just been testing GPT installations using 6.0-release, and it is unlikely to be able to manipulate this disk and still retain any of the GPT partitions.
At this time (6.0 release and -current), the fdisk(8) tool's GPT support is limited to initializing new GPT tables, creating an EFI partition, and revising the OpenBSD Area partition in an existing GPT table. Backup - Install - Restore remains my recommendation for your use case. Alternatively, you may install and boot onto a second drive, leaving this drive untouched. OpenBSD will recognize the foreign partitions if installed on a different drive. --- (Incidentally, on 512-byte sector drives, an OpenBSD-created EFI partition will be 480 KB in size -- 960 sectors. So the 100MB that Windows reserves is unnecessary for OpenBSD.) Last edited by jggimi; 27th September 2016 at 06:59 PM. Reason: clarity |
|
||||
Terry,
I thought I'd add some additional thoughts. It is possible to transition with a single disk, retaining the NTFS partitions you want to retain, but the risk of data loss is extremely high. I've been using OpenBSD for 13 years, and yet I would still back up these partitions before attempting it. 1. Back up the data on the filesystems to be retained. 2. Run the install script, assigning a GPT or MBR to the entire disk. Some systems do not have legacy boot and require GPT. 3. Do NOT accept the auto disklabel(8) partitioning. Instead, deploy custom partitioning. Include the NTFS partitions in the disklabel, using the starting sectors and sizes from the prior GPT. Do NOT give the NTFS partitions mount points. The install script would attempt to format any mount points selected. Is this ugly? Yes. Is there a high risk of data loss? Yes. Would I do this? No. |
|
|||
Buy an external/USB HDD, they don't cost much these days, copy all your files to it, then try installing how you want your internal drive, if it doesn't work no problem, all your data is safe on that external drive.
__________________
Linux since 1999, & also a BSD user. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Can't boot after successful install of 5.9 amd64 on a macbook 4.1 | fvgit | OpenBSD Installation and Upgrading | 12 | 5th February 2017 11:39 PM |
openbsd don't boot of AMD64 | philo_neo71 | OpenBSD Installation and Upgrading | 3 | 19th October 2015 09:42 AM |
10 000 buildable packages for OpenBSD/amd64 in pkgsrc | e1-531g | News | 0 | 12th September 2015 02:45 PM |
Opera 10.60 and OpenBSD 4.7 amd64 | jcdenton | OpenBSD General | 3 | 6th August 2010 12:41 AM |
AMD64 - Hard Drive Partitioning | Turquoise88 | General software and network | 8 | 11th September 2009 05:58 AM |