Disk size different in AFF and ASA system

[fiery coyote]

Has anyone found this difference?

[fiery coyote]

Another question，can I add a disk to a pod manually in ASA R2 ?

[unborn peak]

since ASA R2 uses the disks in a completely different manner (Storage Pods), a small difference is certainly not unexpected. I haven't checked it yet but I guess they finally got rid of the old "partitions" reserved for the kernel, drivers etc.
If you want you can try a node run ... label examinev1 0n.0 in diag mode and look at the "filesystem" start and end blocks, and compare those

[unborn peak]

not that I know of. The system should do that automagically. If it doesn't, I have found that a takeover/giveback should fix that

[stark gale]

Dont know if it's related to your case but there has been a bug where an incorrect size has been reported.

Will check if I can find the bug

[fiery coyote]

In my system,there are two spare disks,I only need one piece,so i want to increase capacity manually.

[fiery coyote]

Thanks

[stark gale]

This bug: https://mysupport.netapp.com/site/bugs-online/product/ONTAP/JiraNgage/CONTAP-533245

Fixed in 9.17.1P7

the bug report shows different disk models but unsure what drives are really impacted by that bug

[stark gale]

Afaik you can't manually do that. Also it's not recommended to add a single disk. The docs say "The minimum number of drives you should add in a single procedure is six." (https://docs.netapp.com/us-en/asa-r2/administer/increase-storage-capacity.html#use-netapp-hardware-universe-to-prepare-for-installation-of-a-new-drive)

Check this KB regarding RAID requirements with ASAr2: https://kb.netapp.com/on-prem/ASAr2/ASAr2_KBs/What_are_the_RAID_requirements_for_ASA_r2

[fiery coyote]

Different situation，the same disk，in AFF and in ASA system，the size is different in the ‘sysconfig -a’ output.

[fiery coyote]

This is helpful，thanks

[stark gale]

So it's the same ONTAP version on both AFF and ASA?

[fiery coyote]

Yes,the same

[stark gale]

ok then I don't think it's that bug. I guess ASAr2 with their SAZ vs. Unified ONTAP with aggrs works differently here.
What ONTAP version and hardware models are these? We have hundreds of systems with our customers - I could check what disk sizes are reported if you like.

[unborn peak]

yeah I agree that Bug doesn't apply to your situation

[unborn peak]

thanks for repeating what I just wrote above 😛

[unborn peak]

again, try a takeover/giveback, in our tests, single stray disks were always picked up after a reboot and added to the pod/saz