plugout.net

Hello

I have an NS2 which I've been using solely as a file-serving NAS, running laCie's native firmware (currently 2.2.8.4). I've been dithering over whether to install the fvdw-sl-console on it and with that in mind I downloaded ver. 14 in readiness - however didn't go further with it at that time. Now I've decided to go ahead, and have therefore today downloaded (latest) update fvdw-sl-15-3 But I now find myself completely stymied!

When (last November) I downloaded update 14 there was only one (.rar) file to download which I was able to unpack without any problem, and the 16 objects it contained included fvdw-sl-console.exe The download for update 15 has as you know 3 such files - named as parts 1, 2 & 3 - which have to be individually downloaded (I presume - at least, that's what I did). Unpacking these in order, when I reach part 2 I'm asked if I want to over-write the .bin file that was the only file in part 1; if I reply 'no' the unpacking aborts, if I reply 'yes' 7zip brings up an error-message "Data error in 'xfvdw-s1-15-3-nwsp2-30may2014.bin'. File is broken" - and still aborts!

Doubtless I'm missing some essential step that's obvious to everyone else and is probably staring me in the face, but to my inexperienced eye this behaviour is totally inexplicable. I would be most grateful if somebody could please explain to me what it is I have to do that I've failed to do?

Edit
I ought to have mentioned that I'm running Windows 8.1

I also don't like the 3 files approach.

Fuddyduddy wrote:Hello

I have an NS2 which I've been using solely as a file-serving NAS, running laCie's native firmware (currently 2.2.8.4). I've been dithering over whether to install the fvdw-sl-console on it and with that in mind I downloaded ver. 14 in readiness - however didn't go further with it at that time. Now I've decided to go ahead, and have therefore today downloaded (latest) update fvdw-sl-15-3 But I now find myself completely stymied!

When (last November) I downloaded update 14 there was only one (.rar) file to download which I was able to unpack without any problem, and the 16 objects it contained included fvdw-sl-console.exe The download for update 15 has as you know 3 such files - named as parts 1, 2 & 3 - which have to be individually downloaded (I presume - at least, that's what I did). Unpacking these in order, when I reach part 2 I'm asked if I want to over-write the .bin file that was the only file in part 1; if I reply 'no' the unpacking aborts, if I reply 'yes' 7zip brings up an error-message "Data error in 'xfvdw-s1-15-3-nwsp2-30may2014.bin'. File is broken" - and still aborts!

Doubtless I'm missing some essential step that's obvious to everyone else and is probably staring me in the face, but to my inexperienced eye this behaviour is totally inexplicable. I would be most grateful if somebody could please explain to me what it is I have to do that I've failed to do?

Edit
I ought to have mentioned that I'm running Windows 8.1

yes you are missing several things. ;)

Please note that the fvdw-sl console package is not the same as a fvdw-sl firmware upgrade package.

The fvdw-sl console
This is an application that runs under windows allowing you to connect to the nas and do several jobs like preparing the internal disk of the nas and install the firmware without removing it, or to interupt boot and talk to u-boot on the nas (the boot loader.
The fvdw-sl console you can download here viewtopic.php?f=7&t=1271

The fvdw-sl firmware upgrade package.
That contains only one file with extension .bin and must be uploaded using the web interface on a nas running the fvdw-sl firmware.
It upgrades the firmware on the nas to the one inside the bin file.

It seems you have downloaded the firmware upgrade pacakge, and of course that doesn't contain the fvdw-sl console

The split rar archive concept
The files of the packages are compressed in a rar archive. Because some users have poor internet connections downloading of big files fails for those. For that reason we split up the archive in chunks of max 25 MB (so three parts for the firmware upgrade package).
You have to download all three files (parts) and put them in a folder together. To extract the archive you only need to open one of these files (not important which one). The extractor will recognize that this archive consist out of three (or more) parts and unpack all files automatically and reconstruct the original file.

Thats why you get the question if you want to overwrite the .bin file. When you unpacked the first file it already extracted the others as well and produced the .bin file. When you then opne the other file and do this agai..well it is obvious.

(You could have know if you had taken time to read on the internet about rar archives and how to unpack them)

Hopefully it is clear now

wd9895 wrote:I also don't like the 3 files approach.

I know wd9895 that you don't like that but it is for a reason, several users seem to have problems to download the big files (bigger then 30 MB), Therefor we split them in rar archive consting out of three parts to avoid numerous requests to sent a split archive to those users.
Personally I think downloading three files instead of one is not a real big job. On my internet connecting it takes less then 10 seconds.
Unpacking is same as with one file just unpack one file of the split archive, it will unpack the other ones automatically

@fvdw

Many thanks for responding so promptly.

(You could have know if you had taken time to read on the internet about rar archives and how to unpack them)

Fair point. As it happens I've never had occasion to use .rar files myself (I use 7-Zip) and don't recall having had to deal with a 3-part one before; still, as you say, I could have googled "rar"... I've now done so and will know what to do next time, especially this:-

...just unpack one file of the split archive, it will unpack the other ones automatically

Unfortunately, having now progressed to the installing stage I've come to a shuddering halt at the point where the install is supposed to begin.

Instruction #7 (in the fvdw console's 'Info' window) says "Log in using the telnet client with username...and password...". On my screen an empty cmd console has appeared (in the title-bar is "DTelnet"), but all my attempts to use it to connect to the NS2 have been fruitless. Simply typing into the cmd console evokes no response whatever, and each time it just times-out.

What am I failing to see this time?

EDIT
And I've subsequently found my NS2 to be entirely inaccessible, either from the Lacie web interface or physically (ie by trying to switch it off by means of the power-button on the rear). It just stays on, and cannot be reached either through 'Map/Disconnect network drive' in Windows Explorer.

Should I attempt a factory reset? Help would be most welcome.

Hi

I'm frozen into complete inactivity whilst I await hoped-for guidance.

Can someone please come to my rescue? Please...?

Hi Fuddyduddy,

About the unavailable telnet login, these points may solve your issue:
- disable your firewall on your PC (or the firewall feature of your antivirus)
- check if you use as LAN IP : 192.168.0.xxx or 192.168.1.xxx
- check if the DCHP server is available from your router (usually is your ISP box)
- Disable all NIC card on your PC except for this one used (wireless or wire NIC)

Note: the NAS Ip when you use fvdw-sl console is 192.168.(0/1).252

in addition to jocko's inputs.

Do not use a wireless connection between pc and lan. Seems that the tftp server of u-boot has problems with wireless transfer.

I assume you have chosen as action "Install fvdw-sl firmware" in the fvdw-sl console

What was the output of step 5. Did the kernel actually load ?
You should have seen something like this in the u-boot window before it disappears (the ip addresses shown will be different in your case)

Code: Select all

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

after that it should have shown something like this that the kernel was loaded and started

Code: Select all

Marvell>> bootm
bootm
## Booting image at 00800000 ...
   Image Name:   Linux-3.9.5
   Created:      2013-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 ...

After that the u-boot window should close and telnet client window shoul automatically popup and it will try to connect to the nas.

So please explain more detailed what you are doing and what results you got then we can offer more effective support ;)

Hi

Many thanks both for your responses.

So please explain more detailed what you are doing and what results you got then we can offer more effective support ;)

I'll do my very best...

But first, there's something that's confusing me which I need to get completely clear. In the instructions for installing the firmware, under "ip address NAS and telnet server" three alternative addresses are listed to choose among. The first two are when devices in the LAN start with 192.168.1.xxx or 192.168.0.xxx; mine start with neither, because my Buffalo Air-Station router's 'DHCP Address Pool' is from 192.168.11.2 for up to 64 addresses (note: '.11.' not '.1.' or '.0.'). I therefore concluded that I must choose the third alternative "Address assigned by your DHCP server" (although in fact my NS2's address is fixed, having been assigned by me).

Was this correct? I note that Jocko tells me to check that the IP address I've used is one of the first two choices only.

fvdw wrote:I assume you have chosen as action "Install fvdw-sl firmware" in the fvdw-sl console

Yes

What was the output of step 5. Did the kernel actually load ?

I don't know for sure whether the kernel loaded but I believe it did. After selecting the UIMAGE file at step two and turning on the NS2 when it signaled it was waiting for u-boot it began flashing (including one or more - couldn't tell exactly - red flashes) then the command window closed itself (I think), and then the telnet client (DTelnet) popped up.

EDIT
I don't remember what was the output of step five (sorry!) - ie whether or not the u-boot window showed the display you illustrated.

After that the ... telnet client window shoul automatically popup and it will try to connect to the nas.

I certainly don't recall this happening.

That's where I came to a grinding halt. It just sits there, dumbly.