i5Js

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About i5Js

  • Rank
    Newbie
  1. Adding my two cens to this fantastical tuto. Finally I got working all the drives via passthrough. What I did was: ** Enable passthroug in the Cougar Point 6 port SATA AHCI Controller. ** Remember, we have now 3 SATA controllers so, we need to modify the SataPortMap in the grub. In may case, look like this: set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=1F SataPortMap=116 SasIdxMap=0' Basically I've modified: 1.- DiskIdxMap=1F to hide the synoboot drive 2.- SataPortMap=116 to tell the bootloader I have one drive in the first SATA controller, 1 in the second and 6 in the Cougar. And boom, worked flawless, recognice perfectly the volume, It was only needed repair the system partiton, and now I have my 4 SATA drives and 1 SSD for cache. Hope this help somebody. Cheers.
  2. Playing with the SataPortMap parameter I've get the ssd working. I've used this settings: SataPortMap=251, I had to select 5 drives in the second controller, because when I put 4 instead 5, one of the RDM drive disapeared. Now I only have two things to fix: ** When I reboot the system, always came with system partition failed of one of the drives. ** The synoboot is detected as esata drive
  3. I have similar issue here. I've an ASM1602 card connect via passthrough and the msata ssd drive is detected as sdaf, which is very far from the 12 drives supported. Any idea to fix this? The other 4 drives are added via RDM
  4. I think I found the problem, but don't know how to solve. The DSM, I guess only recognize some number of drives in a determinate order. In my case, the drive attaced to ASM controller is the sdaf wchich should be the 30th I guess and becasue of that, It can't be added to DSM Any ideas?
  5. Well I can passthough the asm1062 card, but the DSM doesn't recognice its msata drive. Via cli I can see it, but DSM doesn't admin@VM:~$ sudo fdisk /dev/sdaf Welcome to fdisk (util-linux 2.26.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk /dev/sdaf: 59.6 GiB, 64023257088 bytes, 125045424 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xb94a1b35 Device Boot Start End Sectors Size Id Type /dev/sdaf1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdaf2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdaf3 9437184 124840607 115403424 55G fd Linux raid autodetect
  6. I have this card installed but, the drive in the msata connector is not detected by the storage administrator. I don't know ig the driver is not correct.
  7. Well, all compelete. I would like to connect via passthrough a pci with a SSD disk for cache... let's see if I can make it
  8. Many thanks for your answer. Finally I've found the issue. I was using the 1.04b boot loader which is incompatible with my CPU, too old. I'm using now 1.3b and works flawless. I'm going to migrate from 3617 to 3615 to upgrade to 6.2.1 Thanks!
  9. Hello all. I'm trying to follow this tutorial, very nice by the way, but the VM is not able to get any ip from the DHCP. Checking the grub.cfg from the boot image i've realiced that the vid and the pid is not change. do I need to change it? Other question, is there any problem to use the passthrough instead the RDM? Thanks for your help. i5Js