Here I am again. After I spent two days setting the CM board work, I found a fatal problem that I cannot solve it. After I setting the CM board up, flashing the OS in, every time I try to write something to the file system, such as sudo apt-get install something, it shows the EXT4-fs error. Just like the image below shows.
Code: Select all
EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4862: Journal has aborted
E: Read error - read (5: Input/output/ error)
journal commit I/O error
EXT4-fs error (device mmcblk0p2) in ext4_dirty_inode:4981: Journal has aborted
EXT4-fs error (device mmcblk0p2) : ext4_journal_check_start:56: Detected aborted journal
EXT4-fs (mmcblk0p2): Remounting filesystem read-onlyAnd sometimes, when it boots up, the same problem comes up.
I have tried a few solutions I found in Google.
1. Flash other OS version into the CM board. Yes, I have flashed three image I download from http://downloads.raspberrypi.org/raspbian/images/ but each of them has the EXT4-fs error when I try to sudo apt-get install.
2. When the EXT4-fs error came up, I connect it to other pi and tried to fix it by fsck.
Code: Select all
pi@raspberrypi ~/tools/usbboot $ sudo fsck /dev/sda1
fsck from util-linux 2.20.1
dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
? 1
Leaving file system unchanged.
/dev/sda1: 20 files, 1248/7161 clustersIt says that it found a dirty bit in sda1. Then I type
and it seems to had removed the dirty bit. Then I powered up the CM board and try install something, the same problem happened again.
3. Change the SD card. This is the most common solution I found on the forum. But obviously, I cannot change the eMMC on the CM board.
I really don’t know how to fix it. Could anyone help me?
Thanks to the help from ShiftPlusOne and rpdom!!! It is all about the power supply. I was going to connect the CM board to another pi for flashing the image, but I connect the line to power slug by error. And I thought, why not try to boot and install something? Then I try apt-get install, everything goes well!!! No more EXT4-fs error!!!!
Damed official power connector!!
by Vlad Turiceanu
Passionate about technology, Windows, and everything that has a power button, he spent most of his time developing new skills and learning more about the tech world. Coming… read more
Updated on March 4, 2021
- Error EXT4-fs is one frequent, but a vague, issue that can occur on Raspberry Pi devices.
- There is no clear fix for it, but we’re trying to explore some options in the following article.
- If you have any other issues with your Raspberry Pi, visit our Raspberry Pi errors Hub.
- We have a lot of useful guides in our Developer Tools section, so you should check it out.
XINSTALL BY CLICKING THE DOWNLOAD FILE
This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:
- Download DriverFix (verified download file).
- Click Start Scan to find all problematic drivers.
- Click Update Drivers to get new versions and avoid system malfunctionings.
- DriverFix has been downloaded by 0 readers this month.
There is little information on how to get around the most common errors on Raspberry Pi, even on forums or withing the Raspberry community.
One such error is EXT4-fs error, often followed by additional details such as bad extra_isize or reading directory_iblock, but other messages can appear as well.
Users have reported this error after using the device for a few hours, without changing anything, or right after installing the OS and upon trying to install other apps. Also, the error occurs on any PI model.
How do I fix the EXT4-fs error?
It was suggested that sometimes the error disappears when rebooting, but if it doesn’t, it means that there’s a problem with the external hardware, since a fault with the CM board would mean that the same error affects all users of the respective model.
Consequently, Raspberry Pi community followers suggest mainly two reasons: a corrupt SD card and an improper connection to the power source (including a faulty USB cable).
First of all, checking the power supply source is the simplest thing to do. But it is very important when the error appears.
If it occurs some right after first power on, checking again the cables and changing the power source/adapter should do the thing. If it happens sometime after booting, then you should check for another cause, most likely the SD card.
In this sense, many users warned about corrupted or fake SD cards, which might work for a while, but the damage the system. The only solution here is to change the card.
If you’re sure the card is reliable, you should try with another card, mounting a fresh image on it.
You can also use the fsck command hoping that it an correct any corrupted files, but, according to the forums, while it did correct some things, the users still could not use the device.
Any other solutions to the above-mentioned error are welcomed in the comments section below.
Newsletter
I am getting EXT4-FS error on Raspberry Pi 3 randomly. I am attaching a screenshot from the display here:.
After every restart it works normally for a few hours and then crashes. I am running latest version of Raspbian on it. Pi is powered through power adapter.
Any ideas why this happening? Is the SD card corrupt? I am not able to find this log in syslog.
Image Transcript
EXT4-fs error (device mmcblk0p7): __ext4_get_inode_loc:4043: inode #3736018: block 14684221: comm sshd: unable to read itable block
EXT4-fs error (device mmcblk0p7): ext4_wait_block_bitmap:500: comm kworker/u8:0: Cannot read block bitmap - block_group = 453, block_bitmap = 14680069
EXT4-fs (device mmcblk0p7): Delayed block allocation failed for inode 265846 at logical offset 97 with max blocks 1 with error 5
EXT4-fs error (device mmcblk0p7): ext4_journal_check_start:56: Detected aborted journal
EXT4-fs (device mmcblk0p7): Mounting filesystem read-only
EXT4-fs (device mmcblk0p7): This should not happen!! Data will be lost
EXT4-fs error (device mmcblk0p7) in ext4_writepages:2592: IO failure
EXT4-fs error (device mmcblk0p7): ext4_find_entry:1451: inode #131891: comm bash: reading directory lblock 0
(last message repeats several times)
asked Sep 29, 2016 at 10:25
0
The filesystem appears to be getting corrupted repeatedly, and from the sounds of things, that includes while the system is running and not just between boots, which is when it is most likely to occur if you pull the plug at the wrong time.
That should not happen. I would suspect a faulty or worn out SD card at that point. You may also want to check the physical reader on the Pi, if it is a model that uses a full size card the plastic holder can be easily broken without being noticed. The holders on all models can also become lose. However, the holder is most likely not the problem as I think that would cause a very drastic and mysterious failure (as opposed to just filesystem errors) and probably would not corrupt the card (but I could be wrong about that).
answered Sep 29, 2016 at 10:54
goldilocks♦goldilocks
57.3k17 gold badges111 silver badges225 bronze badges
3
I know this is an old thread but I had the same problem and I think I solved it by changing the adapter for the microSD card… maybe it helps someone else.
answered Jul 2, 2020 at 0:28
1
-
hrabeX
- Posts: 13
- Joined: Mon Apr 08, 2013 8:04 am
Memory Card write errors
I have problem with my Pi — every cca 2 hours Memory Card fals to read only mode.
dmesg:
[ 302.569535] EXT4-fs (mmcblk0p2): error count: 2
[ 302.569565] EXT4-fs (mmcblk0p2): initial error at 1365969698: ext4_remount:4584
[ 302.569581] EXT4-fs (mmcblk0p2): last error at 1365969735: ext4_remount:4584
[36046.897283] mmc0: Timeout waiting for hardware interrupt — cmd25.
[36046.901223] mmcblk0: error -110 transferring data, sector 170656, nr 24, cmd response 0x900, card status 0x0
[36046.901735] end_request: I/O error, dev mmcblk0, sector 170664
[36046.901757] end_request: I/O error, dev mmcblk0, sector 170672
[36046.911910] Aborting journal on device mmcblk0p2-8.
[36046.914573] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4550: Journal has aborted
[36047.476950] journal commit I/O error
[36047.492303] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[36047.492339] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[36047.496455] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[36048.136254] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4550: Journal has aborted
[36048.136400] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4550: Journal has aborted
Could anybody help me, please?
-
RaTTuS
- Posts: 10828
- Joined: Tue Nov 29, 2011 11:12 am
- Location: North West UK
Re: Memory Card write errors
Mon Apr 15, 2013 9:15 am
latest version ?
updated ? [sudo apt-get update && sudo apt-get upgrade -y]
tried another SD card?
what make and model of SD card ?
How To ask Questions :- http://www.catb.org/esr/faqs/smart-questions.html
WARNING — some parts of this post may be erroneous YMMV
1QC43qbL5FySu2Pi51vGqKqxy3UiJgukSX
Covfefe
-
hrabeX
- Posts: 13
- Joined: Mon Apr 08, 2013 8:04 am
Re: Memory Card write errors
Tue Apr 16, 2013 7:06 am
It seems, that xbian distro has overclocking enabled by default.
Thanks abishur for pointing it out!
-
abishur
- Posts: 4501
- Joined: Thu Jul 28, 2011 4:10 am
- Location: USA
Re: Memory Card write errors
Tue Apr 16, 2013 1:19 pm
hrabeX wrote:It seems, that xbian distro has overclocking enabled by default.
Thanks abishur for pointing it out!
I’d love to take credit for knowing that about xbian, but the truth is I did not know that 
So has lowering the overclock helped out any?
Dear forum: Play nice 
-
abishur
- Posts: 4501
- Joined: Thu Jul 28, 2011 4:10 am
- Location: USA
Re: Memory Card write errors
Wed Apr 17, 2013 1:12 pm
hrabeX wrote:default xbian 1.0 alpha 5 config.txt:
Code: Select all
arm_freq=840 core_freq=375 gpu_mem_256=128 gpu_mem_512=128 sdram_freq=400 over_voltage=0lowering core_freq to 300 solved the issue:
http://forum.xbian.org/thread-418.html
What are original values, please?
If by original values, you mean without overclocking, then if you deleted all those lines it default to it’s built in settings. Alternatively, if you remote into the pi so you can get to the bash prompt you can run
and there are options to enable or disable overclocking. You might be able to use one of the lower overclocking without any adverse side affects if you want to give it a shot.
Dear forum: Play nice
Return to “Troubleshooting”