On 10/18/18 7:29 AM, Middelschulte, Leif wrote:
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.
I fear when using U-Boot he does not have the chance to use such a
sophisticated boot selection framework as barebox has ;)
But it would be worth making sure that the U-Boot scripts perform as expected.
For debugging, one can also take a look at the raw output of fw_printenv in
userspace
before and after performing mark-good to see if the variables changed according
to your expectation.
It could also help verifying if the variables look the same in U-Boot as they
do in userspace.
It seems that rauc status mark-active rootfs.0 is having some issue ?
Again, you might want to check rauc's logs on this.
Yes, should be really hard to say where the issue comes from with the current
information.
Another crucial information that we need: Which version of RAUC do you use?
Regards, Enrico
[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
--
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
