Reply
Thread Tools Search this Thread
Posts: 36 | Thanked: 12 times | Joined on Aug 2010
#1
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.

Last edited by quanttrom; 03-09-2011 at 01:03 PM.
 
Posts: 1,763 | Thanked: 1,389 times | Joined on Sep 2008 @ Berlin, Germany
#2
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).
 
Posts: 36 | Thanked: 12 times | Joined on Aug 2010
#3
It must be my lucky day since I have all those available at my disposal !!!
 
Posts: 36 | Thanked: 12 times | Joined on Aug 2010
#4
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?
 
Posts: 1,746 | Thanked: 2,096 times | Joined on Sep 2009
#5
Quick question, are you using Power Kernel and if so what speed do you have your processor running at?

Last edited by wmarone; 03-09-2011 at 05:33 PM. Reason: com, ma
 
Posts: 36 | Thanked: 12 times | Joined on Aug 2010
#6
Power Kernel but currently not overclocked.
 
Posts: 36 | Thanked: 12 times | Joined on Aug 2010
#7
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
 
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

 
Forum Jump


All times are GMT -4. The time now is 08:03 PM.