[SOLVED] Only able to boot with ext3

[maxim]

When I decided to do a fresh install on a bigger usb stick, I noticed that I was only able to boot the system with ext3. When I formatted it to ext2, I was unable to ssh in to it.

I went back and checked my old usb stick I noticed that it also had ext3.. and I always thought I was using ext2 . So I don't know if I ever been able to boot from ext2.

This isn't any big problem, I'm quite happy with ext3 (as long as it works of course ) , never had any problems with my old stick. I'm just curious why it isn't working with ext2..

I'm by the way running the newest uBoot.

[moonman]

Run fw_printenv

see if uboot environment variabe usb_rootfstype is set to ext3. It probably is since ext2 doesn't work. This variable gets passed as kernel boot param. so it tells kernel that the frootfs fylesystem is ext3. ext2 would work on ext3 fs, but ext3 on ext2 won't find the journal so it will fail.

[maxim]

Excellent! It was just that. thanks!

[bluechalk2]

I would like to make this change on my black Pogoplug Pro P01, but I'm having trouble with fw_printenv. What are the correct values for fw_env.config?

[moonman]

I believe you need to comment out the one for dockstar:
$this->bbcode_second_pass_quote('', '/')dev/mtd0 0xc0000 0x20000 0x20000

[bluechalk2]

I tried:
/dev/mtd0 0xc0000 0x20000 0x20000

That doesn't work. I get:

# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200

I copied the executable for fw_printenv from my dockstar. Could that be a problem? If so, where do I get the executable?

[moonman]

I just realized p01 is pp pro whoch is armv6. It is not the same as dockstar with a completely different cpu. You should ask in pp pro forum unless anybody in this section knows...

[pepedog]

uboot-env is the package, p01 uses v5 repo
With the cubox fw_printenv is not affected by addresses, they directly access the SPI flash where the parameters are stored
Just experiment with /etc/fw_env.config, try different /dev/mtd numbers

[WarheadsSE]

Actually, the oxnas line that was used by CE used a modified checksum that uboot-env doesn't work with.

[bluechalk2]

For the Pro, the solution to this problem is to use blparam.

See viewtopic.php?f=29&t=2764