Jump to content
XPEnology Community


  • Posts

  • Joined

  • Last visited

Everything posted by MooseMan123

  1. I have a DS1817+ which has an 8 Disk SHR-2 volume setup. I have created a DS3617xs virtual machine. I had to modify the synoinfo.conf file to get DSM to see the physical disks from my passed through LSI 9207-8i HBA. I gave the VM a 20GB datastore to get DSM installed initially If I simply take the disks out of the DS1817+ and throw them into the new system, or will it completely bamboozle the system? If it does the whole "Migrate and install DSM" thing on reboot, it will screw the whole setup since I will then lose access to the disks from the LSI 9207-8i once it installs the new DSM OS. Can I just install them while its on, and just import the array somehow? I don't really want to do trial and error here because while my important data is backed up out the wazoo, I have 15TB of media which is replaceable, but I really don't want to lose it all...
  2. MooseMan123

    DSM 6.2 Loader

    But we are still lacking VMXNET3 for 10G+ networking right? I don't want to drop down to a 1G link when my VM supports well over 10G
  3. MooseMan123

    DSM 6.2 Loader

    Is the ds918 loader the only one that will be released going forward? I have some pretty decent systems that are Ivy Bridge that I don't plan on replacing any time soon. Unless I am mistaken, I am stuck on DSM 6.2-23739
  4. So if I start off the install with 2 drives, and then add 10, it will automatically "mirror" the install to the other drives in the background, no matter what type of separate disk group I make?
  5. I have been playing around with getting DSM running on my second ESXi host for the longest time, but I run into the problem of the disk not being "aligned" 1-12. So I have to modify DSM to allow more disks to see all of them This is fine, but if I ever need to migrate or switch loaders, I get into a loop of installations because as soon as I modify DSM to see more disks, it wants to migrate the install, and then overwrites the modifications again causing the disks not to show up I would be perfectly content with giving my DSM VM a Whatever size virtual disk (Which would be on my nice enterprise NVMe SSD...) and then telling it NOT to put the OS on the storage disks This way, all I would have to do is migrate that virtual disk, and then simply attach the physical disks and import the array Is this possible?
  6. DiskIdxMap=0C00 with SataPortMap=1 gets me nothing, I get the UI, but no disks found
  7. Perhaps I should have added more details, my goal is to get all 12 physical drives to show up while only editing the options on the bootloader, I do not want to have to edit the synoconfig. If the 50MB drive shows or not I don't mind too much. I also don't want to have to rely on a virtual disk with DSM installed I have tried, I have endlessly tried seemingly every configuration No matter what I do I get "No Hard Disks Found". I have tried endless configurations on the SataPortMap and the DiskIdxMap. Nothing makes them show up 1-12 and therefore get detected by the bootloader on first boot with zero modification of synoboot. With Just "1" entered I get all the drives as long as I expand the number of drives in Synoboot With all the numbers I have tried, I either get no webui, or no disks found. Not a single entry has made even a single disk be found by the initial bootloader. I even switched over to the other port on the HBA just in case that would help, but It didn't I am using 1.03b and I have tried both the 15 and 17 loader with no luck. Currently I have 1 vSATA (0:0) with the 50mb VMDK, and then just the LSI 9207-8i passed through
  8. Which tutorial? There are a ton of tutorials, and all the ones I have read only touch on the subject with quite vague points. Everyone keeps telling everyone else to read "the tutorial" but there is no single, main tutorial? The most detailed one is this - It says "append SataPortMap=XX" "where XX is the number of drives" which as far as I know, is wrong, because it would mean the following: I had 12 drives, there is no way I could enter "12" as that would then mean "Port 1 of first controller, and first 2 ports from second controller" which is not what I want at all Then it goes on to contradict the same tutorial and says: "SataPortMap=4 means first 4 ports of 1st controler. SataPortMap=44 means first 4 ports of 1st controler and first 4 ports of 2nd controler. SataPortMap=422 means first 4 ports of 1st controler, first 2 ports of 2nd controler and first 2 ports of 3rd controler." But how do I even tell which drivers are on which controller according to DSM? And I can only use a single digit? I am using 4 SAS/SATA ports plugged into an expander. The numbers don't really make sense. I can't tell it to use the first 12 ports of the first controller as I can only go up to 9
  9. Well, I have been messing around with this for a little while now and I don't think its possible with this hardware. Damn!
  10. Yeah that was my entire point Almost all other storage platforms let you browse snapshots on encrypted volumes. I think the issue is that the encryption is not on the whole volume, but per shared folder
  11. Which guides are you referring to? All I can find is threads with people being confused I have 1 SATA controller for the 50MB VMDK, and then my HBA. It seems like I should be entering 0 12 or 1 12, however I can't go over 9 on the entries...
  12. That's what I am doing, but no luck If I don't modify DSM to allow 24 drives they don't show up, and if I do modify DSM to see 24 drives I get stuck in the loop
  13. I have a DSM intall in ESXi, and I have an LSI 9207-8i passed through with 12 drives attached. For whatever reason, they connect in DSM on ports 13-24. Because of this, I need to modify DSM to allow more than 12 disks once its installed. And because of THAT, I must install DSM on a virtual drive first. (if I could fix that, this problem would probably be moot!) I got everything going in a test VM, and I wanted to simulate migrating the array. So I deleted the 20GB virtual disk I had DSM installed on, and made a new one. As soon as it boots it acts like a fresh install, since it can't see the other drives. So I install DSM and then modify it again to allow 24 drives. But then when I reboot, it must see the drives and it says that I am migrating from a different ds3617xs and need to either re-install DSM, or "migrate". Well, "migrate" involves pointing it at the DSM install file, which then resets the drive count back to 12... So I end up in a loop and can never seem to access the data again. Am I doing something wrong here?
  14. I have a VM intall of DSM, and I want the drives to show as being 1-12 instead of 13-24. Is there anything I can do in the bootloader config to get this done?
  15. I am making a DSM VM to handle my NAS duties, and I have 12 bays through a SAS expander and my LSI 9207-8i Because of the way the drives are presented, I must install DSM on a virtual disk first, then modify it to be able to see all 12 drives. Assuming there is no magic fix to get it to just see all 12 drives right away, how large should I make the DSM install volume?
  16. Some updates: With some help from @Hostilian I managed to get the drives to show up I didn't actually have to edit the grub config, just modifying /etc.defaults/synoinfo.conf worked fine. I didn't have the other file he referenced either. I will be using the below post to get the 50MB disk to go away Its still frustrating I have to edit the synoinfo.conf. I was hoping to get it to "just work" with just bootloader modification So far with 7 random SATA-I and II 80GB and 160GB HDD's (Yes, you read that right. All I had for testing) in SHR I am getting over 350MB/s read and write on a ENCRYPTED folder. This is better performance than my real DS1817+ with all nice shiny new 8TB drives. I guess 8 vCores from an E5-2680V2 helps... I am also still trying to figure out if I will need to keep DSM installed on a virtual disk (Not that I am against it), and what size I should really use
  17. I have a DS1817+ with a dual port Mellanox ConnectX-2. Currently it works fine, and I get the full 10G in iperf From also messing around with xpenology, its clear the 6.2.1 update will break a lot of PCIe devices. What are the chances this also kills my NIC in my genuine Synology? the Mellanox ConnectX-2 is not on the QHL
  18. Perfect, that made them all show up! I may play around with the numbers a little more to see if I can get it to show a max of 12 slots (The max that I have) Have you figured out a way to hide the 50MB VMware disk?
  19. I will be following this thread, as this information would be useful for me too. I just passed through a 9207-8i, and my drive is so far off the numbers it shows as an eSATA drive. What model card do you have?
  20. Okay I did make some progress, I gave DSM a virtual disk and got it installed. I now noticed that the drive does show up, but as an eSATA drive... Time to do some digging!
  21. I have got some parts together for a new virtual DSM build, including an LSI 9207-8i adapter, which is connected to my Supermicro BPN-SAS2-826EL1 backplane I am running ESXi 6.7, and I have passed the adapter through to the DSM virtual machine, however it will not see the single 250GB SATA disk I have currently got in the system. If I pass through the card through to a Windows VM, it works fine and I can see full SMART details Is there any further steps I can take to see any extra log detail, to try and figure this out? From research the LSI 9207-8i should work fine with DSM. Sadly I don't have any more 3.5" disk to throw in, just incase DSM doesn't like that disk for some reason.
  22. It looks like compatibility is pretty wide. Synology are using many different chipsets for USB 3.0 The NEC/Renesas seems to be the most popular. I was able to get a Dell ECS U3N2-D Card for $7 used locally, and it works fine
  • Create New...