Goflex Net stuck on 2.6.37

[glenno]

Ive got a GoFlex Net that was built on Ubit 0.5 and 2.6.37. I have been unable to upgrade to the 3.1 kernel. Ive tried every command with pacman, so I think its a boot image issue more than anything else. Any thoughts on the below??

Ive installed the latest linux package:
pacman -Qi linux
Name : linux
Version : 3.1.2-1
URL : http://www.kernel.org/
Licenses : GPL2
Groups : base
Provides : kernel26 aufs_friendly
Depends On : coreutils linux-firmware module-init-tools>=3.16 mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels of your country
Required By : None
Conflicts With : kernel26
Replaces : kernel26
Installed Size : 16636.00 K
Packager : Kevin Mihelich <kevin@Arch Linux ARM.com>
Architecture : arm
Build Date : Sat 26 Nov 2011 04:39:25 PM EST
Install Date : Sat 12 Feb 2011 01:25:34 AM EST
Install Reason : Explicitly installed
Install Script : Yes
Description : The Linux Kernel and modules


However uname -a still shows:
Linux nas 2.6.37-ubit-01711-g50c16ad #1 Tue Feb 1 14:11:22 GMT 2011 armv5tel Feroceon 88FR131 rev 1 (v5l) Seagate GoFlex Net GNU/Linux


In frustration I grabbed a new HDD and upgraded UBIT to 0.6 and did a fresh install per the instructions. UBIT 0.6 now starts up fine, but kernel 2.6.37 is still running.

However when I look in /boot I think uInitrd is still from the 2.6.37 kernel

-rw-r--r-- 1 root root 2821020 Nov 26 2011 uImage
-rw------- 1 root root 2643844 Feb 12 01:30 uInitrd


Any thoughts? Much appreciated.

[kmihelich]

Not sure where you're picking up the other kernel image. Did it have a NAND install previously that it's pulling from?

[glenno]

I think you are right regarding the NAND boot. I have no idea how UBIT 0.5 worked compared to UBIT 0.6

I have checked the UBIT output and it references a 2.6.37 kernel, so this leads me to that conclusion.

I am not sure if there is a fw_sentenv command I can do to point the boot loader to boot. the output of fw_printenv is below. Not sure what I am looking for, but nothing stands out as bad to me. My only guess is it is trying to boot off the HDD, fails and falls back to a NAND based kernel for bootup. Ive set partition1 as bootable.


bootcmd=run fast_boot; run usb_boot; run hd_boot; run ubi_boot
bootdelay=3
baudrate=115200
ide_start=ide reset
ubi_start=ubi part root
usb_start=usb start
nc_test=ping $ncip
nc_start=setenv stdin nc; setenv stdout nc; setenv stderr nc; version
silent_boot=run silent_rd ubi_args ubi_fallback
fast_boot=run fast_rd ubi_args ubi_fallback
usb_boot=for scan in 0 1 2 3; do run usb_args_$scan ext2_kern ext2_boot; run ext2_rd ubi_fallback; run fat_kern fat_boot; run fat_rd ubi_fallback;done
usb_args_0=boot_dev='usb 0:1'; dev_args='root=/dev/sda1 rootdelay=10'
usb_args_1=boot_dev='usb 1:1'; dev_args='root=/dev/sdb1 rootdelay=10'
usb_args_2=boot_dev='usb 2:1'; dev_args='root=/dev/sdc1 rootdelay=10'
usb_args_3=boot_dev='usb 3:1'; dev_args='root=/dev/sdd1 rootdelay=10'
hd_boot=run ide_start; for scan in 0 1; do run hd_args_$scan ext2_kern ext2_boot; run ext2_rd ubi_fallback; run fat_kern fat_boot; run fat_rd ubi_fallback; done
hd_args_0=boot_dev='ide 0:1'; dev_args='root=/dev/sda1'
hd_args_1=boot_dev='ide 1:1'; dev_args='root=/dev/sdb1'
ubi_boot=run ubi_rd ubi_args ubi_fallback
ubi_args=dev_args='ubi.mtd=root'
rescue=dev_args='ubi.mtd=root rootfstype=preboot'; boot_dev='usb 0:1'; run ext2_kern ext2_auto boot_rd; boot_dev='ide 0:1'; run ide_start ext2_kern ext2_auto boot_rd; run silent_rd ubi_fallback; run fast_rd ubi_fallback; run ubi_rd ubi_fallback
chain=nand read.e 0x800000 0x480000 0x80000; go 0x800200
ethact=egiga0
console=ttyS0,115200
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(pogoplug),-(root)
set_bootargs=setenv bootargs console=$console $mtdparts $dev_args $rd_args netconsole=@$ipaddr/eth0,@$ncipk/
ext2_kern=ext2load $boot_dev $addr_kern /boot/uImage
ext2_auto=ext2load $boot_dev $addr_rd /boot/uInitrd
ext2_rd=ext2load $boot_dev $addr_rd /uInitrd
ext2_boot=run ext2_rd boot_rd; run ext2_auto boot_auto; run boot_kern
fat_kern=fatload $boot_dev $addr_kern /boot/uImage
fat_rd=fatload $boot_dev $addr_rd /uInitrd
fat_boot=run fat_rd boot_rd
ubi_kern=ubifsmount boot; ubifsload $addr_kern /boot/uImage
ubi_rd=ubifsmount ramdisk; ubifsload $addr_rd /uInitrd
ubi_fallback=run ubi_kern boot_rd
silent_rd=ubifsmount silent; ubifsload $addr_rd /uInitrd
fast_rd=ubifsmount fast; ubifsload $addr_rd /uInitrd
boot_kern=run set_bootargs; bootm $addr_kern
boot_rd=run set_bootargs; bootm $addr_kern $addr_rd
boot_auto=rd_args='rootfstype=auto'; run boot_rd
addr_kern=0x680000
addr_rd=0x1100000
ipaddr=10.10.10.6
ncip=10.10.10.5
ncipk=10.10.10.4
serverip=10.10.10.3
led_init=green blinking
led_exit=green off
led_error=orange blinking
stdin=serial
stdout=serial
stderr=serial
ethaddr=02:50:43:fc:65:6a
preboot=run ubi_start silent_boot; run nc_test nc_start; run usb_start

[glenno]

The output of UBOOT/UBIT looks like the below. Id apreciate if someone could post their output so I can see if it points me where to look for issues. Im just not sure if the SATA disks should be showing up as Storage devices, or as USB devices (ie is the SATA behind a USB controller etc. It doesn't seem to matter if I have 1 or 2 disks, it always shows 2 USB devices....

The below is off a fresh build on a new HDD:


U-Boot 2010.09 (Feb 16 2011 - 18:42:02)
UBIT v0.6 by Jeff Doozan and Peter Carmichael
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
UBIFS: mounted UBI device 0, volume 2, name "fast"
UBIFS: mounted read-only
UBIFS: file system size: 2967552 bytes (2898 KiB, 2 MiB, 23 LEBs)
UBIFS: journal size: 1161217 bytes (1134 KiB, 1 MiB, 8 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root: 0 bytes (0 KiB)
Loading file '/uInitrd' to addr 0x01100000 with size 2630339 (0x002822c3)...
Done
UBIFS: mounted UBI device 0, volume 1, name "boot"
UBIFS: mounted read-only
UBIFS: file system size: 3354624 bytes (3276 KiB, 3 MiB, 26 LEBs)
UBIFS: journal size: 1161217 bytes (1134 KiB, 1 MiB, 8 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root: 0 bytes (0 KiB)
Loading file '/boot/uImage' to addr 0x00680000 with size 2940876 (0x002cdfcc)...
Done
## Booting kernel from Legacy Image at 00680000 ...
Image Name: Linux-2.6.37-ubit-01711-g50c16ad
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2940812 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: UBIT-2010.11-00080-g45d63a5
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 2630275 Bytes = 2.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...


The rootfs pointer appears to be correct:

[root@alarm disk]# ls -l by-label/
total 0
lrwxrwxrwx 1 root root 10 Jan 1 10:00 rootfs -> ../../sda1

[kmihelich]

Well that confirms that it's loading from a previous NAND installation. That's why we never officially supported a NAND install, things just eventually go bad in some way.

You might want to check out the forums here: http://forum.doozan.com/list.php?3 and see if anyone has suggestions on migrating completely off of NAND. Or even changing up uboot variables to stop it from loading from ubi first.

[glenno]

Think I will have to. Basically I think all I need is the right commands in fw_setenv to tell UBIT to boot off the rootfs labelled partition.