I’ve tried this update from my Sharespace 4 times now without success. I’m currently on 2.1.92. On each attempt the download reaches 100%, but when I choose to update I get the message :
The firmware image is not valid. Please use a valid firmware image.
Thanks for your help, Gondek. I’ve downloaded the firmware directly, but still no joy.
I bought a 2TB originally, added 2 more drives to give me 4TB, then converted to Raid 5. Maybe there’s an issue with the internal model number, since the firmware filename seems to be specific to your model.
I’m trying a Restore Factory Defaults to see if it builds the configuration correctly before I retry the firmware. Just 1008 minutes to go
Gondek thanks for the update awsome !!! installed the update , the ntfs file system for external usb drives as i needed and saw in the update works fine , testing and other functions as raid 5 4*2tb wd drives 11/2 day to finish then see how things go .
Just got to say thanks for posting that firmware update.
I was getting the ‘path not found’ error everyone else seems to have with the Sharespace and read the solution might be 2.2.9. Then I got ‘connection refused’ error when trying to update firmware.
I was ready to kick the box around the room when I found your post. After clearing the thumbnails in Twonky as advised by WD, I uploaded the firmware, let it update, and everything seems to be working again (although I’m still getting ‘connection refused’ with the firmware update).
Once again, BIG THANKS.
PS. However you did it, please do it again with the next update. It’s the only way I’ll ever get it.
Ok, time to fess up. I finally found that I was the main reason for this problem. After much puzzling over the update scripts and test running sections on /DataVolume I learned that the message was telling me that it ran out of disk space! I had previously done a test install of TwonkyMedia 5.1.2, and made the mistake of installing to /opt instead of using a folder on /DataVolume, so had some 40MB of redundant data in /.
I thought the reset to Factory Defaults would have sorted this, but despite clearing and rebuilding the raid array, it only overwrites files on /, doesn’t delete any extraneous files.
Hope this helps anyone else who has meddled in their ShareSpace beyond their Linux capabilities