They do wear out, mine in my Pinebook Pro was about a year old when I was seeing strange crashes. Loaded up a brand new SD card and I get uptimes of a week or more. And refomatting a misbehaving sd or emmc sometimes works wonders for ueexplainable reasons, it's like it needs to be refreshed periodically..
On 3/21/21, Jordon <open...@sirjorj.com> wrote: > The issue is not the sd card - it is the onboard emmc. I dd’ed the miniroot > image to a micro sd card. I the boot the bbb and run the installer. I set > the install drive to the onboard emmc drive and when it tries to write to > it, I get io errors. This used to work, as i had 5.6 on one of my bbb’s and > 5.8 on another, both booting without micro sd cards in them. > > I have received messages that suggest that this never worked, but I know I > did this years ago following a post from tedu’s website. > > And i did flash the debian ‘flasher’ image to the micro sd card, booted it, > and had it run through its reimaging process, and afterwards the bbb booted > debian just fine, so the micro sd card and the emmc are both functional. > > >> On Mar 20, 2021, at 14:52, Alan Corey <alan01...@gmail.com> wrote: >> >> man mount, then type /read-only to search, / to search for the same >> thing >> again. Sometimes a read-only mount happens if thare's something wrong. >> >> But reformat and try reloading before you throw it away. >> >>> On Sat, Mar 20, 2021, 3:30 PM Fred <open...@crowsons.com> wrote: >>> >>>> On 3/20/21 1:28 PM, Jordon wrote: >>>> I recently decided to play with my BBB boards after ignoring them for a >>> few years (one of them still had 5.6 installed on it!). I have 3 >>> BeagleBone Black boards (2 with 2GB, 1 with 4GB). When i dd’ed >>> miniroot-am335x-68.img to a uSD cards and booted it, it all seemed >>> pretty >>> normal until I got to the part where it actually writes to the onboard >>> storage. It would fail due to IO errors. This happened on all 3 of my >>> boards. I figured it was unlikely that all 3 would have bad flash so I >>> re-imaged one with with a supported debian distro and it worked just >>> fine. >>>> Is there an issue with writing to the onboard storage in 6.8 or is >>>> there >>> some step I missed in the startup phase to get it working? >>>> >>>> Thanks! >>>> >>>> >>> >>> with my BBB[1] I've never used the onboard storage I just boot the uSD >>> with OpenBSD on. The output from fdisk is shown below [2]. >>> >>> Cheers >>> >>> Fred >>> >>> [1] >>> bbb:fred ~> dmesg|head >>> OpenBSD 6.8 (GENERIC) #337: Wed Oct 7 01:35:49 MDT 2020 >>> dera...@armv7.openbsd.org:/usr/src/sys/arch/armv7/compile/GENERIC >>> real mem = 477290496 (455MB) >>> avail mem = 457314304 (436MB) >>> >>> [2] >>> bbb:fred ~> doas fdisk sd0 >>> doas (f...@bbb.crowsons.com) password: >>> Disk: sd0 geometry: 233/255/63 [3751936 Sectors] >>> Offset: 0 Signature: 0xAA55 >>> Starting Ending LBA Info: >>> #: id C H S - C H S [ start: size ] >>> >>> ------------------------------------------------------------------------------- >>> *0: 0C 0 1 1 - 8 254 63 [ 63: 144522 ] >>> FAT32L >>> 1: 83 9 0 1 - 232 254 63 [ 144585: 3598560 ] >>> Linux files* >>> 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] >>> unused >>> 3: 00 0 0 0 - 0 0 0 [ 0: 0 ] >>> unused >>> bbb:fred ~> doas fdisk sd1 >>> Disk: sd1 geometry: 966/255/63 [15523840 Sectors] >>> Offset: 0 Signature: 0xAA55 >>> Starting Ending LBA Info: >>> #: id C H S - C H S [ start: size ] >>> >>> ------------------------------------------------------------------------------- >>> *0: 0C 0 32 33 - 2 42 40 [ 2048: 32768 ] >>> FAT32L >>> 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] >>> unused >>> 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] >>> unused >>> 3: A6 2 42 41 - 966 80 10 [ 34816: 15489024 ] >>> OpenBSD >>> >>> > > -- ------------- Education is contagious.
