freddiep

viewtopic.php?f=2&t=960 I opened a thread on it a bit ago and it seems to be a problem with using a "roll your own" server. The motherboards/BIOS is not the same and it causes issues when it attempts to write back to the BIOS configuration. If I put the system to sleep or shutdown it resets the bios, while if I just turn it off..everything is fine. It would seem to me that the system on close is setting a value in the configuration. One that is specific to the platforms that synology uses.

I'm curious about how dual bios helps.. The execution bios sw is protected, but the configuration is not. The bios configuration is getting overwritten, and depending on what's written is invalidating the profile. I would think that it depends on the default configs as to whether things boot properly (defaults that work vs. configurations that need to be explicitly defined to boot properly).

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.

The biggest issue is that it invalidates any work on WOL. I saw a bunch of people working on it, but if at the end of the day you cannot do a power down without it writing something to BIOS config..and causing a critical error, then it really means WOL is not supported. if there is a particular motherboard/bios combo that doesn't have this issue, I'd like to know it and see if its feasible to change.

I went through the threads on how to setup WOL recently, and was interested in having the XPEnology box use the scheduled power settings. This way I can have it off on a specific time period, but then activate manually from my router if I ever need to boot it during then. What i discovered is that the shutdown inside the GUI (or schedule) has a tendency to clear the BIOS info and reset the date. Tried it on my GA-MA785GM-US2H running the 4.2 (3211) build. If I power the box off suddenly, no issues. I issue a shutdown and the box picks up a 2009 date or worse it gets an invalid profile and clears out all the information (mandating me reconfiguring boot device order, RAID info, reset the time). Thought it was a bad battery so I replaced that, but it is definitely something this software is doing on a software requested shutdown. I saw a few threads around on other sites confirming this as well. Is there any hack in place to correct this?..or has anyone else noticed it?