Hi Gautam,
The filesystem is ext4; the O/S is debian 8/jessie, the image is the
"officially released" BBB image from last spring
(bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz). To date we have not
modified any of the kernel startup scripts, save for setting a serial port
baud rate in /etc/r
ignal to the processor to initiate a shutdown. There is also
some sort of backup battery now planned to provide power during the
shutdown.
Dave
On Wednesday, December 6, 2017 at 12:59:08 PM UTC-5, minde...@gmail.com
wrote:
>
>
>
> On Wednesday, December 6, 2017 at 12:44:27 AM
u?
Dave
On Wednesday, December 6, 2017 at 9:33:09 AM UTC-5, ta...@thinnect.com
wrote:
>
> On Monday, December 4, 2017 at 11:30:32 PM UTC+2, Dave Barndt wrote:
>>
>> Hi,
>>
>> I'm hoping that someone has come across this problem before and can point
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
I apologize - I had tried to post this question an hour earlier but it
didn't seem to show up, but now it seems to have. So moderators, please
feel free to discard this question or the other one if no one's replied yet.
Sorry again,
Dave
On Monday, December 4, 2017 at 4:30:32 PM U
Hi,
I'm hoping that someone has come across this problem before and can point
me in the right direction.
I'm trying to troubleshoot a BeagleBone Black with Debian 8 that appears to
have a filesystem corruption. The system has two partitions, a read-only
rootfs partition and a writable partitio
Hi,
I'm hoping someone has encountered this before and can provide some
guidance. I'm troubleshooting a BeagleBone Black system that has two
partitions, a read-only rootfs partition and a writable partition for
everything else. When it boots, U-Boot completes and hands control to the
kernel, w
