2big NAS

[panda88]

I will try.
As I said you both are the only one who can help me!
Tell me whatever to do!

[fvdw]

Yes the printev command in the uboot console could give some information.

Ps di not fill in in the setenv command the ip address of your oc use the commanline as posted by jocko.
Ps2 You are using at not common ip pool on your router 10.*.*..
I need to check if the standalone kernel support this and set uts ip address correctly. Better would be to use 192.168.1.* or 192.168.0.*. Also the ip pool should allow to use ip's upto from 1 to 254

If this device had 2 disk of each 3TB in it I think it is not a 2big1 but a 2big2. If it is a 2bigpro (with intel cpu), I doubt I think those will have another boot loader then the ARM.

To find out what cpu is inside you open the casing and look at the motherboard if you find a marvell cpu write down the type nr in it or take a picture of the motherboard and post it here

I think it is an arm and that your problem might be the ip settings used by your router

[Jocko]

I need to check if the standalone kernel support this and set uts ip address correctly. Better would be to use 192.168.1.* or 192.168.0.*. Also the ip pool should allow to use ip's upto from 1 to 250

Yes with the old version it works like this but now (since version 6) it reuses directly the laptop's IP to build itself its IP. It is the default NAS Ip built by this way and only set other alternative IP 192.168.(0|1).251 on NAS iface

[panda88]

Thatsa the output of printenv

Code: Select all

Marvell>> printenv
printenv
bootargs=console=ttyS0,115200
bootcmd=run nexus_boot; run legacy_boot
baudrate=115200
loads_echo=0
rootpath=/srv/ubuntu
netmask=255.255.255.0
uboot_capabilities=gpt,lba64
start_lump=lump 3
pre_lump=lump 1
resetdisk=ide reset
boot_fail=lump
loadaddr=0x800000
console=console=ttyS0,115200
kernel_addr=${loadaddr}
mtdids=nand0=nand_mtd
mtdparts=mtdparts=nand_mtd:1m(u-boot),16m(uImage),-(root)
disk_list=0 1
legacy_set_rootfs=if test $boot_disk -eq 0; then rootfs=/dev/sda7; elif test $boot_disk -eq 1; then rootfs=/dev/sdb7; fi
legacy_nand_bootargs=setenv bootargs ${console} reset=${resetFlag_env} root=/dev/mtdblock2;
legacy_nand_boot=echo Booting legacy NAND installer...; if nboot ${loadaddr} uImage; then run legacy_nand_bootargs; bootm; fi
legacy_disk_bootargs=setenv bootargs ${console} reset=${resetFlag_env} root=${rootfs};
legacy_disk_boot=echo Booting legacy layout...; if test ${resetFlag_env} -ne 0; then part_list=6; else part_list="A 6"; fi;for p in ${part_list}; do for boot_disk in ${disk_list}; do if disk ${loadaddr} ${boot_disk}:$p; then run legacy_set_rootfs; run legacy_disk_bootargs; bootm; fi; done; done
legacy_boot=run legacy_disk_boot || run legacy_nand_boot
nexus_max_count=3
nexus_nv_part=3
nexus_inc_count=if test ${boot_count} -eq 0; then setenv boot_count 1; elif test ${boot_count} -eq 1; then setenv boot_count 2; else setenv boot_count ${nexus_max_count}; fi
nexus_set_root=if test $saved_entry -eq 1; then root_part=5; else root_part=4; fi
nexus_load_flags=ext2get ide ${boot_disk}:${nexus_nv_part} /ubootenv boot_count saved_entry
nexus_save_flags=ext2set ide ${boot_disk}:${nexus_nv_part} /ubootenv boot_count ${boot_count}
nexus_load_image=ext2load ide ${boot_disk}:${root_part} ${loadaddr} ${image} && iminfo ${loadaddr}
nexus_uuid=ext2uuid ide ${boot_disk}:${nexus_nv_part}; boot_uuid=${uuid}; ext2uuid ide ${boot_disk}:${root_part}; root_uuid=${uuid}
nexus_bootargs=run nexus_uuid; setenv bootargs ${console} boot=UUID=${boot_uuid} root=UUID=${root_uuid}
nexus_can_boot=test ${bootfail} -eq 0 -a ${countfail} -eq 0 -a ${button} -eq 0 -a ${user} -eq 0
nexus_rescue_countfail=test ${boot_count} -ge ${nexus_max_count}
nexus_rescue_user=ext2get ide ${boot_disk}:3 /ubootenv rescue && test ${rescue} -eq 1
nexus_rescue_bootargs=test -n ${bootfail} && setenv bootargs bootfail=${bootfail} ${bootargs}; test -n ${countfail} && setenv bootargs countfail=${countfail} ${bootargs}; test -n ${user} && setenv bootargs user=${user} ${bootargs}; test -n ${button} && setenv bootargs button=${button} ${bootargs}
nexus_nand_bootargs=setenv bootargs ${console} root=/dev/mtdblock2; if test -n ${boot_disk}; then run nexus_uuid; setenv bootargs ${bootargs} boot=UUID=${boot_uuid}; fi
nexus_boot_rescue=echo Booting Nexus rescue from NAND...; if nboot ${loadaddr} uImage; then run nexus_nand_bootargs; run nexus_rescue_bootargs; bootm; fi
nexus_panic=boot_disk=; run nexus_boot_rescue
nexus_boot=test -n ${resetFlag_env} && button=${resetFlag_env}; for boot_disk in ${disk_list}; do echo Booting Nexus layout from disk ${boot_disk}...; countfail=0; bootfail=0; user=0; if run nexus_load_flags; then run nexus_rescue_countfail && countfail=1; run nexus_set_root; image=/boot/uImage; run nexus_load_image || bootfail=1; run nexus_rescue_user && user=1; if run nexus_can_boot; then run nexus_inc_count; run nexus_save_flags; run nexus_bootargs; bootm; bootfail=1; fi; run nexus_boot_rescue; fi; done; bootfail=1; countfail=; user=;run nexus_panic
run_diag=yes
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
disaMvPnp=no
ethaddr=00:D0:4B:94:F7:C7
ethmtu=1500
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
resetFlag_env=0
bootdelay=0
pcieTune=no
ethact=egiga0
ipaddr=10.0.0.252
ncip=10.0.0.102
serverip=10.0.0.102
stdin=nc
stdout=nc

Environment size: 4289/131068 bytes
Marvell>>

[Jocko]

I think we can detect what is the 2big version by checking the connectors on the rear side :

so
- On a 2big : 1 raid selector switch (safe100/big); 2 USB ports type A and 1 Ethernet port
- On a 2big2 : esata port; 2 usb ports (type A and B) and 1 Ethernet port
- On a 2bignas OS3 : 1 esata port; usb port type A and 1 Ethernet port

Can you detect your version by this way ?(or better post a pic of the rear side)

[panda88]

I think we can detect what is the 2big version by checking the connectors on the rear side :

so
- On a 2big : 1 raid selector switch (safe100/big); 2 USB ports type A and 1 Ethernet port
- On a 2big2 : esata port; 2 usb ports (type A and B) and 1 Ethernet port
- On a 2bignas OS3 : 1 esata port; usb port type A and 1 Ethernet port

Can you detect your version by this way ?(or better post a pic of the rear side)

Based on your description, it is definitely the 3rd version :(

[ img ]

[fvdw]

what does the commands

Code: Select all

blinfo
coninfo

tells you ? (with command help in uboot console you get a list with all build in commands)

[fvdw]

if it is a version 3 then still it is interesting to know which processor is inside, this will enable me to see if we can build a linux package for this generation

[Jocko]

@fvdw
it seems it is a diskless version (NAND) and so on booting, the nas should be able to install a default lacie firmware version .


---edit---
I found the user manual for a 2big nas OS3.
Nothing about empty disk or reset with data loss process

but at least the bootloader seems to have a NAND support

[panda88]

Yes the printev command in the uboot console could give some information.

Ps di not fill in in the setenv command the ip address of your oc use the commanline as posted by jocko.
Ps2 You are using at not common ip pool on your router 10.*.*..
I need to check if the standalone kernel support this and set uts ip address correctly. Better would be to use 192.168.1.* or 192.168.0.*. Also the ip pool should allow to use ip's upto from 1 to 254

If this device had 2 disk of each 3TB in it I think it is not a 2big1 but a 2big2. If it is a 2bigpro (with intel cpu), I doubt I think those will have another boot loader then the ARM.

To find out what cpu is inside you open the casing and look at the motherboard if you find a marvell cpu write down the type nr in it or take a picture of the motherboard and post it here

I think it is an arm and that your problem might be the ip settings used by your router

Btw my io address space is more standard thank you think: https://en.m.wikipedia.org/wiki/Private_network

If I need though I can put another ipv4 on my computer (so not release by my dhcp server).
Tell me the addresses I should try and I will, no problem.
Can I leave though my dhcp server in my 10.0.0.x/24 environment still on?
I am gonna open the case soon then and photograph the mobo in order to send you.