Re: Will this in-place conversion from LEGACY/MBR RAID1 boot to GPT/EFI boot work

[Ram Ramesh <rramesh2400@gmail.com>]

Sorry for trimming the partition table outputs. Here is the full transcript
> n-lata [rramesh] 400 > *sudo fdisk -l /dev/nvme0n1*
> [sudo] password for rramesh:
> Disk /dev/nvme0n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
> Disk model: INTEL SSDPEKNW020T8
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0xa8ebe2b2
>
> Device         Boot    Start        End    Sectors  Size Id Type
> /dev/nvme0n1p1          2048   67110911   67108864   32G 83 Linux
> /dev/nvme0n1p2      67110912 4000797359 3933686448  1.8T 83 Linux
> n-lata [rramesh] 401 > date
> Tue Oct  7 08:51:17 AM CDT 2025
> n-lata [rramesh] 402 > *sudo fdisk -l /dev/nvme1n1*
> [sudo] password for rramesh:
> Disk /dev/nvme1n1: 1.86 TiB, 2048408248320 bytes, 4000797360 sectors
> Disk model: INTEL SSDPEKNW020T8
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x66209137
>
> Device         Boot    Start        End    Sectors  Size Id Type
> /dev/nvme1n1p1          2048   67110911   67108864   32G 83 Linux
> /dev/nvme1n1p2      67110912 4000797359 3933686448  1.8T 83 Linux
> n-lata [rramesh] 403 > *df -h /*
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/md1p1       32G  514M   30G   2% /
> n-lata [rramesh] 404 > *sudo fdisk -l /dev/md1*
> Disk /dev/md1: 1.83 TiB, 2013913219072 bytes, 3933424256 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 5EDF1B4A-C294-4414-A2B1-8ADA6DF7F17A
>
> Device         Start        End    Sectors  Size Type
> /dev/md1p1      2048   67110911   67108864   32G Linux filesystem
> /dev/md1p2  67110912  134219775   67108864   32G Linux filesystem
> /dev/md1p3 134219776  268437503  134217728   64G Linux filesystem
> /dev/md1p4 268437504  402655231  134217728   64G Linux filesystem
> /dev/md1p5 402655232 3933424222 3530768991  1.6T Linux filesystem

Also, no issue with secondary GPT partition table overlapping existing 
(MBR) partitions because I intend to delete all partitions and recreate 
them again as part of GPT conversion. I have free space as current MBR 
partition 1 on both SSDs  (/dev/nvme0n1p1 and /dev/nvme1n1p1) is unused 
and can be trashed.

Regards
Ramesh