upgrade to xfvdw-sl-14-0-nwsp1-23dec2012 from 10-1 failed

[favroom]

Hi Everyone,

Yesterday, I installed fvdw for the first time on my LaCie Network Space V1.
My partition table differed a little bit from the manual:

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System
/dev/sda1 2048 514079 256016 83 Linux
/dev/sda2 514080 1028159 257040 83 Linux
/dev/sda3 1028160 1542239 257040 82 Linux swap
/dev/sda4 1542240 1953520064 975988912+ 5 Extended
/dev/sda5 1544288 2313359 384536 83 Linux
/dev/sda6 2315408 2329424 7008+ 83 Linux
/dev/sda7 2331473 2859569 264048+ 83 Linux
/dev/sda8 2861618 1953520064 975329223+ 83 Linux

I have SSH access and Twonky and Transmission are running fine.

Now I tried to upgade to xfvdw-sl-14-0-nwsp1-23dec2012, but failed!

I am using Chrome on Mac OSX to upload the firmware image using the webinterface.

The error message:
Firmware upgrade step 2 started...
Firmware upgrade failed, upgrade process aborted, reason:
fw upgrade could not unpack firmware package, not a valid format

Any ideas?

[fvdw]

did you unzip the upgrade file you downloaded ?

[favroom]

did you unzip the upgrade file you downloaded ?

Yes, I did.

But what file do I need to select in the webinterface?
There's no firmware.bin, so I uploaded xfvdw-sl-14-0-nwsp1-23dec2012.img
Do I need to rename that file to firmware.bin?

[fvdw]

when downloading an upgrade file and unzipping it you get a bin file with same name but with extension "bin" thats the one you need to upload

[favroom]

when downloading an upgrade file and unzipping it you get a bin file with same name but with extension "bin" thats the one you need to upload

Hi, thanks for your support.

I used this link from the post to download the latest firmware:
--edit link removed-fvdw

That's a zip file that doesn't hold a .bin...

[fvdw]

I downloaded it and it contains the bin file :tapfoot

zip.JPG

[favroom]

I downloaded it and it contains the bin file :tapfoot

zip.JPG

I switched to my Windows8 laptop. Downloaded and extracted the zip. Now I got a .bin file!

Later tonight I will try that .bin file and post here if I succeeded in upgrading the Network Space V1.

Thanks again!

[favroom]

I downloaded it and it contains the bin file :tapfoot

zip.JPG

I switched to my Windows8 laptop. Downloaded and extracted the zip. Now I got a .bin file!

Later tonight I will try that .bin file and post here if I succeeded in upgrading the Network Space V1.

Thanks again!

The upgrade with the unzipped .bin from my Windows8 laptop seemed to be more succesfull. But the reboot resulted in a NWS1 unreachable on it's original address...
When I started the upgrade, everything seemed fine. I got to the third fase, the reboot. Submitting that step did not reboot the NWS1, so I tried to turn the NWS1 off with the switch. Didn't work either in 5 - 10 minutes so I pulled the powercable. After the powercycle I could't reach it anymore...

I dont't think it received a new address from my dhcp server, so I guess I have to hook it up to my laptop again en format the harddisk and start over...

[fvdw]

that should not be necessary. Does the blue flicker with HDD activity when booting ?

Most of the time the problem is that the workgroup you have set on the nwsp1 is not the same as used by your PC. then you can not access it. I would try ip scan to find it

[favroom]

that should not be necessary. Does the blue flicker with HDD activity when booting ?


Yes, the blue light flickers on startup and stops flickering after a while. It is now on.


Most of the time the problem is that the workgroup you have set on the nwsp1 is not the same as used by your PC. then you can not access it. I would try ip scan to find it

I was not trying to connect to it using the Windows workgroup. I tried SSH on the ip address that I manually configured on 10-1, but could not connect. It's not on that ip address anymore.