fsck.ext3 -f /dev/sda2 Yes many times, it then recovers, boots up normally then a few errors later same error all over again.. :( -> loop fsck-error-fsck The worse thing is that I also since then forced that partition (root) to ext2 in the fstab but for some reason unknown to me it persists to wanting to commit to journal anyway even though the partition shows mounted ext2.. what do you think? > > error message: > > > > kernel: journal_bmap: journal block not found at offset 6924 on sd(8,2) > > kernel: Aborting journal on device sd(8,2). > > kernel: ext3_abort called. > > kernel: EXT3-fs abort (device sd(8,2)): > > ext3_journal_start: Detected aborted journal > > kernel: Remounting filesystem read-only > > > > any idea how we can recover from here? is there a way to rebuild an ext3 > > journal? > > Have you tried forcing a fsck of that filesystem? >
