New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About NextLevel

  • Rank
  1. After hours off trying, I give up to set the pass-through drives to be appear as DISK1 to 4. I ended up with DiskIdxMap=0C00 SataPortMap=114 SasIdxMap=0 that give me at least all 4 drives, labeled as Disk 2,3,4,5
  2. .. until I rebooted. Damn, 1st drive is gone again.
  3. Finally, I could make it run with this line in grub.cfg: set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C05 SataPortMap=1 SasIdxMap=0' So the boot drive on controller 0 is invisible (OC = 12 = out of scope) , the first virtual drive on the second controller 1 with volume1 and all the modules is DISK6 (05), and all Perc 6/iR drives are passed through and named DISK1 to 4 in the right order. Thanks to this information: Perfekt
  4. Hello folks I'm so happy that I found this Xpenology project. So nice to have this on my ESXi. Thanks to all tutorials, I was able to setup successfully this : - ESXI 6.0U2 on DELL 410 - Xpenology 3615xs VM with DSM 6.2 - Passing trough the Perc 6/iR card as device to the VM (Surprised that this works at all ) There is just a little problem: Only drive 2,3 and 4 from the Perc are recognized in the Xpenology. They are displayed in Storage Manager as Disk3, 4, and 5.. I thought that maybe Disk2 (this is the 32Gb virtual disk attached while installation) is in conflict with the first drive of the Perc Controller. So I tried to put it from SATA 1:0 to 1:4. After reboot it now appears as Disk6, but the first drive of the Perc is still not visible. After reading some valuable posts here, I think it can maybe solved with DiskIdxMap/SasIdxMap/SataPortMap stuff in the grub, but I have no clue about the relation and what to set. Can someone give me a hint? Thanks