quicknick

Members
  • Content count

    144
  • Joined

  • Last visited

  • Days Won

    2

quicknick last won the day on October 24 2017

quicknick had the most liked content!

Community Reputation

13 Good

About quicknick

  • Rank
    Advanced Member
  1. 10Gbe setup - will this work with 6.1?

    You are correct. It is about money and lock in. Sent from my SM-N950U using Tapatalk
  2. 10Gbe setup - will this work with 6.1?

    It all depends on the use case. I deduced that test4321 just needed connection from 2 nodes. if it was different, then switches would bw the way to go. Even with ESXi hosts or kvm hypervisors traffic can communicate between each other because switching happens on the hypervisor even with multiple portgroups. Or you can get really complicate with VMware and do VXLans, but that is going into the weeds. I keep my traffic east-west and everything north of my fws. ie workstations/laptops/wifi , live in a 1 Gbe world. everything fw, ids ips and below is 10Gbe and all virtual. Sent from my SM-N950U using Tapatalk
  3. 10Gbe setup - will this work with 6.1?

    just get the brocade twinax cables and do pc to pc. forget getting a switch unless you got money to spend. also don't use cisco twinax cables with the brocade 1020. Sent from my SM-N950U using Tapatalk
  4. 10Gbe setup - will this work with 6.1?

    It will be released in my loader slated to be released tomorrow.
  5. 10Gbe setup - will this work with 6.1?

    Cheap route: 10Gbe's are the Brocade (QLogic) BR-1020's and it will always be supported by me because it is what I use. Expensive route: Can't go wrong with most Intel cards because they are easily supported, and most already are
  6. 10Gbe setup - will this work with 6.1?

    I use the cheapest 10Gbe card on the market (got them for $33 bucks ea) with great success, originally the Brocade BR-1020, which then became QLogic BR-1020, and now belongs to Cavium. I have a driver built for it that works great in XPEnology.
  7. Tutorial: DSM 6.x on Proxmox

    The reason why I recommend using as usb image vs making it a vdisk, because you don't have to waste a sata or scsi port, and disk stays hidden as synoboot and not accessible inside DSM.
  8. Tutorial: DSM 6.x on Proxmox

    because then if your disk changes names, it will still work. For example, /dev/sda changes to /dev/sdb, then disk will fail. Using disks by their ID means disks can change to whatever and will still work properly.
  9. Tutorial: DSM 6.x on Proxmox

    virtio drivers are supported in my loader which will be released once I iron out ESXi upgrades. KVM and baremetal are solid though. Also performance is great as iperf3 has proved great performance. DiskStation> iperf3 -c 192.168.0.2 -i 1 -t 20 -R Connecting to host 192.168.0.2, port 5201 Reverse mode, remote host 10.1.0.2 is sending [ 4] local 192.168.0.212 port 44805 connected to 10.1.0.2 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 844 MBytes 7.08 Gbits/sec [ 4] 1.00-2.00 sec 879 MBytes 7.38 Gbits/sec [ 4] 2.00-3.00 sec 898 MBytes 7.53 Gbits/sec [ 4] 3.00-4.00 sec 768 MBytes 6.44 Gbits/sec [ 4] 4.00-5.00 sec 883 MBytes 7.41 Gbits/sec [ 4] 5.00-6.00 sec 899 MBytes 7.54 Gbits/sec [ 4] 6.00-7.00 sec 900 MBytes 7.55 Gbits/sec [ 4] 7.00-8.00 sec 878 MBytes 7.37 Gbits/sec [ 4] 8.00-9.00 sec 907 MBytes 7.61 Gbits/sec [ 4] 9.00-10.00 sec 883 MBytes 7.40 Gbits/sec [ 4] 10.00-11.00 sec 906 MBytes 7.60 Gbits/sec [ 4] 11.00-12.00 sec 828 MBytes 6.94 Gbits/sec [ 4] 12.00-13.00 sec 898 MBytes 7.54 Gbits/sec [ 4] 13.00-14.00 sec 910 MBytes 7.64 Gbits/sec [ 4] 14.00-15.00 sec 758 MBytes 6.36 Gbits/sec [ 4] 15.00-16.00 sec 753 MBytes 6.32 Gbits/sec [ 4] 16.00-17.00 sec 841 MBytes 7.05 Gbits/sec [ 4] 17.00-18.00 sec 960 MBytes 8.05 Gbits/sec [ 4] 18.00-19.00 sec 858 MBytes 7.20 Gbits/sec [ 4] 19.00-20.00 sec 933 MBytes 7.83 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-20.00 sec 17.0 GBytes 7.29 Gbits/sec 0 sender [ 4] 0.00-20.00 sec 17.0 GBytes 7.29 Gbits/sec receiver iperf Done. And it is better to use synoboot.img as virtual USB drive because then it properly works with upgrades.
  10. Tutorial: DSM 6.x on Proxmox

    That is because it is improperly configured. Hit ESC at boot and find out what boot number your USB synoboot.img is. In my case it is number 7. edit your {VM_ID}.conf using vi or nano /etc/pve/qemu-server/{VM_ID}.conf should look something like this when complete: args: -device 'piix3-usb-uhci,addr=0x18' -drive id=synoboot,file=/var/lib/vz/images/100/synoboot.img,if=none,format=raw -device usb-storage,id=synoboot,drive=synoboot boot: 7 cores: 2 ide2: none,media=cdrom memory: 4096 name: NAS-X2 net0: virtio=EA:5C:48:D3:D9:D5,bridge=vmbr1,tag=1010 net1: virtio=6A:53:32:11:A8:9B,bridge=vmbr2,tag=1020 net2: virtio=46:02:AF:FA:F6:F0,bridge=vmbr2,tag=1060 numa: 0 onboot: 1 ostype: l26 sata0: /dev/disk/by-id/ata-SAMSUNG_HD203WI_S285J1RZ601531,backup=0,cache=writeback,size=1953514584K,serial=S285J1RZ601531 sata1: /dev/disk/by-id/ata-SAMSUNG_HD203WI_S285J1RZ601548,backup=0,cache=writeback,size=1953514584K,serial=S285J1RZ601548 sata2: /dev/disk/by-id/ata-SAMSUNG_HD203WI_S285J1RZ601803,backup=0,cache=writeback,size=1953514584K,serial=S285J1RZ601803 sata3: /dev/disk/by-id/ata-INTEL_SSDSC2BA400G3_BTTV321000E5400HGN,backup=0,cache=writeback,size=390711384K,serial=BTTV321000E5400HGN sata4: /dev/disk/by-id/ata-MKNSSDCR60GB_MK140429AS1354202,backup=0,cache=writeback,size=58615704K,serial=MK140429AS1354202 sata5: /dev/disk/by-id/ata-MKNSSDCR60GB_MKN1502R000080784,backup=0,cache=writeback,size=58615704K,serial=MKN1502R000080784 scsihw: megasas serial0: socket smbios1: uuid=7372bb90-1200-4c79-87cb-5b50379cacb5 sockets: 1 Note: The serial0: socket and sockets: 1 allows you to connect to the vty from proxmox server qm terminal {VM_ID}
  11. Jun's Alpha Loader for DSM 6.1

    Back from the dead with some good news... I can confirm with high confidence that upgrading directly from 5.2 or 6.0.2 to 6.1.1 is completely successful. To aid future upgrades as the bootloader matures, I am coming up with a nice backup package to backup of the system 2.4gb partition. I recommend for everyone to do this before they do any upgrade/update. Then the risk is really low to upgrade to any version even when untested. If an upgrade fails it is easy to restore back to previous version you were running if you fail. More on that soon.
  12. XPEnology Configuration Tool & Bootloader DSM 6.0.2-8451

    Not dead, just haven't had time to devote to it yet. Don't worry people it is far from dead and will be released within a few weeks or less. Sent from my SM-N920T using Tapatalk
  13. XPEnology Configuration Tool & Bootloader DSM 6.0.2-8451

    8 CPUs max! This is set inside the OEM kernel. Sent from my SM-N920T using Tapatalk
  14. XPEnology Configuration Tool & Bootloader DSM 6.0.2-8451

    See my post here viewtopic.php?p=82392#p82392 It doesn't use this tool but it's easy to deploy and use. Hi Koroziv, I already tried your image while reading this topic and just tried it again. I always get "Failed to format the disk. (35)" error. I added different types of (virtual) HDDs SCSI/IDE and different controller types but I get the same error. I used latest pat from Synology. having same issue, how did you resolv this? i am guessing the PAT install tries to install on bootimage and not on the new added virtual hard disk / rdm ... Again, this is addressed in 2.3. Will not provide any help to 2.2 as it is hard broke. Sent from my SM-N920T using Tapatalk
  15. XPEnology Configuration Tool & Bootloader DSM 6.0.2-8451

    Do you know ETA? Possibly this weekend. Sent from my SM-N920T using Tapatalk