Tom,
Do you mean it still mounts the new filesystem read-only even if you
change the usbboot environment to "bootargs console=ttyS0,115200
mtdparts=${partitions}
rootdelay=8 root=/dev/sda1 rw; bootm fc000000"?
I wish I could play with the environment a little bit, but I made it to boot
off the USB stick automatically.
I can not interrupt the standard boot process at uboot. I'm still struggling
to bring it back to the standard
boot process, It seems like I have to reload the uboot to overwrite the
'bootargs' environment.
FYR, I also had some warnings when booting.
--------------------------------------------------
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 136k init
INIT: version 2.86 booting
warning: can't open /etc/mtab: No such file or directory
mount: wrong fs type, bad option, bad superblock on tmpfs,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
---------------------------------------------------
I don't know how to fix that.
Zhiwei
On Tue, Jan 5, 2010 at 5:18 PM, Tom Downes <[email protected]> wrote:
> Zhiwei (and others):
>
> We are having the same problem as you upon upgrading to the 20091006
> kernel and the 20091130 etch file system on USB. We have an older
> filesystem (don't recall the date) on one USB stick and the new one on
> another. Both USB sticks are formatted ext2 and are the same
> brand/model.
>
> For some reason, when booting by "run usbboot" it will mount the old
> filesystem read-write but the new filesystem read-only. Doing a
> remount fixes the problem, but of course the boot process has had a
> number of failures along the way.
>
> This is after changing the usbboot environment variable to what you
> list, but when I try to do it with the dollar sign for partitions it
> immediately runs. So if I remove that, it will work. Is that really
> an environment variable? In any case, it works for one system, but
> not the other so I'm not sure it's the issue precisely.
>
> setenv usbboot bootargs console=ttyS0,115200 mtdparts=${partitions}
> rootdelay=8 root=/dev/sda1 rw; bootm fc000000
> saveenv
> run usbboot
>
> (minus the dollar sign for mtdparts)
>
> For both USB sticks it will complain about the file systems not having
> been checked. I have gone through and run "tune2fs -c 0 -i 0" on the
> new stick and done a manual force check with "e2fsck -fp". On the
> ROACH and on a true desktop. Yet it still gives the error. My
> impression is that sometimes the kernel will mount an ext2 fs
> read-only if it doesn't think that it has been checked. I would think
> that this is the source of the problem were it not for the fact that
> the same kernel mounts one disk read-write and the other read-only.
>
> I usually get the date set correctly along the way and do soft reboots
> so that the clock doesn't get too far off. Otherwise I would be
> concerned about automatic checks for a given number of days (despite
> my use of tune2fs).
>
> In both cases it also complains about the jffs2 filesystem not
> mounting properly at the very end of boot.
>
> I'm a bit baffled...
>
> Tom
>
>
