From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Message-ID: <7a2fc0a9cb6bb54455d4cb69403a469e2fe832d8.camel@pengutronix.de> From: Jan =?ISO-8859-1?Q?L=FCbbe?= Date: Thu, 25 Mar 2021 16:52:14 +0100 In-Reply-To: References: MIME-Version: 1.0 Subject: Re: [RAUC] Robust u-boot environment with RAUC List-Id: RAUC Project - Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rauc-bounces@pengutronix.de Sender: "RAUC" To: Einar Vading , "rauc@pengutronix.de" Hi, On Thu, 2021-03-25 at 15:22 +0000, Einar Vading wrote: > We have a Raspberry Pi 4 system set up using RAUC for updates and u-boot for > booting. For some systems in the field we have the u-boot environment on the > FAT boot partition and we mount that in fstab so that RAUC can access it with > the fw_print/setenv commands. > > One issue we have seen is that the env-file gets corrupted every now and then. > After corruption we can't RAUC update. The only solution we have to this > problem now is to delete the corrupted env-file and reboot, then we can > perform the upgrade. > > I have no idea how to track down whatever corrupts the file and I was > wondering if anyone has any input. You could try placing the environment on a separate partition to avoid any potential issues in the FAT implementation. Also, I think U-Boot has a way to support redundant environments. Regards, Jan -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ RAUC mailing list