... mobility grouping on. Total pages: 32480 [ 0.000000] Kernel command line: console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),-(rootfs) root=PARTUUID=00000000-01 rw rootwait [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 ...

... yes you are right -- but how does it work? I found this https://archlinuxarm.org/forum/viewtopic.php?f=58&t=9798&p=50505&hilit=PARTUUID#p50455 . Does this work on the recovery shell? rootfs=`mount | sed -n 's/^\([^ ]*\).* \/ .*/\1/p'` rootuuid=`blkid $rootfs | sed -n 's/^.*\(PARTUUID=\)\"\(.*\)\"$/\1\2/p'` ...

Hello all. I got it. My GFH works absolutely fine. First I tried to set the PARTUUID -- above mentioned by moonman. It is very simple to do this -- start gparted and check the option and commands for the PARTION. There you can create a random UUID for the PARTion ...

... fi; if run loadimage; then if env exists root; then echo root has been defined by user; else part uuid ${devtype} ${bootpart} uuid; setenv root PARTUUID=${uuid}; fi; run mainargs; if run loadfdt; then if run loadrd; then bootz ${loadaddr} ${rdaddr}:${filesize} ${fdtaddr}; else bootz ${loadaddr} ...

So obviously uBoot knows where (using either label/uuid or partuuid) he found the rootfs. Can uBoot pass this information to the kernel then? Again - just a thought...

... UUID="0cd00ea9-8374-44ff-8b5f-053260dfb796" TYPE="ext3" Can someone help me with this? I know that it may something to do with partuuid, but I spent a few hours trying to fix it and I still can't... EDIT: Just changed uEnv.txt to root=LABEL=myLabel Now it's ok

... and then your u-boot was flashed. I didn't make any changes apart from uEnv.txt included into the boot folder. I'm confused with uuid and partuuid stuff so eventually decided to use label instead. Changing label is simple and quick enough, so I can use various flashdrives and one backup ...

@summers Yes, label way works well and I think that I'll be using label rather than uuid or partuuid for the reasons I mentioned above. Thanks for quoting the command ls -l /dev/disk/by-partuuid/ though. Is there a way to change the partuuid on existing flashdrive? If ...

Right, but you have to first read partuuid, then edit uEnv.txt. Then when your flashdrive fails and you restore your backup image to another flashdrive, you have to do it again. Of course it's simple enough for most users, but it could be ...

... flash drive in front socket and you plug/unplug power plug - it does not boot, no green light on front panel I tried to change uEnv from label to PARTUUID - same story. Any advice? I'll solder back serial adapter to the pcb to investigate further, but only if necessary.