stanza

or you can edit some files (not supported of course) and enable RR mode to increase thruput eg 4 x 1Gb ports to acheive rougly 450Mb/s ok I will start a new thread for this .

If your going to blow it away, Might as well download 3827 beta7 and try updating that way (choose migrate) .

I found the tricks to get it to work are Copy files to relevant places Check for update Select manual Cancel Go to your routers interface and disconnect from internet.... But leave router running so it gives out dhcp ip addresses etc Reboot xpenology box Log back into xpenology box and check for update again.... Wait It should now appear Run update and reboot When it comes back alive, log into router and re connect to internet

Hi, snoopy78! May be you can tell the full story - what is needed to build 10G network? I'm absolutely nube in 10G... So everything - controllers, routers, cables - is not clear at all. I do understand that it looks like a little bit off-topic question. But with xpenology and especially sas-based configurations we see real throughoutput up to 10G... So I believe it may be interesting not only for me. May be it shall be a special topic for 10G network hardware environment for xpenology. If you can share your knowledge (or if anyone else can help) I will be thankful much. You can also try out bonding several 1g LAN ports together to bump up your speed between Xpenologies and or say virtualization servers. I will write up a new thread of how to do it if you like. .

What I would like to know is On the REAL DS3612xs which is 12 disk bays We know the default synoinfo.conf file settings So What happens / how does it change automatically when you plug in the optional DX1211 . Which is anther 12 bays We need to find someone with the above, check the files.... Then plug in the expansion and check the files again Tell us what moves/ changes .

@ snoopy78 you could try this for your item 3 http://xpenology.com/forum/viewtopic.php?f=2&t=2130

OK with 7 drives on H310 only upgrade from 3810 beta5 to 3827 beta7 works fine (using migration) all users / settings / files / programs are still there I guess because 3810 beta5 defaults are within 3827 beta7 defaults esataportcfg="0x1000" beta5 esataportcfg="0xff000" << usbportcfg="0xffe000"beta5 usbportconfig="0xf00000" << internalportcfg="0xfff" beta5 internalportcfg="0xfff" << So if you have under 12 drives / ports in TOTAL in use.... you might be good for the upgrade. If you have OVER 12 Drives.... Backup and restore or take the risk and edit synoinfo.conf file ASAP after upgrading as currently it will wipe out your synoinfo.conf changes .

sysctl.conf settings I use are kernel.panic=3 kernel.sem=250 32000 32 256 dev.raid.speed_limit_min = 50000 dev.raid.speed_limit_max = 200000 as for max disks and internalportcfg maybe maxdisks = 24 esataportcfg="0x00" usbportcfg="0xff000000" internalportcfg="0xffffff" might cover most people ? eg 2 x 8 port HBA plus 4 SATA ports on motherboard Still need to get to the bottom of the drive ordering as well why drive numbers jump around? and can we lock them down using either uuid or /dev/disk/by-id ??

unpack the three files inside write synoboot-3827-pre-v1.1_v7.img to a usb stick boot from this new usb stick connect either by synologyassistant or try find.synology.com choose migrate choose 3rd option and feed it the beta7.pat file give new passwords and server name pray when it reboots, connect again and you might have to reinstall applications and users / settings etc. good luck .

Hmmm ok some interesting things Same hardware as above (minus 1 x SAS drive which decided to die ) so No drives attached to Motherboard SATA ports x4 slot has H310 with 7 x 450Gb SAS attached x8 slot has H200 with 4 x 1Tb SATA Changed synoinfo.conf as before to get all drives recognised drives are ordered as H310 drives are recognised 1st and are Drive 5 Drive 6 thru to Drive 11 H200 drives are recognised 2nd and are Drive 12 thru to Drive 15 Installed 3810 Beta5 Setup two volumes Volume 1 = 7 x Drives on H310 + 1 x Drive on the H200 Volume 2 = 3 x Drives on the H200 waited for them to sync and complete installed a couple of programs (audio / media / video station) added users set time zone made some shares SMB and NFS.... disabled AFP copied a movie to one share enabled usage history in resource monitor changed synoinfo.conf file some more to set WOL and MAX DISKS to 22 changed grub.conf to reflect correct MAC address and set a serial number generally fiddled around as you would a normal setup rebooted a couple of times then with system running pulled USB stick and DD'd the later 3827 beta7 to it popped it back in and changed grub.conf to match old USB stick (so it would come back up with same serial and MAC Address / IP Address) rebooted It asked to do the Migration as a normal (non HBA version) would fed it the new PAT file rebooted Both Volumes are degraded so without logging into the web interface, I re-edited the synoinfo.conf file.....which had changed back to default.....and rebooted could see MDRAID trying hard to resync the drives at reboot...."as of course it now had found missing drives" This time I logged into web interface to be greeted by the Volume has been degraded messages Interestingly, Volume 2 was fine....but suggested a scan be done Volume 1 was complaining of being degraded..... Volume 1 was Drives 5,6,7,8,9,10,11 and 12 (Drives 5 to 11 being the 7 drives on the H310 controller) (12 being / was the 1st drive on the H200 controller) Tho now this drive is Drive 15......hence the degraded state Manually manage the volume and add the drive back into the volume and it's all back up and good. even more interesting...... all useres are still there.......all programs are still there....DATA is still there and shares are also....unlike NON HBA upgrades which you have to add all them back in and re create shares etc So.....assumptions are with only one SAS controller and before doing anything on the web interface edit the synoinfo.conf file back to how you had it working and reboot.........maybe the upgrade will work fine? Guess I will have to test that now .

That board uses the i217 lan controller... not sure if those drivers are in any version here. for drivers that do work the way to get WOL working is edit the following files /volume/USB1/usbshare/boot/grub/grub.conf change like so #serial --unit=0 --speed=115200 #terminal serial default 0 timeout 3 fallback 0 title DSM 4.3-3810 - v1.1 Beta 5 root (hd0,0) # vender /vender show # hw_model kernel /zImage root=/dev/md0 ihd_num=0 netif_num=3 syno_hw_version=DS3612xs mac1=001F295521AE mac2=001F295521AF mac3=28924A2B052A sn=B3J4N11333 initrd /rd.gz that is, change the number of lan interfaces to the number you have and change the MAC Addresses to your REAL MAC Addresses then edit these two files /etc.defaults/synoinfo.conf /etc/synoinfo.conf Change any lines relating to your REAL lan interfaces (in my example above I change 3 interfaces (eth0 eth1 eth2) and also the WOL setting from eth0_wol_options="d" eth1_wol_options="d" eth2_wol_options="d" wol_enabled_options="g" to eth0_wol_options="g" eth1_wol_options="g" eth2_wol_options="g" wol_enabled_options="" and reboot see how that goes

ahhh yeah, I was comparing them with the 4 drives on second controller which is only in a x4 slot not a x8 slot. Anyways.... reinstalling 4810 beta5 now will set it up and then make the 4827 beta7 key and see how it handles the upgrade .

Good question, will give that a whirl later and find out .

Just tried out 4827 v7 Beta Interesting it that it doesn't need any HDD's attached to a SATA controller now Tried with Intel Server Board S3200SH 4 gig ram Intel E6550 Core 2 Duo CPU 8 x 450gb 15K SAS Drives off of a H310 4 x 1tb SATA Drives off of a H200 Edited /etc.defaults/synoinfo.conf to be maxdisks = 20 esataportcfg="0x00" usbportcfg="0xff00000" internalportcfg="0xfffff" as only 4 drives recognised initially Installed, created 2 volumes Raid 10 of the 8 SAS drives Volume1 SHR of the 4 x 1TB SATA Drives Volume 2 Reboots fine ===== DAMN those SAS drives and RAID 10 are FAST Couple of DD tests too give it a thrashing writing, then reading a 20g file to each volume time dd if=/dev/zero of=/volume1/test1/ddtest bs=1024000 count=20000 20000+0 record in 20000+0 records out real 0m 34.83s user 0m 0.01s sys 0m 20.00s time dd if=/dev/zero of=/volume2/test2/ddtest bs=1024000 count=20000 20000+0 record in 20000+0 records out real 1m 37.44s user 0m 0.03s sys 0m 20.80s time dd if=/volume1/test1/ddtest of=/dev/null bs=1024000 20000+0 record in 20000+0 records out real 0m 37.48s user 0m 0.00s sys 0m 13.09s time dd if=/volume2/test2/ddtest of=/dev/null bs=1024000 20000+0 record in 20000+0 records out real 1m 36.05s user 0m 0.00s sys 0m 13.99s .

Because when I was trying to get HA working, you could see it was failing with that error So I gather when the REAL Synologies are setup in HA mode....then the LCD's change to reflect the STATUS or Name or IP Address or Master / Slave etc of the HA setup. .

As I discovered, sometimes you have to choose create a volume several times before it actually creates a volume if you watch mdstat output you can see why eg cat /proc/mdstat In brackets you will see the number of drives that are in the MD0 and MD1 Mirror array... it might look like [uU.......] when you choose create volume it might grab another couple of drives and add them to the mirror's eg [uUUU.....] just keep going until you have your 14 drives there (can cound 14 x U's) [uUUUUUUUUUUUUU..] then the volume SHOULD create successfully and survive a reboot.

Try this version http://xpenology.com/forum/viewtopic.php?f=2&t=1361&p=12750#p12750 .

Just forget to edit synoinfo.cfg ^^ This is the default value for DS3612xs. Ahhh interesting, cool

It's trying to write to the LCD screen Which naturally it doesn't have .

I had a similar problem that I could not solve If I used SAS drives in an Intel SAS expander cage.... the drives were recognised as HDD's If I used SATA drives in the same cage....all drives were recognised as SSD with -1C temps Couldn't work around the problem sadly. Maybe try different drives on those two ports? see what you get... Maybe try (if you can) change them (the HDD's via jumpers) from SATA 3 to SATA 2 or SATA 1.5 mode? see if that helps? Xpenology is great, but not Perfect for every situation .

I noticed with this version /etc.defaults/synoinfo.conf has the following esataportcfg="0xff000" usbportconfig="0xf00000" internalportcfg="0xfff" is this a Synology change or a trantor change? .

I have had no issues with MAC address Easiest way I found is Make usb stick Pop it in and boot up Install xpenology pat file Reboot Once up and going, ssh into box and use dmesg output to find your REAL MAC address Then edit the grub.conf file on the usb stick to reflect the real MAC address Eg Vi /volumeUSB/......./boot/grub.conf Change the number of interfaces MAC address's and serial Save and reboot Then ssh back in and edit both synoinfo.comf files to your liking For wake on LAN and number of internal/usb/esata ports etc And your away and going .

Ok the seg fault is to do with the cgi script of the update panel Something to do with libstc** Will have another go at trying to catch the actual output later As it only lasts a short time until the box reboots Can see it on console output eg monitor connected, but doesn't show on sash console output.... So copying the error and pasting it is hard. .

Just setup two more Microservers Used thebay bios 1st install was slow...... reason why [ 23.642201] ata1.00: configured for UDMA/133 [ 23.642256] ata1: EH complete [ 23.648070] ata2.00: configured for UDMA/133 [ 23.648124] ata2: EH complete [ 23.648255] ata3.00: configured for UDMA/133 [ 23.648305] ata3: EH complete [ 23.649466] ata4.00: configured for UDMA/133 [ 23.649515] ata4: EH complete [ 23.649925] ata5.00: configured for DMA/33 <<<<<<<<<<<< [ 23.649974] ata5: EH complete Re checked BIOS settings, as it had port 5 and 6 as IDE mode disabled IDE mode on port 5/6 reboot and [ 23.642201] ata1.00: configured for UDMA/133 [ 23.642256] ata1: EH complete [ 23.648070] ata2.00: configured for UDMA/133 [ 23.648124] ata2: EH complete [ 23.648255] ata3.00: configured for UDMA/133 [ 23.648305] ata3: EH complete [ 23.649466] ata4.00: configured for UDMA/133 [ 23.649515] ata4: EH complete [ 23.649925] ata5.00: configured for UDMA/133 <<<<<<<<<<<<< [ 23.649974] ata5: EH complete

no point getting mad and other users here As I pointed out to you in another thread I have 2 x EX490's which have the same weirdness Tho they do work once up and going you might be best with a USB stick with an activity LED on it so you can watch whats going on Place USB stick in lower rear USB port Boot without drives inserted Once you see usb activity (eg booting) push HDD's in and wait Connect with synology asistant when it comes alive. Pull out USB stick install PAT file when you see it rebooting push usb stick back in if it doesn't work, pull hdd's again and reboot with usb stick in wait for USB activity push HDD's back in see if it comes up as installed. if so, go to storage manager and remove your storage volume. (eg destroy it) and then remake it Wait for it to finish 100% then see f it will reboot by itself with usb and hdd's inserted. failing that spend $30 and get a keyboard video mouse cable off ebay so you can watch whats going one and or change bios boot settings. $30 is a cheap Synology