On Wednesday, December 6, 2017 at 12:44:27 AM UTC+5:30, Dave Barndt wrote: > > Hi Gautam, > > Thanks for the reply! I actually had the same idea last night, and did > manage to boot the board using an image on an SD card, and was able to run > the fsck from there against the bad partition on the eMMC, and saw the > details of the corruption. I was able to repair the partition and > ultimately reflashed the board. So thanks for the reply and the > confirmation! > > But, what I'm still baffled about is: *Why the fsck couldn't run as part > of the kernel startup when the system was booted normally?* I assume the > partition hasn't been mounted at that point yet, so why would the fsck fail > to start? It's really just more of an understanding-type of question. > > Anyway, we 're now looking at ways to prevent sudden or unexpected power > downs from potentially effecting such behavior/corruptions. Found this > reference which looks pretty helpful: > https://www.embeddedarm.com/about/resource/preventing-filesystem-corruption-in-embedded-linux > > ... and the BBB has power down signalling (section 5.10 of the ref manual) > that we take advantage of as well. > > Thanks again! > > Dave > > Hi Dave,
Could you please let me know what the corruption was once you ran fsck from the SD card? I am interested to the see what the corruption was. In case of fsck failure on startup did you lose your tty terminal once the fsck started? Due to this was it waiting for some confirmation or had it just started and you lost the output messages? Is this for something which will go into an actual product and is the requirement to have a robust FS during power failure? Thanks, Gautam. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/2a531a4e-e74d-44ed-a7e6-0683b5a9e983%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
