Hi, Apologies in advance for any breaches of netiquette, I couldn't find any guidelines about submission to this forum but I'd be grateful for your help on something. My /boot filesystem is being remounted shortly after start-up as read-only. 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 Any ideas how I can fix this? My fstab looks like this... LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/hda3 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom iso9660 noauto,user,kudzu,ro 0 0 /dev/hdd4 /mnt/zip auto noauto,user,kudzu,rw 0 0 /dev/fd0 /mnt/floppy auto noauto,user,kudzu,rw 0 0 thrombin:/users/ /users nfs noauto,user,exec,dev,rw,hard,intr 0 0 #/dev/hdb1 /dosc ntfs ro,umask=000 0 0 /dev/hdb2 /dosd vfat ro,umask=000 0 0 tof:/export/home/ /tof nfs noauto,user,exec,dev,rw 0 0 I'm running RH 7.3, installed from rpms so I haven't done any configuration of ext3, and haven't been able to find any documentation on how to. I discovered the problem when trying to upgrade the kernel which, obviously, can't be done with /boot mounted read-only. Curiously, I was able to use up2date to upgrade to kernel-2.4.18-5 recently without this problem. Otherwise, I haven't noticed any effects. Any advice much appreciated, John O'Brien.
Hi, 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 Any ideas how I can fix this? My fstab looks like this... LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/hda3 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom iso9660 noauto,user,kudzu,ro 0 0 /dev/hdd4 /mnt/zip auto noauto,user,kudzu,rw 0 0 /dev/fd0 /mnt/floppy auto noauto,user,kudzu,rw 0 0 remhost1:/users/ /users nfs noauto,user,exec,dev,rw,hard,intr 0 0 #/dev/hdb1 /dosc ntfs ro,umask=000 0 0 /dev/hdb2 /dosd vfat ro,umask=000 0 0 abc:/export/home/ /tof nfs noauto,user,exec,dev,rw 0 0 I'm running RH 7.3, installed from rpms so I haven't done any configuration of ext3, and haven't been able to find any documentation on how to. I discovered the problem when trying to upgrade the kernel which, obviously, can't be done with /boot mounted read-only. Curiously, I was able to use up2date to upgrade to kernel-2.4.18-5 recently without this problem occuring. Otherwise, I haven't noticed any effects. Any advice much appreciated, John O'Brien.
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
Hi, On Thu, Aug 22, 2002 at 02:34:28PM +0100, John K O Brien wrote:> My /boot filesystem is being remounted shortly after start-up as read-only. > > 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)That's a fatal error message indicating that ext3 has been unable to access a part of its journal file. Either the journal metadata has become corrupted (eg. you had a .journal file and tried to delete it), or there's a bad block in the journal. Are there any other log messages nearby to help narrow it down? --Stephen