2big NAS

[panda88]

hi
i am trying to fix my 2big nas that has no OS inside.
I am following the procedure of Jocko (told me on another forum) :

- install fvdw-sl console on your windows laptop
- read help files carefully because if you do not follow the procedure correctly, installation will fail
- keep only one disk (in the left slot when you see the back side)
- run fvdw-sl console
- follow the install steps when you use the action "install fvdw-sl firmware" and declare you have a 2big nas

actually i am stucked at this point: after uploading "UIMAGE-3142-KIRKWOOD-158-standalone" kernel, the command prompt should allow me to connect using telnet, but it doesnt.
Neither manually it works.
I tried to scan all my /24 subnet in order to see if the device is recognized but it seems no, anyway on the dhcp table of my router seems to find correctly the device.
Pay attention that im working in a network with addresses like 10.0.0.x/24 so i start (using cat5cable) 10.0.0.123 ip from my computer and 10.0.0.252 to the nas while uploading.
So, is this a network problem?
I tried also to do the procedure using a cat5crossed cable directly to the nas but since i dont have yet and ip address since the nas is turned on, the console doesnt allow me to choose it so it just shows me the localhost 127.0.0.1 address.
what am i missing or doing wrong?

thank you all

[panda88]

i tried also 2 other uimage since my nas isnt exactly listed:
UIMAGE-26394-2BIG1-27-1-1-1-standalone
UIMAGE-26394-2BIG1-47-1-1-4-standalone

unfortunately, same result.

[Jocko]

Hi,

First, check if this information can fix your issues. https://plugout.net/viewtopic.php?f=7&t=2645

But do not use a cross cable, do not connect directly the nas to the laptop and it must be off when you start fvdw-sl console and boot the NAS only at the required step.
About IP, it is the NAS itself which set its IP according with the laptop IP. So no issue with your subnet.

About kernel, yes you should try to use these kernel versions

---edit---
I moved the topic as according with your pic posted on nas.central your nas seems to be a 2big nas

[panda88]

hi,
thanks for assistance and feedbacks.
i am following all your indications: using just ethernet interface, trying all 3 standalone's kernel for the 2big's model, firewall turned off, one disk only in the first bay, starting with turned off nas...
seems nothing works!
anyway, everytime the kernel hets uploaded. the issue is just when i must connect with telnet :( any other ideas?

thank again

[panda88]

another thing...
sometimes when i start the nas, the disk/disks never starts spinning and the led that shows its activuty gets immediately blue.
sometimes instead, the nas starts blinking red/blu (the disks led) then according to how many are mounted those leds becomes steady and disks spin.
idk why....
idk either why i have never been able to fix it using the *.capsule files that Lacie's support suggested me so far.

[Jocko]

We go to check if you get more information if you upload manually the kernel :
stop you server
So do (fvdw-sl console Action)
- start tftpd server
- start U-boot console and start the NAS when you have the prompt message : "waiting for u-boot.." on the nc window

Then check if you have now the prompt message "Marvell>>"
if yes do these commands

Code: Select all

setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7
ide reset
tftpboot 0x400000 UIMAGE-26394-2BIG1-27-1-1-1-standalone


---edit---

Code: Select all

setenv bootargs console=ttyS0,115200 netconsole=6666@${ipaddr}/,6666@${serverip}/ root=/dev/sda7
ide reset
tftpboot 0x800000 UIMAGE-26394-2BIG1-27-1-1-1-standalone


check if the kernel seems to be uploaded
Note: I am not sure about the address (0x400000) but fvdw can confirm it (he is the expert for that domain)
and then do

Code: Select all

bootm

check if you get some outputs (dmesg output) after the line "Starting kernel ..." like

Code: Select all

[   22.006441] xor: measuring software checksum speed

if not try by using another kernel file

Code: Select all

tftpboot 0x400000 UIMAGE-26394-2BIG1-47-1-1-4-standalone
bootm

---edit---

Code: Select all

tftpboot 0x800000 UIMAGE-26394-2BIG1-47-1-1-4-standalone
bootm

and last attempt with the kirkwood version :

Code: Select all

tftpboot 0x800000 UIMAGE-3142-KIRKWOOD-158-standalone
bootm

(note in this case I am sure about the address 0x800000)

[fvdw]

You can use 0x800000 for 2big1 kernel and kirkwood kernel in the tftpboot command

[panda88]

dear all,
really thanks, thanks and thanks again for your support.
i think you both are the only ppl who really can help me making this nas working again (instead of lacie and seagate support).
nevertheless..
no changes yet.
i tried these 3 procedures and no one works; all stopped at ''starting kernel'' point.
To avoid any misunderstandings, i printed all the screens of my procedure, in case i made something wrong.
What's the next step then? ;)

[ img ] [ img ] [ img ] [ img ] [ img ]

[Jocko]

Hi panda88

That seems to be a bad new.

It seems the kernel is really uploaded but something is wrong with the bootloader (it fails to use it).
So that would mean we does not have a standalone kernel version usable with your NAS.
Maybe it is a 2bignas OS3 and even if it is an arm CPU, it can not use our kernel. :dry

So wait fvdw to confirm my opinion.

[Jocko]

maybe we can find some infomration with environment settings (but unlikely)

So get a uboot console and when you have the message "Marvell>>" do

Code: Select all

printenv

Post here the output