Niklas Gollenstede

Very cool, thank you for the work you put into this as well!

Thanks for your reply! It's been a while since I posted this, and even longer since I wrote the code, so apologies if I miss something: Do such checks exist for (-)j / --move-main-table=sector? If so (and I missed to copy/adjust them), then that's what should be done, yes. If not, then: is moving the backup table more obscure / causing more potential harm than moving the main table? Either way gdisk reports the limited range "usable sectors" (and moving either table does require entering the expert...

Thanks for your reply! It's been a while since I posted this, and even longer since I wrote the code, so apologies if I miss something: Do such checks exist for (-)j / --move-main-table=sector? If so (and I missed to copy/adjust them), then that's what should be done, yes. If not, then: is moving the backup table more obscure / causing more potential harm than moving the main table? Either way gdisk reports the limited range "usable sectors" (and moving either table does require entering the expert...

implement k/--move-backup-table/MoveSecondTable