lacie 5 big network v.1 please support for fvdw

[totorweb]

Removed all disks, same problem.

ok, i had never see the "starting kernel ..." message either in manual u-boot or in standalone boot. So the kernel does never seems to start.
Maybe i'll wait if taetae can try with his nas.

[fvdw]

it is funny because the kernel without the standalone stuff seems to run on his system.
The standalone kernel is the same it only has as extra an initram file system.
I have seen this behaviour on other nas devices when the kernel is to big. Howver On my isp1 that has less ram then the 5big1 a standalone kern of 3 M is no problem

Attached a standalone kernel for 2big1 it might run but will not be able to access your disk. if it runs the kernel size is not the problem

Making a smaller 5big1 standalone kernel is of course possible by skipping some extra's, I will compile that as well

[fvdw]

and a somewhat smaller standalone kernel for 5big1

[totorweb]

ok i have tried both files:

- with the UIMAGE-26394-NWSP2-2BIG1-22-standalone.zip using uboot (the console doesn't want to load this standalone file) same problem.
- with the UIMAGE-26394-NWSP2CL-5BIG1-22-standalone.zip with u-boot and with the standalone option same problem.

still staying in "Verifying Checksum ... OK" state in output

Maybe the problem is not the firmware ?

The nas is working because i can access the lacie web interface when booting normally, just the raid0 volume is in failed state.

[totorweb]

My nas was in 2.2.3 firmware, i had now applied a 5big_Backend_update to allow the update to 2.2.6 (in progress) then i will update to 2.2.8.

Then i will retry to boot standalone firmware. Maybe the 5big_Backend_update do something in the bios or other system configuration.

[totorweb]

still same problem after upgrading official firmware to 2.2.8.

[totorweb]

here is a printenv output, maybe some information can be usefull

Code: Select all

Marvell>> printenv
printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
ethaddr=00:d0:4b:88:55:86
stderr=serial
cpuName=926
enaDebugLed=yes
arcNumber=526
CASset=min
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
enaVFP=yes
enaWrAllo=no
enaICPref=yes
enaDCPref=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:egiga0:none
image_name=uImage
standalone=fsload 0x400000 $(image_name);setenv bootargs $(bootargs) root=/dev/m
tdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x400000;
disaMvPnp=no
eth1addr=00:00:00:00:51:82
overEthAddr=no
pciMode=host
usb0Mode=host
bootdelay=40
bootcmd=if lump 5; then ; else run disk_disk; fi
kernel_addr=0x400000
boot_disk10=disk ${kernel_addr} 4:6
boot_disk9=if disk ${kernel_addr} 3:6; then; else run boot_disk10; fi
boot_disk8=if disk ${kernel_addr} 2:6; then; else run boot_disk9; fi
boot_disk7=if disk ${kernel_addr} 1:6; then; else run boot_disk8; fi
boot_disk6=if disk ${kernel_addr} 0:6; then; else run boot_disk7; fi
boot_disk5=if disk ${kernel_addr} 4:A; then; else run boot_disk6; fi
boot_disk4=if disk ${kernel_addr} 3:A; then; else run boot_disk5; fi
boot_disk3=if disk ${kernel_addr} 2:A; then; else run boot_disk4; fi
boot_disk2=if disk ${kernel_addr} 1:A; then; else run boot_disk3; fi
boot_disk1=if disk ${kernel_addr} 0:A; then; else run boot_disk2; fi
disk_disk=ide reset; run boot_disk1; bootm ${kernel_addr};
ethact=egiga0
bootargs=console=ttyS0,115200 root=/dev/sda7 ro boardType=mv88F5281 productType=
5Big reset=0
ipaddr=192.168.0.45
ncip=192.168.0.12
serverip=192.168.0.12
stdin=nc
stdout=nc

Environment size: 1587/4092 bytes

[totorweb]

normal booting using u-boot give this output

Code: Select all

Marvell>> boot
boot
Waiting for LUMP (5)
no lump receive; continuing

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
  Device 0: OK
Model: ST31500341AS                             Firm: CC4H     Ser#:
 9VS21T6A
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
  Device 1: OK
Model: ST31500341AS                             Firm: CC1H     Ser#:
 9VS2YA2Q
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
  Device 2: OK
Model: ST31500341AS                             Firm: CC4H     Ser#:
 9VS220RH
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
  Device 3: OK
Model: ST31500341AS                             Firm: CC4H     Ser#:
 9VS1V7YP
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)
  Device 4: OK
Model: ST31500341AS                             Firm: CC4H     Ser#:
 9VS1XN8B
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)


Loading from IDE device 0, partition 10: Name: hda10
  Type: U-Boot
   Image Name:   Linux-2.6.22.7
   Created:      2010-10-07  16:10:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1814776 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
## Booting image at 00400000 ...
   Image Name:   Linux-2.6.22.7
   Created:      2010-10-07  16:10:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1814776 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...


[fvdw]

- with the UIMAGE-26394-NWSP2-2BIG1-22-standalone.zip using uboot (the console doesn't want to load this standalone file) same problem.

My fault you need to change NWSP2 to NWSP2CL in that name to trick the console

The funny thing is that the the normal kernel without the initramfs of the the standalone runs fine on tatae system. The initramfs is in fact a small linux filesystem with a static compiled version of busybox. It inititates the network interface and starts a telnet client.

you could try the option load external and use this kernel using the the u-boot console and tftptboot with netconsole support just to see if your 5big1 is able to run a not standalone kernel compiled with the setup I have
I saw you know ho to do do a tftp boot. It should produce output in the u-boot command window as netconsole is supported by the kernel

[totorweb]

i've made a rapid test and YES !! :) the firmware load succefully on the u-boot output, but no ping or telnet possible.
So the standalone seems to be the problem on the 5big1

I will do more tests tuesday or wednesday because l'll be out of home for two days.

I really thank you for your help