[Buildroot] EXT2-fs error

[Johnny Beardsmore]

Hello all,

OK.  I've tried the following, and still no joy.


1) e2fsck the rootfs file on the build machine.  This creates an error thus:



          The superblock could not be read or does not describe a correct ext2

          filesystem.  If the device is valid and it really contains an ext2

          filesystem (and not swap or ufs or something else), then the superblock

          is corrupt, and you might try running e2fsck with an alternate superblock:

              e2fsck -b 8193 <device>


2) After installation, logon from a rescue usb stick, umount the hda,
and e2fsck it.  This works (no EXT2 warning on first boot-up), but
there is a warning on subsequent boot-ups, regardless of the reboot
method.



3) Running e2fsck during installation, by inserting umount (where
necessary), and e2fsck entries in the installation script.  This has
created a number of different errors, but no working solution.



I'm of the opinion that the problem is with the rootfs which is
generated by Buildroot.  The suggestion to check it on the build
machine seemed very promising, and was along the lines of what I
thought I should be doing, but I haven't had any success with it so
far.  This is driven by the way I can check the hda from the rescue
USB, and go no warnings, but then when it's re-booted the warning
returns.



This seems to have dragged on for some time (mostly because I've not
been focussing on this problem).  If anyone has any ideas I'd be
grateful for them.

From: jny0 at hotmail.com
To: buildroot at busybox.net
Date: Thu, 9 Sep 2010 12:35:17 +0000
Subject: Re: [Buildroot] EXT2-fs error









> >bzImage is the kernel file, and I didn't ask you about it.  I'm asking
> >about your filesystem.
>  
> >The rootfs files contain your root filesystem.  Can you tell us clearly
> what you're doing to set up the root filesystem on
> >your device?
> 
> Apologies.  I use the following script (see below) to install the filesystem
> 'rootfs.i486.tar.bz2' and the kernel image 'bzImage'.
> This script is called from /boot/grub/menu.lst on the USB stick.
> 
> 
> echo Setting up main drive...
> echo "d
> n
> p
> 1
> 
> 
> a
> 1
> w
> " | /sbin/fdisk /dev/hda
> /usr/sbin/mkfs.ext2 /dev/hda1
> 
> echo Mounting drive and populating...
> /bin/mount /dev/sda2 /mnt
> /bin/mount /dev/hda1 /mnt/disk
> rm -rf /mnt/disk/*
> /bin/tar -C /mnt/disk/ -xvf /mnt/rootfs.i486.tar.bz2
> mkdir /mnt/disk/var/log/lighttpd
> cp /mnt/grub/menu.lst /mnt/disk/boot/grub/
> cp -av /mnt/home/* /mnt/disk/home/
> cp -av /mnt/etc/inittab /mnt/disk/etc/
> cp -av /mnt/etc/lighttpd /mnt/disk/etc/
> cp -av /mnt/etc/network/* /mnt/disk/etc/network/
> cp -av /mnt/etc/init.d/* /mnt/disk/etc/init.d/
> cp -av /mnt/var/www /mnt/disk/var/
> #umount /dev/hda1
> 
> echo "root (hd0,0)
> setup (hd0)
> quit
> " | /sbin/grub
> 
> 
> echo 
> echo Installation Finished. Please Reboot.
> echo =====================================
> /bin/sleep 8000
> -- 
> View this message in context: http://old.nabble.com/EXT2-fs-error-tp29591683p29641651.html
> Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
 		 	   		  

_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100913/3f6c7941/attachment-0002.html>