I followed the directions at
(except using ext2 for rootfs) and all went well until final boot when
Don't use ext2, it will be a maintenance nightmare, specially with no
rtc battery... Do you have a rtc battery installed on your beagle?
It's not really worth the extra maintenance over ext3...
/dev/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck died with exit status 4
failed (code 4).
An automatic file system check (fsck) of the root filesystem failed. A manual f!
The root filesystem is currently mounted in read-only mode. A maintenance shell.
Give root password for maintenance
(or type Control-D to continue):
btw, is this lenny or squeeze?
Pressing Ctl-D causes a reboot with the same result. I then changed
the bootargs to
setenv bootargs 'console=ttyS2,115200n8 root=/dev/mmcblk0p2
rootwait rootfstype=ext2 rw'
and was able to boot. Question: Why does the original bootargs include
ro instead of rw?
ubuntu/debian need 'ro' vs 'rw' such that fsck will properly run at startup...
Also, to increase longevity and possibly speed, I want to install onto
a bus powered usb hard drive. I understand that u-boot needs to boot
from the SD card, so the strategy is to put the kernel on the SD and
the rootfs and swap on the HD.
I tried the same installation as above, with the following changes:
1. During netinstall, format and install to the HD instead of SD. The
rootfs will be /dev/sda1
2. Change the ultimate bootargs to
setenv bootargs 'console=ttyS2,115200n8 root=/dev/sda1 rootwait
That's fine: I boot mine with: "console=ttyS2,115200n8 root=/dev/sda1
rootwait rootfstype=ext3 ro"
During (1) I had some hiccups, I never got to tasksel, although the
base system seemed to have installed. After (2), booting got pretty
far, but had several errors
Activating swap...[ 32.337860] uncorrectable error : <3>end_request:
I/O error, dev mtdblock0, sector 0
[ 32.345703] Buffer I/O error on device mtdblock0, logical block 0
[ 32.352172] uncorrectable error : <3>end_request: I/O error, dev
mtdblock0, sector 8
[ 32.360015] Buffer I/O error on device mtdblock0, logical block 1
Safe to Ignore, mtdblock0 is the nand... the net install for lenny is
an old 2.6.29 kernel, later versions get rid of that message.
pastebin your dmesg so we can see the rest...
In the end, booting got as far as starting cron, then hung.
Question: Has somebody had this setup before, and how should I deviate
from the stock debian elinux directions?
Yes, multiple installs over the last year. 3-4 beagles running 24/7
on Debian Lenny (dist-upgraded to squeeze)