Often, when I build a new kernel (I build every new stable version.), I get a journal error on the non-boot disk (there's no journal on the boot disk.)
Quote:
|
EXT4-fs error (device sda2): ext4_journal_check_start:61: Detected aborted journal
|
,
before I boot to the new kernel. This error makes it impossible to write to sda2. I boot with
. e2fsck turns up no errors, the computer works properly until the next time I build a kernel. The kernel and its code are on sda1. It's as though the kernel has a new journaling protocol, objects to the old one. I know that's not happening.
