On Saturday, December 9, 2017 at 1:47:29 AM UTC+5:30, Dennis Lee Bieber
wrote:
>
>
> Prior to a lay-off, my last four years were avionics --
> fortunately
> mostly maintenance work for existing software (since my prior 30 years
> experience qualified as "mainframe number crunching",
On Friday, December 8, 2017 at 9:05:02 PM UTC+5:30, Dennis Lee Bieber wrote:
>
> On Thu, 7 Dec 2017 19:17:09 -0800 (PST),
> minde...@gmail.com declaimed the
> following:
>
> > I too have a similar problem but not have worked directly on the
> problem.
> >This is in medical devices where
On Wednesday, December 6, 2017 at 10:40:11 PM UTC+2, Dave Barndt wrote:
>
> Does anything there look strange to you?
>
Can't say it does. Your /var/ file system is writable and gets corrupted -
this is expected. fsck failing to run is unexpected.
Looks like systemd has taken over the
Hi Dave,
I too have a similar problem but not have worked directly on the problem.
This is in medical devices where the instruments power is pulled off
abruptly without shutting down. Also the wear and tear of the eMMC and
detection of errors etc. The problems become much more serious and I
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
Hi Dave,
As you said not unusual but I am not sure. As in the earlier post it is
better not to have fsck ask for confirmation. I feel there is some problem
in the scripts which might have failed and not in the fsck. What is the
filesystem type here?
A battery backup maybe in the form of a
Hi Gautam,
As you requested, here's the output from running fsck on the writable
partition after booting/running from the SD card. Nothing that truly
unusual I don't think?
root@bbb-dev:~# fsck -f -v /dev/mmcblk1p2
fsck from util-linux 2.25.2
e2fsck 1.43 (17-May-2016)
Pass 1: Checking inodes,
Hi Tarmo,
Thanks for the reply! And we are considering doing something like you're
suggesting - adding fsck options to the kernel to do automatic repairs
during startup when possible. Thanks for that.
/etc/fstab just has a few entries. Two partitions and then directories
bound within the
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
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
> me in the right direction.
>
> I'm trying to troubleshoot a BeagleBone Black with Debian 8 that appears
> to have a filesystem corruption.
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
On Tuesday, December 5, 2017 at 3:00:32 AM UTC+5:30, Dave Barndt wrote:
>
> 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
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 UTC-5, Dave
13 matches
Mail list logo
