On 18/09/16 19:41, Benjammin2068 wrote: > I'll check - this is CentOS... but I've (as shown in followup email) played with fdisk (which doesn't bother me) and some of the others... > > now I just have to sort out this offset issue which I think I'm stuck with due to different partition sizes. Don't quite understand what you're trying to do, but ... I'm sure you know this, but getting the physical/logical block size out-of-sync hurts disk performance. And copying a smaller partition into a larger allocated space is perfectly harmless. So... I'd simply use a modern partition manager (such as gdisk) to partition your new drives such that the new partitions are larger than the existing ones, and are properly aligned relative to the drive geometry. Then copy the old partitions across however you were planning - whether it's "mdadm --replace" or stopping the array and "dd old-device new-device" or whatever. If you've got a bit of wasted space, or whatever, who cares. You can resize your file-systems to use all available space, if you wish (can't remember how, whenever I've done that sort of stuff it hasn't been hard). But I'd certainly try and avoid those offset warnings - it smacks to me of a mismatch between 512-byte blocks and 4K disk sectors, and I wouldn't want the drive firmware messing about correcting mismatches between OS 4K blocks and drive 4K blocks. I don't fully understand it but I know there was a lot of grief with exactly this sort of thing in the transition from 512-byte to 4K. Cheers, Wol -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
