stanza

Should be eth0_wol_options="g" wol_enabled_options="" Not eth0_wol_options="g" wol_enabled_options="g"

Even tho DSM 5.0-4528 Update 1 work without any input. Looks like update 2 is not the same Looks like we have to do it the old way again, using the SED command line Follow my old guide for 4.3-3827-XX here http://xpenology.com/forum/viewtopic.php?f=15&t=2999

does it have any onboard memory (eg usb stick?) failing that can you get it to boot from usb? WD Sentinels look like they could be hacked to run Xpenology quite well the 6100 takes up to 16GB ram and has 3 x lan ports. There are a few interesting NAS boxes around that could be hacked into nice Xpenology boxes Lenovo make a nice 6 Bay and the ASUSTOR 8 and 12 Bay ones also look nice. need to find a diskless one that someone is offloading cheap and give it a try .

Here ya go http://stanzabike.net/images/xpenology/versions/

It's enabled by default, it's just the check boxes don't match what is really happening. Same with the WOL settings etc. http://xpenology.com/forum/viewtopic.php?f=2&t=1361&start=270 .

You mean update 5 and not 6 Sent from my iPhone using Tapatalk No he means update 6 5 was and is a minor update, 6 has a bit more DSM 4.3-3827 Update 6 (2014/8/26) Fixed Issues Upgraded OpenSSL to Version 1.0.1i to fix multiple security issues (CVE-2014-3505, CVE-2014-3506, CVE-2014-3507, CVE-2014-3508, CVE-2014-3509, CVE-2014-3510, CVE-2014-3511, CVE-2014-3512, and CVE-2014-5139). Implemented fixes for Kerberos 5 to address multiple security issues that allow remote attackers to cause a denial of service (CVE-2012-1013, CVE-2014-4341, CVE-2014-4342, CVE-2014-4344). Updated to the last version of PHP 5.3, announced EOL by the official PHP development team, to address multiple security vulnerabilities (CVE-2014-3981, CVE-2014-3515, CVE-2013-6712, CVE-2014-0207, CVE-2014-0238, CVE-2014-0237, CVE-2014-4049). ========================== DSM 4.3-3827 Update 5 (2014/7/24) Improvements Improved the stability of volume expansion. .

I actually find myself doing this now I do not create a volume.... 1st I create a DISK GROUP... Then Create volumes on top of the DISK GROUP saves any 16TB volume problems and having to work around them eg 15 x 2TB Drives Create DISK GROUP of Multiple Volumes on Raid Choose Raid 6 Disk Group gets Created = Size of 13 x 2TB Drives (2 of the 15 Drives lost to Raid 6 double parity) 26TB Disk Group Then Create Volume 1 say 12TB Then Create Volume 2 say 3TB for NFS Share to Virtuals Then Create Volume 3 say 6TB for Rsync Backups of Linux Hosts Remaining "Free Space" of the Disk Group can later be used to expand any Volume 1,2 or 3 if I need more space on either .

nanoboot is not the be all and end of in my findings. My preference is still Trantor's 4.3-3827 v7, never gives me any troubles and works on more hardware. for me, I have had too many issues with nanoboot and just dont find it as stable for my uses

You will have to edit the /etc.defaults/synoinfo.conf file to reflect your hardware Normal for a Microserver (without HBA) would be esataportcfg="0x10" usbportcfg="0xfc0" internalportcfg="0x2f" which looks like 0000 0000 0001 0000 < esata 0000 0000 0010 1111 < internalports 0001 1111 1100 0000 < usbports notice looking down the columns (of the 3 rows), that there is not a 1 in the same column so your going to have to work around those values, but adding in an extra 8 ports for the H310 (eg adding an extra 8 x "1's" into the mix to the left of the usbports "1's") .... with each "1" representing a port at a quick guess I recon esataportcfg="0x10" usbportcfg="0xfc0" internalportcfg="0x1fe02f" which looks like 0000 0000 0000 0000 0001 0000 < esata 0001 1111 1110 0000 0010 1111 < internalports 0000 0000 0001 1111 1100 0000 < usbports for more info, read my post here http://xpenology.com/forum/viewtopic.php?f=2&t=2028 .

Yes it should work fine for all updates to 4.3.3827

prob restricted to REAL Synology MAC addresses. should be easy to get around tho. Most MAC addresses are listed first few digits anyways look here reveals http://standards.ieee.org/develop/regauth/oui/public.html Here are the results of your search through the public section of the IEEE Standards MA-L database report for synology: 00-11-32 (hex) Synology Incorporated 001132 (base 16) Synology Incorporated 6F-2, No.106, Chang An W. Rd., Taipei 103 TAIWAN, PROVINCE OF CHINA so make one up starting with 00-11-32 and you should be good (pick a high number to avoid conflicts with existing users) eg 00-11-32-FF-FF-FF

Yes it should work Just have to modify your /etc.default/synoinfo.conf File a little Change lines Max disks = xyz And then modify lines with USB ports and sata / esata ports Probably best to use trantors 3827 v7 HBA version to get it to work best.... Nano boot version can be a bit fussy with sas controllers and network card drivers. http://xpenology.com/forum/viewtopic.php?f=2&t=2028

check your logs, unit will shutdown when HDD's get too hot........do you have adequate cooling for the HDD's? .

Thats normal in a browser type find.synology.com wait let it find your diskstation walk thru the setup and upload the PAT file that came with 4.3.3810 v1.0 untick the creat volume button let box reboot if it overwrote your usb stick, just make it again and plug it back in then come the fun enable SSH access in control panel (or if you have a monitor and keyboard hooked up just log in as root eg type root then the password you gave at install time with a browser on another machine logged into your Xpenology box, open storage manager select hdd management you will probably only see 6 or 8 HDD's detected (hence why we didn't create a volume at install time) so now you need to edit your synoinfo.conf file to reflect your running hardware eg how many USB ports you have on motherboard how many E-SATA ports you have on motherboard how many SATA ports you have on motherboard (not number of disks) to work out the hex codes read here http://xpenology.com/forum/viewtopic.php?f=2&t=2028

Usually if you hit a problem, then work out a fix.... It's best to post back what the fix was/is....so if anyone else comes across the same issue, they can find the answer.

viewtopic.php?f=2&t=2028 Cleanest way is now with trantors 3827 ver7 or ver8

Which dsm version did you try? I recon trantors latest should work with your broadcom's What storage controller is in the server? .

Ok your crazy and blind .

Depends which version xpenology your using You might have to set the MAC address's of the new cards ports if your using trantors version. Easy enough done tho .

Any drives connected to a sas controller will BEGIN AFTER any onboard SATA ports.... Unless you disable the onboard ports in the bios, but depending on which xpenology version your running.... It might work fine without any SATA drives attached....eg Trantors latest HBA version.... But other versions need at least ONE drive on a SATA port for DSM to load onto. .

Is that all it shows? what is inbetween (boot times 3 seconds to 10 seconds?) eg mine shows MicroDS> dmesg | grep "eth" [ 4.012497] jme: JMicron JMC2XX ethernet driver version 1.0.8 [ 5.738922] e1000e 0000:02:00.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1b:21:c2:82:72 [ 5.739022] e1000e 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection [ 5.739081] e1000e 0000:02:00.0: eth0: MAC: 3, PHY: 8, PBA No: E46981-006 [ 5.802623] pcieport 0000:00:06.0: eth1: Tigon3 [partno(BCM95723) rev 5784100] (PCI Express) MAC address 3c:d9:2b:02:0c:ca [ 5.802720] pcieport 0000:00:06.0: eth1: attached PHY is 5784 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0]) [ 5.802774] pcieport 0000:00:06.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [ 5.802826] pcieport 0000:00:06.0: eth1: dma_rwctrl[76180000] dma_mask[64-bit] [ 10.404404] usbcore: registered new interface driver ethub [ 11.554060] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 12.374998] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 14.008049] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 14.011405] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 14.829887] pcieport 0000:00:06.0: eth1: Link is up at 1000 Mbps, full duplex [ 14.829887] pcieport 0000:00:06.0: eth1: Flow control is off for TX and off for RX [ 14.835049] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 24.850009] eth0: no IPv6 routers present Is the lan port disabled in the bios? .

Log in and show the output of Dmesg | grep "eth" .

Does the 9th drive show up in hdd manager? If not edit your synoinfo.conf file to allow past 8 drives .

what device does the broadcom com up as in a "normal" linux system? eg for my emulex card the device is loaded up as be2net so to check whats happening at boot i simply ssh in and run the command dmesg | grep "be2" and dmesg | grep "eth" to see what devices is loaded as what eth device, also gives the MAC address's .