sysupgrade not preserving backup

[Philip Prindeville]

Hi,

I’m running on a Xeon-D supermicro (a SYS-5018D-FN8T) with NVMe as my filesystem.

When I updated, my configuration was reset to factory default (good thing I had a backup tucked away).  At first I thought it was because I had added a partition to my disk trying to pivot to a persistent /var partition, and it was a side-effect of “-p”.

But then I retried it without “-p” after restoring my configuration, and it still failed to preserve the configuration.

I’m at 5175d0a6230.

Also, had a question about why the partitioning of NVMe is different:

root at OpenWrt:~# sfdisk -d /dev/nvme0n1
GPT PMBR size mismatch (2095647 != 1000215215) will be corrected by write.
The backup GPT table is not on the end of the device.
label: gpt
label-id: 2DFF005F-38AC-3ED4-6780-523554859E00
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 2095615
sector-size: 512

/dev/nvme0n1p1 : start=         512, size=       40960, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=2DFF005F-38AC-3ED4-6780-523554859E01, attrs="LegacyBIOSBootable"
/dev/nvme0n1p2 : start=       41472, size=     2054144, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=2DFF005F-38AC-3ED4-6780-523554859E02
/dev/nvme0n1p128 : start=          34, size=         478, type=21686148-6449-6E6F-744E-656564454649, uuid=2DFF005F-38AC-3ED4-6780-523554859E80
root at OpenWrt:~# 

Not sure why the partitions are out-of-order.  It makes adding a new partition that uses the rest of the disk difficult.  Should I reorder the partitions?  Because “-p” isn’t preserving my partition table either.

So I lose the configuration and the partition table.

I’ll order an SSD drive and see if the problem goes away.  But it would be nice to be able to use the NVMe sticks I have lying around.

Thanks,

-Philip