bmacklin

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

1 Neutral

About bmacklin

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Update - My problem is now my ovs-vsctl and network settings are not persisted across reboots. I have added mac3 and mac4 and changed the number of ports in the grub.cfg file When I enable open vswitch, and reboot, I see ovs_eth[0-4] but only eth[01]. I have to ssh into the box to do: ip link set ovs_eth2 down # eth2 is the 10gb port ovs-vsctl add-port ovs_eth2 eth2 ip link set ovs_eth2 up ip link set eth2 up These settings are not persistent across boot. I have to run these commands each time. How do I get synology to persist thes
  2. I have a motherboard with two onboard 1gb ethernet and that was recognized and working no problem. I added a mellanox cx312a 10gb two port sfp+ card and the loaded extra.lzma and extra2.lzma and the card was recognized and works... until I enabled virtual manager which enabled vSwitch. Upon reboot I still see the 4 ports, but the two 10gb ports are inactive and disconnected (but it is directly connected to another machine, was working and transferring at the expected speed before the reboot). So after hours of troubleshooting, I ssh'd in and used ifconfig to
  3. I don't want to hijack this thread too much but the problem was enabling the virtual machine manage which enabled vSwitch. It "masked" the physical eth ports.
  4. Upon reboot, the network card with its two ports are detected but plugging the cable in the port doesn't show up as active. This worked before I rebooted though and I was using a DAC cable between two computers. I added the extra mac addresses to the grub.cfg file as mac3 and mac4 but no change. What do I have to do to fix this for the 918+ again? I read about the two port limitation but I thought adding the extra mac addresses would just work?
  5. I'm an idiot. Plugged my usb drive in and the fat32 partition was mounted by windows. Renamed the original extra and extra2.lmza files and copied the files from the 0.8 syno package and it booted and the mellanox network card showed up!
  6. I have a haswell system with 1.04b and DSM 6.2.2. I have a mellanox connectx-3 (cx312a) card that is not detected. The instructions are still not clear - what exactly do I need to do to get the drivers (0.8) on the usb drive that I have? I'm already on the latest DSM so I don't think I can modify a newer pat file and then upgrade my system. I have downloaded the extra918plus_v0.8 zip file and there are two lzma files. Do I extract both to the second partition on my USB and that's it?
  7. This is amazing news and an awesome workaround! Please let us know if you figure out a way to directly boot windows!
  8. Yeah, it was a long shot. By all accounts it should have been pretty easy and straightforward to have that VMM working but for some reason it just doesn't work for me. I have reinstalled DSM twice now. I also have two ethernet ports. Both are on the same subnet. I dedicated one for cluster-to-cluster communication and tried assigning my VMs to the other one, but no luck.
  9. Why did they disable SHR? I thought it was more flexible and probably better than raid.
  10. Running DSM 6.1.2-15132 baremetal. Everything working great except two issues: 1. Virtual Machine Manager doesn't allow me to noVNC connect to my instances. I can connect the first time during a VM installation, but once windows reboots the noVNC doesn't reconnect and will never connect to it again. I have been able to load the storage drivers during installation... noVNC is unable to reconnect or ever connect again after the first reboot. I tried loading a VMDK of another virtual machine created elsewhere and it won't connect either. 2. SHR is missing as an option during stor
  11. I'm not sure that works - the installation installs the PAT on all disks, including the boot right? Anyway, that's not the biggest issue. The biggest is why I can't get this to work in VirtualBox???
  12. I'm creating a xpenology in a virtual box machine to test it out before putting it in a server. However, I cannot get past the error during DSM assistant installation "error formatting disk". I am following instructions here: http://idmedia.no/projects/xpenology/in ... -or-later/ I have injected a new SN and mac1 address in my syslinux.cfg and it looks like this below. The pat file I'm using is : DSM 5.2-5644 (28.10.15) And the bootloader is XPEnoboot DS3615xs 5.2-5644.1 The installation process formats the boot drive with the bootloader, so each time that it fails I need to