Busybox's fdisk calls warns on >2tb disks

[tlaurion]

4tb drive (>2tb) hits a limit. We need to replace fdisk usage with raw linux /sys or /proc output

Reported by user at https://matrix.to/#/!pAlHOfxQNPXOgFGTmo:matrix.org/$BBCUnUv-0D9IOgneYpNTMynCOz66O9Wrh792tVPmt-I?via=matrix.org&via=nitro.chat&via=envs.net

busybox's fdisk errors (warn; doesn't report !=0) on call and gives following output:

EDIT: I can't replicate bad behavior under Heads with emulated qcow2 disk of 4tb. I need more info/debug traces.

[tlaurion]

Opened https://bugs.busybox.net/show_bug.cgi?id=16276

[tlaurion]

fdisk throws a warning but is not throwing an error at me in testing done under #1884. From my current deep dive of busybox's fdisk code and Heads output parsing, I cannot make sense of reported issue from op matrix discussion. More information needed.

Modified OP.

[tlaurion]

Confirm that's stderr output that should be suppressed for oem factory reset/re-ownership tested under #1889

[tlaurion]

836af32 fixes this (will be merged with #1875 )

Before 836af32

After 836af32

Note that this was a warning all along as theorized/verified by code analysis above and never interfered with operations.
Also note that user never answered poke neither by PM nor in Heads channel.

Closing.