Schnapps

I hope Synology posts the GPL sources for DSM 4.3 on sourceforge, otherwise... we just dream

This is what i would have told you now

Thanks for the info. This is what we said. With Gigabyte's dual bios there are no issues. All Gigabyte MBs come with the 2nd bios duplicate as the 1st one.

No time to worry. No bios updates published yet )

I have the non-USB3.0 I am satisfied with it, although, in the beginning i was dissapointed that i bought the non-USB3.0 version but what the hell, i'm not using USB (well just for booting the DSM) I guess all Gigabyte MBs have this dual-bios protection. I would say just to buy it. I would go now for a MB with dual bios, lots of sata ports (not just 4) and m-itx format (prefferably haswell) but i'm crazy. What i have is more than what i need ))

I will recommend the GA-E350N because it will work just fine, also with the bios reset issue that DSM has. It's also low power, so it's kinda good.

Very nice blog and walk-through! Congrats on your choice! I can bet it's Xpenology ))

or 3211?

Quesiton: If i don't have any issues, should i update my libcrypto file?

Thanks for clarifying this topic fonix

Yes. That works brilliantly to get the MAC correctly programmed. I can get the server to start with a WOL packet from my server. The issue is the shutdown or startup (not sure when the BIOS is being written..from my tests I believe it's only happening as it closes the server down soft). So I can issue the shutdown from the GUI, watch it turn off, then send the WOL packet to start it up. What I notice is that the date then is reset to 2009 in the system and NTP fails to work anymore (messing with it sometimes locks the server up). SSH in to the server shows me the incorrect system date. So sometimes a bootup with wrong date, sometimes an invalid BIOS profile, and sometimes a wiped BIOS... Mostly the latter two. hwclock doesn't link to the device, so I'm not sure where it's doing the write to BIOS configuration. I was curious if anyone had noticed it, and maybe..just maybe modded the system to not mess with it. I have to admit I only noticed this when I configured WOL, so I am not sure if that did not cause this. I have noticed a lot of posts on the topic about shutdown causing BIOS reset, but again..can't tell if they were doing WOL hacks first or not. My BIOS is also reset but fortunately for me, I have no issues with the whole system. Probably because of my Gigabyte MB and its dual BIOS?

didn't really helped too much. i'm also an active googler so i read that thread. Sad though...

So... nobody?

Well, if you find it fits you, knowing about all issues, then this is the win. You can't have it for free and make it work perfectly. It's a win-lose situation Try some more images. The most hardware friendly is the 2668++ v1.3 from viewtopic.php?f=2&t=937 but still I had no real issues with 4.2 3211 x64

Hi, I'm not saying that there are no bugs but try to give us more details about your system and what image are you using. And yeah, stop using telnet. It's insecure. Use SSH!

Try the fix from this thread: http://xpenology.com/forum/viewtopic.php?f=2&t=937&start=20#p4719. Use the libcrypto.so.1.0.0.gz file from Andy's post on the 4th page.

Good input! Thanks

Well my friend, I think we will have to wait for those sources (personal opinion) or, they take the easy way and they publish the first versions of the 4.3 DSM in GPL in order for us to test for them . This is what i would do if i would be Syno.

Synology knows for sure about this community. I guess they also have some people around. My personal opinion is that this project is for geeks (like us). Non-IT users, will always buy the real deal with support from Synology (or other vendors). So Synology guys, Welcome and good luck in gathering as much feedback possible from us!

Hi guys (and girls), I'm having apparently, some issues with my DSM and i don't know the root cause in order to fix them Here is what i see in /var/log/messsages: Jul 17 07:11:20 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 07:21:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 07:31:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 07:41:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 07:51:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 08:01:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 08:11:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 08:21:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 08:31:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 08:41:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 08:51:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 09:01:21 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 09:11:22 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 09:21:23 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 09:31:24 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 09:41:25 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 09:51:26 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 10:01:27 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 10:11:28 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 10:21:29 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 10:31:30 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 10:41:31 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 10:51:32 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 11:01:32 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 11:11:33 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 11:21:33 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 11:31:33 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 11:41:34 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 11:51:35 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 12:01:36 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 12:11:37 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 12:21:38 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 12:31:39 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 12:41:40 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 12:51:41 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 13:01:42 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 13:11:43 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 13:21:44 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 13:31:45 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 13:41:46 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 13:51:47 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 14:01:48 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 14:11:49 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 14:21:50 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 14:31:51 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 14:41:52 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 14:51:53 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 15:01:53 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 15:11:53 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 15:21:53 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 15:31:53 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 15:41:53 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 15:51:53 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 16:01:54 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 16:11:55 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 16:21:56 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 16:31:57 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 16:41:58 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Jul 17 16:51:59 synorelayd[8726]: synorelayd.cpp:563 regist command auth error Any ideas why i get these? What is synorelayd used for?

try this: http://xpenology.com/forum/viewtopic.php?f=2&t=915#p4292

Hi Mitt27, Where do you see this message? Could you please share a screenshot with us? Thanks!

Trantor, you're a sweetheart!

Hi mate, Unfortunately for me, i never heard of AoE before (offcourse, except the well known acronym for Age of Empires) so i read the wikipedia page of it. Sounds nice and interesting, at least for SoHos. For the moment, there is no native AoE implementation and support in Synology's DSM and offcourse neither in Xpenology, which is a clone of the original one. AoE seems nice but like all technologies, it takes time until they get addopted, if they get enough attention anyhow. As i see it, I think I don't need it Anyhow, the Synology OS (DSM) is actually Linux and i ask you, as i do also with all the other enthusiasts on this forum, is to test as it's easy but don't forget to share your results, no matter if there are positive or not. Here's a link in the official Synology forum where somebody is trying to get the same answer as you. Just don't look at the post date ss you might be dissapointed http://forum.synology.com/enu/viewtopic.php?f=106&t=32357

Xpenology or dsm is just a custom linux. Believe me, if you have zfs on your nas, you have the know-how to install zfsonlinux... on linux