Jump to content
XPEnology Community

Kanedo

Member
  • Posts

    89
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Kanedo

  1. If you're most concerned with how your board looks, I'm not sure any argument for ECC or other server board features will sway you. I personally feel uptime and data integrity is more important than anything else with a file server. File servers should be functional and reliable. Looks should be a secondary concern in my book. People who don't recommend ECC are the ones that just haven't lost data YET. Once you've lost data or had corrupt data due to bad RAM, you'll swear by ECC no matter the cost. If you don't have or want to spend the money on a dedicated setup, then by all means use whatever you have. However, if you're building from scratch, definitely get a server board + ECC. Things like IPMI, ECC memory, IOMMU, and Intel NICs are features you'll only appreciate once you've had them. Bottomline is if your board and cpu supports ECC, get them. If it doesn't, then make sure you get it for your next full setup.
  2. It will work. I've done this on two 24 bay supermicro servers with SAS2 expander backplanes. You will want to write a startup script to do this once you get it working as the red locate LEDs will light up again after reboot.
  3. I can tell you how to turn them off. You should be able to find twelve 'locate' files under /sys/class/enclosure/*/*. You might have to do some directory traversal before you can find them. Once you do, change the content of each of the locate file from "1" to "0" and save.
  4. I just tested transferring some large files to my Xpenology server over AFP protocol. Easily hit above 500MB/sec. I suspect it could be higher if I wasn't bottlenecked by SATA3 on my Hackintosh.
  5. No, OSX doesn't have native drivers for Intel 10Gb cards. However, Smalltree sells a rebranded version of Intel cards made specifically for Macs. https://www.small-tree.com/categories/1 ... net-cards/ Smalltree 10GbE drivers https://www.small-tree.com/support/down ... y?cat_id=6 With some hackery, it is possible to spoof the PCI ID of the Intel cards to match those expected by the Smalltree drivers. http://www.tonymacx86.com/network/15613 ... ivers.html UPDATE: Success! http://www.tonymacx86.com/network/15613 ... ost1223519
  6. Good to know that AFP protocol doesn't limit the bandwidth too much. I have an Intel X520-DA2 on the way for my Hackintosh.
  7. I'm using Mellanox Connect-X2 EN cards in XPE and PC. Connecting them is a Cisco SFP-H10GB-CU5M
  8. I'm currently hitting north of 500MB/sec copying between XPE to Win10 PC. I have 10GbE card installed on both XPE server and Win10 PC, connected directly to each other using SFP+ Twinax direct attach cable. You are correct that your 110MB/s is the limit of your Gigabit network. Your disk array and cpu can easily handle more than that. The only practical method to break your 110MB/s limit is to upgrade your network gears to 10GbE.
  9. When you're just streaming or accessing smaller files, gigabit is indeed enough. However, when you need access to tens or hundreds of gigabyte of data, having 10Gb helps a lot. One example is copying huge video files. You are correct that drive performance could be a limiting factor to your transfer speed. However, almost any HDD or SSD sold today can hit above gigabit, so it's not very hard to saturate your 1Gbit connection at all. To saturate 10Gbit, you do need quite a few performant drives in a RAID0, 5 or 6 configuration.
  10. 10GbE can be had for fairly cheap if you go with SPF+ connection instead of RJ45. I have one of these in my Xpenology server and its supported with fairly recent XPEnoboot images. http://www.ebay.com/itm/671798-001-HP-1 ... SwDuJW0Pd9 If your server and client is within 5 meters of each other, you can go with a SPF+ Twinax cable like this below to directly connect them without a switch. http://www.ebay.com/itm/121884479854?_t ... EBIDX%3AIT Between server and client, I can get raw network speed of 10Gbit. For file transfers, I've been able to hit around 500MB/sec on my 12x2TB RAID6 array. I suspect I can reach higher if I had something faster on my client than a single SATA3 SSD.
  11. How much power does this badboy draw?? Power is one of the things I pay attention to as it runs 24x7. My system idles around 100W and goes up to 155W under load. System consists of Xeon 1275v3, 2x8GB DDR3 ECC, LSI 9211-8i SAS2 card, Intel SAS2 Expander, and a Mellanox 10Gb ConnectX-2 EN
  12. Like others suggested in this thread, I too am running xpenology in ESXi 6.0 using PCIe passthrough of LSI 9211-8i + SAS2 Expander. This gives my xpenology guest direct access to bare-metal drives. It also gives me the flexibility to run xpenology anytime as bare metal by booting off a USB stick instead of using VM.
  13. I'm running 13 SATA drivers. I'm currently using a LSI 9211-8i compatible card + SAS2 Expander. Very reliable. The key to seeing all your drives is to modify /etc.defaults/synoinfo.conf and adjust the the ports settings to match your drive enumeration. Oh, and I don't worry about having correct slot number matching. Just use the serial number to determine which drive needs service if necessary. Having correctly mapped drive bay numbering would be nice, but in no way does it impede any functionality if it doesn't.
  14. Running 13 drives here with ESXi 6.0 and all 13 drives connected to the Xpenology VM guest using VT-d PCIe passthrough with a LSI 9211-8i SAS card in IT mode + SAS2 Expander. Not seeing any issues here. Oh, and I'm only using a Corsair CS450M PSU.
  15. Okay, I finally cracked mounting synoboot for 5.2. Here's the updated instruction. First, ssh into your box as root. Create your mount dir Diskstation> mkdir -p /mountUSB Find the next free loopback device. Mine shows /dev/loop0 from a fresh boot. Diskstation> losetup -f /dev/loop0 Setup the loopback device to use /dev/synoboot with offset 32256. NOTE: 32256 = 63 sectors * 512 bytes Diskstation> losetup -o 32256 /dev/loop0 /dev/synoboot Now we mount the loopback device to our mount dir. Diskstation> mount -t vfat /dev/loop0 /mountUSB Now you can see the proper file listing Diskstation> ls -l /mountUSB/ drwxr-xr-x 2 root root 16384 Dec 31 1969 . drwxr-xr-x 28 root root 4096 Dec 6 22:50 .. -r-xr-xr-x 1 root root 116684 Aug 3 16:45 ldlinux.c32 -r-xr-xr-x 1 root root 61952 Aug 3 16:45 ldlinux.sys -rwxr-xr-x 1 root root 24124 Aug 3 16:45 libutil.c32 -rwxr-xr-x 1 root root 26336 Aug 3 16:45 menu.c32 -rwxr-xr-x 1 root root 759 Aug 16 23:29 syslinux.cfg -rwxr-xr-x 1 root root 21538496 Aug 3 16:45 zImage When you're done, unmount your device. Diskstation> umount /mountUSB Then release the loopback device losetup -d /dev/loop0 The reason why we have to go through all this is loopback stuff is because the "mount" command on Synology firmware is a trimmed-down busybox version without the ability to use offset. That's why we have to do it manually. Now, I don't know if the earlier 5.1 boot image was different or if Synology changed the mount binary in 5.2. Either way, this method is currently working for 5.2 until something changes again.
  16. Schmill, I can confirm that I have the same issue as you do with 5.2 Xpenoboot. My original mounting instruction worked for 5.1. So yea, I believe something changed on the 5.2 boot images that prevents us to properly mount it and see the same file listing as in a PC. I'll do some more testing to see what's going on. I am also following your mounting command without "-t vfat" and it auto-mounts using ext2 as well, which isn't what we want. Diskstation> mkdir -p /mountSynoboot Diskstation> cd /dev Diskstation> mount synoboot1 /mountSynoboot Diskstation> mount |grep synoboot synoboot1 on /mountSynoboot type ext2 (0) So something funny is going on here.
  17. My server consists of Supermicro X10SLM-F (C224 Chipset) and an Intel Xeon E3-1275v3 It's pretty similar to what you're trying to build. I can tell you that I have absolutely no issues with my setup.
  18. I also live update the USB stick using dd command. No problems so far.
  19. Guys, I apologize for the bad /dev/synoboot1 mounting command in my original instruction. Let me demonstrate the non-working and working method to mounting /dev/synoboot1 to a folder. This method does NOT work! Diskstation> mkdir -p /mountMe Diskstation> mount -t vfat /dev/synoboot1 /mountMe mount: mounting /dev/synoboot1 on /mountMe failed: Invalid argument NOTE: for some reason, you cannot perform the mount command by declaring the full path of /dev/synoboot1. You must cd into /dev/ first, and then mount synoboot1 This method WORKS!!! Diskstation> mkdir -p /mountMe Diskstation> cd /dev Diskstation> mount -t vfat synoboot1 /mountMe Diskstation> ls -l /mountMe -r-xr-xr-x 1 root root 116632 Jun 5 20:39 ldlinux.c32 -r-xr-xr-x 1 root root 61440 Jun 5 20:39 ldlinux.sys -rwxr-xr-x 1 root root 23488 Jun 5 20:39 libutil.c32 -rwxr-xr-x 1 root root 25676 Jun 5 20:39 menu.c32 -rwxr-xr-x 1 root root 767 Jun 23 02:17 syslinux.cfg -rwxr-xr-x 1 root root 15777952 Jun 5 20:39 zImage I can't explain why the first method with full path does not work, but the second method works for me. I've updated the mounting instruction on the first page with this. Hope it works for you guys too.
  20. You probably don't have "volumeUSB1" folder. You can just create one Diskstation> mkdir /volumeFoobar Diskstation> mount -t vfat /dev/synoboot1 /volumeFoobar UPDATE: Please follow my updated mounting instruction on second post
  21. Okay I just found the solution. Haha! modify syslinux.cfg on your boot loader and assign the vid and pid boot parameters to the vid/pid of your usb stick. To obtain the VID and PID of your USB stick, enter the following command as an admin user cat /proc/bus/usb/devices |grep -e "^$" -e"Vendor" -e "Manufacturer" -e "Product" Mine would return something like this for my Kingston USB stick. ... ... P: Vendor=0951 ProdID=1607 Rev= 2.00 S: Manufacturer=Kingston S: Product=DataTraveler 2.0 ... ... In my case, my Kingston USB stick's VID is 0x0951 and PID is 0x1607 Now, go and edit syslinux.cfg on your xpenoboot usb stick, and modify the "vid" and "pid" values on each of the "APPEND" lines with the values of your USB stick. Sample snippet of my syslinux.cfg with VID set to 0x0951 and PID set to 0x1607 for my Kingston USB stick LABEL xpenology MENU LABEL XPEnology DSM 5.2-5565 KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0951 pid=0x1607 loglevel=0 vga=0x305 Save your changes and reboot the system. If done correctly, your USB device will no longer be enumerated as /dev/sdu, and will not be auto-mounted in DSM. Instead, it should be enumerated as /dev/synoboot. Diskstation> parted -l 2> /dev/null |grep "^Disk /dev/s" Disk /dev/sda: 2000GB Disk /dev/sdb: 2000GB Disk /dev/sdc: 2000GB Disk /dev/sdd: 2000GB Disk /dev/sde: 2000GB Disk /dev/sdf: 2000GB Disk /dev/sdg: 2000GB Disk /dev/sdh: 2000GB Disk /dev/sdi: 2000GB Disk /dev/sdj: 2000GB Disk /dev/sdk: 1500GB Disk /dev/synoboot: 4022MB At any point, you can still manually mount the USB stick. December 6th, 2015 - Updated mounting instruction for 5.1 IMPORTANT: Make sure you cd into /dev first, and then mount synoboot1 Diskstation> mkdir -p /mountMe Diskstation> cd /dev Diskstation> mount -t vfat synoboot1 /mountMe December 6th, 2015 - Updated mounting instruction for 5.2 See viewtopic.php?f=2&t=5605&p=49332#p49332
  22. For anyone using xpenoboot on a USB stick, you may be aware that this boot-loader USB stick is mounted and visible within DSM. On Xpenoboot, it is by default enumerated as /dev/sdu. The partition /dev/sdu1 is mount on /volumeUSB1/usbshare. On a real Synology system, there is also a USB bootdrive embedded inside the chassis. However, I believe there is some check for specific VID/PID during the boot process that prevents a specific Synology USB bootdrive device from being enumerated. I know you can go and click unmount within DSM after it boots. That's not what I am asking. Unmounting it within DSM does not change the fact the USB stick is still /dev/sdu. I would also like to have my system boot up without enumeration of this USB bootdrive at all. Does anyone know a way?
  23. Boot img: XPEnoboot_DS3615xs_5.1-5022.3 So I had a 4x4TB RAID5 array. Tried expanding with another 4TB disk. The disk was correctly added to the raid5 array, but it kept failing on resize2fs. Tried with the test img posted in this tread, and it worked right away. XPEnoboot_DS3615xs_5.1-5022.2-215c67d.img Wasn't this expansion problem suppose to be fixed in XPEnoboot 5022.3?
  24. What's this NASBUF2.zip you attached? I see a Hex file inside. Mind sharing what this hex file is used for?
×
×
  • Create New...