Gronaldo Posted May 12, 2016 Share #51 Posted May 12, 2016 update 1 done on 3 systems same issues as reported here on all 3 systems (bare metal); power/ups etc. Quote Link to comment Share on other sites More sharing options...
Roland1969 Posted May 13, 2016 Share #52 Posted May 13, 2016 Well with all went wrong. My server rebooted and now it is not starting anymore. When I run the Assistant it reports that the internal IP address is changed and that I have to install everything again. Anybody has a suggestion? I hope I didn't lost all of my data ..... Quote Link to comment Share on other sites More sharing options...
brantje Posted May 13, 2016 Share #53 Posted May 13, 2016 Well with all went wrong. My server rebooted and now it is not starting anymore. When I run the Assistant it reports that the internal IP address is changed and that I have to install everything again. Anybody has a suggestion? I hope I didn't lost all of my data ..... Are you sure you did not installed DSM 6? Posted via Xpenology.us Quote Link to comment Share on other sites More sharing options...
Roland1969 Posted May 13, 2016 Share #54 Posted May 13, 2016 Yes very sure because I switched off the upgrades only the improvements were switched on and I checked the number. Quote Link to comment Share on other sites More sharing options...
dusty22186 Posted May 13, 2016 Share #55 Posted May 13, 2016 POWER Quote Link to comment Share on other sites More sharing options...
Roland1969 Posted May 14, 2016 Share #56 Posted May 14, 2016 Well I got it back online. The only thing that is a problem now is to do the forwarding to the NAS to my domain. I had made a backup of the configuration but not all went back again. My files luckily are ok. Quote Link to comment Share on other sites More sharing options...
abced Posted May 17, 2016 Share #57 Posted May 17, 2016 I have also just found out that my router doesn't show Xpenology hostname anymore. It showed it properly before. I can still access it with UNC share using it's hostname normally (luckily!). Quote Link to comment Share on other sites More sharing options...
dutchnas Posted May 18, 2016 Share #58 Posted May 18, 2016 5967.1 is out someone has tested this version? Quote Link to comment Share on other sites More sharing options...
Sonnyboy666 Posted May 18, 2016 Author Share #59 Posted May 18, 2016 5967.1 is out someone has tested this version? Yes, tested it, nothing changed, just some security patches, i think. The Power/UPS problem still there. Quote Link to comment Share on other sites More sharing options...
vicrod74 Posted May 21, 2016 Share #60 Posted May 21, 2016 HP EX495 updated DSM 5.2-5967 through DSM and quick reboot - Smooth sailing! In fact, after updating to DSM 5.2-5967 Update 1, no issues, and no reboot required. Quote Link to comment Share on other sites More sharing options...
SyncGuy Posted June 9, 2016 Share #61 Posted June 9, 2016 So... hibernation and power management setting all ok? I'm on bare metal 5644.5 and not sure whether i should update to 5967.1.. Quote Link to comment Share on other sites More sharing options...
Huberer Posted June 9, 2016 Share #62 Posted June 9, 2016 No, there're problems with these settings. Stay on 5644.5 if you want to be on the safe side. Gesendet von iPhone mit Tapatalk Quote Link to comment Share on other sites More sharing options...
spyrule Posted June 11, 2016 Share #63 Posted June 11, 2016 I upgraded a few weeks back, and only just rebooted my NAS for other reasons (UPS swap), and now I cannot get into my NAS via network. First thing to note, I have not changed any configurations within my network at all (literally shut everything down, swapped an NMC card on my UPS, and powered everything back up). I'm getting an IP on each interface on my NAS (one 10Gig fiber, 1 x 1Gig NIC), and I can ping out from the NAS, but I cannot ping back to the nas from the rest of the local network. If I try to use Synology Assistant, it finds the two ports, but it says connection failed, and gives me the option to "setup" my NIC (which fails). I'm at kind of a loss as to what is going on here... Quote Link to comment Share on other sites More sharing options...
renegadeBE Posted June 12, 2016 Share #64 Posted June 12, 2016 Hello, Have you tested Synology Assistant? (See the returned message) Quote Link to comment Share on other sites More sharing options...
spyrule Posted June 14, 2016 Share #65 Posted June 14, 2016 So, It turns out it was a bad NIC on my Domain Controller (which is also my primary DNS/DHCP server). Once I fixed its connection, everything started to respond and work correctly again. Still not sure why the GUI wouldn't load (even with an IP instead of Domain name), but as long as it working, thats my main concern. Quote Link to comment Share on other sites More sharing options...
agentx Posted October 9, 2016 Share #66 Posted October 9, 2016 Hello, I am now quite sure that 5967 is an issue - my UPS setting is not now working correctly. I did some testing (using free separate HDD) and I am now quite sure that everything worked fine with 5644-8, but under 5967 (0-1-2) this UPS setting (in fact whole part under Hardware & Power) is not usable. For example it is not possible to switch on "Enable UPS support". So my advice is clear: not to upgrade to 5967 ! (On the other hand I have to confess that otherwise everything worked fine until I registered that malfunction, probably UPS setting was working until I tried to change something using DSM, then it was broken ) Quote Link to comment Share on other sites More sharing options...
Bear Posted January 4, 2017 Share #67 Posted January 4, 2017 Regadring problem to set config in the Hardware & Power-menu, which basically means you can't config your UPS, I found out the problem. If you look at the web trafic when you open the menu (Synologs normal web page, control panel-page), you see that the http response is a 500 (not a 200 OK), and you actually get a "Sorry, the page you are looking for is not found"-page back from the Json-request, which of course is ignored. Looking at the request, and trying to remove different part of the json-object thats sent as a parameter, I found out that its SYNO.Core.Hardware.FanSpeed part thats causing the problem. If you remove that, and send the post again, it will return OK. If you look in the /var/log/message file, you will see this entry for each http-request Jan 4 21:36:11 DiskStation entry.cgi_SYNO.Core.Hardware.FanSpeed[1].get[32445]: external/external_fan_adjust_config_full_speed.c:90 Cannot find HIGH fan table. Right about here is where my Xpenology knowledge ends. Something is wack with the Fan settings/config/control, and since it can't get all the details to open the page, you can't edit the page correctly. 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.