Glad you managed to get it to come up. Think the issue that often comes up with PARTUUID, is this is the UUID of the partition. So its a way of point to the partition through the partition table. Usually UUID is the id of the actualy filesystem in the partition ...

Whats strange is on my NSA325 I'm HDD MBR (dos) + PARTUID, and that boots fine. PARTUUID = disk UUID + "-" + two digit part number. So fidks shows the Disk identifier as : Disk identifier: 0x94a2dc27 Root is /dev/sda1 and has id: PARTUUID="94a2dc27-01" ...

... (when lilo could only access the start of HDD). 2) the kernel has many an varied ways of identifying the root file system, labels, UUID, PARTUUID, device. So as these two are so different, uboot boot directory, and kernel root fs, is why they get set up separately. As to can PARTUUID ...

So arch: Jun 07 10:29:37 alarm kernel: Kernel command line: cros_secure console=tty0 init=/sbin/init root=PARTUUID=5c500120-17cb-6145-bd8c-dc975a4f5fd8/PARTNROFF=1 rootwait rw noinitrd and Chrome 2017-06-06T22:46:32.247899+01:00 NOTICE kernel: [ 0.000000] Kernel command line: ...

... as its incompatible. But worth checking that you only end up with the new kernel and uboot. /boot/uEnv.txt you want looking something like: root=PARTUUID=94a2dc27-01 mtdparts=mtdparts=orion_nand:0xC0000(uboot),0x40000(uboot_env),0x80000(old_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) ...

... the root partition. You number ended in in 02 which corresponds to the second partition - so probably right. Yes should work with the device, but PARTUUID is more reliable, helps if other hardware plugged in, as device names can change, but not PARTUUID. Yes the instructions on NSA device don't ...

... at least I'm on both of those packages and on the 4.20 kernel. Then check /boot/uEnv.txt is correct. Mine has in it: root=PARTUUID=94a2dc27-01 where the UUID is got from blkid e.g. $ blkid /dev/sda1: UUID="9c66e1c4-d82b-4606-b686-f5bc6d42e9d9" TYPE="ext4" ...

... else setenv bootpart 1; fi part uuid ${devtype} ${devnum}:${bootpart} uuid setenv bootargs "console=tty0 console=${console} root=PARTUUID=${uuid} rw rootwait" if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /boot/zImage; then gpio set 54 echo fdt: ${fdtfile} if ...

OK on my NSA325 - which is similar to the NSA320 in /boot/uEnv.txt I have: root=PARTUUID=94a2dc27-01 mtdparts=mtdparts=orion_nand:0xC0000(uboot),0x40000(uboot_env),0x80000(old_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) ...

... root=PARTUUID=94a2dc27-01 rw rootwait And you can see the mtdpart - that is setting up where on the flash it draws the lines between the mtd partitions. ...