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 super capacitor would be something.
Just curious as what sort of power event caused so much of problems? Is it
just a normal abrupt power failure or is it some kind of intermittent power
failure?
Thanks,
Gautam.
On Thursday, December 7, 2017 at 2:21:00 AM UTC+5:30, Dave Barndt wrote:
>
> 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, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Unattached inode 45
> Connect to /lost+found<y>? no
> Unattached inode 81
> Connect to /lost+found<y>? no
> Pass 5: Checking group summary information
> Block bitmap differences: +(96768--97021)
> Fix<y>? no
> Free blocks count wrong for group #2 (1174, counted=1428).
> Fix<y>? no
> Free blocks count wrong (1091090, counted=1091344).
> Fix<y>? no
>
> rootfs_var: ********** WARNING: Filesystem still has errors **********
>
>
> 5413 inodes used (1.43%, out of 378256)
> 20 non-contiguous files (0.4%)
> 2 non-contiguous directories (0.0%)
> # of inodes with ind/dind/tind blocks: 0/0/0
> Extent depth histogram: 5389/10
> 419310 blocks used (27.76%, out of 1510400)
> 0 bad blocks
> 1 large file
>
> 3987 regular files
> 1408 directories
> 0 character device files
> 0 block device files
> 0 fifos
> 0 links
> 8 symbolic links (5 fast symbolic links)
> 1 socket
> ------------
> 5402 files
> root@bbb-dev:~#
>
> ------------------------------------------
>
> I did re-run this and fixed the errors, and then the system could boot
> again from the eMMC.
>
> If you look at the log I posted in the original note, yes, I did
> eventually lose ("hang") the serial console terminal session once the fsck
> failed. I couldn't see it waiting for any confirmation, nor did I ever get
> to some sort of console or login prompt.
>
> And yes, this is going into an actual product. Our H/W folks are looking
> at building a circuit that will watch for power failure (or an external
> power button push) and assert the line that the BBB power button currently
> does, to send a signal to the processor to initiate a shutdown. There is
> also some sort of backup battery now planned to provide power during the
> shutdown.
>
> Dave
>
>
--
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/1aeed237-15cc-470a-8957-ab1902613280%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
