3.2 Beta for DS1511 Corrupt?

[adam1v]

I have tried upgrading to the 3.2 beta for my DS1511, have tried both downloading the beta file from my mac and PC, then uploading to the DSM and both occasions it starts the transfer, then halts stating that the upload file is probably corrupt.

Has anyone else found this, can anyone firm the firmware file is safe?

Adam

[deerpark]

I don't know if this is the case here but Synology recommends uploading the file over http, not https because the upload might fail. So if you haven't already, try http.

[adam1v]

Thanks for the advice.
Ive never had a problem in the past, but I will certainly give it a go later.

[adam1v]

Just checked and it was already being uploaded over http.

Something to point out, I currently have no Internet connection, could that affect anything?
Any advice from synology?

[steuben]

Just checked and it was already being uploaded over http.

Something to point out, I currently have no Internet connection, could that affect anything?
Any advice from synology?

I was having similar problems and Synology advised me thusly:

1. If the computer to connect has wifi, please disable it for the duration of the test.
2. Please set the IP address on your computer to 169.254.1.1. The subnet mask should be 255.255.0.0. It will not be necessary to set a default gateway or DNS address.
3. Please unplug the Ethernet cable from the DiskStation and wait for 30 seconds. Plug a straight through Ethernet cable into your computer's LAN port and the DiskStation's LAN port. Allow several minutes for the DiskStation to assign itself an IP address.

*Please note that you will not need to use a crossover cable for this.*

Then proceed with update via DSM.

If that does not work, You can try clearing your internet browser cache. Also verify that the update file is on the local hard disk.

I did none of this, however, because I reset my Synology (keeping the data intact) and then installed the .pat via Synology Assistant from 'scratch,' which worked.

[adam1v]

Thanks for your help.
Gave the instructions a try but got the same error :/

[adam1v]

Just put all the settings back, i.e the ip address back to normal and I can no longer browse the mapped shares.
There appears to be an issue resolving tge host name, ie \\diskstationname doesn't open the shares (when it did before), but \\ipaddress does show the shares.

Any ideas?

[adam1v]

To clear up the above post, the subnet mask was set to 255.255.0.0 (so was missing a .255).

Im still very keen to get the beta firmware installed, if anyone else has any other suggestions?

[mr-user]

Same issue here.
Eventually it worked !!!

Here is what happened to me:
- I applied the update about 6 times.
- Each attempt looked like it was successful but every time I checked teh DSM version it was still showing teh previous version of DSM (i.e. not the current BEAT version)
- I performed some reboots of the DS1511 via the DSM > RESTART command hoping this would somehow assist. I then re-applied teh updates to teh DSM-BETA. Still no good.
- I then decided to turn off teh DS1511 via the power button on front. Then turned power back on.
- The DS1511 then booted up and showed teh new version of the DSM-BETA.

Have now been using teh new DSM-BEAT for about a week.

Hope thsi helps.

[adam1v]

not really, as this would only get to "uploading the file" before giving the error message.
I've now searched a bit more and think it could be related to the lack of free space on the internal flash memory (im only guessing here).

Im not confident with telnet, but if it is a memory issue, i'll go through and delete some unused languages or something.

[adam1v]

Just ran df -h in telnet and there's 238mb free in dev/md0

I assume this is where it's trying to unpack the 174mb firmware?

Can someone tell me the necessary command to browse said directory, list all files and delete the unwanted?

Adam

[maxxfi]

To learn to use the CLI, you can read the wiki: http://forum.synology.com/wiki/index.ph ... ng_the_CLI

Basically, everything what you see after you type "cd /" is system partition, except the directory volume1, volume2, etc. which are mountpoints to data partitions.

I suggest that you start with "du -hs /var". /var is supposed to contain temporary (VARiable) data.
If the number that you get is not that big, scan all the directories with:
"du -hs /[a-u]*". This command will give you the size for each directory beginning with a letter from a to u.

Anyway, yes, 238MB is not much left, and IMHO it can cause problems. As you should have started with DSM 3.0/3.1, you should have at least 1GB of free disk for /dev/md0

[adam1v]

Maxx,
Var is less than 500kb, here's a screenshot

[adam1v]

This should work http://img856.imageshack.us/i/imagexje.jpg

[maxxfi]

Hm... I was expecting that /dev/md0 was about 2 GB of size, as it should be for DS installed with DSM 3.0 and newer. Or are those disks coming from an older NAS, like a DS409 ?
The values from 'du' command seem to be roughly ok, not much where you can trim any extra.