On Thu, 17 Mar 2022 20:08:55 -0700 Marc MERLIN <marc@xxxxxxxxxxx> wrote: > old drive: > Device Model: ST6000VN0041-2EL11C > Serial Number: ZA18WX4T > LU WWN Device Id: 5 000c50 0a47d527a > Firmware Version: SC61 > User Capacity: 6,001,175,126,016 bytes [6.00 TB] > Sector Sizes: 512 bytes logical, 4096 bytes physical > > 8 128 5860522584 sdi > 8 129 5860521543 sdi1 > > > new drive: > Device Model: ST6000VN001-2BB186 > Serial Number: ZR118A1Y > LU WWN Device Id: 5 000c50 0dba1b3c0 > Firmware Version: SC60 > User Capacity: 6,001,175,126,016 bytes [6.00 TB] > Sector Sizes: 512 bytes logical, 4096 bytes physical > > 8 160 5860522580 sdk > 8 161 5860521536 sdk1 > > New drive is 4 sectors shorter, so I assume I can't use it as a replacement in my md5 > array because it's 4 sectors too short, or does swraid5 not need the last few sectors > of a drive? > > Looks like formatting as MDR won't help, I'm still 4 sectors short. Check "Used Dev Size" in "mdadm --detail" of your array. I suppose that is how much (at least) it actually needs from any new member to be suitable for the array. If you find it needs more than the size of sdk1, as an emergency measure you could wipe off the partition table and add the entire sdk as the array member. While usually not recommended, if you don't boot other operating systems on the same machine (that could see the "raw" drive and mess with it), it should not cause any problem. However there should not be such size difference in the first place, check your dmesg if drive detection messages report "HPA", and/or check with "hdparm -N" if there's this HPA enabled, cutting off a portion of the drive at the end. -- With respect, Roman
