From: "Middelschulte, Leif" <Leif.Middelschulte@klsmartin.com>
To: "abhishekr@eximiusdesign.com" <abhishekr@eximiusdesign.com>,
"rauc@pengutronix.de" <rauc@pengutronix.de>
Subject: Re: [RAUC] Regarding booting problem ,when booting manually
Date: Thu, 18 Oct 2018 05:29:35 +0000 [thread overview]
Message-ID: <25a1ab58699c9c46783d4358039e1b2ce6de8f1c.camel@klsmartin.com> (raw)
In-Reply-To: <CALYWmf92CU3d5L1ySp10LXpjY+ztgB1g2kZZ2crYijMoFoY0tA@mail.gmail.com>
Hello Abhishek,
Am Donnerstag, den 18.10.2018, 10:46 +0530 schrieb Abhishek Kumar Rai:
> Hi Team,
>
> I am facing one issue after doing following steps:
> 1. flashing any image in appfs.
> 2. rauc status mark-active rootfs.0.(Activated rootfs.0)
Is this update considered successful by rauc? What do the logs say? If you're using systemd, you might want to check using `journalctl -u rauc`.
> 3. reboot
> It is booting from rootfs.1,instead of rootfs.0 which has been marked active.
If your update was indeed succesful, your boot target's `remaining_attempts` (see [0]) are 0.
>
> It seems that rauc status mark-active rootfs.0 is having some issue ?
Again, you might want to check rauc's logs on this.
[0] https://www.barebox.org/doc/latest/user/bootchooser.html#the-bootchooser-algorithm
BR,
Leif
>
> Please find system.conf content below
> {{{
> $ cat /etc/rauc/system.conf
> [system]
> compatible=eximius
> bootloader=uboot
> mountprefix=/mnt/rauc
> statusfile=/factory/rauc.status
>
> [keyring]
> path=cert.pem
>
> [slot.rootfs.0]
> #device=/dev/mmcblk1p1
> device=/dev/disk/by-path/platform-219c000.usdhc-part1
> type=ext4
> bootname=A
>
> [slot.rootfs.1]
> #device=/dev/mmcblk1p2
> device=/dev/disk/by-path/platform-219c000.usdhc-part2
> type=ext4
> bootname=B
>
> [slot.appfs.0]
> #device=/dev/mmcblk1p5
> device=/dev/disk/by-path/platform-219c000.usdhc-part5
> type=ext4
> bootname=app
> }}}
> Please provide your valuable input or suggestions on the above problem.
>
> Regards,
> Abhishek Rai
>
>
> 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.
> _______________________________________________
> RAUC mailing list
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2018-10-18 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 5:16 Abhishek Kumar Rai
2018-10-18 5:29 ` Middelschulte, Leif [this message]
2018-10-18 5:57 ` Enrico Joerns
2018-10-18 6:51 ` Abhishek Kumar Rai
2018-10-18 7:07 ` Abhishek Kumar Rai
2018-10-18 7:28 ` Enrico Joerns
2018-10-18 7:26 ` 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=25a1ab58699c9c46783d4358039e1b2ce6de8f1c.camel@klsmartin.com \
--to=leif.middelschulte@klsmartin.com \
--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