BeagleBone Black - Aborting journal on device mmcblk0p2-8

16 views
Skip to first unread message

Mone

unread,
Jan 28, 2018, 9:21:45 PM1/28/18
to BeagleBoard
Good Afternoon,

I am using an image file that is converting any file system into read only, which I understand, is basically corrupting file system. I flash the image on the SD card and run
sudo apt-get update && sudo apt-get install vim

This is giving the following error:

[  229.949699] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:742: gro  up 17, 86 clusters in bitmap, 0 in gd
[  229.962166] Aborting journal on device mmcblk0p2-8.
[  229.970955] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[  229.978290] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[  229.989936] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[  230.002606] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[  230.015247] EXT4-fs error (device mmcblk0p2) in ext4_ext_remove_space:2871: Journal has aborted
[  230.027309] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[  230.039636] EXT4-fs error (device mmcblk0p2) in ext4_ext_truncate:4354: Journal has aborted
[  230.051220] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[  230.063843] EXT4-fs error (device mmcblk0p2) in ext4_orphan_del:2704: Journal has aborted
[  230.075416] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
dpkg
: error processing archive /var/cache/apt/archives/python2.7_2.7.6-8ubuntu0.4_armhf.deb (--unpack):
 unable to securely remove
'//usr/share/doc/python2.7/ACKS.gz.dpkg-tmp': Read-only file system

Looking into /etc/fstab:

/dev/mmcblk0p2  /       auto    errors=remount-ro       0       1
/dev/mmcblk0p1  /boot/uboot     auto    defaults        0       1
# UNCONFIGURED FSTAB FOR BASE SYSTEM


I understand that changing 
errors=remount-ro
to
defaults
would solve the problem. Also, I know that fsck and reboot does solve the issue as well. However, I am more interested in getting to know the root cause of this issue. After reading posts online, I starting doing hardware checks. I am using smartmontools, however, SMART tool does not do health check for eMMC. Is there any way I can check the disk drive health? Also, any ideas/help towards troubleshooting would be greatly appreciated. Please let me know if I ma moving in the right path for troubleshooting the problem.

Thanks!
Reply all
Reply to author
Forward
0 new messages