I just got a new harddisk, because my old RAID of 3x 1 TB disks are getting filled and I'm running out of space. In the end I'll have replaced my old disks by 3x 4 TB disks. Currently the setup is as this:
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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 Disk identifier: 0x38d543a1 Device Boot Start End Blocks Id System /dev/sda1 * 63 514079 257008+ 83 Linux /dev/sda2 514080 4707044 2096482+ 82 Linux swap / Solaris /dev/sda3 4707045 13092974 4192965 83 Linux /dev/sda4 13092975 1953520064 970213545 5 Extended /dev/sda5 13093038 15197489 1052226 83 Linux /dev/sda6 15197553 1953520064 969161256 83 Linux
Same to the other 2 disks, of course. So, I have (for x=[abc]):
For the new disks I want a more simple layout like this maybe:
If it works, I would be fine without any special /boot partition anyway, but there's another problem: on the old disk set I have LVM and a Volume Group named "vg" and on the new disk I have a Volume Group named "lv":
PV VG Fmt Attr PSize PFree /dev/md4 vg lvm2 a-- 1.81t 129.53g /dev/md6 lv lvm2 a-- 3.64t 3.58t
I made some Logical Volumes on "lv", copied over my system, ran update-grub and grub-install /dev/sdX and rebooted. In the grub menu I can select my desired new root partition, but when I try to boot from it, grub is not able to find the root device. Config lines within grub looks like this (from memory):
search --no-floppy --fs-uuid --set-root=0d54bd89-6628-499f-b835-e146a6fd895f
The UUID within grub matches the same UUID of /dev/lv/root, but grub states that I can't find the disk. The needed modules like for LVM and RAID are loaded, so I assume a problem with multiple Volume Groups, because a simple "ls" from within grub just shows Logical Volumes for Volume Group "vg", but not a single one of the second Volume Group "vg".
Is there a limitation in Grub2 for the number of supported Volume Groups? Does it only find the first created Volume Group? Is there a way to work around this limitation or is it a bug?