Skip to first unread message

Sebastián Sáez

unread,
Oct 5, 2017, 9:38:57 AM10/5/17
to BeagleBoard
Hi,

I have used many beaglebones (BBGW) and there is one that has twice get this error at boot:

rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

I think this may be because the emmc is faulty.

Is there any script that allows emmc testing?


regards,
Sebastián

Sebastián Sáez

unread,
Oct 5, 2017, 9:55:44 AM10/5/17
to BeagleBoard
here the full log
 
rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/mmcblk1p1 requires a manual fsck
modprobe: module i8042 not found in modules.dep
modprobe: module ehci-orion not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
modprobe: module ohci-hcd not found in modules.dep

Robert Nelson

unread,
Oct 5, 2017, 9:57:06 AM10/5/17
to Beagle Board, Sebastián Sáez
No, this is normal... If you just yank power, consitently...

ext4 does have some safe guards for improper shutdowns. However if
you don't allow it to properly fix it up, eventually it'll get "too"
corrupted to automatically fix itself..

Regards,

--
Robert Nelson
https://rcn-ee.com/

Robert Nelson

unread,
Oct 5, 2017, 9:58:42 AM10/5/17
to Beagle Board, Sebastián Sáez
On Thu, Oct 5, 2017 at 8:55 AM, Sebastián Sáez <otr...@gmail.com> wrote:
> here the full log
>
>>
>> rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>> (i.e., without -a or -p options)
>> fsck exited with status code 4
>> The root filesystem on /dev/mmcblk1p1 requires a manual fsck
>> modprobe: module i8042 not found in modules.dep
>> modprobe: module ehci-orion not found in modules.dep
>> modprobe: module uhci-hcd not found in modules.dep
>> modprobe: module ohci-hcd not found in modules.dep

fsck.ext4 /dev/mmcblk1p1

Sebastián Sáez

unread,
Oct 5, 2017, 10:28:48 AM10/5/17
to Robert Nelson, Beagle Board
thank for the info :)
--
Sebastián

mjki...@gmail.com

unread,
Jun 27, 2018, 4:22:44 PM6/27/18
to BeagleBoard
What about these options?

https://andicelabs.com/2014/07/automatic-root-filesystem-repair-boot/


1) Edit  /boot/cmdline.txt with the option fsck.repair=yes

OR

2) Edit  /lib/init/vars.sh  file  and set FSCKFIX=yes


Should one of these work?   Or are you saying repeated use over time will eventually cause problems?


Regards, Mike

Reply all
Reply to author
Forward
0 new messages