mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Abhishek Kumar Rai <abhishekr@eximiusdesign.com>
To: ejo@pengutronix.de
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Issues when executing rauc ,while booting from usb
Date: Tue, 23 Oct 2018 14:46:37 +0530	[thread overview]
Message-ID: <CALYWmf8NMouNvOXpZm_XA87vOo_j7y+jE3z5wDPrpJEAmU1QBA@mail.gmail.com> (raw)
In-Reply-To: <4028e6f4-25a1-0030-955e-5c56a445334b@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 6099 bytes --]

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=ttymxc0,115200 root=PARTUUID=*1b325bba*-01
rootwait rw *rauc.slot=A* video=mxcfb0:dev=lcd,TRULY-WVGA,if=RGB24,rotate

=3 consoleblank=0 vt.global_cursor_default=0

*USB:*

Kernel command line: console=ttymxc0,115200 root=PARTUUID=*00000000*-01
rootwait rw video=mxcfb0:dev=lcd,TRULY-WVGA,if=RGB24,rotate=3 consolebl

ank=0 vt.global_cursor_default=0


*USB post-boot logs*

*root@test:~# mount*
/dev/sda1 on / type ext4 (rw,relatime,data=ordered)
...

...
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=ordered)
...

...
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=rootfs,
device=/dev/disk/by-path/platform-219c000.usdhc-part1, type=ext4, bootname=A
      state=booted, description=, parent=(none), mountpoint=(none)
      boot status=good
  rootfs.1: class=rootfs,
device=/dev/disk/by-path/platform-219c000.usdhc-part2, type=ext4, bootname=B
      state=inactive, description=, parent=(none), mountpoint=(none)
      boot status=bad

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  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
> trying 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 installation
> attempt below
> >
> > *root@test:~# /usr/bin/rauc --mount=/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=/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örns                |
> 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 |
>
>

-- 














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


attachments) may be confidential, proprietary, privileged, or 
otherwise


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


conveyed only to the designated recipient(s). Any use, dissemination, 



distribution, printing, retaining or copying of this e-mail (including 
its 


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


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


that you have received this e-mail in error, please notify the 
sender 


immediately (by replying to this e-mail), delete any and all 
copies of 


this e-mail (including any attachments) from your system, and 
do not


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






-- 
_This e-mail message (including any attachments) may be confidential, 
proprietary, privileged, or otherwise exempt from disclosure under 
applicable laws. If you are not an intended recipient, please delete this 
message. Thank you.
_

[-- Attachment #1.2: Type: text/html, Size: 16145 bytes --]

[-- Attachment #2: Type: text/plain, Size: 65 bytes --]

_______________________________________________
RAUC mailing list

  reply	other threads:[~2018-10-23  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 11:02 Abhishek Kumar Rai
2018-10-18 13:07 ` Enrico Joerns
2018-10-23  9:16   ` Abhishek Kumar Rai [this message]
2018-11-06  9:57     ` Enrico Joerns

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALYWmf8NMouNvOXpZm_XA87vOo_j7y+jE3z5wDPrpJEAmU1QBA@mail.gmail.com \
    --to=abhishekr@eximiusdesign.com \
    --cc=ejo@pengutronix.de \
    --cc=rauc@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox