pm1982 Posted June 27, 2015 Share #51 Posted June 27, 2015 You have to downgrade and do not install update 2. Quote Link to comment Share on other sites More sharing options...
nick w Posted June 27, 2015 Author Share #52 Posted June 27, 2015 Got to be hardware related. Nic drivers? Sent from my Nexus 6 using Tapatalk Quote Link to comment Share on other sites More sharing options...
knightshade Posted July 1, 2015 Share #53 Posted July 1, 2015 Same problem here with a N40L. I'm on 5.2-6555 update 2 and: -My NAS is invisible for synology assistant -my windows share wasn't working, had to power off/on SMB service -ressource monitor isn't working Don't know what to do. I've not noticed teh issue with Synology assistant, but haven't really tried. I did have the issue with SMB Resource monitor isn't working correctly AND I noticed a lack of event emails coming from the system (This is the most troublesome) Toying with the best approach... Considering a clean install. I"m on a N54L, so those theorizing that the issues are on the N40L would be guessing wrong. Quote Link to comment Share on other sites More sharing options...
pm1982 Posted July 1, 2015 Share #54 Posted July 1, 2015 I'm on 5.2-6555 (HP N40L) for about a week and I see that everything is working well: WoL, hibernation, resource monitor, SMB, Synology Assistant etc. There must be something wrong between XPEnology loader and 5.2-6555 Update 2. Quote Link to comment Share on other sites More sharing options...
knightshade Posted July 7, 2015 Share #55 Posted July 7, 2015 I thought that I would post an update in case others are having similar issues. I downgraded to 5.2-5565 and the issues seemed to all be resolved. I then upgraded to 5.2-5565 Update 1, and the issues re-introduced themselves. So I've again downgraded to 5.2-5565 Once downgraded: - My NAS is again visible for synology assistant - my windows share is available upon boot (no need to cycle the off/on the SMB service) - resource monitor is working again - SSH is available upon boot - Notificaiton emails are working ok - Time between boot and the Web interface being available seems reduced Now that 5.2-5592 is out, I think that I'm going to sit tight for a bit - and see what happens. Quote Link to comment Share on other sites More sharing options...
nick w Posted July 8, 2015 Author Share #56 Posted July 8, 2015 Knightshade. Is that a n40l or n54l? Thanks n Sent from my Nexus 6 using Tapatalk Quote Link to comment Share on other sites More sharing options...
gus84 Posted July 8, 2015 Share #57 Posted July 8, 2015 Knightshade, can you describe the process used to downgrade from 5.2 6656 U2 to the 5.2 6656 Quote Link to comment Share on other sites More sharing options...
knightshade Posted July 8, 2015 Share #58 Posted July 8, 2015 Knightshade. Is that a n40l or n54l? HP ProLiant G7 N54L MicroServer Knightshade, can you describe the process used to downgrade from 5.2 5565 U2 to the 5.2 5565 High level, I followed this guide: xpenology.me/how-to-downgrade-from-dsm-5-2/ log in as root at the console Edit /etc.defaults/VERSION (using vi at the console) Set the line minorversion=”1" and buildnumber=”5021" (I suspect any number less than 5565 would have actually worked) Reboot, selecting install/upgrade Once the NAS has rebooted, I did an installation of DSM 5.2-5565 pat file as a manual installation, and used “migration” to keep my accounts and settings Once installed, Control Panel -> "Update & Restore" -> DSM Update -> Update Settings -> uncheck "Check for DSM updates automatically" Quote Link to comment Share on other sites More sharing options...
knightshade Posted July 27, 2015 Share #59 Posted July 27, 2015 I thought that I would share an interesting twist.... I upgraded my second XPEnology box (to 5.2-5565), applied no Updates - and am seeing some of the same issues. So - it is "interesting" that downgrading resolved my issues previously... But it would appear that the "cause" may not in fact be the updates. I read that 5.2-5592 is forthcoming - so it will be interesting to see what results from that in comparison. Quote Link to comment Share on other sites More sharing options...
nick w Posted July 28, 2015 Author Share #60 Posted July 28, 2015 I thought that I would share an interesting twist....I upgraded my second XPEnology box (to 5.2-5565), applied no Updates - and am seeing some of the same issues. So - it is "interesting" that downgrading resolved my issues previously... But it would appear that the "cause" may not in fact be the updates. I read that 5.2-5592 is forthcoming - so it will be interesting to see what results from that in comparison. Yeah. Would be interesting when we get 5595 5.2 bootloader Sent from my Nexus 6 using Tapatalk Quote Link to comment Share on other sites More sharing options...
knightshade Posted July 31, 2015 Share #61 Posted July 31, 2015 I'm still playing - but thought that I would post initial results (same on 2 N54L's) NAS #1: Boot to new bootloader Migrate: 5.2-5592 (Working - visible in Synology Assistant & working resource monitor) Apply Update 1 (Still Working) Set Static IP address Reboot No longer visiable in Synology Assistant Broken Resource monitor (0%, bars at center) Downgrade (Migrate): 5.2-5592 (Working) Set Static IP address (visible in Synology Assistant & working resource monitor) Reboot !! No longer visible in Synology Assistant Broken resource monitor NAS #2: Boot to new bootloader Migrate: 5.2-5592 (Working - visible in Synology Assistant & working resource monitor) Set Static IP address (Working - visible in Synology Assistant & working resource monitor) Reboot No longer visiable in Synology Assistant Broken Resource monitor (0%, bars at center) Still experimenting - but same issues appear to remain. Quote Link to comment Share on other sites More sharing options...
knightshade Posted July 31, 2015 Share #62 Posted July 31, 2015 Simple case: NAS #2: set to DHCP, Applied Setting Resource Monitor Started to work! Set back to static IP, Applied Setting Resource Monitor still working Reboot: Synology Assistant still showed nothing. Resource Monitor broken again Nas #1: (I played a bit more here, but no more success) IPv6 Set to "Off" IPv4 Uncheck "Enable Jumbo Frame" Apply Still Broken Reboot Still Broken ??Noticed "Enable Jumbo Frame" is checked again.... set to DHCP, Applied Setting Resource Monitor Started to work Synology Assistant still showed nothing. Rebooted again Synology Assistant still showed nothing. Logged in at console. NO IP address assigned! 2: eth0: mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:11:32:xx:xx:xx brd ff:ff:ff:ff:ff:ff ifconfig eth0 down dhclient -r eth0 dhclient eth0 Can access NAS ok via assigned IP address Resource monitor working Set to Static IP, applied setting Resource monitor working Synology Assistant still showed nothing. So - not sure what I've learned through all of this, other than I can get Resource monitor to kickstart by toggling the IP between static and DHCP. It makes no difference on whether or not it can be found in Synology Assistant Quote Link to comment Share on other sites More sharing options...
knightshade Posted August 2, 2015 Share #63 Posted August 2, 2015 I caught an interesting post in another thread: People, there isn't a problem with your mtu is there? I had an issue where many services wouldn't start including IPV4 and it was mtu based: had to manually change the two synoinfo.conf files to negotiate back to 1500 mtu. See earlier post: http://xpenology.com/forum/viewtopic.php?f=2&t=5026&start=1120#p39666 dead The details in the linked post seem to match what we have been discussing here, and editing /etc/synouser.conf appears to be the fix. Edit: Tested it with success. Login at console vi /etc/synoinfo.conf Find the line: eth0_mtu="2000" replace with: eth0_mtu="1500" save file (:wq!) Reboot Shows up in Synology Assistant again, and all services look to start correctly. The services are also available much quicker after a reboot. Now - I noticed that ONLY eth0 was set to 2000: eth3_mtu="1500" eth2_mtu="1500" eth1_mtu="1500" eth0_mtu="2000" That makes me wonder: Might an alternative solution for some to simply use a different port? At the very least - it appears that knowing that MTU is at the core of the issue should help all of us. Quote Link to comment Share on other sites More sharing options...
zhaobb Posted August 9, 2015 Share #64 Posted August 9, 2015 My N54L runs 5.2.5655 and was plagued with this issue since updated from 5.1. After changed the MTU setting as you instructed, my N54L can startup without the need of a manual "dhclient eth0" command any more! My kudos! Quote Link to comment Share on other sites More sharing options...
andywhit Posted August 9, 2015 Share #65 Posted August 9, 2015 Successfully updated my N54L from DSM 4.3 -> 5.2 5592.2 today. It was very easy and I had no problems. Even managed to get the power-off on press of power button working so I'm a happy boy Quote Link to comment Share on other sites More sharing options...
phguk Posted August 14, 2015 Share #66 Posted August 14, 2015 Andywhit, would you mind describing the steps you followed ? I'm currently sitting at DSM 5.1-5022 Update 5 but am a bit confused whether I can simply jump to (install) the latest 5.2 5592.2 or does this upgrade have to be accomplished in a series of steps. Thanks in advance Paul Quote Link to comment Share on other sites More sharing options...
andywhit Posted August 14, 2015 Share #67 Posted August 14, 2015 No probs. You should look to go to DSM 5.2 5592 first, then apply update 1 and then update 2. Firstly I BACKED UP everything I wasn't prepared to risk losing. Then the following steps. 1. I downloaded the XPEnoboot 5.2-5592.2 DS3615xs boot image from http://xpenology.me/downloads/ 2. Followed the preparing the new boot image steps in here -> http://idmedia.no/general/installing-or ... 2-or-later (basically edited syslinux.cfg and added in my current serial number and mac address) 3. Burnt the edited boot image to a new USB stick. 4. Booted up the N54L with the new stick inserted and selected the Install/Upgrade boot option (you'll need your N54 plugged into a monitor + keyboard) 5. When the install/upgrade boot had completed then on a PC used synology assistant to locate the NAS and connected to it. 6. Downloaded the 5592 PAT file from http://xpenology.me/downloads/ ( NOT Update 1 or Update 2, we do this later) 7. In the DSM connected to in step 5 select the downloaded PAT file and load it. 8. Sit back and let DSM apply the PAT file. 9. When done, log in to DSM and update any packages indicating they need an update. 10. Manually applied DSM 5592 Release 1 in DSM, using the PAT file from http://xpenology.me/downloads/ 11. When applied, rebooted NAS. 12. Logged back into DSM and manually applied 5592 Release 2 using the PAT file from http://xpenology.me/downloads/ That's it. Quote Link to comment Share on other sites More sharing options...
phguk Posted August 15, 2015 Share #68 Posted August 15, 2015 Fab - these steps worked for me too and I'm now successfully running DSM 5.2-5592 Update 2. One more question: can you elaborate on your earlier comment "Even managed to get the power-off on press of power button". What did you change/update to accomplish this ? When I press the power button, my N54L server simply powers off abruptly Many thanks Paul Quote Link to comment Share on other sites More sharing options...
grunera8 Posted August 24, 2015 Share #69 Posted August 24, 2015 Thanks, it works for me. I'm now on 5592 update 2 on my N54L!! Quote Link to comment Share on other sites More sharing options...
max123 Posted August 26, 2015 Share #70 Posted August 26, 2015 My bare metal H54L is still running 5.1-5055. I read there is an ACL error when using encrypted folders in 5.2-5565. Can someone confirm if encrypted folders work in 5.2-5592? Quote Link to comment Share on other sites More sharing options...
jmvioque Posted August 28, 2015 Share #71 Posted August 28, 2015 Hi all, I did same procedure than andywhit, but update direct to Update 3 from DSM , first reboot no volumes , that's "normal" next reboot everything OK Sorry no encrypted folders... Bye JM Quote Link to comment Share on other sites More sharing options...
BeatMaster Posted September 4, 2015 Share #72 Posted September 4, 2015 Upgraded from 5.0-4528 Update 2 to 5.2-5592 Followed the guides on generating a serial number and MAC address and added the VID and PID for USB pen Performed upgrade which took a couple of attempts via find.synology.com Static IP changed to DHCP and was a bit tricky to get it to switch to static IP but once done, run smoothly now USB drive for Crashplan now stays connected where previously it would randomly disconnect Have applied Update 1 but not sure whether to do Update 2 and Update 3 Thanks everyone for help and advice Quote Link to comment Share on other sites More sharing options...
werty1st Posted October 25, 2015 Share #73 Posted October 25, 2015 Hello at all, i've read many post regarding the encrypted folders acl error but so far nobody seems to have found a solution. can somebody tell why the "encrypted folders" is not working like on 5.1? and why is there so little information about that topic? does nobody use this feature? kind regards, werty Quote Link to comment Share on other sites More sharing options...
ntr1656 Posted October 27, 2015 Share #74 Posted October 27, 2015 VPN server is not work in N54L when updating to 5.2 However it work on Vm ware in same version. Quote Link to comment Share on other sites More sharing options...
barat Posted December 5, 2015 Share #75 Posted December 5, 2015 Hi, I have a question. Do I need to flash my n54l network card with synology MAC, or it is enough if it's only in xpenoboot config file? Quote Link to comment Share on other sites More sharing options...
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.