First installation on empty HDD's. Steps??

[thekarmola]

1. From the console install fimrware will not work and can't connect via terminal.
2. Tried to write image to disk from the console and successfully formatted drive with MSDOS not the GPT. Reboted Lacie but i can't find it on my network, tried Assistant but nothing :(
(On the first chose from the console i have chose UIMAGE-26394-2BIG1-47-1-1-4-standalone ) and via de terminal Kirkwood big2

At the first chose via the console UIMAGE-3142-KIRKWOOD-171-standalone i can;t connect via the terminal..

What is wrong here?

I don't understand what you are doing.

What kind of machine do you have ? a lacie 2big-vs2 or 2big-vs1. You mention before it is a vs2, in that case you must use as said the
UIMAGE-3142-KIRKWOOD-171-standalone kernel when it is a vs1 then indeed you need the UIMAGE-26394-2BIG1-47-1-1-4-standalone

On the first chose from the console i have chose UIMAGE-26394-2BIG1-47-1-1-4-standalone ) and via de terminal Kirkwood big2

what do you mean with "via the terminal" ? Is this after you have logged in with telnet using username : root and password: giveit2me ?
Where you able to login with telnet client using the UIMAGE-26394-2BIG1-47-1-1-4-standalone ?

What i have: Lacie 2big network v2

I have just 2 scenarios with no luck:

1. Via FVDW console click on Write firmware image to disk and chose UIMAGE-3142-KIRKWOOD-171-standalone
Result: No luck to connect using terminal.

2. Via FVDW console click on Writefirmware image to disk and chose UIMAGE-26394-2BIG1-47-1-1-4-standalone
Result: Succesfully connected using TFTP and from there via that blue screen formatted the drive and there chose the Kirkwood 2big2 image.
-> But after reboot the NAS no luck to get an IP..


Another thing is when i chose from de FVDW console install firmware instead of Write firmware image to disk, also no luck to connect via TFTP.

[fvdw]

:scratch :scratch

Result: Succesfully connected using TFTP

How do you connect using TFTP?

(there is no tftp server running on the nas)

ps what is the ip adress pool your router is using ?

[fvdw]

what you report is questionable

a 2big vs2 cannot be booted with a kernel for 2big vs1 or other way around, lets clarify things so we are sure which device you have

questions
selecting write firmware and selecting the standalone kernel (kirkwood)
1.Does the window appears mentioning waiting for uboot ?
2. If yes does this window shows that uboot is interupted and that the kernel is uploaded , you should see it in that window and it should finisih with booting kernel. After that it should close
3. 15 seconds after closing that window the telnet window should come up, doe it comme up ?
4. Can you loging using that telnet window ?.

And the same questions when using the 2big1 kernel

=========================
For your information

the output in the waiting for uboot window should be something like this when the kernel uploads form your pc.
If you do not see similar output then no kenrl is uploaded and of course telnet will fail to connect
NOTE THAT THIS OUTPUT BELOW IS AN EXAMPLE your file names and ips'will be different

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################
done
Bytes transferred = 3123520 (2fa940 hex)

Marvell>> bootm 0x800000
bootm 0x800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2012-12-23  21:59:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3123456 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

[thekarmola]

what you report is questionable

a 2big vs2 cannot be booted with a kernel for 2big vs1 or other way around, lets clarify things so we are sure which device you have

questions
selecting write firmware and selecting the standalone kernel (kirkwood)
1.Does the window appears mentioning waiting for uboot ?
2. If yes does this window shows that uboot is interupted and that the kernel is uploaded , you should see it in that window and it should finisih with booting kernel. After that it should close
3. 15 seconds after closing that window the telnet window should come up, doe it comme up ?
4. Can you loging using that telnet window ?.

And the same questions when using the 2big1 kernel

=========================
For your information

the output in the waiting for uboot window should be something like this when the kernel uploads form your pc.
If you do not see similar output then no kenrl is uploaded and of course telnet will fail to connect
NOTE THAT THIS OUTPUT BELOW IS AN EXAMPLE your file names and ips'will be different

Code: Select all

Marvell>> tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################
done
Bytes transferred = 3123520 (2fa940 hex)

Marvell>> bootm 0x800000
bootm 0x800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2012-12-23  21:59:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3123456 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

My LAN network address is 192.168.1.x

2big1 kernel:
1. Yes
2. When using via the console I see the ## and the kernel upload the image.
3. it close of 15 seconds and the Telnet popup open it.
4. I see the login and logged on as Root.

Kirkwood Kernel standalone:
1. Yes
2. When using via the console I don't see the ## and the kernel will not upload the image.
3. it close of 15 seconds and the Telnet popup open it.
4. I don't see anything to login in the terminal. And after some seconds it says not connected.

[fvdw]

That means you have a 2big vs1.

When you are logged in via telnet. Run fvdwsl-programs and choose install firmware, in the menu select orion 2big1 as device.

Remark.
It is remarkable that you mention that kirkwood kernel is not uploaded. At least it should be uploaded and then fail to start as it is a kernel for a kirkwood based device.
Anyhow if the 2big1 kernel is uploaded and you can login with telnet it means you have an orion based 2big vs1.

[fvdw]

I added some comments to my previous post

[thekarmola]

That means you have a 2big vs1.

When you are logged in via telnet. Run fvdwsl-programs and choose install firmware, in the menu select orion 2big1 as device.

Remark.
It is remarkable that you mention that kirkwood kernel is not uploaded. At least it should be uploaded and then fail to start as it is a kernel for a kirkwood based device.
Anyhow if the 2big1 kernel is uploaded and you can login with telnet it means you have an orion based 2big vs1.

Via the console uploaded
UIMAGE-26394-2BIG1-47-1-1-4-standalone image. Used by the console write image to disk. Succesfully logged in terminal via root and the password. Used command sl-promgrams at sayed in the how to and installed orion 2big vs1 with 0.0.04 uboot image. Choesed the option write firmware on a disk in the terminal. Everyting gooing fine and rebooted via reboot - f

No luck. Nas start up but can t see via my network and on the dhcp server.

[fvdw]

:disapprove Only writing a firmware image to a disk partition is not enough!
That action can only be used if a disk partition has gone corrupt.
For first install you must choose option "install firmware". Beside writing firmware images to several partitions it also prepare nas database and more. If you don't do that your nas will not be able to boot the firmware.

in fvdw-sl-program
choose option 1. Install fvdw-sl firmware on a hard disk

This will start fvdw-sl-installer

in fvdw-installer
choose option 7: lacie orion 2big vs1 with u-boot 1.1.4

and use msdos as partition table as uboot on a 2big1 is not able to read a disk with gpt partition table

[thekarmola]

:disapprove Only writing a firmware image to a disk partition is not enough!
That action can only be used if a disk partition has gone corrupt.
For first install you must choose option "install firmware". Beside writing firmware images to several partitions it also prepare nas database and more. If you don't do that your nas will not be able to boot the firmware.

in fvdw-sl-program
choose option 1. Install fvdw-sl firmware on a hard disk

This will start fvdw-sl-installer

in fvdw-installer
choose option 7: lacie orion 2big vs1 with u-boot 1.1.4

and use msdos as partition table as uboot on a 2big1 is not able to read a disk with gpt partition table

When i choose via the console install firmware, nas gooing off and dont come up after uboot and telnet can't connect it. But write image firmwaee option the nas come up and telnet works as wel.

[fvdw]

When i choose via the console install firmware, nas gooing off and dont come up after uboot and telnet can't connect it. But write image firmwaee option the nas come up and telnet works as wel.

1. First switch off your nas but still connected to LAN.
2. Then start fvdw-sl console and
3. choose install firmware,
4. select the correct standalone kernel.
5. After window with text waiting for uboot... appears then start your nas.
6. Wait for upload of kernel completed and telnet client to appear,
7 login with telnet
8. give command for fvdw-sl-programs

Did you exactly folliw this sequence.
Where in above sequence does your nas poweroff?