htpcdude

Are you using a Gigabyte B85M-HD3 motherboard? Did you get the WOL to work?

Are you using a Gigabyte B85M-HD3 motherboard? Did you get the WOL to work?

Sorry, meant to say you can use an eSATA expresscard adapter to add a second eSATA single drive enclosure, while using the E6400 built in eSATA port for your first eSATA single drive enclosure. I gave up trying to find an eSATA expresscard adapter that was eSATA multiplier compatible which also worked with DSM. I had to abandon my plans on using an E6400 for my XPEnology unit.

Sorry, meant to say you can use an eSATA expresscard adapter to add a second eSATA single drive enclosure, while using the E6400 built in eSATA port for your first eSATA single drive enclosure. I gave up trying to find an eSATA expresscard adapter that was eSATA multiplier compatible which also worked with DSM. I had to abandon my plans on using an E6400 for my XPEnology unit.

If that is a Dell Latitude E6400, no. The eSATA on this laptop does not support port mutipliers. You will only see one drive from that duo dock as the notes on the product link you provided says "In order to address both SATA HDDs the mainboard's eSATA controller must be Port Multiplier capable!" One option is to get an eSATA expresscard adapter

Does this synoboot have hba (SCSI/SAS drivers)?

I believe this may help. viewtopic.php?f=2&t=1086&p=8501&hilit=downgrade+to+4.2#p8501

Update: Followed procedure from viewtopic.php?f=2&t=1086&p=8501&hilit=downgrade+to+4.2#p8501 to trick the system to do a migration to DSM 4.3-3810 - v1.1 Beta 5 No loss of data but some loss of configuration.

Hello, I am running DSM 4.3-3810 - v1.1 Beta 4. I would like to try Beta 5 but I don't want to loose my configuration. Is there a way to get the new .pat file over to my Beta 4 installation? TIA,

You can also try RAID mode. Raid implies AHCI. It must be hardware because I had this same problem on an Intel DQ35MPE which is using the same BIOS as my Intel DQ35JOE

I believe BIOS reset issue is a hardware compatibility issue, not a software issue. I think DSM wants to keep time using GMT and not your local time zone. Like all modern OS, DSM wants to modify the BIOS to its correct time (GMT). Since your BIOS is not compatible with the way DSM wants to modify the time, you get a corrupted BIOS after reboot. I've found DSM doesn't like the BIOS from Supermicro but is ok with ASUS. With ASUS BIOS, I can set the shutdown time but setting a wake up time corrupts the BIOS. The best compatibility I've found so far is from Intel motherboards, specifically the DQ35xxx motherboards. I am able to schedule a wake up time with the Intel motherboards. DSM probably also doesn't like UEFI.

Hi, Can someone add the driver for a Sil3132 SATALink Controller? http://www.sonnettech.com/support/kb/kb ... tion=a3#a3 I am trying to get this working on a laptop via an expresscard 34 adapter to an external exclosure requiring an FIS-based port multiplier. I have tried both XPEnology DS3612xs DSM 4.2 build 3211++ (repack v1.2) and XPEnology DS3612xs DSM 4.3 build 3810++ (repack v1.0). Only one of the SATA drives in the enclosure is recognized. This same hardware setup works if the OS is Windows (7, Server 2008 & 2012) or Ubuntu 12.04 Or, can someone recommend an expresscard 34 eSATA adapter that is FIS-based port multiplier compatible that works with xpenology? Thanks,

Just update the image links now. Please recheck. What do you when you don't have 4 NICs? Do you leave the old MAC addresses there or enter 0?

Setting eth0_wol_options="g" seems to force it to appear to be on but I still cannot use the DSM gui to change it and when off it will not wake from sleep using a magic packet sent from somewhere else on the network. Even after a reboot the change in configuration does not see m to take. Thanks for suggesting Chris Since you have access to a N36L and N40L, do a search in the forum for S99ZZZ_Shutdown. There is a thread '[sOLVED]Wake On LAN (WOL)' where they used S99ZZZ_Shutdown.sh to get WOL working. I don't have access to these Microservers and I couldn't use S99ZZZ_Shutdown.sh to get WOL to work on my hardware.

I have been struggling with WOL also. I finally got it to work on a Dell Latitude D630 and from what I can tell, if you can't toggle it on in DSM's control panel, it won't work. You can force the setting by modifying /etc/synoinfo.conf but I couldn't get WOL to work that way. Updated: WOL can work even if you can't toggle the setting in DSMs Control panel, by modifying /etc/synoinfo.conf

It will use serial number from vender file. I just took sn=B3J4N00001 out of my menu.lst and now my unit has no serial number

I ran into the same issue. Found the same workaround. Took me almost a day to find the typo. The synoboot-trantor-4.2-3211-v1.2.img's menu.lst is wrong. This is the line with the problem: kernel /zImage root=/dev/md0 ihd_num=0 netif_num=1 syno_hw_version=RS3612xs mac1=3C4A9277BA7C syno_hw_version=RS3612xs should be syno_hw_version=DS3612xs. There is no rackstation 3612xs. Also, your config will leave your unit without a serial number. I am new to synology/xpenology so I don't know if that will cause an issue. Try this: kernel /zImage root=/dev/md0 ihd_num=0 netif_num=1 syno_hw_version=DS3612xs mac1=3C4A9277BA7C sn=B3J4N00001