Jump to content
XPEnology Community

netware00

Transition Member
  • Posts

    6
  • Joined

  • Last visited

Posts posted by netware00

  1. I don't have an experience with WD red drives so can not comment on their performance.

    You PC should be capable of faster transfer speed.

    Is you NAS already have a lot of data or you still can experiment with different RAID configuration? I would try RAID 10 or RAID1 (mirror) fist to determine the bottleneck and a baseline for fine tuning.

    Also I would also try to leave less RAM on the HP (1-2GB only) for testing. I know it sounds counter-intuitive, but I read of the negative impact of excessive RAM on NAS and you really don't need that much for 5x2GB disk configuration on DSM with EXT4 filesystem.

    Try to copy very large single file between PC and NAS vs many small files for testing.

     

    Thanks XPEH, PC to PC can easily jump up to 100Mb. The 8GB x 2 memory for the Xpenology is overkill, memory usage rate only at 3% top at the 16Gb pool. That config was for freeNAS 1TB needs 1GB ram. I'll swap back to stock 2 x 2GB ECC Ram.

  2. by XPEH » 26 Apr 2013 16:57

     

    wenlez wrote:

    what kind of disk read / write speed do you get with RAID5 with these HP Microservers?

     

    I have tested HP N54L (same MB, faster CPU at 2.2Ghz) With single NIC its saturated 1Gbps link. With dual 1Gb NICs and LAG ~150MBps without jumbo frames. Basically similar performance as DS412+

     

    Hi XPEH,

     

    I'm using HP N40L, mob BIOS, 16GB none-ECC RAM, 5 x 2T WD Red DISK (5400), 4K sector format and nighthawk mob firmware microserver-dsm-4.2-02.05.2013.img and DS3612xs_3202-Repack.pat (big thanks for the great work). My file transfer speed on CIFS only gets 30~40MBps (E8400 Win7 PC to DSM with Gigabit connection).

     

    I add an Intel Gigabit CT Single Port Copper NIC EXPI9301C, enable Jumbo Frame (8K) in DSM network interface, enable Jumbo Frame in Cisco SF300 switch, check the SMB2 and Large Frame option in DSM Windows file share. It's not getting any better. Try to disable CIFS database optimization feature, no difference as well. Before Xpenology, that HP box is running freeNAS 8.3 with LSI 9220-8i - IT mode (remove in the Xpenology setup), which can get 50+MB for CIFS.

     

    Can you please give me any advices on the Xpenology setup?

     

    Thanks in advance.

     

    netware00

  3. Ok, do you need sources or binaries?

     

    The binaries are here(v2): http://yadi.sk/d/fTRkFMyU3D8Yc

     

    This is based on odie82544's DS3612xs_3202-Repack images, so thanks for those! Only the kernel, modules and linuxrc.syno are modified so far.

     

    The archive contains both the .pat file for installation and .vmdk file for boot.

     

    Create the virtual machine to esxi and add hardware:

    • IDE controller with single harddisk (vmdk file in archive). Boot from this.
    • PVSCSI controller and raw harddisks or vmdk files for data. I've tested with 3 disks so far.
    • VMXNET3 network. Only single interface in bridged mode is tested so far. MAC address can be anything.

     

    Follow the installation instructions elsewhere in this forum to install the pat file.

     

    I wouldn't use this for anything else than evaluation yet.

     

    Great work, Jukolaut, thank you very much for sharing it.

  4. Hi netware00,

     

    I'm running ESXi 5.1 (build 1021289) with the 4.2 DSM build 3202.

    I followed the Idiot's Guide posted here: LINK

     

    What I noticed: after adding everything in ESXi the Paravirtual SCSI controller (for the SCSI disk) was not added properly.

    So I needed to go to EDIT SETTINGS, tick the box SHOW ALL DEVICES. (see screenshot)

    Make sure that SCSI Controller 0 is set to Paravirtual. Optionally I removed the Floppy Drive and CD-Rom drive, as Synology Devices do not have have them.

     

    Thanks Panja, I actually have the same config as your vm, it didn't work, the DSM vm won't get the IP from DHCP server at all. I guess the odie82544 image doesn't support the vmnet3 NIC. I go through your LINK again, and find the mob version. Now the DSM vm is running perfectly on my ESXi server, thank you very much!! :grin:

  5. Schnapps wrote:

    Hi Panja,

    My suggestion is to use the 3202 or 3202-repack as everybody found these builds very stable. I personally have a 3202 in production .

    I can do the waiting part as well, but the thing is that Synology published the gpl sources just for x86 on build 3211 and nobody knows when they will publish what we need and want.

    If you want, you can test the 3211 for x86. There is a nice thread started by a passionate fellow but try to understand the x86 limitations.

    ~

    Vic

     

    PS: my system never consumed more than 2GB.

     

     

    I'll go for the 3202 build than. It works well on my ESXi machine so why not!

     

    Thanks all for the replies!

     

    Hi Panja,

     

    Do you install the DSM 4.2 build 3202 on ESXi 5/5.1 successfully? For my white box ESXi 5.0, SA can NEVER found the DSM vm, and I did change the vm NIC MAC to match the one that show in the boot screen. VM is built bases on 64bit other Linux, 256Mb IDE 0 boot drive, 100Gb PVSCSI x 2, 1G memory, 1 x NIC with mob MAC add.

     

    So far, I can only load the XPEnology DS3612xs DSM 4.1 build 2668++, but the IDE boot drive will be changed during the PAT file installation. The system will stop at the first re-boot and have the GRUB 22 error. even I re-upload the VMDK file or lock the original VMDK before the PAT installation, neither of those methords work for me. Can you please give me any advices, many thanks.

     

    netware00

×
×
  • Create New...