GoFlexNet not getting IP

Cool!!!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Finally I have installed the packages I use and everything seems to be running fine.
Thanks again for all the help.

So yesterday I updated the system and I am back to sqaure one, the GFN is not booting up. This time the error is different, seems some kernel issue. Here is the complete log, please have a look.

http://pastebin.com/5AxLYun7

Neptune Wrote:
-------------------------------------------------------
> So yesterday I updated the system and I am back to
> sqaure one, the GFN is not booting up. This time
> the error is different, seems some kernel issue.
> Here is the complete log, please have a look.
>
> http://pastebin.com/5AxLYun7

Looks like your rootfs was corrupted. Mount it on a different Linux box and use e2fsck to check and fix error. Remember to do the sync command before shutdown. And then tak it back to the GFNet and cold start.

BTW, after you've booted back into Arch, look into changing the u-boot env that defines your rootfs file system. This indicates that it is set to Ext2, but your rootfs is Ext3. This does not have anything to do with the corrupted rootfs, but should make it consistent anyway. And do this in serial console to make sure that it works before setting permanently.

27.725321] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2
[   27.731890] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Tried running e2fsck but it didnt helped, got the same error.
Further, I took a new USB drive, formatted it with ext3 and untar archlinuxalarm but got this error.

http://pastebin.com/iecwbFia

[   16.043375] Starting init: /sbin/init exists but couldn't execute it (error -13)
[   16.052916] Starting init: /bin/init exists but couldn't execute it (error -13)
[   16.063365] Starting init: /bin/sh exists but couldn't execute it (error -13)

Maybe this can help you get to the bottom of this error;
http://free-electrons.com/blog/debugging-init-failures/

It seems that the system got corrupted and I have reinstall from scratch which I did and now I am getting alarm login.
Another problem, GFN is not getting IP and in log it can be seen as eth0 is not ready.

Output: http://pastebin.com/dDd2M0Ww

My eth0 file:

Description='A basic dhcp ethernet connection'
Interface=eth0
Connection=ethernet
IP=static
AutoWired=yes
Address=('192.168.1.12/24')
Gateway='192.168.1.1'
DNS=('192.168.1.1')
Hostname=GoFlexNet

## for DHCPv6
#IP6=dhcp
## for IPv6 autoconfiguration
#IP6=stateless

@Neptune,

To really fix and prevent your rootfs corruption, you need to change u-boot env rootfs type to be consistent with what you have on the USB drive. If you're not sure how, please post your u-boot envs. In serial console,

printenv

Your dmesg showed that you're still having problem.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 11/30/2014 06:00PM by bodhi.

printenv: http://pastebin.com/3h89stbU

Your current env:

usb_rootfstype=ext2

In serial console, change to ext3:

setenv usb_rootfstype ext3

then let it boot

boot

After verifying everything is working OK, set it permanently in Linux:

fw_setenv usb_rootfstype ext3

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ok, Thanks. Will do later today as I am out.
Hope this will resolve the network issue also.

bodhi Wrote:
-------------------------------------------------------
> Your current env:
>

> usb_rootfstype=ext2
>

>
> In serial console, change to ext3:
>

> setenv usb_rootfstype ext3
>

> then let it boot
>

> boot
>

>
> After verifying everything is working OK, set it
> permanently in Linux:
>

> fw_setenv usb_rootfstype ext3
>

Changed the env in serial console, booted into Alarm but after that I am unable to set the env in Alarm. I am getting error as fw_setenv not found.

Further getting this error when it loads Alarm



Arch Linux 3.14.4-1-ARCH (ttyS0)

localhost login: [ 42.569396] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 42.575486] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 44.300558] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[ 44.310391] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 46.429643] EXT3-fs error (device sda1): ext3_lookup: deleted inode referenced: 368514
[ 47.596763] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready



Edited 1 time(s). Last edit at 12/01/2014 11:31AM by Neptune.

Your roofts still has error. Have you tried to use a different Usb drive? Perhaps this drive is bad.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ok, I again reformatted the drive and installed Archlinux again and this time its getting IP(although I have set it as statis IP, it is getting random IP, but this we can solve later).
I have 2 issues now, when I boot into Archlinux and issue command

What I did:
I interrupted the boot sequence and typed this

setenv usb_rootfstype ext3

then

boot

After booting done in Archlinux, I did pacman -Syu and gave this command

fw_setenv usb_rootfstype ext3

but got this error

[root@goflexnet ~]# fw_setenv usb_rootfstype ext3
Cannot parse config file: Invalid argument
Error: environment not initialized
[root@goflexnet ~]#

Neptune Wrote:
-------------------------------------------------------
> Ok, I again reformatted the drive and installed
> Archlinux again and this time its getting
> IP(although I have set it as statis IP, it is
> getting random IP, but this we can solve later).
> I have 2 issues now, when I boot into Archlinux
> and issue command
>
> What I did:
> I interrupted the boot sequence and typed this
>
> setenv usb_rootfstype ext3
>
> then
>
> boot
>
> After booting done in Archlinux, I did pacman -Syu
> and gave this command
>
> fw_setenv usb_rootfstype ext3
>
> but got this error
>
> [root@goflexnet ~]# fw_setenv usb_rootfstype ext3
> Cannot parse config file: Invalid argument
> Error: environment not initialized
> [root@goflexnet ~]#

Does your env config looks like this:

cat /etc/fw_env.config

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

[root@goflexnet ~]# cat /etc/fw_env.config
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# MTD device name Device offset Env. size Flash sector size
#/dev/mtd2 0x0000 0x20000 0x20000

# segate dockstar:
# /dev/mtd0 0xc0000 0x20000 0x20000

# iomega iconnect
# /dev/mtd0 0xa0000 0x20000 0x20000

# CuBox
# /dev/mtd0 0xc0000 0x10000 0x10000

# CuBox-i/Hummingboard
# /dev/mmcblk0 0x60000 0x2000 0x2000
[root@goflexnet ~]#

What a f' mess :)) where did you get this roofts?

In your serial console please print the u-boot version:
> version

It you are running u-boot installed by Jeff's script or my u-boot build then the fw_config should look like mine showed above.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Ha-ha, don't know, but I downloaded the archive last time when it got messed up. I am downloading again the latest version.

Here is the version output

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
GoFlexNet>

^ I tried to instal the latest Uboot

wget http://archlinuxarm.org/os/armv5te/boot/goflexnet/goflexnet.sh
chmod +x goflexnet.sh
./goflexnet.sh

But got this error


[root@goflexnet ~]# chmod +x goflexnet.sh
[root@goflexnet ~]# ./goflexnet.sh

Downloading flash utilities..
blparammd5sum: invalid option -- 's'
Try 'md5sum --help' for more information.
[FAILED]

Failed to install U-Boot. DO NOT REBOOT
Please seek assistance at:
http://archlinuxarm.org/forum
#archlinux-arm on irc.freenode.net
[root@goflexnet ~]#

Your u-boot even though it is old, it's fine. Don't try to mess with it for now. You can just download the latest Arch rootfs and create a new USB thumb drive, format it as Ext3 with it (on a different Linux box), and boot with it.

If you're desperate to get anything working, temporarily use my rootfs (Updated 31 Oct 2014 Rootfs Debian-3.17.0-kirkwood-tld-1) and boot with it. I know you want to run Arch, but just to prove to yourself that your u-boot is fine, you should boot Debian as an experiment.

And whichever rootfs you use to boot, the /etc/fw_env.config content should be:

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/02/2014 11:26PM by bodhi.

Ok, I downloaded and installed the Archlinux and here is the output.
I am unable to get the env output.

[root@alarm ~]# cat /etc/fw_env.config
cat: /etc/fw_env.config: No such file or directory
[root@alarm ~]#


And here is the complete output, does this looks better?

http://pastebin.com/tQQLJ3WV


Also the printenv output from the serial console:

http://pastebin.com/bGmpMqec



Edited 1 time(s). Last edit at 12/03/2014 12:07PM by Neptune.

Neptune Wrote:
-------------------------------------------------------
> Ok, I downloaded and installed the Archlinux and
> here is the output.
> I am unable to get the env output.
>
> [root@alarm ~]# cat /etc/fw_env.config
> cat: /etc/fw_env.config: No such file or
> directory
> [root@alarm ~]#
>

Create this file and copy the content above to it.

>
> And here is the complete output, does this looks
> better?
>
> http://pastebin.com/tQQLJ3WV
>
>
> Also the printenv output from the serial console:
>
> http://pastebin.com/bGmpMqec

Much better! no file system error.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I found that doing system update using pacman -Syu is breaking something and if I do the update, its resulting into kernel panic.

Here is the complete log

http://pastebin.com/fnFX6N1n

Please suggest, do I need to update the uboot? If yes, how to do that safely?

So I took the plunge and updated the uboot using the details here: http://forum.doozan.com/read.php?3,12381,page=1

Here is my print env, please have a look.

http://pastebin.com/gsTGLcFY



(Also please tell me how to copy all the contents of the boot sequence using the serial console. I am using script xyz.txt before running the screen command but it only capture partial output. )



Edited 2 time(s). Last edit at 12/07/2014 10:37AM by Neptune.

Is there a problem? or were you booting normally? it's hard to tell without seeing the entire serial console log. You can just copy and paste what on the screen to a text file.

You can also connection serial console with picocom. Install picom with apt-get (or on Arch, pacman).

And to run it:

picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 12/07/2014 04:12PM by bodhi.

I was not able to capture the whole log earlier. Anyways, here is the complete log

http://pastebin.com/GEaVNyf4

Neptune Wrote:
-------------------------------------------------------
> I was not able to capture the whole log earlier.
> Anyways, here is the complete log
>
> http://pastebin.com/GEaVNyf4

Everything looks great!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Cool.
Thanks a lot for all the help.

@Neptune,

One more thing! I've noticed that your USB drive is a little slow coming up. It did not affect the boot process, though. However, if you'd like to be a little more sure about booting, add this env to your u-boot env (15 is number of seconds u-boot takes to detect the drive before timing out):

fw_setenv  usb_ready_retry 15

My u-boot build has an extra timeout period for USB where you can set it to as long as you'd like u-boot takes to detect the USB drive. This is not in the mainline u-boot. If this env is not set, it uses the default time out period of 1 second.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Done, thanks a million.