stanza

I have one of these in mine http:// http://www.ebay.com.au/itm/1x-IBM-49Y79 ... 153&_uhb=1 Popped it in and was recognized right away and gave me 2x 10gb ports. I believe they are just rebranded emulex virtual fabric adapter II cards.... Which are on the hardware comparability list .

Anything / something with lots of front 5.25" bays Then you can easily add "4in 3" or "5in 3" bay devices. I have an old cooler master stacker, so with 4 of the 4 in 3 devices that easily takes 16 drives.... And could hold 20 with a swap to more expensive 5 in 3 devices.... Slightly large than a normal full tower, but more benifit I guess Another good one "rack mount" ....but remove the ears and it's just a small tower on its side..... Is the se3016 jbod Cheap and holds 16drives with a sas expander included. Attach any computer to it with an external sas HBA and a sff8088 cable.... Ebay on e again is your friend .

Try trantors 3827 beta 7 version out Might get lucky and it will be recognised Is the card actually on synology hardware list? .

Hunt ebay for an old supermicro sc933 chassis Maybe get lucky and find a SCSI version cheap, then hunt ebay for either a sas expander backplane or the plain 15x sata port backplane. Swap fans for some quiet ones and you will have a nice system. As a tip, these are also rebranded into "riverbed steelhead" application accelerator's.....usually come with some power hungry dual AMD motherboard inside. Sell that off to recoup some cost .

Have you set any power saving settings in the bios?

power down does work, BUT there is a bucket load of things that wake the drives back up...... Not really worth it in my opinion.......as when you look at the logs.....the drives are constantly spinning up and down.....sometimes every half hour.....which can't be good for them. Just leave them spin I say.......really what power are you going to save? vs the cost of new drives in a shorter period of time due to the constant power on / offs? .

6 works fine in mine just have to edi the /etc.defaults/synoinfo.conf file and add the WOL settings for the last two ports DS3612xs is qualified to run with a quad port intel card (it's in the supported list) so 8 should be feasible .

Separate switches per port, or direct connect (server to server) Yes link stays up even if 3 of the 4 links drop. .

Well not for load balancing, but for speed you can try http://xpenology.com/forum/viewtopic.php?f=2&t=2476

I believe it's not the timed shutdown..... but the timed wakeup / turn on that causes the problem. eg REAL synology has a spesh bios that can be configured to turn on at ZYZ time.......which naturally the Microserver doesn't.....and as such with it trying to modify that AREA of the bios on the microserver causes the issue. .

Must admit, I didn't try the multi volume raid option yet.... Which SHOULD get around the problem. Eg mdadm to pool the 19 x 2 tb drives together.... Then make under 16tb vg volumes (which are ext4) upon this array. Had the hdd overheating problem And yes had the wrong CPU core problem, which would be a kernel apic problem.... Not sure about a work around for that unless there is some grub setting to fix it? .

Yes real one has probably got a later linux kernel than the ones here.... Hence they don't have / have fixed the problem of expansion. I have a 19 drive box waiting for this fix myself... Waiting as in ... Not game to transfer everything over to it just yet because of this issue. ( as some drives are in use in other boxen)... So once I go I can't go back just yet. .

You might have hit the 16tb ext4 problem I would guess. Eg, the versions of software (kernel) within xpenology can't expand an ext4 partition past 16tb... Tho you can get around it with other tools... Eg expand the volume in another OS then remount back in xpenology.... Bit of a pain, I know. So you have two options... Either run as you are.... Expand in another OS and remount. Or wait until you have more drives, and create a volume larger than 16tb straight up. Tho you will still have a problem later if a drive dies.... And you need to replace it. (Eg hit the expansion problem again. ) Not much of a work around as yet.... Unless Trantor comes up with a workaround kernel tools etc. .

You might be out of luck getting all 56 drives recognised, But you can read my guide to get as many as you can going here http://xpenology.com/forum/viewtopic.php?f=2&t=2028

whats the result of running dmesg | grep "eth" ?? eg should look something like MicroDS> dmesg | grep "eth" [ 3.963415] jme: JMicron JMC2XX ethernet driver version 1.0.8 [ 5.683880] e1000e 0000:02:00.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1b:21:c2:82:72 [ 5.683973] e1000e 0000:02:00.0: eth0: Intel(R) PRO/1000 Network Connection [ 5.684039] e1000e 0000:02:00.0: eth0: MAC: 3, PHY: 8, PBA No: E46981-006 [ 5.747672] pcieport 0000:00:06.0: eth1: Tigon3 [partno(BCM95723) rev 5784100] (PCI Express) MAC address 3c:d9:2b:02:0c:ca [ 5.747769] pcieport 0000:00:06.0: eth1: attached PHY is 5784 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0]) [ 5.747823] pcieport 0000:00:06.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] [ 5.747874] pcieport 0000:00:06.0: eth1: dma_rwctrl[76180000] dma_mask[64-bit] [ 12.026424] usbcore: registered new interface driver ethub [ 13.135052] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 13.967390] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 15.395072] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx <<<<<<<<<<<<<<<<<<<<<<<<<<<<<[ 15.398447] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.327801] pcieport 0000:00:06.0: eth1: Link is up at 1000 Mbps, full duplex <<<<<<<<<<<<<<<<<<<<<<<<<<[ 16.327801] pcieport 0000:00:06.0: eth1: Flow control is off for TX and off for RX [ 16.332294] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 25.874082] eth0: no IPv6 routers present Make note, mine has an extra Intel CT Single port card installed.......eth0....but eth1 (onboard broadcom Tigon3) should show connection @ 1000 Mbps

Have you enabled "Usage History" in resource monitor? eg performance monitoring every 15mins? etc? as it has to log this data somewhere

Gday again Trantor. Hey just wondering if you can get / add virtio_blk up and going? Managed to get This Beta7 up and running under KVM on Ubuntu Which is interesting in that you can PASSTHRU whole HDD to the virtual Synology..... without needing VT-D to passthrough a whole controller ala ESXi etc So this way there is no need to make Xpenology need SAS HBA support..... Xpenology just see's SATA Drives. Tho, naturally it's SLOW (eg 10mb/s transfers to each drive) without proper KVM virtio drivers But it looks like someone has managed to get virtio working in an older version...(not totally successful...but a start) http://xpenology.com/forum/viewtopic.php?f=2&t=991&p=4910&hilit=libvirt#p4910 Would make for a Nice "All in One System" that would give people an option instead of ESXi

It's trying to write stuff to a SYNOLOGY BIOS which the N54L isn't..../ cant / so it screws it up when attempting to do so. eg Real Synology bios probably has something / a setting etc to allow you to shut down the NAS.... then wake it back up at a certain time eg only turn on between 5PM and 11PM.....then turn back off again. N54L doesn't have this capability....along with other Synology capabilities..... which if you want / need you are best purchasing a REAL Synology. If not and your happy with the N54L, then you have to also put up with some short comings from paying a cheaper price .

common problem, which is caused when you enable the power schedule... solution is to NOT enable any schedule

G'day Trantor, any way to stop dsm spinning down the drives "SAS" at reboot time? I don't mind it when it's a shutdown, but for a reboot it's really annoying .... As then the drives all have to spin back up.... And that's when the order gets shuffled around I think. ? Thanks mate .

BE WARNED, it's best to make a backup....or perform this on a test system to make sure it is going to work before proceeding ================================================= ================================================= OK here is a quick guide on how to update Trantors 4.3-3827 beta7 to fix the Heartbleed problem Just as with the 4.3-4810 update 4 fix to stop your system getting a virus / trojan You should update your 4.3-3827 if you have your system accessible from the internet This is a similar but slightly different way to update your system to my other thread http://xpenology.com/forum/viewtopic.php?f=2&t=2049 1st step make sure SSH is enabled Open Control Panel and select the Terminal icon Select "Apply" and return to Control Panel 2nd Step The Update Check Select "DSM Update" Select "Update Settings" Choose "Important Updates Only" Select "OK" It will now check and show there is an "Update 2 Available for download" Select the "Download Button" and wait for it to arrive BUT DO NOT SELECT "Update Now" BUT DO NOT SELECT "Update Now" BUT DO NOT SELECT "Update Now" BUT DO NOT SELECT "Update Now" Now we have to SSH into our Xpenology box and run 2 commands to enable the update to work eg replace 10.0.0.29 with the IP Address of your Xpenology box ssh root@10.0.0.29 root@10.0.0.29's password: BusyBox v1.16.1 (2014-02-11 20:19:16 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. MicroDS2> Now we can have a look at what the Update package contains, by changing to the hidden @smallupd@te_deb Directory stored on your volume1 to save you the trouble.....here is the list MicroDS2> cd @smallupd@te_deb/ MicroDS2> ls apache-2.2.x-virtual-worker-bromolow-bin_2.2.25-3827-s2_all.deb flashupdate_4.3-3827-s1_all.deb iptables-1.4.2-bromolow-bin_1.4.2-3827-s1_all.deb libsynosdk-bromolow-bin_4.3-3827-s1_all.deb libsynosdk-bromolow-bin_4.3-3827-s2_all.deb lnxscemd-2.0-bromolow-bin_4.3-3827-s1_all.deb lnxsdk-bromolow-bin_4.3-3827-s1_all.deb openssl-1.0.x-bromolow-bin_1.0.1f-3827-s1_all.deb openssl-1.0.x-bromolow-bin_1.0.1g-3827-s2_all.deb php-5.3.x-bromolow-bin_5.3.28-3827-s1_all.deb samba-3.6.x-bromolow-bin_3.6.9-3827-s1_all.deb smallupdate_4.3-3827-s2_all.deb synosearchagent-bromolow-bin_4.3-3827-s2_all.deb Now we make sure we are in the root directory (Top Level Directory) MicroDS2> cd / Having a look we can see there is an autoupd@te.info file MicroDS2> ls -asl Should show something similar to MicroDS2> ls -asl 4 drwxr-xr-x 23 root root 4096 Apr 30 19:50 . 4 drwxr-xr-x 23 root root 4096 Apr 30 19:50 .. 4 drwxr-xr-x 2 root root 4096 Apr 30 01:06 .old_patch_info 4 -rw------- 1 root root 1024 Apr 30 01:07 .rnd 4 drwxr-xr-x 2 root root 4096 Apr 30 01:07 .system_info 4 -rw-r--r-- 1 root root 817 Apr 30 19:50 autoupd@te.info <<<<<<<<<<<<<<<<<<<<<< 4 drwxr-xr-x 2 root root 4096 Apr 30 01:06 bin 56 drwxr-xr-x 10 root root 57344 Apr 30 19:31 dev 4 drwxr-xr-x 26 root root 4096 Apr 30 19:38 etc 4 drwxr-xr-x 24 root root 4096 Apr 30 19:31 etc.defaults 4 drwxr-xr-x 2 root root 4096 Feb 12 18:06 initrd 20 drwxr-xr-x 20 root root 20480 Apr 30 19:49 lib 4 drwxr-xr-x 2 root root 4096 Apr 30 01:06 lib64 4 drwx------ 2 root root 4096 Feb 12 17:58 lost+found 4 drwxr-xr-x 2 root root 4096 Feb 12 17:48 mnt 0 dr-xr-xr-x 175 root root 0 Apr 30 19:31 proc 4 drwxr-xr-x 3 root root 4096 Apr 30 01:06 root 4 drwxr-xr-x 2 root root 4096 Apr 30 01:06 sbin 0 drwxr-xr-x 12 root root 0 Apr 30 19:31 sys 0 drwxrwxrwt 10 root root 1280 Apr 30 19:53 tmp 4 drwxr-xr-x 8 root root 4096 Apr 30 01:06 usr 4 drwxr-xr-x 14 root root 4096 Apr 30 19:31 var 4 drwxr-xr-x 11 root root 4096 Apr 30 01:06 var.defaults 4 drwxr-xr-x 14 root root 4096 Apr 30 19:50 volume1 4 drwxr-xr-x 3 root root 4096 Apr 30 19:31 volumeUSB1 We need to change this file to allow the update to work properly To change the file all we need is to run two simple commands MicroDS2> sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 then MicroDS2> mv /autoupd@te.info1 /autoupd@te.info Be warned, the system will reboot once we perform the next step...so make preparations in case you are in the middle of a file copy etc. So now back in Xpenology web interface we can select the Update Button Once the system have rebooted, you can check if all went ok by once again selecting "DSM Update" inside control panel Which should show (if all went correctly) .

http://xpenology.com/forum/viewtopic.php?f=2&t=2892

If your having troubles getting gigabit working.... Try a different cable. 9 times out of ten... Auto detect will down negotiate to 100m if it detects a problem. .

EX490 works fine.... Tho your probably netter off with a N36L N40L or N54L Microserver....as it will hold more memory, is epandable with 2 x PCIE slots... and hold and extra 2 Drives. .

How have you configured your synoinfo.conf? . I haven't configured the synoinfo file...I've followed the standard guide for installing...it seems that it's only my USB wifi device that the N40L can't see after the upgrade. try changing the following lines (if you are using only 5 x HDD's ....4 drive bays plus motherboard SATA and have left the E-SATA still as an E-SATA port) esataportcfg="0x10" usbportcfg="0xfc1" internalportcfg="0x2f" .