3 thoughts on - Migrating To Nvme And Expand

• Are you using the MD devices as Physical Volumes ?If ues, then create a PV from that NVME and then pvmove. Best Regards,Strahil Nikolov

  On Wed, Mar 31, 2021 at 21:16, Jerry Geis wrote: I have older SATA disks (2 of them size 2T) in a software raid config running CentOS 7.

  /dev/md127 is / and xfs
  /dev/sda2 is swap
  /dev/md126 is /home and xfs

  I desire to get a new (single) NVME 4T disk.

  What is the correct way to copy the software raid to a single “new” NVME
  disk ?
  then expand the /home file system to All the remaining space?

  Thanks,

  Jerry

• PV from that NVME and then pvmove.

  more /proc/mdstat Personalities : [raid1]
  md126 : active raid1 sdb3[2] sda3[0]
  1866465280 blocks super 1.2 [2/2] [UU]
  bitmap: 4/14 pages [16KB], 65536KB chunk

  md127 : active raid1 sdb1[0] sda1[2]
  52461440 blocks super 1.0 [2/2] [UU]
  bitmap: 1/1 pages [4KB], 65536KB chunk

  This is the mdstat. the md126 just has /dev/sdb3 and /dev/sda3 – and md127 has the /dev/sdb1 and /dev/sda1

  Thanks

  Jerry

• So you are not using LVM and everything gets more complicated.

  For sure, you have to do the movement while booting from a rescue disk. Either you use some partition cloning/rearrangement tool (assuming they are able to cope with a RAID1 source) or you simply create new filesystems, format them and copy all the files over. I would go for the second option, and really use LVM on the NVMe and not assign all the space to /home because that is almost irreversible while gradual expansion is very easy to do later. Then, adjusting grub to use the NMVe is also necessary. And, of course, checking which drive the BIOS is set to boot from.

  This is all easily doable for experienced users, but in each step there is a chance to make bad errors.

  Regards.