Many thanks to Daniel Barbar for his help with this...
1. Unmount the filesystem:
# umount /boot
2. Run e2fsck:
# e2fsck /dev/hda1
3. Disable the journal on /boot:
# tune2fs -O ^has_journal /dev/hda1
4. Remount /boot with rw options:
# mount -t ext2 -o rw /dev/hda1 /boot
5. Change /etc/fstab to mount /boot using ext2 instead of ext3:
I've been able to reboot, upgrade the kernel, create and delete files on /boot
and (so far) haven't seen any error messages.
I'm guessing that I can now go and reconvert /boot back to ext3? But that's
a job for tomorrow, I have to go drink some beer now :->
John O'Brien
>
> My /boot filesystem is being remounted as read-only. I'm not sure what
> triggers
> it, I've seen the messages below waiting for me at the login prompt in
> the
> morning and they've also popped up as I was fiddling around in /boot
> trying to
> figure out what was wrong.
>
> I get the following messages...
>
> journal_bmap_Ra7a5f568: journal block not found at offset 12 on
> ide0(3,1)
> Aborting journal on device ide0(3,1)
>
> ext3_abort called
> EXT3_fs abort (device ide0(3,1): ext3_journal_start: Detected aborted
> journal
> Remounting filesystem read-only
