[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 mount problem after upgrading kernel

On 28 Feb 2002, Stephen C. Tweedie (sct redhat com) wrote:

> Hi,
> On Sat, Feb 23, 2002 at 02:55:33PM +0100, Jan Söderholm wrote:
> > I use RH 7.2 (the download version) with kernel 2.4.9-13 (upgraded by 
> > using the Up2date program). Today i used Up2date (version 2.7.11) to 
> > upgrade to 2.4.9-21 (kernel, headers and source). I get the following 
> > error while the new kernel is booting:
> > 
> > EXT3-fs: unable to read superblock
> > mount: error 22 mounting ext3
> > pivotroot: pivot_root (/sysroot, /sysroot/initrd) failed: 2
> Do you have an "/initrd" root directory?  If not, make one.
> Cheers,
>  Stephen

Actually, you should check to see if you used to have an EXT3 file system,
and maybe the journal got clobbered somehow (effectively now only an EXT2.)

Your /etc/fstab might look something like this: (note the "ext3" in the
first two lines)

  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/hda2 	swap        	swap  	defaults        0 0
  /dev/cdrom	/mnt/cdrom  	iso9660	noauto,owner,kudzu,ro 0 0
  /dev/fd0  	/mnt/floppy 	auto  	noauto,owner,kudzu 0 0
  none      	/proc/bus/usb	usbdevfs	noauto 0 0

When you run " /sbin/tune2fs -j /dev/hda# " it will add a default journal
file back onto the file system if one is missing. 

Your kernel panic should disappear.

(I wonder why hasn't this simple test been put into the kernel yet? If FS
type is EXT3, and there's no journal, tell user to go and create one or
proceed with defaults...)

Richard Chadderton
Watcher -(at)- Vigilans.NET

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]