Maxhawk

Members
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Maxhawk

  • Rank
    Newbie
  1. I've had my R720xd since mid January and have had Xpenology running on ESXi since then. I've had zero issues and I'm very happy with the setup. I'm using the H310 mini to control two 2½" SSD drives in rear flex bays for VM storage and an IT-flashed H310 for the front 12-bays. The H310 is passed through in ESXi so Xpenology can control the drives directly, with access to the SMART data and temperature readings. I can't comment on whether this would be an upgrade to your Supermicro. I can only say that everything has been 100% stable with 9 total VMs and it seems I'm barely taxing my dual Xeon 2630L CPUs.
  2. Maxhawk

    DSM 6.1.6-15266 Update 1

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.6-15266 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Gigabyte GA-P35-DS3R - Additional comments: NO REBOOT REQUIRED
  3. The DDSM network is called Nick-Synology. The only other changes I made to the default was to change NIC teaming to Route based on IP hash which should not affect this. I cant remember if I made changes to the security policy of the default vSwitch0 for the managment network, but I see that it's not all set to No FWIW. This switch is on a separate NIC port from vSwitch Intel.
  4. Thanks this worked! I know I tried one of those to Yes but not all three. Also it turns out you don't have to turn these on for the entire vSwitch. I did it only on the port group where I specified the VLAN ID and DDSM got an IP address first try.
  5. Maxhawk

    DSM 6.1.6-15266

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: ESXi 6.5 U1 - Additional comments: REBOOT REQUIRED
  6. Maxhawk

    DSM 6.1.6-15266

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 Update 1 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: Baremetal (Gigabyte GA-P35-DS3R) - Additional comments: REBOOT REQUIRED, manual update with previously downloaded file
  7. I'm trying to install a second instance of DSM by using DDSM in Docker in an ESXi environment. The reason I can't spin up another XPE VM instance is because all 12 of my drive bays on the backplane are being passed through by an H310 controller (flashed IT mode=HBA). The issue I'm having with the ESXi VM instance is I can't get network connectivity on the DDSM. I've tried DDSM on a separate bare metal installation and it worked fine set up the same way. The only significant difference is one is bare metal while the other one is ESXi. On ESXi I've presented XPE with 2 virtual network cards on different subnets. DSM gets an IP address from both subnets but DDSM can talk to neither of them. This is an ESXi issue, but I can't exactly go asking on a Synology forum about use with ESXi. I was just hoping that someone here may have done it so I know it's possible. Everything looks right as configured in ESXi. Thanks for reading.
  8. Maxhawk

    DSM 6.1.5-15254 Update 1

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.5-15254 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: ESXi 6.5U1 on Dell R720xd - Additional comments: No Reboot Required
  9. The physical hard disks as reported by DSM DS3615xs (6.1.x) don't start at 1. Is there any way to change this? It doesn't hurt anything but my OCD doesn't like it. I'm installed in a ESXi 6.5 VM running on a Dell R720xd with an H310 controller flashed to IT mode passed-through to XPE. There's a separate H310 mini mono in IR mode that ESXi uses. The drive numbers are actually counting backwards from 44 as I installed the 8TB disks first and later added the other drives. Thanks for any help or insight.
  10. Maxhawk

    DSM 6.1.5-15254

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Installation type: Bare Metal (Gigabyte GA-P35-DS3R V1.0) - Additional comments: Requires reboot
  11. Maxhawk

    DSM 6.1.5-15254

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 Update 5 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Installation type: VM ESXi 6.5U1 (Dell R720xd) - Additional comments: Requires reboot
  12. Maxhawk

    Different MAC for Jun 1.02b loader

    Thanks @Polanskiman, I hadn't paid attention to that tutorial since it was about migrating and not a fresh install, and as a noob I didn't realize the steps were relevant to a fresh install. Now it makes sense, but I didn't think to revisit the thread. Will DSM complain if I try to change the loader's serial number on an existing 6.1.4 installation?
  13. Maxhawk

    Different MAC for Jun 1.02b loader

    When I used Jun's 1.02b loader on a spare PC it was a simple process with ESXi to create a VM, copy the synoboot.img and .vmdk files to the VM, and create a drive pointing to synoboot.vmdk. I did this multiple times while getting used to the installation process and trying ds3615xs vs ds3617xs. I used the exact same process on the R720xd I just received this week and couldn't get it working. Xpenology was not being assigned an IP address (I was looking at my router's lease table). I eventually found some internet threads saying you can go into the command line during boot and type in set mac1=00x11x32x2cxa7x85. This allowed DHCP to get an address and Xpenology worked as expected. The MAC address that showed up in my router matched the address that ESXi was assigning the network card. After a few iterations of this I decided to hard code the IP address in DSM (as opposed to setting static IP assignment by MAC that I normally do). This however still would not work unless I used the 'set mac1=' command during boot. After some research I found you could update the grub.cfg with a new MAC and serial number. I couldn't figure out how to extract grub.cfg from the synoboot.img but I was able to find MAC address in synoboot.img with a hex editor: I changed this to my ESXi assigned MAC address (00:0c:29:61:e4:a4) but I still couldn't the loader to get an IP address but would if I used set mac1=00x11x32x2cxa7x85. Is there a way to change the default MAC address in synoboot or am I stuck with manually assigning 00:11:32:2c:a7:85 to Xpenology?
  14. Thanks for the responses. I've installed ESXi and Xpenology 6.1 alpha on a machine I built with old spare parts just to get my feet wet. Due to the old CPU (Core 2 Duo E6750) I have to use ESXi 6.0 as this CPU is no longer supported in 6.5. I've got 5 WD 1TB green drives and a 60 GB SSD. The motherboard is a Gigabite GA-P35-DS3R and has 8 built in SATA ports. I've installed two HP NC360T (Intel 82571) for a total of 4 gigabit ports. 1. I notice I'm not able to create a datastore as RDM. Is this because I don't have a separate drive controller? Will RDM become an option if I have an H200/H310 in IT mode? 2. Since I can't use RDM I'm simply creating a virtual disk to present to Xpenology. I notice that DSM can't read the drive temperature but the S.M.A.R.T status says OK. Will temperature readings work when RDM is used? Is the S.M.A.R.T "ok" status a false positive the way I've connected the drives? 3. What's the proper way to do ethernet link aggregation with ESXi and Xpenology? I found within ESXi I can create a switch that does load balancing between two NICs and Xpenology sees only LAN 1. Alternatively I can present the Xpenology with two NICs and let DSM create an 802.3ad bond between LAN 1 and LAN 2. Is there any difference? 4. There are folks who consider Xpenology to be a hack and don't think it's reliable and stable. However I'm using a DS3617xs .PAT file that I downloaded directly from Synology so the DSM software certainly is "authentic". Is it the boot image that's considered the "hack"? 5. I'm now considering a Dell R720xd because it seems every generation of hardware comes with significant improvement in power efficiency. Two to three years of power bill savings will pay for the difference in hardware cost from the R510 I was eyeing before. I don't expect there to be any issues, but are there any known issues with using Xpenology with the R720xd? 6. I've seen some ESXi/Xpenology tutorials that say the boot drive should be set up as IDE (0:0). However when I use the 1.02b boot image and 1.01 .VMDK file, ESXi only lets me choose SCSI. Is that because the .VMDK file is set up to use SCSI instead of IDE? 7. My boot drive (SSD) shows up as one of the drives in DSM. Is there any harm in leaving it there? Is there a way to prevent DSM from seeing it? Thanks again for bearing with my noob questions.