On Sun, May 15, 2011 at 10:35 AM, Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Sun, May 15, 2011 at 5:15 AM, Scott M. Jones
<scott(a)aprr.org> wrote:
> I'm trying the F13-beta3 rootfs on a Beagleboard-XM and I get this at
> bootup:
>
> fsck: cannot check /dev/mmcblk0p2: fsck.ext3 not found
> fsck: cannot check /dev/mmcblk0p2: fsck.ext3 not found
Note that the filesystem gets checked at every boot. On the ARM
systems I have, just booting them tends to trigger a fsck. This is
because the date that the filesystem was last mounted, is in the
future. On boot, the clock of the board gets set to some date around
1970. To solve this, I tend to set the time between fsck intervals
'0', which disables the check:
# tune2fs -c 0 /dev/mmcblk0p2
In order to have the systemtime corrected, I use ntpdate.
> I checked in /sbin and there is a fsck.cramfs but no fsck.ext3.
My root
> partition is ext3.
The appropriate fsck utilities are usually installed by anaconda based
installs so maybe its something we explicitly need to add to the
rootfs.
> I am able to fsck by moving the SD card to an F14/Intel system, but is
> there a package I can add to get the ext3 fsck on ARM?
Yes, its in the e2fsprogs package.
And in case you need any other binaries, you can use yum like
# yum install /sbin/fsck.ext3
or
# yum install e2fsprogs
An "rpm -qf /sbin/fsck.ext3" on your F14 will also point you to the
package that contains that file.
Cheers,
Niels