maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N900 (https://talk.maemo.org/forumdisplay.php?f=44)
-   -   Broken ext3 journal - Read-Only /home (https://talk.maemo.org/showthread.php?t=70864)

quanttrom 2011-03-09 16:57
Broken ext3 journal - Read-Only /home
 
so I am facing a weird issue after an unwanted reboot:

Code:
[  29.197082] journal_bmap: journal block not found at offset 12 on mmcblk0p2
[  29.197113] Aborting journal on device mmcblk0p2.
[  30.251464] ext3_abort called.
[  30.251495] EXT3-fs error (device mmcblk0p2): ext3_journal_start_sb: Detected aborted journal
My understanding is that the journal is broken, I need to "nuke" it, delete it, w/e and recreate it.

Am I correct?

Any help is appreciated.

michaaa62 2011-03-09 19:36
Re: Broken ext3 journal - Read-Only /home
 
Do not do this manually!
Let fsck take care of things.
Best scenario: You have BackupMenu installed and you have a Debian- or Ubuntu-PC or -Live-CD at hand: Start your N900 with the keyboard out, type 'w' to export the internal microSD to your PC read/write. Then run fsck from the PC on your second partition of the N900.
You could also try to fsck from BackupMenu, but i had no success with that (but did not try it recently).

quanttrom 2011-03-09 20:58
Re: Broken ext3 journal - Read-Only /home
 
It must be my lucky day since I have all those available at my disposal !!!

quanttrom 2011-03-09 21:17
Re: Broken ext3 journal - Read-Only /home
 
Nope, didn't work.

I tried using fsck.ext3 on both a ubuntu machine with the method you described. It supposedly repaired the filesystem but no luck.

I also logged into BackupMenu through the console option and executed the fsck from there as well. It reportedly fixes the problem as well but when I reboot and the filesystem is still mounted as root only because the journal block cannot be found.

Any other ideas?

wmarone 2011-03-09 21:33
Re: Broken ext3 journal - Read-Only /home
 
Quick question, are you using Power Kernel and if so what speed do you have your processor running at?

quanttrom 2011-03-09 21:37
Re: Broken ext3 journal - Read-Only /home
 
Power Kernel but currently not overclocked.

quanttrom 2011-03-09 22:03
Re: Broken ext3 journal - Read-Only /home
 
Finally fixed it !!

fsck alone did not fix the problem. I had to:

Code:
running fsck
tune2fs -O ^has_journal
tune2fs -j
re-reran fsck

maurochiado 2013-09-06 08:41
Re: Broken ext3 journal - Read-Only /home
 
Hello everyone,

I'd like to revive this thread to ask some info.
After the last update I received (busybox), I got a corrupted /home (mmcblk0p2). I get the same type of errors in dmesg:

Code:
Nokia-N900-42-11:~# dmesg | grep error
[    2.702301] onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
[  20.503662] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
[  27.489013] journal_bmap: journal block not found at offset 12 on mmcblk0p2
[  27.489044] Aborting journal on device mmcblk0p2.
[  27.499572] __journal_remove_journal_head: freeing b_committed_data
[  28.321105] ext3_abort called.
[  28.321136] EXT3-fs error (device mmcblk0p2): ext3_journal_start_sb: Detected aborted journal
[  28.321166] Remounting filesystem read-only

[  28.823242] EXT3-fs error (device mmcblk0p2): ext3_journal_start_sb: Detected aborted journal
The solution proposed in the last post didn't work. Here are the answers:

Code:
Nokia-N900-42-11:~# tune2fs -O ^has_journal /dev/mmcblk0p2
tune2fs 1.41.3.maemo0 (12-Oct-2008)
The needs_recovery flag is set.  Please run e2fsck before clearing
the has_journal flag.
Nokia-N900-42-11:~#

Nokia-N900-42-11:~# tune2fs -j /dev/mmcblk0p2
tune2fs 1.41.3.maemo0 (12-Oct-2008)
The filesystem already has a journal.
Nokia-N900-42-11:~#
I read somewhere I could get a fsck on boot. Here is the dumpe2fs:

Code:
Nokia-N900-42-11:~# dumpe2fs -h /dev/mmcblk0p2
dumpe2fs 1.41.3.maemo0 (12-Oct-2008)
Filesystem volume name:  RX-51_2009SE_1.2
Last mounted on:          <not available>
Filesystem UUID:          a5361279-079d-43dd-988e-dd73c7e61882
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:        unsigned_directory_hash
Default mount options:    (none)
Filesystem state:        clean with errors
Errors behavior:          Continue
Filesystem OS type:      Linux
Inode count:              131072
Block count:              524288
Reserved block count:    26214
Free blocks:              384775
Free inodes:              105782
First block:              0
Block size:              4096
Fragment size:            4096
Reserved GDT blocks:      127
Blocks per group:        32768
Fragments per group:      32768
Inodes per group:        8192
Inode blocks per group:  512
Filesystem created:      Thu Jan  1 01:00:02 1970
Last mount time:          Thu Sep  5 21:14:39 2013
Last write time:          Thu Sep  5 21:14:39 2013
Mount count:              75
Maximum mount count:      1
Last checked:            Tue Jul  2 09:04:03 2013
Check interval:          86400 (1 day)
Next check after:        Wed Jul  3 09:04:03 2013
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:    28
Desired extra isize:      28
Journal inode:            8
Default directory hash:  half_md4
Directory Hash Seed:      56b9927d-a890-419f-92e3-d561bf20d9ed
Journal backup:          inode blocks
Journal size:            4112k

I set the check time with the following commands:

Code:
Nokia-N900-42-11:~# tune2fs -c 1 /dev/mmcblk0p2
tune2fs 1.41.3.maemo0 (12-Oct-2008)
Setting maximal mount count to 1
Nokia-N900-42-11:~#

Nokia-N900-42-11:~# tune2fs -i 1d /dev/mmcblk0p2
tune2fs 1.41.3.maemo0 (12-Oct-2008)
Setting interval between checks to 86400 seconds
Nokia-N900-42-11:~#
I restarted the device a number of time but the "Last checked" value does not change.

1rst question
What values should I use? Is the automatic fsck at boot even supposed to be performed on a corrupted partition?

2nd question
running a fsck on a mounted filesystem could break it:

Code:
Nokia-N900-42-11:~# fsck /dev/mmcblk0p2
fsck 1.41.3.maemo0 (12-Oct-2008)
e2fsck 1.41.3.maemo0 (12-Oct-2008)
/dev/mmcblk0p2 is mounted.

WARNING!!!  Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? no

check aborted.
Nokia-N900-42-11:~#
How would this happen? Is there any way to kill almost any process to prevent any write, and perform the fsck, albeit with risk?

Thank you!


All times are GMT. The time now is 16:23.

vBulletin® Version 3.8.8