Hi All,
I need to migrate a Fedora server from a mechanical hard drive running legacy boot to an NVMe drive that requires EUFI to boot.
Am I stuck reinstalling everything?
Many thanks, -T
On Jul 8, 2020, at 16:32, toddandmargo via users users@lists.fedoraproject.org wrote:
Hi All,
I need to migrate a Fedora server from a mechanical hard drive running legacy boot to an NVMe drive that requires EUFI to boot.
Am I stuck reinstalling everything?
Is this a BIOS limitation? I don’t think there’s any reason why you couldn’t boot via legacy to a GPT-labeled disk with GRUB installed.
But if you are migrating, you could boot off the old disk with the nvme hardware attached, and set it up with a UEFI partition, a separate /boot partition, and the rest as LVM, and then migrate the data. Once you have the correct UUID of the non-LVM volumes updated in your fstab, and the grub2-efi-x86_64 package installed, you can give it a try to switch over.
-- Jonathan Billings billings@negate.org
---- On Wed, 08 Jul 2020 13:54:29 -0700 Jonathan Billings billings@negate.org wrote ----
On Jul 8, 2020, at 16:32, toddandmargo via users users@lists.fedoraproject.org wrote:
Hi All,
I need to migrate a Fedora server from a mechanical hard drive running legacy boot to an NVMe drive that requires EUFI to boot.
Am I stuck reinstalling everything?
Is this a BIOS limitation? I don’t think there’s any reason why you couldn’t boot via legacy to a GPT-labeled disk with GRUB installed.
But if you are migrating, you could boot off the old disk with the nvme hardware attached, and set it up with a UEFI partition, a separate /boot partition, and the rest as LVM, and then migrate the data. Once you have the correct UUID of the non-LVM volumes updated in your fstab, and the grub2-efi-x86_64 package installed, you can give it a try to switch over.
The motherboard has both legacy and eufi on it.
The original drive was partitioned as msdos and Fedora was installed as legacy boot.
The new NVMe drive requires EUFI to be seen by the bios and by Fedora . Fedora requires gtp to install to an NVMe drive
Even though I knew it would not work, I tried clonzilla'ing the two.
The issue stands that the new drive has to be gpt, have a 1 mb empty space at the beginning to accommodate the EUFI boot stuff and another partition for Fedora to handle the EUFI boot stuff
I currently have the NVMe drive with Xfce and FC32 installed on it. But I now have the bios back to legacy and the NVMe drive has disappeared again (which is what I temporarily want).
The scope of this server has changed dramatically, so reinstalling might no be such a bad idea. It would dump a lot of sins of the past. I just was to restore users, groups, /home, /export, samba, ftp and I am good to go.
Oh, and I am upgrading the old server from 30 to 32 at the moment
-T
On 07/08/2020 03:11 PM, toddandmargo via users wrote:
The original drive was partitioned as msdos and Fedora was installed as legacy boot.
OK, but I'm sure that the partition was reformatted, and not as msdos because Fedora can't run off of that kind of filesystem. How is the partition formatted now?
On 2020-07-09 05:47, Joe Zeff wrote:
On 07/08/2020 03:11 PM, toddandmargo via users wrote:
The original drive was partitioned as msdos and Fedora was installed as legacy boot.
OK, but I'm sure that the partition was reformatted, and not as msdos because Fedora can't run off of that kind of filesystem.
What did you mean by that?
GNU Parted 3.3 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA Crucial_CT525MX3 (scsi) Disk /dev/sda: 525GB Sector size (logical/physical): 512B/512B
Partition Table: msdos <----------
Disk Flags:
Number Start End Size Type File system Flags 1 1049kB 1501MB 1499MB primary ext4 boot 2 1501MB 19.6GB 18.1GB primary linux-swap(v1) 3 19.6GB 525GB 505GB primary ext4
On Wed, Jul 08, 2020 at 03:47:58PM -0600, Joe Zeff wrote:
On 07/08/2020 03:11 PM, toddandmargo via users wrote:
The original drive was partitioned as msdos and Fedora was installed as legacy boot.
OK, but I'm sure that the partition was reformatted, and not as msdos because Fedora can't run off of that kind of filesystem. How is the partition formatted now?
I think he is referring to the partition table, not filesystems.
Fred
On 2020-07-09 05:57, Fred Smith wrote:
On Wed, Jul 08, 2020 at 03:47:58PM -0600, Joe Zeff wrote:
On 07/08/2020 03:11 PM, toddandmargo via users wrote:
The original drive was partitioned as msdos and Fedora was installed as legacy boot.
OK, but I'm sure that the partition was reformatted, and not as msdos because Fedora can't run off of that kind of filesystem. How is the partition formatted now?
I think he is referring to the partition table, not filesystems.
So, you think he meant fat or ntfs? I can't recall an "msdos" file system.
On Jul 8, 2020, at 18:42, Ed Greshko ed.greshko@greshko.com wrote:
So, you think he meant fat or ntfs? I can't recall an "msdos" file system.
No one in this thread is talking about filesystems, but instead disk petition tables.
Linux and Windows On x86 use disks that are partitioned with a DOS partition table (or disk label for old Unix folks). It’s what has the Master Boot Record:
https://en.wikipedia.org/wiki/Master_boot_record
We now also use a GUID Partition Table for partitioning disks, and it’s required for UEFI. Most modern hardware supports GPT.
https://en.wikipedia.org/wiki/GUID_Partition_Table
-- Jonathan Billings
On Jul 8, 2020, at 20:20, Jonathan Billings billings@negate.org wrote:
petition tables
Er.... partition tables.
-- Jonathan Billings
On 2020-07-09 08:19, Jonathan Billings wrote:
On Jul 8, 2020, at 18:42, Ed Greshko ed.greshko@greshko.com wrote:
So, you think he meant fat or ntfs? I can't recall an "msdos" file system.
No one in this thread is talking about filesystems, but instead disk petition tables.
No one except the person who wrote "not as msdos because Fedora can't run off of that kind of filesystem".
Yes, I'm being pedantic. I try hard to avoid ambiguity. And it helps to be precise.
On Jul 8, 2020, at 17:11, toddandmargo via users users@lists.fedoraproject.org wrote:
The motherboard has both legacy and eufi on it.
The original drive was partitioned as msdos and Fedora was installed as legacy boot.
The new NVMe drive requires EUFI to be seen by the bios and by Fedora . Fedora requires gtp to install to an NVMe drive
Even though I knew it would not work, I tried clonzilla'ing the two.
The issue stands that the new drive has to be gpt, have a 1 mb empty space at the beginning to accommodate the EUFI boot stuff and another partition for Fedora to handle the EUFI boot stuff
The 1mb empty partition at the beginning of a GPT labeled disk is only needed if you are booting via Legacy boot. While booting via UEFI (the correct order of those letters) you will need the EFI partition to be much larger than that since it needs to hold at least one EFI executable and the grub config and related bits.
I currently have the NVMe drive with Xfce and FC32 installed on it. But I now have the bios back to legacy and the NVMe drive has disappeared again (which is what I temporarily want).
The scope of this server has changed dramatically, so reinstalling might no be such a bad idea. It would dump a lot of sins of the past. I just was to restore users, groups, /home, /export, samba, ftp and I am good to go.
Oh, and I am upgrading the old server from 30 to 32 at the moment
I know I needed to rebuild my Fedora server recently, the LVM version used to build it was so old that I was getting warnings in my log watch reports. A testament to how well fed up/dnf system-upgrade has worked, I suppose. Anyway, I took the opportunity to LUKS-encrypt my disks the last time I installed.
It shouldn’t be difficult to mount the old disk and copy over relevant data.
-- Jonathan Billings
On Wed, Jul 8, 2020 at 5:11 PM toddandmargo via users users@lists.fedoraproject.org wrote:
---- On Wed, 08 Jul 2020 13:54:29 -0700 Jonathan Billings billings@negate.org wrote ----
On Jul 8, 2020, at 16:32, toddandmargo via users users@lists.fedoraproject.org wrote:
Hi All,
I need to migrate a Fedora server from a mechanical hard drive running legacy boot to an NVMe drive that requires EUFI to boot.
Am I stuck reinstalling everything?
Is this a BIOS limitation? I don’t think there’s any reason why you couldn’t boot via legacy to a GPT-labeled disk with GRUB installed.
But if you are migrating, you could boot off the old disk with the nvme hardware attached, and set it up with a UEFI partition, a separate /boot partition, and the rest as LVM, and then migrate the data. Once you have the correct UUID of the non-LVM volumes updated in your fstab, and the grub2-efi-x86_64 package installed, you can give it a try to switch over.
The motherboard has both legacy and eufi on it.
The original drive was partitioned as msdos and Fedora was installed as legacy boot.
The new NVMe drive requires EUFI to be seen by the bios and by Fedora . Fedora requires gtp to install to an NVMe drive
Even though I knew it would not work, I tried clonzilla'ing the two.
Odd since you can restore one partition at a time in clonezilla. So, if you partition new drive (LVM/whatever), you then feed the partitions. But I have only done that by first creating a clonezilla server.
The issue stands that the new drive has to be gpt, have a 1 mb empty space at the beginning to accommodate the EUFI boot stuff and another partition for Fedora to handle the EUFI boot stuff
I currently have the NVMe drive with Xfce and FC32 installed on it. But I now have the bios back to legacy and the NVMe drive has disappeared again (which is what I temporarily want).
What if you boot off a liveCD and then move the bits you want to save, mentioned below? Also, your box cannot boot off the NVMe drive and then mount old drive?
The scope of this server has changed dramatically, so reinstalling might no be such a bad idea. It would dump a lot of sins of the past. I just was to restore users, groups, /home, /export, samba, ftp and I am good to go.
I take you are then just rsyncing it?
Oh, and I am upgrading the old server from 30 to 32 at the moment
-T _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 2020-07-08 22:20, Mauricio Tavares wrote:
On Wed, Jul 8, 2020 at 5:11 PM toddandmargo via users
Even though I knew it would not work, I tried clonzilla'ing the two.
Odd since you can restore one partition at a time in clonezilla.So, if you partition new drive (LVM/whatever), you then feed the partitions. But I have only done that by first creating a clonezilla server.
I did the whole thing. And I knew better, but ...
I created a dual legacy / EUFI dual boot flash drive with a full version of Fedora on it. I found that Fedora always thinks it has the original EUFI or original legacy boot on the drive. I suppose you could configure it out, but the project is something to behold.
What if you boot off a liveCD and then move the bits you want tosave, mentioned below? Also, your box cannot boot off the NVMe drive and then mount old drive?
Oh it is easier than that. I have full access to the original drive and a wonderful "dump" backup of the original drive. It will not be too hard to migrate the data over. And it will dump all the sins of the past. And I already have Fedora 32 installed on the NVMe drive.
The scope of this server has changed dramatically, so reinstalling might no be such a bad idea. It would dump a lot of sins of the past. I just was to restore users, groups, /home, /export, samba, ftp and I am good to go.
I take you are then just rsyncing it?
I will just use cp and krusader
I was just hoping there was a utility out there that would do it all for me. But, I am thinking it would be better to start over.
-
Ed Greshko -
Fred Smith -
Joe Zeff -
Jonathan Billings -
Mauricio Tavares -
Todd Chester -
toddandmargo