plugout.net

I tried to install on SPD8020 Firmwareupgrade fvdw-sl-9-0 but do get the following message

Datei hochgeladen.
Fehler:

Any glimpse?

Actual firmware installed:
fvdw firmware version 5.1 release 16 oct 2009

thank you for support
Kind regards
Frank

edit fvdw 24 nov 11
I checked out why people can have this problem. All were with versions below fvdw-6-0 and got the error message:file uploaded. error !

I found the reason. This is because in firmware upgrade menu of versions befor 6-0 more checks were then done then in the newer versions. To pass these test in the old version the upgrade package needs another file that is no longer include since version 9-0. This because in the newer versions the not necessary checks are taken out and this extra file is no longer needed
I forgot about this change :mrgreen: , sorry for the inconvenience. I added an extra version in the download section of the spd8020 fvdw-sl-10-1 release that can be used by user that still have 5-1 or lower running to be able to upgrade in one step.
viewtopic.php?f=7&t=234&p=1481#p1481

the only reason can be that you uploaded a corrupt file or not the right one, you must unzip the archive first and upload the file with extension .bin

well. I downloaded now the third time as I had this idea of corrupted file myself but still I try to upload the .bin file and it shows the same error.
I see in bottom line of internet explorer that system_upgrade.php is started. The process indicator is indicating until approx. mid term that something is uploading. Then it stalls for about 1 minute and the NAS is not responding anymore and at the bottom line ""waiting for http:/nas-ip/system/system_upgrade.php appears together with the error message as described.
Does the uploaded Zip of fvdw-sl-9-0 is really non corrupted? I do not have corruption issues with all my other downloads...
Puzzled...
rgds
Frank

No the file is not corrupt otherwise more people would have complained about it.
I have seen a similar problem in the past on spd8020's that had a deviating partition structure. It appeared that there is a serie out there having system partitions with size of only 100 MB for the firmware. The normal size is about 256 MB. When trying to upload the firmware and write it to a too small partition the same error happened as you describe.
But then you should have problems already with version 4.2 or above. You mentioned you have 5-1 installed, so this is strange

How experienced are you with putty and linux ?

well i'm not an expert but i can read and follow instructions. I installed e.g. different mediaserver to my iomega ix2 cloud. there i had to use putty and some other linux commands. let's put it that way... i know how to handle delicate matters... so if there would be lead where to look for the right settings and some trial and error advice would be appreciated.
rgds
frank

ok first check to be made is to check partition structure

login via ssh with putty and give the command

Code: Select all

fdisk -l

and report the output here

It should list the partition structure, it should look like this

Code: Select all

/ # fdisk -l

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

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1          32      257008+ 83 Linux
/dev/sda2   *          33          64      257040  83 Linux
/dev/sda3              65          96      257040  82 Linux swap
/dev/sda4              97      121601   975988912+  5 Extended
/dev/sda5              97         144      385528+ 83 Linux
/dev/sda6             145      121601   975603321  83 Linux
/ #


sda1 and sda2 should be 32 cylinders in size

ps the size of sda6 is dependent on the hard disk you have inside

--edit I checked the firmware upgrade file (spd8020), I downloaded it just now unpacked it and also unpacked the bin file (its a gz archive) to check md5 checksum of the disk image of the firmware. It gave the correct result, this means the file I downloaded was not corrupt

Now here the report.
As it seems you a 1TB drive installed where I instead run a 500Gig set.
Firmware 1.2.9.fw fvdw 5.1

~ # fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 32 257008+ 83 Linux
/dev/sda2 * 33 64 257040 83 Linux
/dev/sda3 65 96 257040 82 Linux swap
/dev/sda4 97 60801 487612912+ 5 Extended
/dev/sda5 97 144 385528+ 83 Linux
/dev/sda6 145 60801 487227321 83 Linux
~ #

rgds

mmm...thats the correct output, so as expected this disk should be able to install fvdw-sl-9-0

Then the only explanation I can think of is that something is damaged in the running firmware.

Instead of the using the webinterface you can do the upgrade manually.
In the download section you can find a a package for preparing new hard disk viewtopic.php?f=7&t=130
Download the file fvdw-sl-9-0-phn-spd8020-HDD-install-package.zip
This archive contains a disk image fvdw-sl-9-0-phn-6sept2011.img size about 156 MB
You can check if is corrupt or not by checking md5 checksum of the file and compared that with the number in the MD5 file

Basically the manual install is that we will write this disk image to a system partition and that we change the boot settings to use at boot the partition were we have written this image to.

Now the star behind sda2 in your fdisk -l output means the system is booting from partition sda2, so we must write the disk image to sda1. To do this copy the disk image file fvdw-sl-9-0-phn-6sept2011.img to a share on the nas, for example create a share using the web interface with name "fvdw".
Now connect to the nas via ssh using putty and write the disk image to partition sda1 using this command

Code: Select all

dd if=/share/1000/fvdw/fvdw-sl-9-0-phn-6sept2011.img of=/dev/sda1

This only works if you have put the image in the share with name "fvdw"
It will take some time to execute and complete the dd command.
Be sure you entered the command correctly, "dd" is a powerful command thta when used wrong easily can destroy data on your disk on a place that was not intended.

When finished it will mention xxx records in and a line with xxx records out with xxx being a number the numbers in both lines should be the same

Now change partition to use for boot. This can be done as follow

enter in putty the command

Code: Select all

fdisk /dev/sda

This will sstart fdisk and a command line will appear to give fdisk commands.
on the command line of fdsik enter the command : a
it will respond with "enter a partition number"
enter the number: 2
enter again the command: a
enter now partition number : 1

Now enter the command : p
It will list the partition table and now the * should be behind sda1 and not anymore behind sda2
if you have that result then
enter the command: w
this will write the changes to the the partition table and close fdisk
If you do not use the w command and exit fdisk then the changes will not be made
Its easy to check if the changes are made by starting up fdisk again and use the p command.

It should look like this

Code: Select all

...
   Device Boot      Start         End      Blocks  Id System
/dev/sda1   *          1          32      257008+ 83 Linux
/dev/sda2             33          64      257040  83 Linux
/dev/sda3     

If everything is fine then close putty and reboot the spd8020 and keep your fingers crossed if it boots. it then should come up with the new firmware.

success, fvdw

success!
did as mentionend and with a charm the new fw was loaded.
many thx for your support.
kind regards
frank

glad to hear you got it working Frank :ugeek: