<div dir="ltr">Greetings,<div><br></div><div>Using the latest BBB image from the snappy developers site:</div><div class="gmail_extra"> <p><span><i>(BeagleBoneBlack)ubuntu@localhost:/etc$ sudo cat fstab |grep boot</i></span></p> <p><i><span>/dev/mmcblk0p1 /</span><span>boot</span><span>/u</span><span>boot</span><span> auto sync 0 2</span></i></p> <p><span><i>(BeagleBoneBlack)ubuntu@localhost:/etc$ mount|grep boot</i></span></p> <p><i><span>/dev/mmcblk0p1 on /</span><span>boot</span><span>/u</span><span>boot</span><span> type vfat (rw,relatime,sync,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)</span></i></p></div><div class="gmail_extra"><br></div><div class="gmail_extra">However in our images (we change the kernel to provide support for capemgr kernel module) we are unable to get the "sync".</div><div class="gmail_extra"><br></div><div class="gmail_extra">Tried modifying "/etc/fstab" manually but everytime we reboot it returns to:</div><div class="gmail_extra"><i>/dev/mmcblk0p1 /boot/uboot auto defaults 0 0</i><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Any suggestion on how to include "sync"?</div><div class="gmail_extra">Thanks,</div><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><b>Víctor Mayoral Vilches</b><div>CTO & Co-Founder</div><div><br></div><div><img src="http://erlerobotics.com/blog/wp-content/uploads/2014/10/erle_corporativo_5.0_72px_nobackground.png" width="96" height="96"><br></div><div><br></div><div><b>Erle Robotics</b></div><div><a href="http://erlerobotics.com" target="_blank">erlerobotics.com</a> | <a href="mailto:victor@erlerobot.com" target="_blank">victor@erlerobot.com</a></div><div><a href="tel:%2B34%20616151561" value="+34616151561" target="_blank">+34 616151561</a><br></div><div><i>skype</i>: v.mayoral<br></div><div><br></div></div></div></div></div></div></div></div></div></div> <br><div class="gmail_quote">2015-04-29 0:27 GMT+02:00 Steve Langasek <span dir="ltr"><<a href="mailto:steve.langasek@canonical.com" target="_blank">steve.langasek@canonical.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi Gábor,<br> <span><br> On Tue, Apr 28, 2015 at 10:47:48PM +0200, Gábor Paller wrote:<br> > Why is the boot partition mounted writable to start with?<br> <br> </span>Because this is the place where we have a writable space shared between the<br> OS and the bootloader that we can use to tell whether a boot was successful.<br> Without this, it's impossible to implement automatic fallback on failed boot<br> because there's no way to know that a boot was attempted but failed.<br> <br> With a recent image, /boot should certainly be mounted 'sync' as mentioned.<br> If you're using the current 15.04 image and it's not, it's a bug. If it is<br> mounted 'sync' and you're still seeing corruption, that's a different bug.<br> <br> --<br> Steve Langasek Give me a lever long enough and a Free OS<br> Debian Developer to set it on, and I can move the world.<br> Ubuntu Developer <a href="http://www.debian.org/" target="_blank">http://www.debian.org/</a><br> <a href="mailto:slangasek@ubuntu.com" target="_blank">slangasek@ubuntu.com</a> <a href="mailto:vorlon@debian.org" target="_blank">vorlon@debian.org</a><br> <div><div><br> > On Tue, Apr 28, 2015 at 10:46 PM, John Lenton <<a href="mailto:john.lenton@canonical.com" target="_blank">john.lenton@canonical.com</a>><br> > wrote:<br> ><br> > > “defaults,sync” would do the same :) but what I meant was that AFAIK we've<br> > > switched to have the boot partitions be like that now. The people who<br> > > actually did this or would know without a doubt are in a week-long sprint<br> > > so hard to reach right now though.<br> > ><br> > > On 28 April 2015 at 21:43, Gábor Paller <<a href="mailto:gaborpaller@gmail.com" target="_blank">gaborpaller@gmail.com</a>> wrote:<br> > ><br> > >> John, is it enough to sync the boot partition? E.g. in /etc/fstab:<br> > >><br> > >> Before:<br> > >> /dev/mmcblk0p1 /boot/uboot auto defaults 0 2<br> > >> After:<br> > >> /dev/mmcblk0p1 /boot/uboot auto rw,suid,dev,exec,auto,nouser,sync 0 2<br> > >><br> > >> Is this what you have in mind?<br> > >><br> > >><br> > >> On Tue, Apr 28, 2015 at 9:56 PM, John Lenton <<a href="mailto:john.lenton@canonical.com" target="_blank">john.lenton@canonical.com</a>><br> > >> wrote:<br> > >><br> > >>> Víctor, are you still seeing this with the images that mount boot with<br> > >>> the "sync" option?<br> > >>><br> > >>> On 28 April 2015 at 19:31, Gábor Paller <<a href="mailto:gaborpaller@gmail.com" target="_blank">gaborpaller@gmail.com</a>> wrote:<br> > >>><br> > >>>> it also happened to me many times. ever since i started shutting down<br> > >>>> the system properly (shutdown -h now), the problem disappeared. it seems to<br> > >>>> be related to switching off the power unexpectedly (unexpectedly for the<br> > >>>> system).<br> > >>>><br> > >>>> regards,<br> > >>>> gabor<br> > >>>> On 28 Apr 2015 8:26 pm, "Víctor Mayoral Vilches" <<a href="mailto:victor@erlerobot.com" target="_blank">victor@erlerobot.com</a>><br> > >>>> wrote:<br> > >>>><br> > >>>>> Hi there,<br> > >>>>><br> > >>>>> At Erle Robotics we've been doing quite a bit of testing with Snappy<br> > >>>>> and we honestly love it.<br> > >>>>><br> > >>>>> Unfortunately the images get corrupted from time to time and that<br> > >>>>> makes it really troublesome. The reason seems to be related to a bad<br> </div></div>> >>>>> shutdown process where some files in the *system-boot* partition get<br> <span>> >>>>> corrupted (if not the whole partition itself). When dealing with drones we<br> > >>>>> connect and disconnect the batteries as needed thereby we constantly<br> > >>>>> reproduce this problem.<br> > >>>>><br> > >>>>> After the image goes wrong the only noticeable change is that the<br> </span>> >>>>> *system-boot* partition seems wrong. When booting with a corrupted<br> <span>> >>>>> image we get this behavior<br> </span>> >>>>> <<a href="https://gist.github.com/anonymous/ad19776c93eccd2d1d43" target="_blank">https://gist.github.com/anonymous/ad19776c93eccd2d1d43</a>> (it ends up<br> <span>> >>>>> switching into eMMC)<br> > >>>>><br> > >>>>> When inspecting the system-boot partition:<br> > >>>>><br> </span>> >>>>> *cat snappy-system.txt *<br> > >>>>> *cat: snappy-system.txt: Input/output error*<br> <span>> >>>>><br> > >>>>> And for some reason, the whole system-boot partition seems wrong since<br> > >>>>> there's no way to edit it (complains about permissions and read-only file<br> > >>>>> system, tested with root and tried also repairing the partition but it did<br> > >>>>> not help).<br> > >>>>><br> > >>>>> This is an issue that appeared a while ago and we hoped it'll get<br> > >>>>> solved eventually but keeps coming in newer images and many users might<br> > >>>>> have experienced it.<br> > >>>>><br> > >>>>> Has anyone looked into this? Help would be much appreciated.<br> > >>>>> Kind regards,<br> > >>>>><br> </span>> >>>>> *Víctor Mayoral Vilches*<br> > >>>>> CTO & Co-Founder<br> > >>>>><br> > >>>>><br> > >>>>><br> > >>>>> *Erle Robotics*<br> > >>>>> <a href="http://erlerobotics.com" target="_blank">erlerobotics.com</a> | <a href="mailto:victor@erlerobot.com" target="_blank">victor@erlerobot.com</a><br> > >>>>> <a href="tel:%2B34%20616151561" value="+34616151561" target="_blank">+34 616151561</a><br> > >>>>> *skype*: v.mayoral<br> <div><div>> >>>>><br> > >>>>><br> > >>>>> --<br> > >>>>> snappy-devel mailing list<br> > >>>>> <a href="mailto:snappy-devel@lists.ubuntu.com" target="_blank">snappy-devel@lists.ubuntu.com</a><br> > >>>>> Modify settings or unsubscribe at:<br> > >>>>> <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a><br> > >>>>><br> > >>>>><br> > >>>> --<br> > >>>> snappy-devel mailing list<br> > >>>> <a href="mailto:snappy-devel@lists.ubuntu.com" target="_blank">snappy-devel@lists.ubuntu.com</a><br> > >>>> Modify settings or unsubscribe at:<br> > >>>> <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a><br> > >>>><br> > >>>><br> > >>><br> > >><br> > ><br> <br> > --<br> > snappy-devel mailing list<br> > <a href="mailto:snappy-devel@lists.ubuntu.com" target="_blank">snappy-devel@lists.ubuntu.com</a><br> > Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a><br> <br> </div></div><br>--<br> snappy-devel mailing list<br> <a href="mailto:snappy-devel@lists.ubuntu.com" target="_blank">snappy-devel@lists.ubuntu.com</a><br> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a><br> <br></blockquote></div><br></div></div>