Fix UBI volume names: resolve from mtdparts before ubi create

[widgetii]

Summary

The UBI volume name was resolved BEFORE ubi_partmap was populated from --mtdparts, so the first UBI partition always got the filename (mtd2) instead of the real partition name (rootfs). The kernel then couldn't find ubi0:rootfs and panicked with ENODEV (-19).

One-line fix: move vol_name = real_name to after mtdparts parsing.

Test result

Full 7-partition NAND restore on hi3516av200 with 4 UBI volumes — camera boots vendor firmware:

UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode ✓
UBIFS: mounted UBI device 4, volume 0, name "upgradefs" ✓
UBIFS: mounted UBI device 5, volume 0, name "appfs" ✓
UBIFS: mounted UBI device 6, volume 0, name "exdata" ✓
(none) login:   ✓

Command used:

defib restore -c hi3516av200 -i /tmp/restore_av200/ \
  -p /dev/uart-hi3516av200 \
  --uboot ~/git/u-boot-hi3519v101/u-boot-hi3516av200-universal.bin \
  --mtdparts "hinand:1M(boot),4M(kernel),8M(rootfs),16M(data),16M(upgradefs),64M(appfs),19M(exdata)" \
  --power-cycle

Test plan

• 326 tests pass, lint + mypy clean
• Full restore on hi3516av200 hardware: all partitions written, camera boots, UBIFS mounts

🤖 Generated with Claude Code