Jump to content
XPEnology Community


  • Posts

  • Joined

  • Last visited

Everything posted by MooseMan123

  1. I don't have any USB 3.0 ports on this board, so sadly I can't just throw that controller into DSM. Its an X9 Dual 2011 Supermicro board, I think I am just 1 generation behind USB 3.0 implementation I have a metric butt-load of PCI-e slots though, so its no problem to throw a card in there. The passthrough with ESXi doesn't really matter, anything will work for that, its purely if its supported in DSM. I know quite a few people have added USB 3.0 PCIe cards, but there isn't much detail out there on brands/chipsets etc
  2. I will be passing through the entire card
  3. Same issue here on an ESXi installation using 1.03b with either the 3615xs or 3617xs loader when I updated to 6.2.1 It doesn't help you much, but its not just you! Earlier version of DSM works fine
  4. I have DSM running in ESXi, so it has no available USB 3.0 ports. I am looking to purchase the most compatible USB 3.0 card so I can pass it through to the VM I searched the forums, however there wasn't too much info out there. Has anyone got any recommendations for the most generic chipset USB 3.0 card that should be supported for the foreseeable future?
  5. Lets hope they finally allow us to browse the contents of BTRFS Snapshots on Encrypted folders! I also wouldn't mind being able to format external drives as BTRFS and encrypt them I can hope for file deletion in HyperBackup, but I feel like that is never going to happen
  6. I had to edit the .img, the VMDK contains no reference other than "synoboot.img" Also, perhaps the link changed, because the download got me 1.03b
  7. MooseMan123

    DSM 6.2 Loader

    I think I answered my own questions here. This thread is very confusing since the main post is talking about the DS918+ loader, but the thread is discussing past edits which are no longer visible These are not incremental updates, they are three separate versions. DS918+ - Happens to have a new 1.04 update and supports DSM 6.2.1 DS3617xs - Only has 1.03 and doesn't fully support the latest DSM (This should be the go-to loader for newer systems) Does NOT support VMXNET3 DS3615xs - Only has 1.03 and doesn't fully support the latest DSM (Should be more compatible with older systems) - Does NOT support VMXNET3 The grub issue I had above was strange, it ended up just working. Perhaps some weird glitch in ESXi keeping something in memory. I am now running 23739 on my ESXi 6.7 Host (Supermicro X9, Dual E5-2680 V2's) with the DS3617xs 1.03 loader with no issues. I did update to 6.2.1, however then I lose 10G networking through VMXNET3 (Since its not supported!) For safety I have been keeping my NIC's in a Bond with at-least one e1000e just so I don't completely lose networking If you do want to upgrade to a new bootloader on ESXi, you do NOT have to swap out the vmdk file, you can just swap out the .img file. Once you boot. you will have to see if the DSM bootloader pulled a new IP, and "upgrade" the installation with the correct .pat file (Since they are different between versions) Can we expect a new 1.04 for the DS3617xs or DS3615xs? It would be nice to be on the latest update while retaining 10G networking!
  8. I think I answered my own question, yes it just works And if you scroll part way down on the grub config, it shows the version
  9. MooseMan123

    DSM 6.2 Loader

    I currently have a DSM 6.2 ESXi installation based on the older 3615 loader, and I wanted to upgrade to this bootloader (New 1.04) I replaced the synoboot.img on my ESXi datastore, I get the splashscreen with Jun's email address, but I never get any response from the IP. Is there some extra steps I need to do in order to get this working with ESXi? I have both an e1000E and a vmxnet3 NIC, so if its a compatibility problem with vmxnet3 then it shouldn't be an issue. I also did try to use the 3617 bootloader with the same VMDK, but I get the following...
  10. Thanks, Will it just boot up as normal with the new bootloader? Or do I have to do some kind of configuration/repair? Also, is there any way to actually tell the version of the bootloader? I have the synoboot.img but I can't find the version anywhere
  11. Does the VMDK simply point to the synoboot.img? If I want to update my bootloader, do I just simply swap the synoboot.img thats located in the datastore, or do I need to get a new VMDK and IMG file? On that same note, is it even possible to just swap out the bootloader, say going from 1.03 to 1.04, since they use different base NAS models?
  12. Thanks, Just tried that and it worked fine (I did it 1:1, but it didn't care)
  13. I have DSM installed and running perfectly. What is the consensus on doing updates? I assume if I update to the latest DSM and it breaks, I am pretty much SOL? Is there any way to "go back" so to speak? I am going to build a second virtual NAS just for testing updates, this way I can do the following: 1. Wait for reports of successful install under ESXi 2. Test on testing DSM install 3. Wait a week 4. Push to main production install What do you guys do?
  14. I have DSM installed in a VM and its working perfectly, but I don't want to update and break everything So, I want to make a second virtual NAS for testing, but I don't want to give it any real disks. Is there any way to get DSM installed on a virtual disk? When I boot I get the message that there was no hard disks found. The synoboot file is SATA 0:0 and the virtual drive is 0:1 Any ideas?
  15. Nope this is over the network with vmxnet3. Doing an iperf I actually get around 16Gb/s (But my disks would never be able to match that...) E1000E will max out at 1Gb/s no matter what simply because its only a gig network adapter
  16. I just got my virtual NAS setup in ESXi 6.7 with 2 cores of an E3-1270 V2, 2GB of RAM and gave it an E1000E NIC and a vmxnet3 in active/failover (For compatibility, in case one stops working with an update) I have 3 x 4TB 3.5" disks and a super old 1TB Samsung drive all in SHR and I get around 400MB/s read, 330MB/s write. So this is either fixed, or your guys setup has something wrong. I thought I would post, as this thread could put people off!
  17. Hey, I am thinking of following this guide to get my colo storage in better shape. If I wanted to back the VM up, what parts are actually what? I assume the OS is on the actual drives themselves? So if I had a storage failure on my ESXi host, I would just rebuild the bootloader? If my VM failed, could I throw the disks in a real Synology and access the data? Thanks
  • Create New...