manfriday Posted April 23, 2015 #1 Posted April 23, 2015 Has anybody tried update 5 yet, if so what is the 411? Quote
jundar Posted April 23, 2015 #2 Posted April 23, 2015 XerSonik did that. Please look at bottom of page in Russian section using the link below: viewtopic.php?f=5&t=3059&start=1580 No idea about 411, sorry Quote
manfriday Posted April 23, 2015 Author #3 Posted April 23, 2015 on phone dial 411 = information. dial 911 = emergency Quote
manfriday Posted April 23, 2015 Author #4 Posted April 23, 2015 thanks jundar - Update 5 works fine, no special requirements, just let system do the work Quote
wakkawakka Posted April 23, 2015 #5 Posted April 23, 2015 anyone can confirm this is clear to install/update from 5.1-5022.4 ? Quote
manfriday Posted April 23, 2015 Author #6 Posted April 23, 2015 anyone can confirm this is clear to install/update from 5.1-5022.4 ? I thought I did but if you missed it. All Clear Current DSM version: DSM 5.1-5022 Update 5 DSM date: 2015/04/22 Status: Your DSM version is up-to-date. Quote
wakkawakka Posted April 23, 2015 #7 Posted April 23, 2015 And you did the update from within your current xpen rig using the built-in update feature? Quote
wakkawakka Posted April 24, 2015 #8 Posted April 24, 2015 Huh... I tried to do this and my rig is saying, in red text at the Control Panel / DSM Update tab: Insufficient capacity for this update. The system partition requires at least 350 MB. I have 2x 2TB in here as basic disks, each has well over 500GB free........... what gives? How can I check to see what XPEN thinks my "system partition" is?? I did have a 64GB SSD in at one point but have since removed it so all I have are the 2x 2TB SATA's connected to my onboard SATA controller. Quote
Thecapri Posted April 24, 2015 #9 Posted April 24, 2015 i just did the update all is fine for me also Quote
wakkawakka Posted April 24, 2015 #10 Posted April 24, 2015 Shoot... Trying to troubleshoot this. Same error persists. Where I am looking to see what xpen thinks is my system drive? I originally had 64GB SSD which was Volume 1 which has since been removed. I have 2x 2TB Volume2 and Volume3 i do not have a Volume 1. What file am I looking to edit to fix this? Quote
holybabel Posted April 24, 2015 #11 Posted April 24, 2015 Update works fine for me. No restart, everything is ok. Quote
sony21 Posted April 24, 2015 #12 Posted April 24, 2015 updated without problems. all seems ok for me too. Quote
leejbarker Posted April 24, 2015 #13 Posted April 24, 2015 Can I update this with normal boot or should I boot using install / update path? Quote
WiteWulf Posted April 24, 2015 #14 Posted April 24, 2015 Just a quick /me too for all working installed through the web interface. I tried it on a virtualbox VM first to check then installed for real on my HP Microserver Gen8 Quote
leejbarker Posted April 24, 2015 #15 Posted April 24, 2015 Worked for me... Web interface... Didn't even restart! Quote
aneelley Posted April 24, 2015 #16 Posted April 24, 2015 I just did this on my backup Xpenology server. Did it through the GUI like normal. Didn't have to reboot. All is working fine. I also rebooted afterwards for good measure. I can confirm everything looks to be in order. Quote
wakkawakka Posted April 24, 2015 #17 Posted April 24, 2015 Congrats to those who were able to update just fine. In my case I was not able to do so. I went ahead and unplugged my 2x 2TB drives (which had version 4) and put in an SSD. Formatted SSD and did a clean install from scratch, was able to successfully upgrade to 5. I plugged my 2x 2TB back in (they are basic disks, not in a raid) and the system went BACK to version 4 and when I tried to update again got same error message as before. Any ideas? How was I able to get a new install done on the SSD, successfully upgrade to version5, but as soon as I plug the old sata drives back in the system "downgraded" itself to v4 and wont let me update? Surely someone else has hit this snag? ANY input is appreciated.. I really don't want to backup all the data to other drives and redo the whole NAS. Quote
aneelley Posted April 24, 2015 #18 Posted April 24, 2015 (edited) I had bad results when I tried to even use a SSD as a separate volume. It locked the system up solid and I had to reboot and it would never get to a login prompt. I wound up having to boot with a Ubuntu flash drive and use the shred command to shred a few sectors on every disk and then reboot with the xpenology boot loader flash drive. I only use a SanDisk Cruzr flash drive for booting. Not a SSD. I should also note that my flash drive is 16GB in size. Edited April 24, 2015 by Guest Quote
marius.tranzistor Posted April 24, 2015 #19 Posted April 24, 2015 Working great! Sent from my iPhone using Tapatalk Quote
JMRR Posted April 24, 2015 #20 Posted April 24, 2015 i have the same problem. it says it need more capacity for update. Quote
wakkawakka Posted April 24, 2015 #21 Posted April 24, 2015 JMRR - Did you make any changes to the drives after initial install? In my case I had SSD as vol1 and 2tb vol2 2tb vol3. I removed the vol1 ssd awhile back and that is what caused my problems. I did a clean install but as soon as i put my 2tb drives back in my system downgrades itself to v4. Quote
JMRR Posted April 25, 2015 #22 Posted April 25, 2015 i didnt, the setup is the same from the beginnig. Quote
jice Posted April 25, 2015 #23 Posted April 25, 2015 JMRR - Did you make any changes to the drives after initial install? In my case I had SSD as vol1 and 2tb vol2 2tb vol3. I removed the vol1 ssd awhile back and that is what caused my problems. I did a clean install but as soon as i put my 2tb drives back in my system downgrades itself to v4. Hi, I'd got lot of issues when i tried to remove vol1 (photostation database, etc...) (vol 1 = 250 GB, vol2 = 2*2 TB). I'd backup the data of vol2 on another disk, format the 2TB disks and restart from the beggining... Good luck... Quote
DracoR Posted April 26, 2015 #24 Posted April 26, 2015 Congrats to those who were able to update just fine. In my case I was not able to do so. I went ahead and unplugged my 2x 2TB drives (which had version 4) and put in an SSD. Formatted SSD and did a clean install from scratch, was able to successfully upgrade to 5. I plugged my 2x 2TB back in (they are basic disks, not in a raid) and the system went BACK to version 4 and when I tried to update again got same error message as before. Any ideas? How was I able to get a new install done on the SSD, successfully upgrade to version5, but as soon as I plug the old sata drives back in the system "downgraded" itself to v4 and wont let me update? Surely someone else has hit this snag? ANY input is appreciated.. I really don't want to backup all the data to other drives and redo the whole NAS. Change boot order in the BIOS? Since one of your 2TB disk still contain update 4 and your BIOS might redirected to that disk as primary boot device. Atleast this is only if you have installed the previous synology on one of those Quote
Jman420 Posted April 26, 2015 #25 Posted April 26, 2015 Congrats to those who were able to update just fine. In my case I was not able to do so. I went ahead and unplugged my 2x 2TB drives (which had version 4) and put in an SSD. Formatted SSD and did a clean install from scratch, was able to successfully upgrade to 5. I plugged my 2x 2TB back in (they are basic disks, not in a raid) and the system went BACK to version 4 and when I tried to update again got same error message as before. Any ideas? How was I able to get a new install done on the SSD, successfully upgrade to version5, but as soon as I plug the old sata drives back in the system "downgraded" itself to v4 and wont let me update? Surely someone else has hit this snag? ANY input is appreciated.. I really don't want to backup all the data to other drives and redo the whole NAS. I hate to be the bearer of bad news, but you may have potentially corrupted your entire setup. I accidentally ended up in a similar situation with QNAP software (through a very similar process). While these systems support hot-swapping and replacing hard drives, I do not recommend doing so with the hard drive hosting your System Volume. This tends to get installed on the hard drive set as Master in the BIOS (and I would assume that the SSD was the one you used originally). By installing Update 5 on the SSD and then putting the SATA drives back you have removed the volume which has Update 5 installed on it and are now booting from the volume with Update 4. This could either be a result of your BIOS Settings or the Jumper Settings on the Hard Drives themselves (some hard drives allow you to specify Slave/Master by sliding little plastic covers over pins). The best option I can suggest is to backup as much of your data as you can, re-format the drives you intend to use in your NAS and start from scratch. An alternative, although I'm not sure if it will turn up anything useful, is to SSH into the server before trying to install Update 5 and run this command: tail -f /var/log/messages This should show any output from the Update process and may give you some more insight into what is actually going wrong. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.