OpenWrt Forum Archive

Topic: Changeset #26245 (BusyBox blkid removal)

The content of this topic has been archived on 28 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello,

I'm having problems getting extroot to work if the extroot device is specified by UUID (if I specify it by device path it works fine). Originally I have posted that in the forum General Discussion forum, however now that it seems to be a bug in OpenWrt, I believe here is the right place to continue.

I've been doing some debugging and while I'm yet to confirm my theory after I'm back from work, it all sums up. I believe that the extroot by UUID support was broken by changeset #26245.

At the time when JFFS2 overlay is mounted on /tmp/overlay and /tmp/overlay/etc/config/fstab is scanned for the target extroot partition, the blkid command is used to determine which partition corresponds to the UUID specified by the user. The problem is, blkid is no longer included in the boot root filesystem so the attempt to read UUIDs of detected partition fails. And I was unable to find anything that would add /tmp/openwrt/sbin to the PATH variable so that blkid from JFFS2 can be used.

Is this all true or am I missing something? I'm not the only one with this problem (and none of the other people has ever got it solved) so I think I might be correct.

Today I'm going to confirm that the blkid command cannot be found and if yes, I will try setting PATH/LD_LIBRARY_PATH to see if blkid from the JFFS2 partition can be used instead.

In the meantime any input is most welcome. Thank you.

I was right. I have just submitted a patch to fix this.

The discussion might have continued from here.