From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-io1-xd2e.google.com ([2607:f8b0:4864:20::d2e]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1gEsnz-000106-Am for rauc@pengutronix.de; Tue, 23 Oct 2018 11:16:53 +0200 Received: by mail-io1-xd2e.google.com with SMTP id a23-v6so406876iod.7 for ; Tue, 23 Oct 2018 02:16:51 -0700 (PDT) MIME-Version: 1.0 References: <4028e6f4-25a1-0030-955e-5c56a445334b@pengutronix.de> In-Reply-To: <4028e6f4-25a1-0030-955e-5c56a445334b@pengutronix.de> From: Abhishek Kumar Rai Date: Tue, 23 Oct 2018 14:46:37 +0530 Message-ID: Subject: Re: [RAUC] Issues when executing rauc ,while booting from usb List-Id: RAUC Project - Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0943448865==" Errors-To: rauc-bounces@pengutronix.de Sender: "RAUC" To: ejo@pengutronix.de Cc: rauc@pengutronix.de --===============0943448865== Content-Type: multipart/alternative; boundary="0000000000005995ab0578e1d481" --0000000000005995ab0578e1d481 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Enrico, Thanks for your prompt reply. For us the 'realpath' command is working fine. The devices do exist at the respective location. Below are the logs from our end for the post-boot scenario and the bootargs. It seems RAUC is trying to look for device ' 00000000-01' whereas the actual device is '1b325bba-01'. Is there a way we can configure RAUC in userspace to look for device 1b32bba-01 in place of 00000000-01? *Kernel bootargs* *MMC: * Kernel command line: console=3Dttymxc0,115200 root=3DPARTUUID=3D*1b325bba*-= 01 rootwait rw *rauc.slot=3DA* video=3Dmxcfb0:dev=3Dlcd,TRULY-WVGA,if=3DRGB24,= rotate =3D3 consoleblank=3D0 vt.global_cursor_default=3D0 *USB:* Kernel command line: console=3Dttymxc0,115200 root=3DPARTUUID=3D*00000000*-= 01 rootwait rw video=3Dmxcfb0:dev=3Dlcd,TRULY-WVGA,if=3DRGB24,rotate=3D3 conso= lebl ank=3D0 vt.global_cursor_default=3D0 *USB post-boot logs* *root@test:~# mount* /dev/sda1 on / type ext4 (rw,relatime,data=3Dordered) ... ... root@test:~# root@test:~# root@test:~# *root@test:~# ls /dev/disk/by-partuuid/** /dev/disk/by-partuuid/1b325bba-01 /dev/disk/by-partuuid/1b325bba-03 /dev/disk/by-partuuid/1b325bba-05 /dev/disk/by-partuuid/1b325bba-02 /dev/disk/by-partuuid/1b325bba-04 root@test:~# root@test:~# *root@test:~# realpath /dev/disk/by-partuuid/** /dev/mmcblk1p1 /dev/mmcblk1p2 /dev/mmcblk1p3 /dev/mmcblk1p4 /dev/mmcblk1p5 root@test:~# root@test:~# *root@test:~# rauc status* rauc-Message: Failed to resolve realpath for '/dev/disk/by-partuuid/ *00000000*-01' Failed to determine slot states: Did not find booted slot *MMC post-boot logs* *root@test:~# mount* /dev/mmcblk1p1 on / type ext4 (rw,relatime,data=3Dordered) ... ... root@test:~# ls /dev/disk/by-partuuid/* /dev/disk/by-partuuid/1b325bba-01 /dev/disk/by-partuuid/1b325bba-03 /dev/disk/by-partuuid/1b325bba-05 /dev/disk/by-partuuid/1b325bba-02 /dev/disk/by-partuuid/1b325bba-04 root@test:~# root@test:~# *root@test:~# realpath /dev/disk/by-partuuid/* * /dev/mmcblk1p1 /dev/mmcblk1p2 /dev/mmcblk1p3 /dev/mmcblk1p4 /dev/mmcblk1p5 root@test:~# root@test:~# root@test:~# root@test:~# *root@test:~# rauc status* Compatible: klondike-test Variant: (null) Booted from: A Activated: rootfs.0 slot states: rootfs.0: class=3Drootfs, device=3D/dev/disk/by-path/platform-219c000.usdhc-part1, type=3Dext4, bootn= ame=3DA state=3Dbooted, description=3D, parent=3D(none), mountpoint=3D(none) boot status=3Dgood rootfs.1: class=3Drootfs, device=3D/dev/disk/by-path/platform-219c000.usdhc-part2, type=3Dext4, bootn= ame=3DB state=3Dinactive, description=3D, parent=3D(none), mountpoint=3D(none= ) boot status=3Dbad root@test:~# Regards, Abhishek On Thu, Oct 18, 2018 at 6:37 PM Enrico Joerns wrote: > Hi Abhishek, > > On 10/18/18 1:02 PM, Abhishek Kumar Rai wrote: > > Hi Team, > > > > I am working on boot from a USB flash drive and try to flash the data > (rfs/appfs) to MMC partitions using RAUC. I am currently facing some > issues on the same. The same scenario works well when we boot from NFS an= d > try to flash the data to MMC partitions. > > > > By attempting to boot from a flash drive partition that has RAUC and > trying to install the bundle to MMC are we trying to do something that RA= UC > supports or are we missing something? > > > > Please find the related logs for USB flash drive based RAUC installatio= n > attempt below > > > > *root@test:~# /usr/bin/rauc --mount=3D/run/rauc service* > > *rauc-Message: Failed to resolve realpath for > '/dev/disk/by-partuuid/00000000-01'* > > rauc-Message: Failed to obtain name de.pengutronix.rauc > > root@test:~# > > root@test:~# > > root@test:~# > > *root@test:~# ps ax | grep rauc* > > 380 ? Ssl 0:00 /usr/bin/rauc --mount=3D/run/rauc service > > 392 ttymxc0 S+ 0:00 grep rauc > > root@test:~# > > root@test:~# > > *root@test:~# rauc status* > > *rauc-Message: Failed to resolve realpath for > '/dev/disk/by-partuuid/00000000-01'* > > Failed to determine slot states: Did not find booted slot > > Please provide your valuable suggestions and input on the same > > this all shows the same issue, RAUC cannot resolve the > /dev/disk/by-partuuid/00000000-01 symlink > to the actual device. What does > > ls -la /dev/disk/by-partuuid/00000000-01 > > give you? > > What RAUC tries is pretty much the same as > > realpath /dev/disk/by-partuuid/00000000-01 > > does this work calling manually? Maybe it's an issue that you do not have > a disk ID set. > > > Best regards, Enrico > > -- > Pengutronix e.K. | Enrico J=C3=B6rns = | > Industrial Linux Solutions | http://www.pengutronix.de/ = | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 = | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 = | > > --=20 The information contained in this e-mail message (including=20 any=C2=A0 attachments) may be confidential, proprietary, privileged, or=20 otherwise exempt from disclosure under applicable laws. It is intended to=20 be=C2=A0 conveyed only to the designated recipient(s). Any use, dissemination,=C2=A0 distribution, printing, retaining or copying of this e-mail (including=20 its=C2=A0 attachments) by unintended recipient(s) is strictly prohibited and=20 may=C2=A0 be unlawful. If you are not an intended recipient of this e-mail, or=20 believe=C2=A0 that you have received this e-mail in error, please notify the=20 sender=C2=A0 immediately (by replying to this e-mail), delete any and all=20 copies of=C2=A0 this e-mail (including any attachments) from your system, and=20 do not disclose the content of this e-mail to any other person. Thank you=20 for your cooperation. --=20 _This e-mail message (including any=C2=A0attachments) may be confidential,= =20 proprietary, privileged, or otherwise=C2=A0exempt from disclosure under=20 applicable laws. If you are not an intended recipient, please delete this= =20 message. Thank you. _ --0000000000005995ab0578e1d481 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Enrico,

Thanks for your p= rompt reply.


For us the 'realpath' command is working fin= e. The devices do exist at the respective location. Below are= the logs from our end for the post-boot scenario and the bootargs. = It seems RAUC is trying to look for device '<= span style=3D"background:rgb(255,153,153) none repeat scroll 0% 0%">= 00000000-01' whereas the actu= al device is '1b325bba-0= 1'. Is there a way we can confi= gure RAUC in userspace to look for device 1b32bba-01 in place of 00000000-01?


Kernel bootargs

MMC: <= br> Kernel command line: console=3Dttymxc0,115200 root=3DPARTUUID=3D1b325bba<= /b>-01 rootwait rw rauc.slot=3DA video=3Dmxcfb0:dev=3Dlcd,TRULY-WVGA,= if=3DRGB24,rotate

=3D3 consoleblank=3D= 0 vt.global_cursor_default=3D0

USB:

Kernel command line:= console=3Dttymxc0,115200 root=3DPARTUUID=3D00000000-01 rootwait rw v= ideo=3Dmxcfb0:dev=3Dlcd,TRULY-WVGA,if=3DRGB24,rotate=3D3 consolebl

ank=3D0 vt.global_cu= rsor_default=3D0


USB post-boot logs=

root@test:~# mount
/dev/sda= 1 on / type ext4 (rw,relatime,data=3Dordered)
...

...
root@test:~#
root@test:~#
root@test:~#
root@= test:~# ls /dev/disk/by-partuuid/*
/dev/disk/by-partuuid/1b325bba-01=C2=A0 /dev/disk/by-partuuid/1b325bba-03= =C2=A0 /dev/disk/by-partuuid/1b325bba-05
/dev/disk/by-partuuid/1b325bba-02=C2=A0 /dev/disk/by-partuuid/1b325bba-04 root@test:~#
root@test:~#
root@= test:~# realpath /dev/disk/by-partuuid/*
/dev/mmcblk1p1
/dev/mmcblk1p2
/dev/mmcblk1p3
/dev/mmcblk1p4
/dev/mmcblk1p5
root@test:~#
root@test:~#
root@= test:~# rauc status
rauc-M= essage: Failed to resolve realpath for '/dev/disk/by-partuuid/000000= 00-01'
Failed to determine slot states: Did not find booted slot


MMC post-boot logs

root@test:~# mount
/dev/mmc= blk1p1 on / type ext4 (rw,relatime,data=3Dordered)
...

..= .
root@test:~# ls /dev/disk/by-partuuid/*
/dev/disk/by-partuuid/1b325bba-01=C2=A0 /dev/disk/by-partuuid/1b325bba-03= =C2=A0 /dev/disk/by-partuuid/1b325bba-05
/dev/disk/by-partuuid/1b325bba-02=C2=A0 /dev/disk/by-partuuid/1b325bba-04 root@test:~#
root@test:~#
root@= test:~# realpath /dev/disk/by-partuuid/*=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0 =C2=A0
/dev/mmcblk1p1
/dev/mmcblk1p2
/dev/mmcblk1p3
/dev/mmcblk1p4
/dev/mmcblk1p5
root@test:~#
root@test:~#
root@test:~#
root@test:~#
root@= test:~# rauc status
Compatible:=C2=A0 klondike-test
Variant:=C2=A0=C2=A0=C2=A0=C2=A0 (null)
Booted from: A
Activated:=C2=A0=C2=A0 rootfs.0
slot states:
=C2=A0 rootfs.0: class=3Drootfs, device=3D/dev/disk/by-path/platform-219c00= 0.usdhc-part1, type=3Dext4, bootname=3DA
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 state=3Dbooted, description=3D, parent=3D(no= ne), mountpoint=3D(none)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 boot status=3Dgood
=C2=A0 rootfs.1: class=3Drootfs, device=3D/dev/disk/by-path/platform-219c00= 0.usdhc-part2, type=3Dext4, bootname=3DB
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 state=3Dinactive, description=3D, parent=3D(= none), mountpoint=3D(none)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 boot status=3Dbad

root@test:~#

Regards,

= Abhishek


On Thu, Oct 18, 2018 at 6:37 PM Enrico Joerns <ejo@pengutronix.de> wrote:
Hi Abhishek,

On 10/18/18 1:02 PM, Abhishek Kumar Rai wrote:
> Hi Team,
>
> I am working on boot from a USB flash drive and try to flash the data = (rfs/appfs) to MMC partitions using RAUC. I am=C2=A0 currently facing some = issues on the same. The same scenario works well when we boot from NFS and = try to flash the data to MMC partitions.
>
> By attempting to boot from a flash drive partition that has RAUC and t= rying to install the bundle to MMC are we trying to do something that RAUC = supports or are we missing something?
>
> Please find the related logs for USB flash drive based RAUC installati= on attempt below
>
> *root@test:~# /usr/bin/rauc --mount=3D/run/rauc service*
> *rauc-Message: Failed to resolve realpath for '/dev/disk/by-partuu= id/00000000-01'*
> rauc-Message: Failed to obtain name de.pengutronix.rauc
> root@test:~#
> root@test:~#
> root@test:~#
> *root@test:~# ps ax | grep rauc*
> 380 ?=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Ssl=C2=A0=C2=A0=C2=A0 = 0:00 /usr/bin/rauc --mount=3D/run/rauc service
> 392 ttymxc0=C2=A0 S+=C2=A0=C2=A0=C2=A0=C2=A0 0:00 grep rauc
> root@test:~#
> root@test:~#
> *root@test:~# rauc status*
> *rauc-Message: Failed to resolve realpath for '/dev/disk/by-partuu= id/00000000-01'*
> Failed to determine slot states: Did not find booted slot
> Please provide your valuable suggestions and input on the same

this all shows the same issue, RAUC cannot resolve the /dev/disk/by-partuui= d/00000000-01 symlink
to the actual device. What does

=C2=A0 =C2=A0ls -la /dev/disk/by-partuuid/00000000-01

give you?

What RAUC tries is pretty much the same as

=C2=A0 =C2=A0realpath /dev/disk/by-partuuid/00000000-01

does this work calling manually? Maybe it's an issue that you do not ha= ve a disk ID set.


Best regards, Enrico

--
Pengutronix e.K.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Enrico J=C3=B6rns=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |
Industrial Linux Solutions=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0| http://www.pengutronix.de/=C2=A0 |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |<= br> Amtsgericht Hildesheim, HRA 2686=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| = Fax:=C2=A0 =C2=A0+49-5121-206917-5555 |


The information contained in this e-mail message (including any=C2= =A0

attachments) may be confidential, proprietary, privileged, or othe= rwise

exempt from disclosure under applicable laws. It is intended to be= =C2=A0

conveyed only to the designated recipient(s). Any use, disseminati= on,=C2=A0

distribution, printing, retaining or copying of this e-mail (inclu= ding its=C2=A0

attachments) by unintended recipient(s) is strictly prohibited and= may=C2=A0

be unlawful. If you are not an intended recipient of this e-mail, = or believe=C2=A0

that you have received this e-mail in error, please notify the sen= der=C2=A0

immediately (by replying to this e-mail), delete any and all copie= s of=C2=A0

this e-mail (including any attachments) from your system, and do n= ot

disclose the content of this e-mail to any other person. Thank you= for your cooperation.

This e-mail message (including any=C2=A0attachments) may be= confidential, proprietary, privileged, or otherwise=C2=A0exempt from discl= osure under applicable laws. If you are not an intended recipient, please d= elete this message. Thank you.
--0000000000005995ab0578e1d481-- --===============0943448865== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUkFVQyBtYWls aW5nIGxpc3Q= --===============0943448865==--