Hi Phil/anyone this is useful for. So I think I made the same mistake as you (although maybe not, but it looks like it) - if you go to https://beagleboard.org/latest-images you'll see that there's the main distribution, but also ones that are specifically made to be flashed to the eMMC (for example in June-2020 its: https://debian.beagleboard.org/images/bone-eMMC-flasher-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz)
After installing this, rather than the *non-*eMMC-flasher version (ie. AM3358 Debian 10.3 2020-04-06 4GB SD IoT) - I had no problems with the read-only errors I was getting before. Clearly they made some changes for this image specifically for eMMC, and as Tarmo points out, eMMC should indeed be very reliable - so this makes sense. Would be interesting if this was indeed the issue for you or something else? On Wednesday, May 13, 2020 at 11:33:40 PM UTC+10, [email protected] wrote: > > Caveat: I'm an embedded veteran, but a first-time beagle-bone user. > (Purchased from Arrow) > > I'm having this problem that I can bring up my Blue using Cloud-9 and > things go great for a while. > Then, after a variable amount of time 10-30 minutes, the file system seems > to switch to read-only. > > I have connected to wifi and got my feet wet using online instructions, > and to bring up StrawsonDesigns Robotics cape. > My first sign of trouble was that the Blue went unresponsive on Cloud 9, > because it can't write to: > > /var/lib/cloud9/.c9/state.settings > > [image: ReadOnlyError2.jpg] > > > So, I did some research and could not find anyone else reporting this > issue lately. > > So in true nerd form, I tried again several different ways. > > My initial efforts had been using the built-in flash, so I spun up a new > bootable micro SD card and I was back up and running again. > > The first time the system went rogue it was during. an apt-get update > attempt. > > So I naturally tried again. > > Same result.. the update failed part way through with read only errors. > > So I tried again, spun up a new SD card and this time I did not do the > update. > > I cloned the StrawsonDesigns code base and was experimenting again (just > running the examples) and after a while I started getting read only file > system issues again. > > My next attempt at fixing the problem was to install a new eMMC image on > the board itself. > This went fine and I was back up and running again. > I experimented with the robotics cape code for a while, and then left the > Blue running on my desk. > > I came back 30 min later, and my FS was read-only again. > > I think I've considered most things I'm doing and can't figure out the > problem. I'm looking for help. > > - I'm running on USB power from a high-end powered USB hub > - Once the FS goes read-only I can still log in through the wi-fi > connection and run shell commands that do not need to write to files > - I have yet to write a single script or line of code, so I don't think > I'm causing the problem. > - The same problem occurs on internal or external drives. > - I'm not filling up the drive or anything like that > > df -h > Filesystem Size Used Avail Use% Mounted on > udev 215M 0 215M 0% /dev > tmpfs 49M 5.2M 44M 11% /run > /dev/mmcblk1p1 3.5G 1.9G 1.5G 57% / > tmpfs 242M 0 242M 0% /dev/shm > tmpfs 5.0M 0 5.0M 0% /run/lock > tmpfs 242M 0 242M 0% /sys/fs/cgroup > tmpfs 49M 0 49M 0% /run/user/1000 > > Kernel: 4.19.94-ti-r42 > BeagleBoard.org Debian Buster IoT Image 2020-04-06 > Debian: 10.3 > > Currently running on a: > MODEL_BB_BLUE > Robot Control library Version: > 1.0.4 > > Any suggestions??? > > Phil. > -- 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/292d8bc4-2c6f-4619-ac95-4bdf2ecc0a06o%40googlegroups.com.
