CronM Posted December 27, 2013 Share #1 Posted December 27, 2013 Hello, first of all I apologize for my English. I hope this post can help more people having the same problems. Took 2 days reading post in the forum and testing in my n54l with XPEnology DS3612xs DSM 4.3 build 3810++ (repack v1.0) (Great Work) problems encountered bios corruption After much testing I have come to the conclusion that corruption changes occurring in different outfits, occurs when programming an automatic start. Automatic or manual shutdown does not reproduce the problem in my n54l. Corruption includes damage to the system time, reset the bios settings and even corruption that prevents booting (need reinstall original bios) Wake on lan It works by changing the mac and running the command ethtool -s eth0 wol g http://xpenology.com/forum/viewtopic.php?f=2&t=1353 http://xpenology.com/forum/viewtopic.php?f=2&t=665&start=10 HDD Spin Down / Hibernation THANKS for the script sync; /usr/syno/bin/synousbdisk -umount sdu; >/tmp/usbtab original post http://xpenology.com/forum/viewtopic.php?f=2&t=6&start=340 It is necessary to remove the USB pendrive for the disks enter in a state of hibernation (bug?) results: not working in original bios works with modified bios Link to comment Share on other sites More sharing options...
fonix232 Posted December 28, 2013 Share #2 Posted December 28, 2013 The BIOS corruption is caused by DSM's tight coupling with the hardware and its base software (the BIOS). On all Synology products, there's a custom BIOS with specific fields that control e.g. automatic boot, etc. Now, the problem begins with the way a general BIOS is built - it is a very basic set of code, and provides no higher level accessibility (you cannot modify BIOS from a running OS using a general interface, unlike UEFI) With BIOS, you need to write direct bytecode on the CMOS chip. And as Synology's BIOS structure is different from the regular BIOS', direct writing of the CMOS corrupts it. In some cases it even makes the system unbootable. For me the biggest problem was the "pinkeye" bug, that caused the HP health LED stay blue no matter what. The BLUE LED was simply always active. Even if another LED was active, in my case, this was the red LED, making it a really vivid pink. Link to comment Share on other sites More sharing options...
CronM Posted December 29, 2013 Author Share #3 Posted December 29, 2013 With the scheduled startup disabled and BIOS mod everything works OK No problems with the LED for now. Thanks for the info. Link to comment Share on other sites More sharing options...
ChmaDK Posted December 30, 2013 Share #4 Posted December 30, 2013 Trying to get the HDD hibernation working. Running 4 3TB WD green in the bays and an 750GB sata on the top shelf. They dont seem to hibernate even though ive followed your fine links in the earlier post. Is it possible you could tell me what bios youre using and your settings regarding the sata ports ? Link to comment Share on other sites More sharing options...
CronM Posted February 10, 2014 Author Share #5 Posted February 10, 2014 Use synousbdisk -enum to locate the mount name in my case is sdu use the script sync; /usr/syno/bin/synousbdisk -umount sdu; >/tmp/usbtab enter in hdd configuration and set 10 minutes hdd hibernation, and check log entry. Disconnect from web interface and wait 10 minutes... Its working on default BIOS settings on 4.3. I only changed SATA speed to 3.0 Gbps and video memory to minimun. other BIOS settings I've tested and works: To enable top SATA port and HOT Plug. From the main screen go to ‘Chipset > Southbridge Configuration > SB SATA Configuration’ and make sure your settings are the same as below OnChip SATA Channel = Enabled OnChip IDE Type = IDE SATA IDE Combined Mode = Disabled SATA EPS on all PORT = Enabled SATA Power on all PORT = Enabled follow this link http://www.synology.com/en-us/support/faq/568 for other limitations Good luck. Link to comment Share on other sites More sharing options...
Recommended Posts