first installation, can't make it !

[chapy23]

I did read but you probably see that english is not my first language.
So, i'm having some difficulties to understand everything.
French for those type off "hack" don't really exist (it's OK).

Now, how can i be sure that my nwsp2 is lite ?
Can i see that somewhere in the web interface of fvdw-sl firmware version 15-2 ?
I'm not sure, i'm ready to flash u-boot without the help of someone.
Is there any place like IRC(live chat) that i can have ressource people (guru like you) to help ?

thank's again for help and reply.

chapy23

[chapy23]

It looks like i have a classic :-(

glad to have 256 of ram but difficulty to flash bootloader ;-(

any help would be well receive !

bye

chapy23

[fvdw]

be happy, the classic is the better device ;)

The fvdw-sl console has an option to write an updated u-boot version to flash, it also has a hep page describing how to do it
Use wired connections to connect the pc running the console and nas to the lan DO NOT use wireless.
Remember flashing is at own risk.

To check if you need to flash you can do following
Boot the nas with the firmware, connect to the nas via ssh using a ssh client like Putty (username : root password: giveit2me
At the command line give as command

Code: Select all

dmesg  | grep console

you will get some lines output, post that output here or check if it contains cap=gpt,lba64
If it contains that then there is no need to write a new u-boot version to flash. If it doesn't then..well it is obvious I guess

[kevin39]

What is the interest of updating the u-boot ?

[fvdw]

What is the interest of updating the u-boot ?

on the nwsp2 classic enabling support for disks > 2 TB in the boot loader

[kevin39]

Ok, thanks

[chapy23]

root@LACIE-NAS:/ # dmesg | grep console
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=ASTON_KW
[ 11.785096] console [ttyS0] enabled
[ 12.443702] console [netcon0] enabled
[ 12.447350] netconsole: network logging started

not seem to have cap=gpt,lba64 support :-(

the only thing that i'm not so happy about flashing the u-boot is that from the start i'v try to update my LaCie drive.
I'm not able to communicate with it using fdw-console :-(
(remember, always stuck at the "freeing init memory!!!")

I read a old post from you and your talking about using standalone kernel.
I'm pretty sure i'v try that with same result.

bye

chapy23

[fvdw]

remember, always stuck at the "freeing init memory!!!")

yes thats normal for the the standalone kernel. I t means it is ready and loaded.
However how did you start the standalone kernel. You must use the task load standalone kernel in the console
If you do that you normally do not see the net console output but the u-boot window closes automatically and after 12 seconds a telnet client will be started that will allow you to connect to it (ps you firewall setting could block it).
So you must have done something different

To flash u-boot the standalone kernel is not used but the u-boot console of the fvdw-sl console.
That uploads the new u-boot image and write it to flash

[chapy23]

Let me try to explain what is happening

First here my setup

lacie = 192.168.2.9
windows7 = 192.168.2.6
a ping give me reply as the lacie is up running with fwdl-15.2

now i start fwdl-console with Action - Standalone kernel load and start
i then power off and power on the lacie.
there is a netconsole screen running waiting for 192.168.2.9
after 2-3 seconds, lacie led blink red and blue and the netconsole screen react.
couple of line going there: serverip$ and tftp program load automaticly and transfer the UIMAGE i choose: UIMAGE-395-NWSP2CL-179-standalone
then all those windows close, from that time i have to tell you that i lost the ping reply from 192.168.2.9 (the lacie)
after (yeah 12 seconds) telnet screen trying to connect to 192.168.2.9 and timeout.
probably normal as the lacie is not responding with his IP anymore.

anything i do wrong in all the step above ?

quick question, if i can successfully "talk" with my lacie (fdwl-console) can i flash u-boot immediatly ?
i mean, is the 1TB drive will work also with that new bootloader ?
so when i receive my new 4tb drive, i will be ready :-)

thank's

bye

chapy23

[fvdw]

Let me try to explain what is happening

First here my setup

lacie = 192.168.2.9
windows7 = 192.168.2.6
a ping give me reply as the lacie is up running with fwdl-15.2

now i start fwdl-console with Action - Standalone kernel load and start
i then power off and power on the lacie.
there is a netconsole screen running waiting for 192.168.2.9
after 2-3 seconds, lacie led blink red and blue and the netconsole screen react.
couple of line going there: serverip$ and tftp program load automaticly and transfer the UIMAGE i choose: UIMAGE-395-NWSP2CL-179-standalone
then all those windows close, from that time i have to tell you that i lost the ping reply from 192.168.2.9 (the lacie)
after (yeah 12 seconds) telnet screen trying to connect to 192.168.2.9 and timeout.
probably normal as the lacie is not responding with his IP anymore.

anything i do wrong in all the step above ?

the standalone kernel is assigning ithe nas two ip adresses 192.168.0.252 and 192.168.1.252
It also tries to get a dynamic one from the dhcp server in your lan but that might fail, it also might be different from 192.168.2.9 you need to check which ip has been assigned by your dhcp server (router).
This problem can be avoided by adapting your lan settings to let router use 192.168.0.xxx or 192.168.1.xxx range for ip addres and use for the nas 192.168.0.252 or 192.168.1.252 as ip.

Please note that when ip pool used by your dhcp server is 192.168.2.xxx and if it uses the standard net mask then it can see ip's outside the 192.168.2 range

quick question, if i can successfully "talk" with my lacie (fdwl-console) can i flash u-boot immediatly ?

if the u-boot console of the fvdw-sl console works ok (it does otherwise you could not load the standalone kernel), then the answer is yes

i mean, is the 1TB drive will work also with that new bootloader ?

yes the new one is also able to handle disk smaller then 2 TB. In fact it then will support disks with ms-dos partition table (for disk < 2TB) and disks with gpt partition tables (for disks > 2 TB but also < 2TB).
The old bootloader only support disks with ms-dos partition tables
so when i receive my new 4tb drive, i will be ready :-)

thank's

bye

chapy23[/quote]