Re: RAID b/w GPT and NON GPT partition.
Muhammad Yousuf Khan a écrit :
> Thanks Arno, Pascal and Gary with your input i manage to copy the partition
> to new drive in GPT format and my all drives (mdadm devices) are synced
> now.
>
> I have 4 RAID1 Partitions for all for different purpose.
>
>
> md1 : active raid1 sdb5[2] sda5[0]
> 9763768 blocks super 1.2 [2/2] [UU]
>
> md3 : active raid1 sdb4[2] sda4[0]
> 474902392 blocks super 1.2 [2/2] [UU]
>
> md2 : active raid1 sdb3[2] sda3[0]
> 976561016 blocks super 1.2 [2/2] [UU]
>
> md0 : active raid1 sdb1[2] sda1[0]
> 3904500 blocks super 1.2 [2/2] [UU]
>
>
> but there are few confusions. actually in my old drive. there was a
> extended partition for SWAP.
I guess you mean a logical partition. An extended partition cannot
contain anything but logical partitions.
> however when i copy the partition table with
> gdisk "x" and "u" option it created the file successfully however. i can
> not see extended in the output. gdisk -l /dev/sdb
Extended and logical partitions do not exist in GPT. There is no need
for them anymore. Their purpose was to workaround the 4-partition limit
of the MBR. In GPT, the limit is at least 128.
> Number Start (sector) End (sector) Size Code Name
> 1 2048 7813119 3.7 GiB FD00 Linux RAID
> 3 27344896 1980469247 931.3 GiB FD00 Linux RAID
> 4 1980469248 2930276351 452.9 GiB FD00 Linux RAID
> 5 7815168 27344895 9.3 GiB FD00 Linux RAID
>
> number "5" is the swap partition as i know it from size.
No, partition 5 is a RAID member. I guess you mean that the RAID array
/dev/md1 it belongs to is used as a swap device.
> and i also
> attached that partition to my mdadm drive md1 which was set to swap by me
> and it is successfully synced. now my question is as i can not see the
> extended partition type in the list by attaching "5" partition to the swap
> directory.
Huh ? "Swap directory" ?
> have i done it the right way thing or i have done it wrong?
Nothing wrong.
> my last question is making the new 2TB drive able to boot.
> when i run the command grup-install it gives me error.
> # grub-install /dev/sdb
> /usr/sbin/grub-setup: warn: This GPT partition label has no BIOS Boot
> Partition; embedding won't be possible!.
> /usr/sbin/grub-setup: error: embedding is not possible, but this is
> required when the root device is on a RAID array or LVM volume.
> if i change the type to "ef02" (Bios Boot Partition) i may not be able to
> attach that partition to my current raid level.
Don't change the type of an existing RAID partition ! mdadm does not
care about the partition type, but if you change the type to "BIOS boot"
and run grub-install, then it will overwrite the contents of the partition.
You need to create a new partition with the "BIOS boot" type. It can
usually be as small as 50 kB. It will fit in the unallocated space
before partition 1, or between partitions 1 and 5 (partition are not in
order). Or just put it in the free space after the last partition.
Just one comment : your new disk has 0.5 TB unused space. You could have
created bigger partitions to use the whole disk space. This way when you
replace the remaining 1.5 TB disk with a bigger one, it would have been
possible to extend the size of the RAID arrays to take advantage of the
disk capacity.
Reply to: