mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: Abhishek Kumar Rai <abhishekr@eximiusdesign.com>
Cc: rauc@pengutronix.de
Subject: Re: [RAUC] Issues when executing rauc ,while booting from usb
Date: Tue, 6 Nov 2018 10:57:41 +0100	[thread overview]
Message-ID: <5cc35974-aa76-dcf8-63f8-a303c1714b32@pengutronix.de> (raw)
In-Reply-To: <CALYWmf8NMouNvOXpZm_XA87vOo_j7y+jE3z5wDPrpJEAmU1QBA@mail.gmail.com>

Hi Abhishek,

I fear I left this mail uncommented..

On 10/23/18 11:16 AM, Abhishek Kumar Rai wrote:
> 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

In USB boot, PARTUUID is 00000000 and realpath won't work for this. You need to set a valid disk id in your USB MBR in order to make this work.

> _*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

Your logs show that there are definitely no /dev/disk/by-partuuid-symlinks for the USB stick (and thus that realpath does not work for USB; as you can see there are only mmc-symlinks).
Of course your eMMC is still fine, but you do not boot from it.

> 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

Yes, RAUC needs to detect where it is booted from to operate safely.

One option is to obtain this info from the root= by finding the appropriate root device.
Another (actually the preferred) option of identifying the booted device in RAUC is to pass this information explictily from the bootloader via kernel command line arg 'rauc.slot=<bootname>'.

> _*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:~#

Ok, this works fine as expected :)


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 |


_______________________________________________
RAUC mailing list

      reply	other threads:[~2018-11-06  9:57 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
2018-11-06  9:57     ` Enrico Joerns [this message]

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=5cc35974-aa76-dcf8-63f8-a303c1714b32@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=abhishekr@eximiusdesign.com \
    --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